31–40 of 63 posts
Latest commit 5fdc936 on Dec 18, 2015 Is this still an active project? 4 months is a long time to pass without a commit published.
Sometimes software is just "done", you know, or only needs updates every few years.
Latest commit 5fdc936 on Dec 18, 2015 Is this still an active project? 4 months is a long time to pass without a commit published.
Sometimes software is just "done", you know, or only needs updates every few years.
Plus, it's security software.
Earlier quoted context omitted.
It depends on a long list of crappy bloated software If you don't actually want to test the software, and just want to create a production mobile/desktop application, then it depends on codova, cordova-icon, cordova-splash, semver and it's own source code. That's not a long list. If you want to test it, then it's probably not a shock that it pulls in testing frameworks for testing javascript UIs. including something…
> That's not a long list It's not the list of top-level pieces of software, it's the amount of code that could have contact with the plaintext or the encryption keys. > If you don't actually want to test And build! Don't forget the building itself. It's not so much harder to exploit an app even if all you have access to is its build stage. ---- This is security software we are talking about. The more lines of code th…
https://www.passwordstore.org/
For syncing, either use git, or something like syncthing. It doesn't really matter, because all synced files are encrypted by GnuPG before any syncing tools gets access to it.
Latest commit 5fdc936 on Dec 18, 2015 Is this still an active project? 4 months is a long time to pass without a commit published.
I lean towards "No". For example, this was never merged: https://github.com/SpiderOak/Encryptr/pull/180 I eventually closed it because I keep an eye on https://github.com/pulls and it was unnecessary clutter.
Earlier quoted context omitted.
It depends on a long list of crappy bloated software If you don't actually want to test the software, and just want to create a production mobile/desktop application, then it depends on codova, cordova-icon, cordova-splash, semver and it's own source code. That's not a long list. If you want to test it, then it's probably not a shock that it pulls in testing frameworks for testing javascript UIs. including something…
> That's not a long list It's not the list of top-level pieces of software, it's the amount of code that could have contact with the plaintext or the encryption keys. > If you don't actually want to test And build! Don't forget the building itself. It's not so much harder to exploit an app even if all you have access to is its build stage. ---- This is security software we are talking about. The more lines of code th…
I was slightly puzzled what they meant by "zero-knowledge encryption", but after looking around a bit it looks to be more of a buzzword than really related to zero-knowledge proofs (besides them using SRP for password validation). As far as I know, all password managers like Lastpass, 1Password, etc. use client-side encryption of data. Does this do anything new?
I'm a little confused by this. The project page makes it sound like someone's weekend project, complete with a donation link, but in fact it seems to be the client for one of SpiderOak's products. In any case, I'm having fun reading about some of the projects used to build this, including Crypton. Will this work with any Crypton server, or is it somehow tied to SpiderOak? Edit: "I am happy to announce that SpiderOak…
Earlier quoted context omitted.
They tried to coin a new (unrelated) sense of this term about two years ago in order to try to explain services where the service provider doesn't have access to your data. I agree that it's confusing because of the much more clearly established technical term with a different meaning, and I don't think SpiderOak's sense has caught on outside of the company. Can anyone suggest a better term? Some people like "end-to-…
Steve Gibson calls this type of design "Trust No One" (TNO), which I quite like. But I think "end-to-end encrypted" is fine and has caught on with the public to some extent.