woranl

I use client certificate authentication (or mTLS) to access internal services. It requires the client device to present a digital certificate during the TLS handshake, so I don’t need to white list any IP addresses.

What about something like this: A javascript bookmarklet that fetches the html page with SRI, then turn the file into a blobURL and run. Within the html page, all resources are chained with SRI.

OAuth 1.0a requires API requests to be signed.

It would be nice if I can feed an image blob to it, and return the edited image as a blob programmatically - i.e. without the need for an UI to open or download the image. That will help integration/embed it into other apps.

If you have a dedicated bucket just for this and the authentication is just for that bucket, then is it still considered insecure?

I get that a lot, just have to restart that Docker desktop to push the saved changes to volume.

"The problem with Microsoft is they just have no taste. They have no taste and I don't mean that in a small way, I mean that in a big way" - Steve Jobs

Which version of OAuth implementation is at risk? 2.0 and 1.0a are quite different.

I beg to differ. Impact will not be easily felt by businesses if it relies on trickle down consequences. In a capitalistic society, employers and employees don’t share the equal power dynamics.

Tax the companies that deliberately and unnecessarily decided to go against climate policies. Let them feel the direct economic impact for their action. If we are to shield these initiators from the consequence through a series of convoluted economic maneuvers, then nothing will get changed and it’s just business as usual.