Viewing profile — maxtaco
maxtaco
HN member- Joined
- Thu, Mar 10, 2011, 7:08 PM UTC
- HN karma
- 416
- Public activity
- 139 items
- HN profile
- View on Hacker News ↗
About maxtaco
MIT PhD 2008 from the PDOS group
[ my public key: https://keybase.io/max; my proof: https://keybase.io/max/sigs/qfuA9DvtaEpA5I3h42XnrOdlozCYGfn3nNsn492YAvU ]
Recent public activity
-
comment
Comment #47952733
Use extreme caution running arbitrary code on your machines, especially obfuscated code that tickles kernel bugs! (edited)
-
comment
Comment #47826753
Backpointers to earlier epochs in append-only cryptographic data structures like key transparency logs. If the client last fetched epoch 1000, and the server reports the current ep…
-
comment
Comment #47815437
Amazing man, with many important contributions over a very long career. The Rabin Cryptosystem (like RSA, but with public exponent 2) is notable for two reasons. First, unlike RSA,…
- story
- story
-
comment
Comment #47629885
I think in practice it doesn't work to deserialize only verified data. Snowpack has a mechanism for this but I found it impractical to require all use cases fit this form. I'm not …
-
comment
Comment #47614036
Bingo!
-
comment
Comment #47608276
It seems like in that PR, the fact that the OID wasn't checked is part of the problem. I think a better system wouldn't compile or would always fail to verify if the OID (domain se…
-
comment
Comment #47607081
Hi, post author here. Agree that the idea isn't tricky, but it seems like many systems still get it wrong, and there wasn't an available system that had all the necessary features.…
-
comment
Comment #47606933
It should be possible to change the name of the type, and this happens often in practice. But type renames shouldn't break preexisting signatures. In this scheme you are free chang…
-
comment
Comment #47606672
I would say two problems with the asn.1 approach are: (1) it seems like too much cognitive overload for the OIDs to have semantic meaning, and it invites accidental reuse; I think …
-
comment
Comment #46529495
Also on the front page of HN right now is a job posting for Optery (YC W22). Seems like they are growing really fast.
-
comment
Comment #46406506
An intended use case for FOKS ( https://foks.pub ) is to allow long-lived durable shared secrets between users and teams with key rotation when needed.
- story
-
comment
Comment #45239035
I think one could build something nice on top of FOKS ( https://foks.pub ).
-
comment
Comment #44532311
No incremental fetch right now other than what postgresql provides by default. If you're hosting a FOKS server, there is important metadata to backup too. The best docs for the KV …
-
comment
Comment #44531989
An attack that might be of concern with this configuration is the server suppressing updates to this JSON file, or showing different versions of the JSON file to different clients.…
-
comment
Comment #44531936
Thanks for these great questions! - limiting users to delete/push/force; this is possible but I don't see how to cryptographically guarantee it. The server can't really help since …
-
comment
Comment #44529667
This would be a great application for us! We are not exactly there yet, for reasons of privacy. Right now, there is no way for alice@host to allow unauthenticated users to view her…
-
comment
Comment #44527614
Easy multi-accounting is something that I hope we already have (`foks key switch` is pretty smooth). It's a feature I use a lot (I have a personal account on @foks.app and our comp…
-
comment
Comment #44527183
Thanks Danny! The Keybase team (not including me) deserves all the credit, I've been gone for over six months. It's a great team and I miss working with them.
-
comment
Comment #44527168
Thanks! Would love to see a file sync app, an MLS-based chat (where the encryption key is essentially a combination of the keys output from MLS and the PTK from FOKS). Password man…
-
comment
Comment #44524750
I'm not familiar with Radicle, but I'll check it out. For (1), consider the case of that server being hosted on AWS. Even though only members are authorized to SSH into it, the pla…
-
comment
Comment #44509608
It's not as seamless. You need to first make a team, then invite (or add) that user into the team, and then use `foks kv put --team `. One key difference is that in Keybase, all us…
-
comment
Comment #44505115
Correct! Remote members of the team get access to shared team keys, and the team's data, even though they don't have accounts on that server. Knowledge of the team key suffices to …