Is there a way to automate opening a bunch of frequently used SSH sessions all at once on a Linux based workstation? I'd like to type a single command and wind up with a single terminal window having three tabs.
Tab 1 would be labeled "web-logs" and would [upon connection] have a "tail -F" of my nginx logs.
Tab 2 would be labeled "mail-logs" and would [upon connection] have a "tail -F" of my postfix logs.
Tab 3 would be labeled "lily" and would have a typical interactive session to my minetest server.
I am currently using Asbru Connection Manager which works great, but I'd like to think I could do this with a simple terminal window. Am I wrong?
If you've ever looked at SSH server logs you know what I'm about to say: Any SSH server connected to the public Internet is getting bombarded by constant attempts to log in. Not just a few of them. A lot of them. Sometimes even dozens per second. And this problem is not going away; it is, in fact, getting worse. And attackers' behavior is changing.
The graph attached to this post shows the number of attempted SSH logins per day to one of @cloudlab s clusters over a four-year period. It peaks at about 3.4 million login attempts per day.
This is part of a study we did on our production system, using logs of more than 640 million login attempts, covering more than 1,500 hosts on our side and observing more than 840 thousand incoming IP addresses.
A paper presenting our analysis and a new, highly effective means to block SSH brute force attacks ("Where The Wild Things Are: Brute-Force SSH Attacks In The Wild And How To Stop Them") will be presented next week at #NSDI24 by @sachindhke . The full paper is at https://www.flux.utah.edu/paper/singh-nsdi24
Wir sind dieses Wochenende nur durch unglaubliches Glück und extrem knapp an wohl einer der grössten Katastrophen rund um die globale IT-Sicherheit vorbeigeschrammt.
Phuh! Doch — was ist eigentlich passiert? Wie konnte das überhaupt geschehen? Und was können (und müssen) wir tun, um dies zukünftig zu vermeiden?
Before executing important commands and scripts over #SSH, use #screen in case of disconnect. If your connection drops or you close the terminal, you can SSH back in and enter screen -r to recover from where you left off. Being reunited with that hanging command prompt will be a relief! #tuesdaytip#gnu#linux#cli#admin
Edit: the solution was to add the following configuration to "%USERPROFILE%.cargo\config":
[net]
git-fetch-with-cli = true
Original post:
Has anyone been able to get SSH working on Windows where your #rust dependency is a private repo?
Ex:
(Cargo.toml)
hello_world = { git = "ssh://git@github.com-HelloWorld/AustinHellerRepo/HelloWorld.git" }
You may notice that the host is "github.com-HelloWorld" and that's because that's what works on my Linux machine (via the ".ssh/config" file setup). I want the same Cargo.toml line to work on my Windows machine.
I keep getting "unknown host" errors when I "cargo build" but using git in the repo works just fine.
I would hope that it's just a matter of adding the correct host somewhere. Any help would be appreciated. #ssh#windows
With #tailscale#ssh i can use every #nix buildon my machine with my phone , without installing a single thing on phone but ssh utils
iirc it wasnt the same with plain ssh
We've released #PuTTY version 0.81. This is a SECURITY UPDATE, fixing a #vulnerability in ECDSA signing for #SSH.
If you've used a 521-bit ECDSA key (ecdsa-sha2-nistp521) with any previous version of PuTTY, consider it compromised! Generate a new key pair, and remove the old public key from authorized_keys files.
Other key types are not affected, even other sizes of ECDSA. In particular, Ed25519 is fine.
Am I missing out by using SSH tunnelling to expose an application on my laptop to the Internet, for development purposes? #SSH#Networking#WebDevelopment#WebDev
SSH aliases are so awesome! I learned about this very recently. I have something like the following in my .ssh/config file for every server I SSH into:
Host servername
HostName <domain_or_ip_address>
User <my_username>
IdentityFile <path_to_my_private_key>
, and it lets me just go like, ssh servername, enter my passphrase, and be logged in. #Linux#ssh
Wow, @linux does actually improve efficiency over time...
I just compiled a minimal kernel 6.5 for OS/1337 targeting #i486 instead of #i686 and the resulting binary is even 10kB smaller than the one for 6.4.12...
For real: That's awesome cuz it allows me to make the #Floppy version for #486SX a reality and still have #Toybox & #dropbear as #SSH client in it...
Cudos to @torvalds and the maintainers for that:
They really did cleanup the codebase and made it #smol|ler!
Do you people use #emacs to work on #remote machines?
I do most of my work on a remote machine and I usually run emacs in #screen via #SSH.
However, lately I'd like to try something like #tramp mode (#trampmode)
I'm curious if anybody has experiences to share and/or suggestions.
You can sign your git commits with SSH keys. GitHub uses the public key for both showing the "verified" badge, and also allowing pushes. What if I don't want to allow pushes with that key anymore, but don't want to invalidate past signatures? #git#GitHub#ssh