Re:TrueCrypt developer says no to license change for forking
by jiggy2011 on Wednesday June 18, 2014 @12:17PM
(#7910920)
They are frightened that tptacek might say mean things about their hashing algorithms.
[ Parent
| on HN ]
Re:TrueCrypt developer says no to license change for forking
by toomuchtodo on Wednesday June 18, 2014 @01:27PM
(#7911353)
I'm not even in the security space and I'm sometimes afraid of tptacek's rebuttals to my comments.
Re:TrueCrypt developer says no to license change for forking
by tptacek on Wednesday June 18, 2014 @01:37PM
(#7911422)
Their hashing algorithms?
Re:TrueCrypt developer says no to license change for forking
by chimeracoder on Wednesday June 18, 2014 @01:40PM
(#7911446)
Or their node.js implementation of DNSSEC!
Re:TrueCrypt developer says no to license change for forking
by tptacek on Wednesday June 18, 2014 @01:44PM
(#7911476)
Contrary to popular belief I don't have a huge problem with Javascript. I'm just as likely to make fun of you for implementing DNSSEC in Haskell.
Re:TrueCrypt developer says no to license change for forking
by chimeracoder on Wednesday June 18, 2014 @01:47PM
(#7911488)
I thought you did for Javascript for crypto purposes, though, (ie, a pure node.js implementation), not Javascript in general, right?
Re:TrueCrypt developer says no to license change for forking
by tptacek on Wednesday June 18, 2014 @01:55PM
(#7911537)
My problem is content-controlled Javascript (or "browser Javascript", although that term is less useful what with browser extension Javascript, which isn't content-controlled).