I somehow love this story… we had great fun and made it from total outsider with no chances into the final, almost winning against the overlords. My dear colleague Marcel Hilzinger and me were so close to really, really embarrassing Microsoft – but in the end, Sauron’s powers were stronger. Maybe next time, we thought, but they never invited us Linux-Magazine Journalists again. I guess they had good reason to do so. 🙂
I wonder how much money our government has thrown out of the window for this, and I wonder how the truely great work from Microsoft pays off here. They claim to block Finfisher which is a large part of our German Bundestrojaner, and here is a wonderful and detailed blogpost about how they did it and about the amazing findings they made in the multiple layers of virtualization and obfuscations. “FinFisher is such a complex piece of malware that, like other researchers, we had to devise special methods to crack it.”
Finfisher is using an onion-like shell system of six layers around their payload (whatever that may be). And it has several virtual machines built-in with up to 32 opcodes specifically created for this system, all but to protect, obfuscate and hide the payload. But what does the payload do? On that, Microsoft’s engineers write:
“It is evident that the ultimate goal of this program is to steal information. The malware architecture is modular, which means that it can execute plugins. The plugins are stored in its resource section and can be protected by the same VM. The sample we analyzed in October, for example, contains a plugin that is able to spy on internet connections, and can even divert some SSL connections and steal data from encrypted traffic.”
A really good read this article is. And if you find the time, read this amazing work by Tora.
Troy Hunt did it again: After August 2016, where he provided a password checking service testing against list with 320 million passwords (“HIBP” and “Pwned Passwords”) he now launched “Pwned Passwords V2” with more than half a billion passwords. If you dare, and if you trust him, you can enter your favorite password here and with the blink of an eye you will see if it is on Troy’s list. If so, then it has been cracked, used before or similar. The Password “password” e.g. has been seen 3 million times, as the new counter in Troy’s tool shows. Plus, the website holds some healthy information and guidelines from NIST on password reuse. Continue reading 500 Million passwords leaked→
This is a talk that I first gave as a workshop, together with my wonderfully skilled and experienced colleagues Jake Edge (LWN) and Deb Nicholson (OIN) during the 12. KDE Akademy in Tallinn, Estonia in 2012. Where then we did it as a full-day workshop, this video is from QtCon 2016, and it’s more a presentation of 1:00 hour. This is one of my favourite presentations and the one booked the most – I did it at SUSECON, openSUSE conference and SUSE Labs, too and for a variety of other hosts.
This talk will tell, teach and train open source community members, company leaders, developers and open source project leads how to deal with the press.
Documentation is team work, yes – but can you do it collaboratively? Yes, but not in collaborative editing. Git is your friend, a good workflow needs to be chosen, and then everyone on your team may choose the editor he loves. Etherpad, Google Docs and such are tools for short texts, but not for professional editing. In this article for Linux Magazine Germany I explain how we work at SUSE.
The error is on OSI Layer 8, and even the best technology won’t help you if you use it wrong. In this article about the Darknet (Heise I’X, in German) I demystify many “given” assumptions. No NSA, no police, nobody needs to crack your cryptography if you do the same silly mistakes like so many others before you.
In this article for Heise I’X (in German) I present statistical and empirical evidence why it usually is a bad idea to force your users to change their password regularly. In fact, you’ll maybe push users to use patterns for their passwords that are cracked much easier than their password. What is a good password, and why you should only change it when you have reason for doubt. “You will need good reason to push your users into regularly changing their passwords – and only in few cases or insecure environments this may make sense at all…”
Open Source. Security Theater. Leadership. Journalism.