Some of the features you have pointed to are sitting waiting for someone to come along and design/write them. Most of this wider work has been updated within the last couple of weeks, ricochet is still actively being worked on & used - just not in the most visible places right now. There are also a few experiments regarding running on mobile and using ricochet and these other libraries for other things besides traditional IM. There is currently a bunch of (official|unofficial) work going on in the wider ecosystem - most of it related to factoring out the base library to go to make it more useful as well as porting the main client to go. Hi, I don't speak for but I think some context might be useful. It's actually way smarter than that, as I understand it, but that gives me enough of a mental model to work with it as a lay person. I'm probably summarizing it very poorly, but my mental model for it is roughly, at the end of every message I send you, I tell you what new password I will use when I send you the next message. There's also a weaker form of Perfect Forward Secrecy (think of it as "offline"), but the risk is that if the communication if broken at any moment, then you can't recover from within that channel - meaning you'd need to go back to the person out of band, and restore communication. I only propose a limited number of days to lessen the storage costs.įor the rotating keys, as I understand it, there's Perfect Forward Secrecy, but it's very chatty (think of it as "online"). ![]() But in my defense, I'm trying to come up with a way to make it easy for a lot of people to use, thus making it easier for everyone to hide in plain sight.įor the "guaranteed expiration," I am actively assuming bad actors would download and archive all messages. And I'm essentially inventing dead drops. ![]() Also, yes, I recognize that key management is THE PROBLEM. If they arrive out of sequence, he knows to be supremely suspicious. And if Bob wants Alice to be able to send him messages, then he (out of band) has to give her a huge list of IDs he'll be watching for, in sequence. Bob should also be rotating his IDs all the time. Rickycook responded to this part with a proposal, but I have my own take on some of it:įor the "tied to a unique piece of data," that's why I want Bob to download lots of messages, hiding the fact that the person at 14.85.101.86 is the user with the recipient ID of ntULzh2AeEgPH9bKxrn3gUL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |