Sorry, this entry is only available in German. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.
Nachdem App Security immer wichtiger wird, und mein letzter Blog darüber schon eine Weile her ist, möchte ich diesen hier fortsetzen. Diverse Grundlagen, dass man z.B. immer SSL zur Kommunikation verwendet, sollten ja jedem Entwickler bekannt sein. Um aber die App besser abzusichern, müssen wir auch auf die “andere Seite” schauen, also den Blickwinkel eines Angreifers beachten. Dies wird hier am Beispiel “lokale Datenspeicherung” beschrieben.
I can’t think how often I’ve heard that sentence. In any case, here’s what Edward Snowden has to say about it, “Arguing that you don’t care about privacy because you have nothing to hide is like arguing that you don’t care about free speech because you have nothing to say.” So, if you’ve also found yourself saying or thinking it at some point, please continue here, because I’m sure you will have a different view when I’m done.
What kind of data am I releasing into the world and how can I protect personal information from being stolen or misused? These are frequently asked questions nowadays, but unfortunately, there is no universal answer that works for everyone. Nevertheless, I would like to give you some pointers on how to better protect your privacy in the digital age.
There’s hardly a mobile app that relies solely on static content. And in order to load content dynamically, http-based protocols are most often used. In this article, I will tell you some things you should be aware of when using an http connection with SSL and how you can avoid man-in-the-middle attacks.
Setting up an OpenVPN Server with multiple WANs can be really frustrating and there is almost nothing about it on the internet. With a bit of effort, we managed to get it done. And now we show you how.