thepyphone VS java-keyring

>> Modern smartphones however, seem like walled gardens in which I have no control at all.

By design, I think.

>> I am locked into a single OS on my smartphone, which either spies on you or is locked down even more. Every iteration a bit more control is taken away from the user.

I got so fed up with this, I abandoned the whole mobile infrastructure and built my own phone with a Raspberry Pi 3B+. The Raspberry Pi is pretty open hardware (yes, I'm aware it's not perfect). For software I used Python 3, C and GTK. It does voice and SMS/MMS only, but that is enough for me.

I built it for myself. It's stable enough that I use it as my daily driver.

I am in the process of open sourcing the code and putting" rel="nofollow">https://github.com/another2020githubuser/thepyphone">putting it out on github.

I truly hope an open hardware smart phone becomes available soon. Until then, I'll use my home grown PyPhone to get by.

I agree that general purpose

If you are going to take a stand for open computing, you are going to have to make sacrifices. You will have to give up a lot of conveniences. As a technologist you will have to give both time and money. Apple and Google are not going to give up their billion dollar industries voluntarily. You will have to stop giving them money. And you will have to stop using their services.

My solution? I built myself a phone out of a Raspberry Pi 3 with a Touch Screen and a Logitech Headset. It does SMS/MMS and voice only. I've been using it for over a year now as my daily driver.

I'm going to open source the code. Check out https://github.com/another2020githubuser/thepyphone for more details. Right now there is just a README out there, the real code exists in a private git repo. I'm reviewing the code and stripping out private details so I don't end up doxxing myself :)

If you like the idea, please star the github project. I could use the encouragement. Thanks.

https://github.com/javakeyring/java-keyring

People are complaining that the OS is not able to securely identify between two applications in the same user context. So they filed a bogus CVE, where the content of the CVE is basically "Linux is not an iPhone". It is a OS app sandboxing feature request, masquerading as a bug report to the keyring team.

Read the belated reply from the gnome keyring folks, pleading with people to understand what the linux security model is, and that linux doesn't have the sandboxing capabilities that have been rolled out to other (paid) operating systems:

https://wiki.gnome.org/Projects/GnomeKeyring/SecurityPhiloso...

Yet people don't understand. They are demanding that everything be turned into an iphone (in terms of app sandboxes) but they are also demanding that once the OS vendor has the power to install a chokepoint around all the apps, that they wont set up a little toll booth there as well.

But IMO asking vendors to not exploit that for commercial gain is only going to be safeguarded by regulation. It's not going to be safeguarded by consumer choice.