- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
cross-posted from: https://lemmy.ml/post/25679666
I recently put together a detailed opsec guide that covers practical steps for reducing your digital footprint, securing communications, and avoiding common pitfalls people make when trying to stay private online.
The goal was to create something that’s actually useful and not just the usual “use a vpn and tor” advice. I tried to break down realistic methods that can help both beginners and people already familiar with opsec.
Id love to get some feedback from the community - what’s missing, what could be improved, and if there’s anything you disagree with.
Searx is unmaintaned, there is a fork called SearXNG.
good catch! Will change it.
Okay I’m not sure if this is offtopic but, I feel like this kinda fit here:
So here’s an Encrypted Communication method that’s “Off Grid”:
Rattlegram is an app on iOS/Android that alllows converting a string of text to audio and play it over your phone’s speaker
Secure Space Encryptor (SSE) (known as Paranoia Text Encryption on iOS) is an Open Source app that can encrypt text.
- Use SSE to encrypt text (both the sender and receipient need to share a password over a secure channel beforehand)
- Copy-Paste the Ciphertext to Rattlegram (Rattlegram will convert the ciphertext into an audio)
- Play the audio over the radio
- On the other end, use Rattlegram to turn the audio back to the ciphertext
- Use SSE to decrypt.
Or replace SSE with OpenPGP, but the problem with PGP messages, is that they are much longer and you need to send multiple Rattlegram transmissions to send the entire ciphertext, basically its more time consuming. You want to finish your transmissions as soon as possible.
You probably want an airgapped device that have the aforementioned apps pre-installed.
Voila! Off-Grid Encrypted communications.
(Encryption is illegal over Ham Radio in many jurisdictions btw. I will neither confirm nor deny that I have tested sending an encrypted transmission 😏)
Thanks for making this @[email protected], I found this a useful writeup :)
youre welcome!
I skimmed it really quick. Looks like a really good writeup! You talk about stylometry, you might be as paranoid as I am.
I don’t even try to hide my speech patterns, but I should.
Will try to give it a slow read when I have time. I like your work so far!
Thanks! Take your time and share your opinion after reading.
I’ve read it more slowly now. I think it could use a few edit passes to get things condensed into fewer categories. I felt I was reading the same advice in multiple contexts.
The amount of bullshit was near zero, I really think you know what’s up. Sometimes, you left out basic “everybody knows” details, and I had to process for a moment to decide if it was because you were unaware or just for brevity. I concluded that you just wanted to write about the important stuff and not rehash old tips. That’s a good thing.
Be safe out there.
Hi thanks again! Can you expand what you mean by “it could use a few edit passes to get things condensed into fewer categories” and “I felt I was reading the same advice in multiple contexts”. Would love to fix it.
I read over it again just now. I don’t know wtf I was talking about… disregard that criticism. I was just searching for something productive to feedback, I guess. I think I’m just getting a general feel of disorganization that I can’t quite put my finger on. Perhaps you’ve been editing since I last read, and that is why I no longer feel that way?
BTW, do you follow Michael Bazzell’s work? He’s got several books that are very informative. It seems you may have read them or at least heard his podcast. If not, you’re in for a treat.
Hey, I just added table of contents, you can even look at github commits (https://github.com/whos-zycher/opsec-guide/commits/main/)
Ill check his work for sure!