RommieDroid

joined 5 days ago
[–] RommieDroid@programming.dev 5 points 9 hours ago

Why would you upgrade, it's worse.

[–] RommieDroid@programming.dev 1 points 19 hours ago

If they go public I'm changing distros

[–] RommieDroid@programming.dev 2 points 19 hours ago

The cutting edge/novel techniques was what I was looking for, this is really cool. I'll look into it more.

[–] RommieDroid@programming.dev 5 points 20 hours ago (4 children)

Why don't we have an open source anti-cheat protocol that is a demon-level service. Everyone hates kernel anti-cheat, but only because they're close source, so why don't we have one that's open source. Seems like a simple solution.

[–] RommieDroid@programming.dev 3 points 20 hours ago (3 children)

I still use VirtualBox with Windows 10 to launch all the Affinity products because GIMP is so bad. And for browser fingerprint protection, e.g. chrome (ungoogled) on windows, because no browser fakes it. Not mullvad, Tor or Brave.

[–] RommieDroid@programming.dev 1 points 20 hours ago

Yeah, it's much harder to completely hide the fact you're using encryption.

[–] RommieDroid@programming.dev 9 points 21 hours ago

Oof 😅 0.59 nanoseconds. I dang messed up. This would be a good project for students to identify the weaknesses. Like the Theprimeagen says the problem with the tutorials is they're neatly packaged, refined end products and you miss out on all the learning and debugging. You sound like you know what you're talking about and the 1-byte block size is a huge mistake. I think I'll do some more research into the different algorithms. Thanks for having a look, and weighing in.

[–] RommieDroid@programming.dev 3 points 21 hours ago (3 children)

I hear you, XOR is bad 💀 I should just use the crypto library.

[–] RommieDroid@programming.dev 5 points 21 hours ago (1 children)

Hey, thanks for the thoughtful breakdown. I probably should label it: warning random IT grad project. I mistakenly believed I could make something that was good, well it's a lot more difficult. You're right that this doesn’t provide the kind of plausible deniability I initially hoped for, the decoys were just a workaround, because I couldn't find the type of algorithm I wanted.

The query parameters are masked with HTTPS so you're not revealing any extra data, it would just look like any other redirect if you were packet sniffing. And when visiting the destination links, your normal OPSEC still applies, like changing your DNS, using a VPN, etc. I was just seeing if this project would find some sort of use, but I only spend two days on it and it was a fun learning experience.

 

~Update~

You can now encrypt plain text, so anything you want. With this, you can send sensitive information over insecure channels or share publicly with real plausible deniability. (below 2000 characters works without issue)

~Changes~

I rebuilt the system with a different encryption design, and address many of the flaws pointed out in V1.

I really wanted any password to always decrypt so you never know if you are right. I found the XOR algorithm that does this, but there is an entropy problem, where an incorrect password will almost always output non-common characters, I attempted to solve this at its core by diving into the math and some research papers but got nowhere, as it seemed to be almost impossible.

I tried finding an algorithm that would give me perfect plausible deniability, so if you shared a link X with a password you could use a different password and get Y, saying you never intended to share X. It doesn't exist 😢 I came up with a workaround by adding decoys which are mutable XOR ciphers joined, it allows you to set what other data is included, so you can tailor your alibi.

Here is the demo link. There are three memes you can find

Password: test1, test2, test3

~Safety~

It should be safe to share data encrypted with this method, I did some basic brute force tests and did not find any shortcuts, I have a rough estimate of a billion years on a server farm for a 12digit password.

~Considerations~

@calcopiritus@lemmy.world said:

"There’s 2 secrets here: the link and the password. And to share it with someone you need to share 2 secrets: the locked link and the password."

A strong password is almost impossible to crack, but you can use a popular text link tool like pastebin with expiry to mask the encrypted data. As for eliminating the password, I have considered using the site as the 'shared secret' so you share just the cipher, and if you know the URL you can paste it in, and it would be encrypted/decrypted with a derived key the site stored.

[–] RommieDroid@programming.dev 4 points 3 days ago (1 children)

fr, windows hides the file type by default.

[–] RommieDroid@programming.dev 8 points 3 days ago

Om, AppImage is portable exe. Has it's uses.

[–] RommieDroid@programming.dev 3 points 3 days ago (1 children)

dpkg doesn't? I sometimes use apt install command but didn't think it mattered if the deb package was configured right.

 

I know it's not that hard $ dpkg -i but opening the terminal gives normies an aneurysm and thanks to the crazy gatekeeping gen alpha doesn't know what a file type is now.

I use Ubuntu btw. Personally, the App store's on Linux confused me a ton, setting up Flatpak and some other package repositories. I much preferred the windows way, shocker, with just downloading and double-click the exe file.

Do I have to make a pull request myself to get this done, or what is the debate on this?

 

I made this tool so you can share 'locked' links safely & anonymously with a password. It gives you plausible deniability and crowd blending when sharing privates links.🔒

https://qrc.site/anon (open sauce) 🦑

view more: next ›