defiancedigital

Completely agree !

So, if you "don't have good good UI skills" please stop your comments about QtQuick ...

No

Any comments about android service support ?

"C++ coder ... often have poor interface skills, anyway" ... troll inside

You should consider that c++ lambdas does not offer the same level of connection that signal/slot does (direct,queue,blocking,unique) ...

I'm not disturb by moc. Meta object/programmation is a modern approach of OO.

If you have never taste the limit of Webkit/HTML/CSS/jQuery for client side application, you should stay away of QtQuick criticism.

I remember Vidalia (https://blog.torproject.org/blog/plain-vidalia-bundles-be-di...)

many bugs ... pity

Could not read the video on OSX with Safari :-/

Some informations have leaked about a new transport layer based on swallow. Yes, a swallow carrying a coconut !!!

don't worry ntp will fail before, in 2036 ;-)

Redesign of nix command line is a good thing. Nix should be more intuitive.

I totally agree that nix is the future of package management.

hydra vs unicorn dixit github :

Hydra = 1,934 results (https://github.com/search?utf8=&q=hydra)

Unicorn = 1,878 results (https://github.com/search?utf8=&q=unicorn)

Winner Hyra !!!

Ask HN: Is "hydra" the most used open source project name ?

Implementing complete secure communication solution is an hard topic. For now, signal and its axolotl protocol is considered by the community as the top secure communication project. Challenging signal and strong experienced developpers like Moxie will be very complicated (but not impossible ! ...working on defiance;-). It is impossible to claim that your app is the "the most secure" without providing source or documentation (or I did not find them). How community could review your project ... This is not credible, or maybe it is a joke ?

This looks like OSX distribution app. I prefer nix ...

Maybe against monoculture and user experience with pkg-src on OSX was very bad for years. Nix introduces modern concepts that pkg-src will never have without complete rewrite ... so we need to look forward

End to end encryption ... with bots examining your chat to provide adds. Maybe we should call this end to _and_ google :-)

I didn't see anything about renegotiation. If clients present their certificates during first handshake, it will lead to security concerns. Attackers could observe client's certificates (extract meta-data, de-ano clients ...). If renegotiation is used it will drastically reduce "Bonus DDOS mitigation"

I'm looking at libaxolotl-c. I'm a little bit disturbed about perfect forward/future secrecy. Perfect forward secrecy ensure that a session key cannot be compromised if a long-term key is compromised in future. With something like OTR even if a session key is compromised at n, session key at n-1 or n+1 will not be compromised. Here, we got perfect forward/future secrecy.

If i take a look at axolotl, in scenario Alice send message to bob when Bob is offline:

(1) , (2)

MK = HMAC-HASH(CKs, "0") // (3)

msg = Enc(HKs, Ns || PNs || DHRs) || Enc(MK, plaintext)

Ns = Ns + 1

CKs = HMAC-HASH(CKs, "1") // (4)

return msg

We can see that Alice re-use CKs to get a new symmetric key. So if an attacker get CKs(n) he could easily compute CKs(n+1) CKs is not a long term key, but we cannot honestly call this _perfect_ futur secrecy... One more thing, if I remember correctly, according of perfect forward secrecy definition, an implementation must NOT re-use previous session key to derive a new one ...

I'm wrong ?

(1) Quoted from https://github.com/trevp/axolotl/wiki

(2) see session_cipher_get_or_create_message_keys (https://github.com/WhisperSystems/libaxolotl-c/blob/0640b5ac...)

(3) i think we should read MK = HKDF(HMAC-HASH(CKs, 0x00) see ratchet_chain_key_get_message_keys (https://github.com/WhisperSystems/libaxolotl-c/blob/0640b5ac...)

(4) i think we should read MK = HMAC-HASH(CKs, 0x02) see ratchet_chain_key_create_next (https://github.com/WhisperSystems/libaxolotl-c/blob/0640b5ac...)

According to WhatsApp security whitepaper, strp master key is sent throw network. Even inside encrypted payload, it breaks pfs...