001100 010010 to [email protected]English • edit-22 years agoIt's Open Source!lemmy.dbzer0.comimagemessage-square215fedilinkarrow-up11.82Karrow-down1139file-text
arrow-up11.68Karrow-down1imageIt's Open Source!lemmy.dbzer0.com001100 010010 to [email protected]English • edit-22 years agomessage-square215fedilinkfile-text
minus-squareEuphoricPenguinlinkfedilinkEnglish1•2 years agoYou can always brute force the SSH login and take a look around yourself. If you leave an apology.txt file in /home, I’m sure the admin won’t mind.
minus-squareDr. JenkemlinkfedilinkEnglish1•2 years agoLol, unlikely SSH is exposed to the net. You’ll probably need an RCE in the service to pop a shell.
minus-squareEuphoricPenguinlinkfedilinkEnglish1•edit-22 years agoThat’s not universally true, at least if you’re not on the same LAN. For example, most small-scale apps hosted on VPSs are typically configured with a public-facing SSH login.
You can always brute force the SSH login and take a look around yourself. If you leave an apology.txt file in /home, I’m sure the admin won’t mind.
Lol, unlikely SSH is exposed to the net. You’ll probably need an RCE in the service to pop a shell.
That’s not universally true, at least if you’re not on the same LAN. For example, most small-scale apps hosted on VPSs are typically configured with a public-facing SSH login.