HN user

zmanian

3,966 karma

[ my public key: https://keybase.io/zmanian; my proof: https://keybase.io/zmanian/sigs/FGNFuns4rr-oTPpDHVqxkgWpszClo0j7G6HyiwtlMco ]

Posts127
Comments394
View on HN
dcfoundation.io 3mo ago

Show HN: Endo Familiar, an O-cap based JavaScript agent sandbox

zmanian
13pts3
www.reddit.com 6y ago

New RustCrypto releases: `aead`, `block-cipher`, `crypto-Mac` and more

zmanian
1pts0
medium.com 9y ago

An analysis of secure messengers and key change UX

zmanian
5pts0
www.chicagoreader.com 9y ago

Inside the Chicago Police Department’s secret budget

zmanian
233pts153
arstechnica.co.uk 9y ago

Rethinking Linux Kernel Security

zmanian
8pts1
github.com 9y ago

Sarkara: A NACL-Style Rust Post Quantum Crypto Library

zmanian
3pts0
sammantics.com 9y ago

Applications of Zero Knowledge Proofs in Blockchains

zmanian
2pts0
blog.torproject.org 9y ago

The Tor Project Social Contract

zmanian
18pts0
cse.iitk.ac.in 9y ago

Secure Memory in a Haskell Cryptographic Library

zmanian
1pts0
z.cash 9y ago

Privacy Enhanced Payment Channels for ZCash

zmanian
3pts0
research.microsoft.com 10y ago

Checked C

zmanian
336pts156
medium.com 10y ago

Interviewing Phineas Fisher about Hacking and Anarchism

zmanian
3pts0
internals.rust-lang.org 10y ago

New Rustlang error format

zmanian
4pts0
www.scribd.com 10y ago

The Text of Feinstein/Burr Encryption Backdoor Bill

zmanian
5pts2
www.zdnet.com 10y ago

California's proposed crypto backdoor bill turns into a tax on secure devices

zmanian
7pts0
www.marketplace.org 10y ago

Implanted RFID tracker found in sex trafficking victim

zmanian
6pts1
z.cash 10y ago

How to generate the SNARK parameters for Zerocash securely

zmanian
1pts0
bitcoincore.org 10y ago

Zero Knowledge Contingent Payment Executed on the Bitcoin Network

zmanian
10pts1
v8project.blogspot.com 10y ago

V8 4.9 91% Es6 support

zmanian
5pts0
www.buzzfeed.com 10y ago

How the FBI pressures Muslim immigrants to become informants

zmanian
2pts0
eprint.iacr.org 10y ago

Intel SGX Explained

zmanian
95pts47
www.themill.com 10y ago

Cloud Based Rendering and Light Field Displays

zmanian
9pts4
www.zdnet.com 10y ago

U.S. demands iMessage backdoor in secret court

zmanian
18pts2
money.cnn.com 10y ago

Secret Lives of Superhero Hackers

zmanian
3pts0
blog.torproject.org 10y ago

Tor's first real donation campaign

zmanian
3pts1
fusion.net 10y ago

Detailing the CMU Tor Hidden Services Attack and Tor's Response

zmanian
91pts16
mjg59.dreamwidth.org 10y ago

What is hacker culture?

zmanian
4pts0
blog.torproject.org 10y ago

Tor 2.7.5 released First stable release in 2.7

zmanian
3pts0
www.slate.com 10y ago

Inside the Sony Hack

zmanian
78pts21
www.benthamsgaze.org 10y ago

Scaling Tor Hidden Services

zmanian
85pts2

Tor doesn't support UDP so no HTTP/3 but one would expect most services would be available for the foreseeable future over HTTP/2 as well.

NSL can't require to collect new business records. They can only compel you to disclose business records that you already have.

This is beyond the legal authority of an NSL.

Tendermint 0.10.2 9 years ago

It's hard to evaluate the security of a flippant comment but there is clearly a security benefit of live BFT system vs a non-BFT system.

Tendermint 0.10.2 9 years ago

You would need to compromise 2/3rd of the keys in the genesis block. But yes but this tradeoff unlocks massively high transaction throughput.

Tendermint 0.10.2 9 years ago

I prefer if people differentiate between systems with a PKI and systems without a PKI.

Systems without a PKI like PoW or PoET can be rather centralized like Bitcoin today or decentralized like Bitcoin before the emergence of mining pools.

Systems with a PKI can have an onchain PKI like Cosmos. One of the challenges in an on chain PKI system is you need some of kind social pre-consensus on launch. The crowdfunding established an part of an initial pre-consensus but there are more moving pieces coming.

Tendermint 0.10.2 9 years ago

Tendermint is a BFT algorithm implementation and state machine replication system. The app(state machine) can implement a proof of stake protocol.

Proof of stake functionality is provided by the cosmos sdk which is under development.

Tendermint 0.10.2 9 years ago

Because someone needs to show you a valid set of transitions in the PKI from the original keys in the genesis block to the current attacker controlled PKI.

Tendermint 0.10.2 9 years ago

In a BFT protocol based cryptocurrency, an attacker who acquired 2/3rds of the tokens in the network would be able to double spend at will and censor transactions to gain control of more of the network.

They would not be able to rewrite past history.

The only response to an attack would be hard fork.

The point of this format to push data over the wire in a format that is both semantically richer and authenticatable using techniques like object-hash. This gets us to one true unambiguous representation of the data which you need for redactable signatures and rich credentials.

What should happen is either

- A shared key should be passed over the e2e text channel and used as part of the DTLS setup. I'm unclear if this actually a possibility in WebRTC.

- Each side can send a fingerprint of the peers public key to each other over the text channel and the software can authenticate there is no MITM

Vuvuzela seems great except your anonymity is guaranteed by a set of high availability and capacity servers.

Those servers need to independently operated and resistant to global compromise.

We don't really have a good template for a system like this. We have centralized HA systems and decentralized high churn systems like Bittorrent and Tor.

I've been intrigued by the observation that forthcoming "proof of stake" blockchain systems have very similar requirements in terms of availability and capacity to anonymous messaging systems. I wonder if we can use the nodes in a PoS system to bootstrap an anonymity system like Vuvuzela.

This post was also extensively discussed back then. It is a classic but yeah 2014 belongs in the title.

It's interesting that encrypted messaging has exploded since 2014 but spam has not yet become that much of a problem.

I have a few hypothesizes about this.

1. Decentralization won in 1970 - 2005 protocol design because reliable computers were very expensive. It was economically advantageous to have a decentralized network of unreliable computers than centralized unreliable protocols. Reliable compute has now become commoditized by the cloud services. This creates a pressure for centralization.

2. Decentralized protocols have not aged well(TCP/IP, SMTP), have deep security flaws and have proven difficult to upgrade. This has created new centralization pressures to cope with the security flaws(Gmail, Cloudflare)

3. There continue to be pressures for decentralization related to both politics and security pressures. Tor and blockchain cryptocurrencies are excellent examples of these. But decentralization is unlikely to extend all the way to edge devices and instead operate in a federated fashion.