linux4noobs

1356 readers

1 users here now

linux4noobs

Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.

Seeking Support?

Mention your Linux distro and relevant system details.
Describe what you've tried so far.
Share your solution even if you found it yourself.
Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
Properly format any scripts, code, logs, or error messages.
Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.

Community Rules

Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
Posts must be Linux oriented
Spam or affiliate links will not be tolerated.

founded 1 year ago

MODERATORS

PlutoParty@programming.dev

Using Wireshark to verify encryption (sh.itjust.works)

submitted 3 months ago by Ponziani@sh.itjust.works to c/linux4noobs@programming.dev

6 comments fedilink hide all child comments

I am trying to use wireshark to verify that my outgoing rsync is encrypted. I can easily see that the SSH protocol packets are reported as "Encrypted packet." The other packets being exchanged are TCP packets, I am not sure how to actually verify if these are encrypted, and if not, if they contain anything sensitive.

Should TCP be encrypted? Can they leak anything when facilitating the ssh connection? How can I tell?

all 7 comments

sorted by: hot top controversial new old

[–] yggdar@lemmy.world 8 points 3 months ago (1 children)

TCP is on a lower level than SSH, usually SSH uses TCP as its underlying transport layer. TCP as such is not encrypted, but it can of course be used to transport encrypted data.

Are those packages not part of the same SSH connection according to Wireshark?

[–] Ponziani@sh.itjust.works 2 points 3 months ago (1 children)

It looks like everything is in 1 stream, maybe that answers your question? I am capturing traffic only on port 22 briefly while the rsync is running to look at the packets

[–] yggdar@lemmy.world 3 points 3 months ago* (last edited 3 months ago) (1 children)

If the timestamps line up, maybe Wireshark just doesn't manage to understand the entire exchange. What could happen is that Wireshark sees the SSH handshake, and after that it might become just encrypted gibberish due to the encryption. In that case the SSH traffic could just show up as "some kind of TCP".

Do you see an SSH handshake, followed by random crap on the same ports?

(I'm not a Wireshark expert, just an IT guy trying to help!)

[–] Ponziani@sh.itjust.works 2 points 3 months ago (1 children)

Im a little knowledgeable with this stuff but i do not know how to see the "handshake" itself, but maybe this is synonymous with what i am doing:

Right click any of the packets (TCP or SSH) > Follow > TCP stream

From there i can see some info about the ssh protocol and connection, as well as the 2 devices communicating (Operating systems used) followed by random gibberish which is the encrypted data.

When I analyze the TCP packet "frames", they contain data including the motherboard manufacturer, but packets themselves look like its just gibberish.

Thanks by the way for trying to help me :)

[–] yggdar@lemmy.world 2 points 3 months ago (1 children)

Well, if

Wireshark identifies it as a single stream
Wireshark sees gibberish "TCP" and not an SSH connection
The gibberish comes after the SSH stuff that you could see (the stuff in there is going to be the handshake, my bad, that is a bit of a technical term)

Then we can be quite confident that your connection is indeed encrypted!

And of course, you're welcome!

[–] Ponziani@sh.itjust.works 2 points 3 months ago

Ok thank you!