Simple ssh without password

I have to ssh into a server where the source and destination .ssh folder was empty (but ssh was installed)

Here are the steps needed (using rsa)

locally generate and get the content of the key (line starting with ssh-rsa...)

$ ssh-keygen -t rsa
$ cat ~/.ssh/id_rsa.pub 
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDb...rGSQxR8t xxx@xxxxxx

remotely

$ cd ~/.ssh 
$ touch authorized_keys
$ chmod 600 authorized_keys
and then to append the content of the public key to the list of authorized key

$ vi authorized_keys

In one command:

$ cat .ssh/id_rsa.pub | ssh user@host 'cat >> .ssh/authorized_keys'

Popular posts from this blog

Fixing "DerInputStream.getLength(): lengthTag=109, too big" in Android Studio

This happened to me in Android Studio after AndroidX migration and using the new testing framework. Even deleting the existing ~/.android/debug.keystore was failing for me The solution was regenerate it manually (accept all questions as empty and say yes at the last one) $ keytool -genkey -v -keystore debug.keystore -storepass android -alias androiddebugkey -keypass android -keyalg RSA -keysize 2048 -validity 10000 And copy it $ rm ~/.android/debug.keystore $ cp debug.keystore ~/.android/debug.keystore
Read more

Simple Samba setup on Lubuntu

I have a simple lubuntu server where I setup a ssh server. While it is sufficient to access a driver/folder from another linux machine using sftp, it is a pain from Windows & Mac, so unfortunately, samba is still needed here. For simplicity I needed only one samba user that I could map to a single user on my lubuntu machine Following the various tutorial I ended up doing this with simple commands Install samba $ sudo apt-get install samba Add myuser to the samba $ sudo smbpasswd -a myuser Export the drive I needed (no guest user) $ sudo vi /etc/samba/smb.conf to add the following export (no real option needed here) [files] path = /media/music/files writeable = yes save and Restart samba $ sudo service smbd restart
Read more

Solving: insufficient permissions for device: user in plugdev group; are your udev rules wrong

This happens on Ubuntu almost each time I add a new device: Check that your are in plugdev group $ id uid=1000(alex) gid=1000(alex) groups=1000(alex),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),127(kvm),129(libvirt),134(chrome-remote-desktop) If not (i.e. plugdev not displayed), add it: $ sudo usermod -aG plugdev alex If you get 'insufficient permissions for device: user in plugdev group; are your udev rules wrong' when trying to debug, you'll need to add your device: First i used lsusb to find my vendor id (here I guess google) $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub ... Bus 001 Device 025: ID 18d1:4ee7 Google Inc. .. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub .. Bus 001 Device 020: ID 05e0:2106 Symbol Technologies USB2.1 Hub As suggested in https://developer.android.com/studio/run/device.html the solution was to sudo gedit /etc/udev/rules.d/51-android.rules Add th...
Read more