Earlier quoted context omitted.
That's not true. Cookies can have a 'secure' attribute which tells the browser to send them only over TLS
in 2011?
Klarna users are being signed in to random accounts
321–330 of 517 posts
Re: Klarna users are being signed in to random accounts
#322Re: Klarna users are being signed in to random accounts
#323Earlier quoted context omitted.
That only protects the user's password. The auth cookie will be sent in all subsequent requests in plain text. EDIT: that's how firesheep ( https://en.wikipedia.org/wiki/Firesheep ) hijacked sessions for e.g.
That's not true. Cookies can have a 'secure' attribute which tells the browser to send them only over TLS
Re: Klarna users are being signed in to random accounts
#324Does Klarna still do the IQ test as part of their hiring process?
They did that? Although, I guess Google does IQ tests too in effect? But it's called "solve this puzzle" and "here's a riddle".
Re: Klarna users are being signed in to random accounts
#325I'm just guessing, but... "developer gets a great idea - let's push an update to the API as a GET request so we can cache this on the CDN... forgetting that the JWT token is potentially returned in the call. Now, whoever makes the call first gets their JWT token stored for everyone else to load instead when the API call is made." Ta-da, Klarna.
I introduced a similar bug into one of my products in the past (Be honest, who hasn't?). But I'm surprised here because Klarna is a quite mature product and something like this shouldn't really happen at that stage.
Re: Klarna users are being signed in to random accounts
#326Earlier quoted context omitted.
A recruiter contacted me aswell and I asked about their salary. They pay 50k euro for juniors in berlin with afaik no stock vesting. How they even manage to get qualified personnel is beyond me, I would expect much more for a fintech with over 3B evaluation
50k in euro's is pretty ok for European developers, no?
Re: Klarna users are being signed in to random accounts
#327Earlier quoted context omitted.
In their statement they deny accessing bank details: > The bug led to random user data being exposed to the wrong user when accessing our user interfaces. It is important to note that the access to data has been entirely random and not showing any data containing card or bank details (obfuscated data was visible). This means that it has been impossible to access a specific user’s data. This is not the experience of t…
I believe it is the case, that when you see your stored payment method is is obfuscated such that it only reveals the last 4-5 digits. Same with bank details as far as I know. However, showing the card issuer/bank + the final 4 or 5 digits of an account or card number is still extremely distressing. There are some services and vectors out there that can be engineered with just that information for sure. Combine that…
However, to the layperson, "bank details" definitely includes name of bank and last 4 digits of account number. It does come across as deceptive to use that terminology to respond to customer complaints.
Re: Klarna users are being signed in to random accounts
#328I'm just guessing, but... "developer gets a great idea - let's push an update to the API as a GET request so we can cache this on the CDN... forgetting that the JWT token is potentially returned in the call. Now, whoever makes the call first gets their JWT token stored for everyone else to load instead when the API call is made." Ta-da, Klarna.
Re: Klarna users are being signed in to random accounts
#329Earlier quoted context omitted.
Let's Encrypt started in 2014 to address HTTP overuse. In 2011, I (in-house corp app dev) was still stuck with HTTP services (behind a firewall, accessible only via VPN). In 2014, public facing mobile apps using HTTP was prevalent enough to prompt name and shame campaigns. [1] My fuzzy memory suggests some banks were still using HTTP. [1] https://arstechnica.com/information-technology/2014/08/new-w...
I started doing professional web development in 2011. It was very clear at the time that not using HTTPS for any site with a login was an BAD practice that made your users less secure. There were clearly people and institution still using bad practices, but risks were clear to most web developers. What was shifting at the time was developer views on using HTTPS for non-secure, unauthenticated portions of websites. Th…
Re: Klarna users are being signed in to random accounts
#330Earlier quoted context omitted.
Yes, sadly a quite common part in too many recruitment processes here in Sweden.
My first job at a consulting company out of uni I had to to an IQ test that could also indicate if I had rabies. It had questions like "are you afraid of water", "have you showered in the last three weeks", "have you felt more aggressive lately"...
[1] https://en.wikipedia.org/wiki/Minnesota_Multiphasic_Personal...