You can follow the steps here to use a previous version of the desktop app to extract the keys: https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93
The javascript didn't seem to send the extracted data anywhere, but I did disconnect from the internet while running the script.
Errm...
Remote wipes are possible. Log into your Apple/Google account, figure out how to find your device, then perform a remote wipe.
If tomorrow's race goes on as planned and Stroll participates, that's tomorrow's race. If for some reason Stroll can't participate tomorrow, he won't escape this penalty.
I was looking through this community because my daughter was recently diagnosed, but this comment hit a nerve.
I cannot stand socks that feel wrong, and no, I cannot explain what exactly "wrong" means. I don't own more than 1 identical pair of socks: each pair has a clear left and right sock, so mixing up 2 identical pairs is a nightmare.
More practical: the main version is on my desktop PC. That one gets synced automatically to my NAS. This NAS makes a nightly incremental backup to a cloud provider.
Once you have a setup like this, maintaining it is peanuts. Pay the bills on time and setup email alerts to let you know if drives are going bad or you're reaching your storage limits.
You do need to ensure you're testing your recovery plans once in a while. A backup is worthless if you can't restore it
Not sure what part you don't understand, but I'll try and help: Snopes (a fact checking website) shows that the way links are displayed nowadays (the new link presentation or new way links are presented) on X (formerly Twitter) lacks any sense -> snopes shows the folly of it.
Unless you have siblings. Then you're the less successful evolutionary branch that died out.
I’m going to have to stop replying because I don’t have the time to run every individual through infosec 101.
Sorry, but you're missing the point here. You cannot do anything with a password without storing it in memory. That's not even infosec 101, that's computing 101. Every computation is toggling bits between 1 and 0 and guess where these bits are stored? That's right: in memory.
The backend should never have access to a variable with a plaintext password.
You know how the backend gets that password? In a plaintext variable. Because the server needs to decrypt the TLS data before doing any computations on it (and yes I know about homomorphic encryption, but no that wouldn't work here).
Yes, I agree it's terrible form to send out plain text passwords. And it would make me question their security practices as well. I agree that lots of people overreacted to your mistake, but this thread has proven that you're not yet as knowledgeable as you claim to be.
I recently saw this video about the British Library. They collect everything that's published in the UK (books, magazines, papers, leaflets, flyers, ...). One of the librarians makes a pretty good case about the use of collecting and preserving everything. Even (or especially) the things you don't think are worth preserving.
Just following the rules
As a manager in software engineering: this! If I learned that one of my devs was wasting time like this, I'd want to know. Just make sure to stick to the facts.