Conversation

Notices

1. Embed this notice
   Gabriel (gabriel@fedi.libresolutions.network)'s status on Thursday, 16-Oct-2025 11:27:20 JST Gabriel

   • Zergling_man

   @Zergling_man
   Can't get hacked if attackers can't SSH in!
   Brilliant! I'm sure this has no flaws at all.

   • ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Thursday, 16-Oct-2025 11:27:19 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to

     • Zergling_man
     @gabriel @Zergling_man This is why i use a vpn
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Thursday, 16-Oct-2025 12:13:24 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to

     • Zergling_man
     @Zergling_man @gabriel Thats why you use a irregular port / you also can do tcp tunneling to hide vpn (very rarely do you need to do this though)
   • Embed this notice
     Zergling_man (zergling_man@sacred.harpy.faith)'s status on Thursday, 16-Oct-2025 12:13:25 JST Zergling_man

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @dcc @gabriel They're probably blocked too.
   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Thursday, 16-Oct-2025 20:14:42 JST 翠星石

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     • Zergling_man
     @Zergling_man @dcc @gabriel >It's *outbound* 22.
     Outbound TCP chooses a random output - port 22 is only the destination port.
     
     ssh can be screwed with by dropping packets with port 22 as the destination port (as well as any other program that uses 22), or via deep packet inspection.