Security should be a thing. An important thing actually. But I, as many other app developers, only know some basics. More common sense that real expertise. But that doesn’t mean that I’m not worry about the security of the app I work on, and that’s why I come here to write a bit about my tries hiding some API keys from others. I tell you my case.
With this post I want to introduce you to one of my side projects. This introduction will serve to explain what the project consists of, how long I have been working on it and why I started to work specifically this idea.
I will try to be very general in my posts and probably will not write only about programming, although right now it is a big part of what I am doing so it takes up all my time dedicated to the application.
I remember that once I felt with the world at my feet. I felt able to do everything. I was using Realm as local database for my Android site project apps. And I felt like that all the people who don’t use it were really wrong. But it was just a bubble. Nice but fragile. And after a lot of headaches the bubble bursted.
Disclaimer: In this post I don’t want to give the feeling that I don’t like Realm or that it isn’t a good database. I will just tell you in a few lines my experience and why, after more than a year using it I gave up and started to use another local database for my projects. I’m probably more guilty of the headaches than Realm
Ok, ok, I know. It has passed almost a month since the last post. But you know, holidays, new year, a cold winter… but I’m here again to conclude this serie about the security audits in mobile devices. In part 1 we saw what were the requirements that we need before start with the audit. In part 2 we actually started with the audit and saw some of the phases of an audit. In this last part we will see the last phases of an audit.
In the last post I have shown you the previous steps to init an audit with all the warranties to make a good job. In this post the fun begins. As in the past, I will explain you the basics of the next phases of the audit.
A few months ago I enjoyed my first online course. The topic? Security. Specifically, mobile devices security. More specifically, mobile devices security audits. As an Android developer I’m really concerned about security, not only as a developer, also as a user.And because I think that what I learned there can interest you I will try to explain it here.Probably it is too much content for only one post so I will divide it in two or three parts.
Security have become an important part of everyone’s life. And, when we talk about online security, everything have changed a little bit since Snowden leaked all the information and documents about the fact that we have been being observed for the USA government and the NSA. Now, the people are worry a little bit more about their privacy, but what hasn’t changed a lot is the worry of the people about their security online.
People don’t want to be worried about security. Should be the companies and developers who must have always an eye in give the best in security to the user.
With the purpose to serve as a reminder to companies, has been created the OWASP project. To help companies and developers to don’t forget some aspects of the online security.
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.