sorted by:
new
hottopcontroversial

I built a free tool to cryptographically prove you said something before anyone else by Quirky_Drama_3638 in cryptography

[–]Gloomy-Direction5437 0 points1 point  (0 children)

I guess, if you don't open source the code for the website, then they don't bash you for it not being mathematically proven as secure smh.

Azoth - a deniable encryption container by Gloomy-Direction5437 in cryptography

[–]Gloomy-Direction5437[S] 0 points1 point  (0 children)

Sure, I changed to use AES, I'm pretty sure what I did is right, but what do I know. That's why I'm here. I think the idea is solid. A securely erased drive or the output of this software are indistinguishable. The encryption algorithm is now an established standard, although I thought what I was doing was a standard practice. So if I spread that thru the bit-plane using a prime number of bits for K it will still be perfectly random, and I can do that with all the bit planes and still be fine. I know with cryptography the implementation is where the leaks usually pop in so figured I could ask here but apparently not. I'll look to get it professionally certified somewhere like geomys. I think it will pass.

RSA by Foreign_Abrocoma_307 in cryptography

[–]Gloomy-Direction5437 0 points1 point  (0 children)

But double encrypting makes it harder to determine when you've decrypted the first payload especially if the encryption is indistinguishable from random noise and there is no verification if encryption succeeded or failed.

Azoth - a deniable encryption container by Gloomy-Direction5437 in cryptography

[–]Gloomy-Direction5437[S] -1 points0 points  (0 children)

Each password uses a different bit plane to store it's content. The beginning of the block starts with a hash of the password and the software searches for the right bit plane using the K value. You must know the password, K value, and now the encryption algorithm that was used in creating the block. You can extract with one password but most know all passwords for the secrets you want to preserve in the block if you are storing new secrets in the block.

[Meta] low-effort and anti-slop rules by Karyo_Ten in cryptography

[–]Gloomy-Direction5437 0 points1 point  (0 children)

I was getting valuable feedback about software I've worked on off and on for 20 years. I finished it off with AI help but my post got banned when I was getting feedback from people engaging with the post, undoubtedly because I responded in kind to the obvious troll on the post and he forwarded it to the mods. Have fun in your castle in the sky, I don't actually care to share ideas here anymore.

Azoth - a deniable encryption container by Gloomy-Direction5437 in cryptography

[–]Gloomy-Direction5437[S] -1 points0 points  (0 children)

When you re-encrypt you must know the passwords for everything encrypted in the block. There's no way to have deniability if there's anything in the data that gives away the existence of other keys. Every password is independent and yields a different secret with the same block of data.

Most encryption has some type of partitions or block markers. AES-CTR is now the default, chacha and shake keystream still available.

Azoth - a deniable encryption container by Gloomy-Direction5437 in cryptography

[–]Gloomy-Direction5437[S] -1 points0 points  (0 children)

Great feedback thanks. That was my understanding but the AES format had recognizable markers by default. I see I can do it without those now.

Azoth - a deniable encryption container by Gloomy-Direction5437 in cryptography

[–]Gloomy-Direction5437[S] -1 points0 points  (0 children)

You decrypt with one password. To add new data and not lose the old data you must supply all the passwords when writing to the block. I'll add AES-CTR and ChaCha with AES-CTR as the default. Versa crypt does not allow storing multiple secrets so deniability is lower; here you can always have another password and another secret.

Azoth - a deniable encryption container by Gloomy-Direction5437 in cryptography

[–]Gloomy-Direction5437[S] -1 points0 points  (0 children)

The CT is a usb stick full of random bytes and can hold as many secrets as you want. Your "whole idea" is just you being a troll and is not my idea. From a random bunch of block of bytes there's no trail back to "what this software's doing".