Note to self:
Install the Open-ssh optional Windows feature
Create the keys using ssh-keygen Upload the pub key to the Linux server:
type $env:USERPROFILE\.ssh\id_rsa.pub | ssh {IP-ADDRESS-OR-FQDN} "cat >> .ssh/authorized_keys"
Note to self:
Install the Open-ssh optional Windows feature
Create the keys using ssh-keygen Upload the pub key to the Linux server:
type $env:USERPROFILE\.ssh\id_rsa.pub | ssh {IP-ADDRESS-OR-FQDN} "cat >> .ssh/authorized_keys"
If the old Cisco ASA 5505 won’t boot, you need the Cisco console cable You can then use ROMMON to figure
Not really any good reason, unless you have a really large org or some policy preventing this. There have been some
When adding newer domain Controllers to a MS network, we might be using the old FRS and we have to upgrade