3 ms·
This article is based around the source that author claims to be faked in another article, http://blog.erratasec.com/2014/07/validating-xkeyscore-code.html http
by jdong 12y ago
This article is based around the source that author claims to be faked in another article, http://blog.erratasec.com/2014/07/validating-xkeyscore-code.html http://blog.erratasec.com/2014/07/validating-xkeyscore-code....
edit: fixed link
- csandreasen 12y agoI think you mean this one: http://blog.erratasec.com/2014/07/validating-xkeyscore-code.html http://blog.erratasec.com/2014/07/validating-xkeyscore-code....
- jdong 12y agoThanks, clipboard wasn't syncing properly.
- dobbsbob 12y agothat article: "The filename xkeyscorerules100.txt is implausible. Source files do not end in ".txt" and the term "rules" is an odd choice." Looks to me like a typical sample config file that you rename xkeyscorerules100 after editing just like how you would create /etc/udev/rules.d/51-android.rules or SELinux custom module policy before compiling.
- Torgo 12y agoYeah, there are so many reasons it could have a .txt extension the criticism is not plausible. The first thing I thought of was, somebody nontechnical in the reporting pipeline changed the extension to .txt so it would open automatically in a text editor on their OS. Or, they pasted the contents in notepad and saved it, which would automatically append the .txt extension.