782 karma · joined February 4, 2016
> If you have a pot of money that is immune to bank runs, over time, modern finance will find a way to make it vulnerable to bank runs. That is an emergent property of modern finance. No one sits down and says “let’s make pension funds vulnerable to bank runs!” Finance, as an abstract entity, just sort of does that on its own.
https://www.bloomberg.com/opinion/articles/2022-09-29/uk-pen...
You mentioned some missed out on the government grants - was that the main cause?
s/man/woman, in this case of course.
That’s down from 35 when I raised the issue 2 years ago!
How would you like me to let you know about these?
They didn’t seem interested in resolving!
There is no formal route to production, but you might meet senior people who could help.
They’re still a target for someone wanting to cause disruption or engage in hybrid warfare - imagine a simultaneous hack of all the neobanks, possibly followed by a few of the traditional banks a week later for maximum impact?
They’re still a target for someone wanting to pivot into other organisations they might be connected to, such as card networks or regulators.
We should assume good faith on the part of James Liu and Robert Adams unless you have evidence to the contrary.
To your point about carrot and stick - yes, the carrot here is likely excellent financial compensation for doing the main job, and the experience on the resume, same as all your colleagues. Amazon aren't going to pay you extra because your hobbies are impacted by their policy - at junior to mid levels it's take it or leave it.
Creeps are going to creep, but it's legitimate to want to reduce the number of avenues they can do that.
Yes, it will be evident that the commits appeared in the git history, but not necessarily how they got there. If the git repo on disk suddenly has that commit, and no other usual indicators of compromise, that doesn't really give you anywhere to start looking for, what we agree is, the interesting vulnerability. All you have is "we know this box/service was definitely rooted, so look at all our infrastructure end-to-end".
They care about the exploit enough to move - of course. But do they care enough to investigate and find the actual exploit? Or hand over the server image to someone who does? Unless they've wrapped it in some PHP, it's probably not their core competency. I don't follow the PHP project, so I don't know the answer to that.