@mikko @jeremiahg "other reasons" is why Detekt actually has some credibility.
-
-
Replying to @dakami
@dakami@jeremiahg In our case, "other reasons" means customer confidentiality. Not governments trying to shut us up.1 reply 2 retweets 8 likes -
Replying to @mikko
@mikko@jeremiahg how common is it for customers to ask you *not* to add protections against a given piece of malware?2 replies 3 retweets 2 likes -
Replying to @dakami
@dakami@jeremiahg No customer (and no government) has ever asked us not to add detection on some specific malware.2 replies 4 retweets 3 likes -
Replying to @mikko
@mikko@jeremiahg When you detected Regin, and were asked not to talk about it, did you still quietly deploy detection against it?3 replies 3 retweets 5 likes -
Replying to @dakami
@dakami@mikko@jeremiahg Yes, this is the most pertinent question.1 reply 0 retweets 0 likes -
Replying to @iblametom
@iblametom@mikko@jeremiahg OK, to be even more fair, "asked not to talk about it" is actually the default state under NDA's2 replies 1 retweet 1 like -
Replying to @dakami
@dakami@iblametom@mikko@jeremiahg I think a clear statement from FSecure would put a lot of minds at rest.2 replies 1 retweet 2 likes -
Replying to @ProfWoodward
@ProfWoodward@dakami@iblametom@jeremiahg Malware decoded, detection added, no press release as customer doesn't want one. That's it.5 replies 11 retweets 8 likes -
Replying to @mikko
@mikko@dakami@iblametom@jeremiahg so fsecure has been able to detect since 2009?3 replies 0 retweets 0 likes
@ProfWoodward @mikko @dakami @iblametom @jeremiahg Very few AV detected in 2009, detections seem to have increased over the years.
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.