digitalFatteh 10 points 8 months ago

This just amazes me. Back when I was a kid I felt like BBS and newgroups were the tits. But this, just wow, well done keep up the crazy good work people. You are most certainly the future of us.

path: 0 22300363, hotness: undefined, score: 10, children: 0

eleijeep 7 points 8 months ago

Hi, could you explain how key exchange works and why you chose AES-256 in CBC mode?

save

path: 0 22301092, hotness: undefined, score: 7, children: 2

hereforawhile 5 points 8 months ago

You will need to establish a shared secret in person in advanced or over a trusted channel out of band.

You can configure your preferred cipher in the menu. Currently aesgcm is not included because it will require additional packages. `openssl enc' is not compatible with aesgcm due to to complexities in handling the authentication tag. I do plan on integrating this in the future however.

I think It's important to note this later of encryption is completely redundant with Tor integration. We are already e2ee encrypted with without openssl encryption. I just saw no reason not to include it as overhead is minimal.

save

path: 0 22301092 22302116, hotness: undefined, score: 5, children: 0

KeenFlame 0 points 8 months ago

Here is the key
(Optional) Thank you

save

path: 0 22301092 22301177, hotness: undefined, score: 0, children: 0

msspwn 6 points 8 months ago

Extreamly cool. But why tor and not i2p? Could using a non tor framework also work?(perhaps ssh tunnels)

save

path: 0 22300167, hotness: undefined, score: 6, children: 7

hereforawhile 9 points 8 months ago

With some work we should theoretically be able to configure any networking pipe. I like Tor for it's large distributed userbase/built in plug and play circumship transports and reliability is the short answer. It passes simple text encoded audio which should make it really easy to plug n play other networks. Also, I'm using open SSL as an additional encryption layer, it should be possible to configure any other encryption primatives you want easily. It doesn't have to use this library. It's just the one I chose.

save

path: 0 22300167 22300304, hotness: undefined, score: 9, children: 3

digitalFatteh 2 points 8 months ago

Is there a limit to the size of what could be sent or could someone maliciously record something capable of grinding the system to a halt ?

save

path: 0 22300167 22300304 22300417, hotness: undefined, score: 2, children: 2

hereforawhile 3 points 8 months ago

I haven't tried to break that yet, but I should find out the limits. I have sent pretty lengthy payloads while on 6kbs encoding quality with no issues. I know we can send aleast 60 second

save

path: 0 22300167 22300304 22300417 22300550, hotness: undefined, score: 3, children: 1

digitalFatteh 3 points 8 months ago

Just thinking on Government actor point of view. Sticking a Concerto down the system.

But I imagine today’s internet is pretty malleable to that sort of thing. I’d hope. I’m super new to the onion side of things having traded for convenience and now relearning some of the new old ‘stuff’. MeshCore and Meshtastic being another mind blowing but exciting doohickey to me.

save

path: 0 22300167 22300304 22300417 22300550 22300962, hotness: undefined, score: 3, children: 0

phase 1 point 8 months ago

It's socat. It could be whatever stdin/out (socat, netcat, ssh, ip, ipsec, wireguard, ...).

save

path: 0 22300167 22304104, hotness: undefined, score: 1, children: 0

quick_snail 1 point 8 months ago

I'm glad you chose Tor and not i2p.

save

path: 0 22300167 22303456, hotness: undefined, score: 1, children: 1

chortle_tortle 2 points 8 months ago

What are your takes on the two, and why do you prefer Tor?

save

path: 0 22300167 22303456 22304566, hotness: undefined, score: 2, children: 0

rezz 5 points 8 months ago

Now this is sick.

save

path: 0 22301110, hotness: undefined, score: 5, children: 0