Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dfranke
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
45 ms
·
361.
▲
by
dfranke
17y ago
Alright, that's pretty damning. As of now, I'm jumping on the "let's ban Techcrunch links from HN" bandwagon.
362.
▲
by
dfranke
17y ago
Everyone is notorious for making bad estimates. It's just that developers make estimates more often than most other professions do. http://lesswrong.com/lw/jg/planning_fallacy/
363.
▲
by
dfranke
17y ago
ISTR that there was a supreme court case long ago, pertaining to CB radio, establishing that prohibiting these warnings is unconstitutional. My Google-fu is failing me, though. Anyone know the name of the case?
364.
▲
by
dfranke
17y ago
Maybe he could word it like this: advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and its contr
365.
▲
by
dfranke
17y ago
Nah, that'd be one-time pads.
366.
▲
by
dfranke
17y ago
There are plenty of scenarios where someone would be watching you type your password through a camera, but doesn't control placement of the camera. The most common case would be a security guard who is paid to monitor the cameras but had n
367.
▲
by
dfranke
17y ago
Replying to the complainant with an explanation of Tor.
368.
▲
by
dfranke
17y ago
http://www.foxnews.com/story/0,2933,526972,00.html but the answer to the OP's question is that the feds are aware of all this, and they don't mind: http://esr.ibiblio.org/?p=1096#comment-237988
369.
▲
by
dfranke
17y ago
I'm running one on Linode. I filed a support ticket first to let them know. This was the answer: Tor exit nodes are not against our TOS, but we will forward any abuse reports on to you and we do expect them to be handled. Also, keep an ey
370.
▲
by
dfranke
17y ago
One must be at least slightly lucky in order to not undergo a total existence failure due to random quantum fluctuations.
371.
▲
by
dfranke
17y ago
To anyone still paying attention to this thread: I'm taking back any implication that encouraging this is a good idea or that it would turn out well, after observation of all the idiotic ham-handed DDoS attacks presently being perpetrated u
372.
▲
by
dfranke
17y ago
Why not weapons? With a competent instructor, the accident risk is lower than for any of your suggested alternatives.
373.
▲
by
dfranke
17y ago
Ding ding ding! You win the thread. It'll break DKIM/Domainkeys too if you have 8-bit characters in your headers. Paws off my mail, Zed.
374.
▲
by
dfranke
17y ago
This is amusingly serendipitous with today's XKCD.
375.
▲
by
dfranke
17y ago
I'm with you on CTR mode: it's a uniquely dangerous recommendation to anyone who needs to be soliciting recommendations in the first place. If you're encrypting a file, then the obvious, elegant thing to do is to use position in the file a
376.
▲
by
dfranke
17y ago
Ah, alright; that makes more sense. Journalism fail.
377.
▲
by
dfranke
17y ago
Apple also introduced a handy new feature called "Find My iPhone," designed to help iPhone owners who have misplaced their device. Lose the device under the sofa, and users will now be able to send the phone a message ordering it to make a
378.
▲
by
dfranke
17y ago
I suspect this is motivated by performance concerns. The overhead of the centralized filtering they do is massive, and a friend living in China tells me that it hurts net responsiveness badly. Since the Chinese government already seems to
379.
▲
by
dfranke
17y ago
Playing devil's advocate: perhaps it seems wasteful in isolation, but if it were not for running the risk of owing many times the actual damages worth of attorneys' fees, companies would be able to screw large groups of people for small sum
380.
▲
by
dfranke
17y ago
$1.9M is a sucky amount of overhead, but it doesn't seem like the class should be entitled to much more than it got. If there's no evidence that anything except email addresses were stolen, and the breach was accidental, then I don't see m
381.
▲
by
dfranke
17y ago
Not even close.
382.
▲
by
dfranke
17y ago
Unfortunate name collision: http://en.wikipedia.org/wiki/CLU_(programming_language)
383.
▲
The paper regarding the 2^52 attack on SHA-1 is now on eprint [pdf]
(eprint.iacr.org)
12 points
by
dfranke
17y ago
|
1 comments
384.
▲
by
dfranke
17y ago
I am.
385.
▲
by
dfranke
17y ago
I'm not quibbling over credit; I just think this kind of simultaneity is a fascinating phenomenon. No doubt both of our thought processes got tweaked by the cluster of other security posts that were showing up on HN at the time.
386.
▲
by
dfranke
17y ago
It's not really a question of known weaknesses because it's not designed to be secure in the first place; it only performs a single round. Its purpose is to be fast and to be "random enough" for scientific applications.
387.
▲
by
dfranke
17y ago
Wow. This post has been sitting on my hard drive for a little under a month waiting for arc3's release, and the hack itself was a few evenings' work, so this was simultaneous discovery damn near to the day. I'm not sure who was first; I n
388.
▲
by
dfranke
17y ago
sudo make me a sandwich.
389.
▲
by
dfranke
17y ago
I think by 'specific account' he means 'chosen account', in which case he'd be correct without more targeted social engineering.
390.
▲
by
dfranke
17y ago
Thanks, I think that's the most elaborate compliment I've ever gotten.
More ›