johnduhart
Joined 14 years ago
Joined 14 years ago
So do we need to wait for abuse with this specific piece of technology in order to be concerned?
> It emits an event, then immediately returns a response — meaning it always reports success (201), regardless of whether the downstream email handler succeeds or fails.
It should be understood that after Lambda returns a response the MicroVM is suspending, interrupting your background HTTP request. There is zero guarantee that the request would succeed.
1: https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtime-...
Okay, but then you implement storage of the refresh token and build this bespoke JWT re-issuance logic. So where's the win here? Just use sessions.
1: https://www.polygon.com/news/527186/destiny-steven-bonnell-s... 2: https://en.wikipedia.org/wiki/Destiny_(streamer)#Post-Twitch...
The Government taking action against a citizen for voicing opinions it does not agree with falls pretty clearly into what the 1st amendment covers. This is not a "yelling fire in a crowded theater" type scenario where speech is being restricted for the benefit of many.
5.5% of what, dmm?
https://www.healthcaredive.com/news/unitedhealth-unh-2024-re...
> the Minnesota healthcare behemoth reported adjusted profit of $25.7 billion — an all-time record.
No, I don't believe that's at all what was happening. I really recommend reading the original compliant[1]. TCS was leveraging their employees with access to CSC's documentation and source code to glean information about how a particular feature was implemented, _not_ for supporting Transamerica, but for reimplementing the feature in their own product.
From paragraph 29 of the compliant:
> A TCS employee, who upon information and belief is part of the U.S. BaNCS development team, wrote in an email: “Quite honestly, I’m not sure how VTG [Vantage] does this today, so maybe we should engage [TCS employees with access to the Vantage source code] if we want to emulate that?”
The complaint goes on to describe the engineers sending the actual source code to the team. This is pretty clear cut theft IMO.
https://github.com/golang/go/issues/44577#issuecomment-11378...
> We did consider caching clones, but it has security implications and adds complexity, so we decided not to. It is certainly not trivial to do and not something we are likely to do based on this issue.
Drew continues to act as though he is always correct, and any viewpoint that isn't his is just moronic. I've repeatedly seen this behavior from him in multiple venues over the years, and I'm happy to see the wider community start calling this out as childish.
That's simply not true. I'm able to log onto GitHub on my corporate device using a passkey that's kept in 1Password on my iPhone.
https://bughunters.google.com/blog/passkeys