Couldn’t agree more — Much like running my own DNS or email server, I don’t think I’ll ever go back to running my own website directly on the internet. It’s just not worth the hassle. For stuff only I use, it sits behind my VPN. For anything that _must_ be public, it’s going behind a WAF someone else can run.
unless you’re stating crypto primitives should only be written in assembly
Yes, that's exactly what I'm stating.
Have a look at openssl, boringssl, nspr, etc. They all implement the core modular arithmetic for RSA and the s-box table for AES using assembly language. There is no reliable way to prevent a C compiler from "optimizing" your constant-time code into non-constant-time code.
another rust TLS implementation
rustls uses assembler (from boringssl) for these routines. It is not 100% rust, and that's a good thing.
So that the things that change only appear to update, not a flash of the entire screen. If the request is slow, this makes a bigger difference of course.
They release every month so although the releases might not sound big in isolation, the sum of what they release over a course of let's say year is quite exciting.
Last really big one (for me) was support of SIMD instructions in the compiler, other releases had improvements here and there.
I will given Berlin credit here — after checking in to our accommodations (took a taxi from the airport), I poked a ticket machine, quickly saw the Union Jack flag and got the machine into English. Couple minutes later we had our 1 week passes in hand. In general I found the system very approachable, using google maps for route planning.
It is ok, but still a far cry from London for example, where you simply hold your card while entering and it automatically gives you the best price for your account. So if you drive around a lot as a tourist you just cap at the weekly price once you reach it.
If you tried that in Germany there would be a legal challenge on the grounds that a system which knows where the user travelled infringes on privacy :D
With the caveat that the cap is always a fixed Monday to Sunday period, so if your stay doesn't align with that, you'll get to pay an additional capping period.
I mean yes — that’s the point. If untrusted parties have access to your keys, it’s already game over. You’ve lost. Disabling them is the nicest thing an attacker can do for you.
Not really: it depends on the permissions assigned to the keys.
I wouldn’t like to wake up to an email that says “your key has been disabled because someone anonymously reported is as leaked, sorry if this has broken your entire system”.
What do you do with this, outside of obviously quarantining and/or disabling the key? How was it leaked? What’s the context?
Indeed, so you’re building all this tooling and complexity and introducing more issues for the very small intersection of people that:
1. Are not malicious
2. Have access to a key
3. Are unable or unwilling to commit it to GitHub
It would be great if this stuff was public and available without a central authority. But after working on it for a while it seems like a fairly good compromise.
There’s already an entire pipeline that handles a key being compromised when it is found on GitHub. All the “tooling and complexity” you need is a simple HTML form to ask for a key and where you found it, and some server-side code to trigger the same pipeline when somebody submits the form.
There are three issues with the use of GitHub here:
1. Not everybody knows that AWS will invalidate tokens committed into a public GitHub repository.
2. There is a window (67 seconds according to OP) in which the compromised token is public but working. For the “small intersection of people”, you could bring it down to 0.
3. GitHub protects GitHub keys, and apparently AWS keys, but does it protect Azure keys? Or GCP keys?
Not necessarily people but systems. Your code hosting platform, your mailing-list host, your chat app, ... are all examples of systems who are hopefully not malicious and could easily add this auto-revoke-publicly-leaked-secret feature, if it was a simple consistent scheme like an HTTP DELETE to a URL.
Canadian but also lived in the US. Have not lived in the EU.
For Canada, while geographically large population wise it’s very small compared to the US. The big Canadian banks are targeting a similar sized demographic to California.
I’m less familiar with Europe, but I’m guessing most nations still have prominent national retail banks, with some having an EU wide market? Those national retail banks would effectively be regional in the US.
