Privacy Guides
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
- We prefer posting about open-source software whenever possible.
- This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
- No soliciting engagement: Don't ask for upvotes, follows, etc.
- Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
- Be civil, no violence, hate speech. Assume people here are posting in good faith.
- Don't repost topics which have already been covered here.
- News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
- Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
- No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
- No misinformation: Extraordinary claims must be matched with evidence.
- Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
- General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
Additional Resources:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List
view the rest of the comments
I rolled my own, actually. I don't store any passwords (even encrypted). Instead, I just append the site name to my base password (which is in my head), hash it, and base-52 it. (I also start each password with the same uppercase letter, lowercase letter, punctuation mark, just to ensure it gets past any bullshit filters)
I like that there's nothing that can be leaked (except what's in my head) and nothing to be lost and nothing to back up.
Can you please elaborate on each step. I'm not sure on the hash and base52 - do you use a program you're written to do that for you? A simple example would be fantastic.
Yeah I wrote the code for it. It's simple enough that I could write it again if needed.
By "hash" I mean SHA256 (though if I were to do it all again, I would probably use a different hash algorithm these days, but whatever, good enough). "base52" means turning the SHA256 binary code into a sequence of letters/digits. That part I wrote, too, but it's quite straightforward.
quiet similar to what Masterpasswordapp does!
That's ingenious.
Can you elaborate on a detail for me?
I understood everything up to "base-52 it."
I understand how converting base-10 to base-52 works, but that doesn't include alphabetical characters. What are you converting from? Are you numbering A=1, B=2, C=3...?
Sorry I just realized I should have said base 62. That's all the letters and numbers, plus digits, too.
The hashing step gives you a binary sequence, so you're actually converting from base 2, not from base 10. You treat the result of the hash as a giant binary integer and then repeatedly divide by 62, keeping track of the remainder. 0 = 0, 1 = 1, ..., 9 = 9, 10 = a, 11 = b, ..., 36 = z, 37 = A, 38 = B ..., 61 = Z