Twitter bestof: @4Dgifts had seen the libotr bug before the bet deadline but no one verified https://www.x41-dsec.de/lab/advisories/x41-2016-001-libotr/ … https://twitter.com/4Dgifts/status/659140835850780672 …
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @4Dgifts
@4Dgifts@FiloSottile It was not an easily fuzzed vuln.2 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @4Dgifts
@4Dgifts@FiloSottile In general, I’m sure yes, but they were looking as an exercise for their CGC toolset.1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @4Dgifts
@4Dgifts@FiloSottile@dguido I think they blogged about it.1 reply 0 retweets 0 likes -
Replying to @tqbf
@tqbf@4Dgifts@FiloSottile yes, and the bugs found today were all in code we didn't look at afaik.http://blog.trailofbits.com/2016/01/13/hacking-for-charity-automated-bug-finding-in-libotr/ …2 replies 0 retweets 6 likes -
Replying to @dguido
@dguido@4Dgifts@FiloSottile Oh, you were also pre-decryption, right.1 reply 0 retweets 0 likes
Replying to @tqbf
@tqbf @4Dgifts @FiloSottile Yes, pre decryption and no SMP. We only looked at core, not pidgin utilities.
3:05 PM - 9 Mar 2016
1 reply
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.