But that’s theoretical thinking and the real world is indeed more shades of gray.
See you in Madrid!
1,550 karma · joined April 30, 2012
[ my public key: https://keybase.io/arnar; my proof: https://keybase.io/arnar/sigs/lf4Zbpd04PZPXu_eZyGhPVoef2BuJ0p5VUuzV8ZXD4I ]
But that’s theoretical thinking and the real world is indeed more shades of gray.
See you in Madrid!
ducks for cover
Macaroons are very much grounded in capability thinking, where it is a “feature” that principals such as the user agent in your case don’t need to have representable identities. So there’s nobody to authenticate, except the fact that it was a holder of the previous macaroons tag, which means they had the authority it represented.
In other words, not needing something like a PKI is somewhat the point of it all.
If you have the need to authenticate the intermediate principals, eg because they have pre-existing identities already, then the capability model in general may just be a distraction. They could just sign their desired attentuations with their own identity key.
(And thanks! I’m still citing your Velvet Underground comparison.)
Macaroons are an abstract thing. They don't define an encoding format, nor any semantics or language for the caveats. So a lot of detail is left up to the implementer, which is why they're fairly hard to use. Their basic form is also built on symemtric keys and hmacs, so only the issuer can verify, which is a significant limitation in the real world.
AFAICT Biscuits define those (protobuf for encoding, a logic language for the caveats) and use public keys instead to allow other parties than the issuer (=holder of the root key) to verify them.
https://lightpaintingphotography.com/light-painting-history/
Signing is different from encrypting.
https://en.wikipedia.org/wiki/Digital_Signature_Algorithm
And yes, 100% agree we can do better in terms of explaining passkeys. The hardest part is that different audiences require such different approaches.
When you log in later, the server uses an API to give your client a random unique challenge (just some bytes), you unlock and approve and the pwm signs some stuff including the challenge and sends the signature back. The server verifies with the public key, and is satisfied because only your private key could’ve generated that signature.
But you are exactly right - this is detail and the UX is essentially the same as having the pwm generate random passwords that you never get to see or copy.
Yes and no, respectively.
It's too early to completely replace all methods with passkeys, but the hope is that as they gain better support and understanding websites will be able to make other methods rare/exceptional. For exceptional cases such as account recovery, as opposed to day-to-day account sign-in, there is room to apply a lot of other abuse signals and other methods to make it harder for attackers.
More here: https://security.googleblog.com/2023/05/so-long-passwords-th....
In short we can only verify PINs, and only a very limited number of guesses, enforced by hardware.
Because when evil.example requests the passkey it has to do so through browser APIs [1], and it can't lie about its domain name. Your browser is what reaches out to your phone, which is how your phone learns what domain you are actually on.
[1] https://www.w3.org/TR/webauthn-2/
In this case your phone wouldn't even show you your passkeys from good.example.
And if you both use iOS, you can Airdrop a passkey: https://support.apple.com/guide/iphone/share-passkeys-passwo...
Note that passkeys come out of the collaboration of many industry partners within FIDO and WebAuthn. I.e. it's not "Apple PassKeys" -- just "passkeys".
See for example https://fidoalliance.org/passkeys/
(disclaimer/context: I work on passkeys at Google)
2/3rds of the time, your initial choice will be a goat. In those cases the host deliberately avoids opening the remaining door with a car - thereby telling you where it is.
If you chose the car door initially, then indeed you get no new information. But that only happens 1/3rd of the time.
I am curious if that changes your opinion.
Not specifying a register (e.g. "0) just means the commands, including x and p, will use the " register, aka the unnamed register. By itself, p is equivalent to ""p.
:reg shows you all the registers and their current contents.
This seems like a good description: https://www.brianstorti.com/vim-registers/
Edit: Oh I guess you are saying it was unexpected that delete or change commands clobber yanked contents of the unnamed register.
Ctrl-T does the same in emacs, and also in readline based programs like bash, as well as everywhere on macOS.
Long term, tipping just means these employers can compete for labor against other (non-tip) industries forced to pay higher, and without having to reflect that additional cost in their prices to the end customer.
The idea that the employer is the one getting the tip is a myth, and a well bolstered one for obvious reasons.
Personally I also find it exhausting to have to judge every single service I get. So I just tip a standard amount, there’s absolutely no feedback involved. So there is no point.
There are lots of downsides with very few upsides.
I am sold, even as someone comfortable with writing complex queries.