@KevinSMcArthur From us? Unknown at this point as they aren't actually a product we offer. It was a one time thing for FB so far.
-
-
Replying to @GreatAmus
@GreatAmus@KevinSMcArthur I think its not a good idea. Its no different than internal names.2 replies 0 retweets 0 likes -
Replying to @rmhrisk
@rmhrisk@GreatAmus@KevinSMcArthur Very different from internal names. At most 1 entity can control an onion address. Public key is the ID.1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____@GreatAmus@KevinSMcArthur that is a meaningful difference, But if its not one entity, its one key and if it has serverauth...1 reply 0 retweets 0 likes -
Replying to @rmhrisk
@rmhrisk@BRIAN_____@GreatAmus@KevinSMcArthur the onion addresses are natively backed by 1024-bit RSA, so collide that + regular cert3 replies 0 retweets 1 like
@pzb @rmhrisk @GreatAmus @KevinSMcArthur I understand your point now. But it isn't a collision attack, but preimage, that would be an issue.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.