You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 14, 2023. It is now read-only.
boot with sdcard and wait for cloud-init to finish
there is no /home/pirate/.ssh/authorized_keys
there is /root/.ssh/authorized_keys with invalid content:
no-port-forwarding,no-agent-forwarding,no-X11-forwarding,command="echo 'Please login as the user \"NONE\" rather than the user \"root\".';echo;sleep 10" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPDz/lROfK9tdARDHTMPH/vU6MmkpcAfMNViaigHyqPy verglor
The text was updated successfully, but these errors were encountered:
#cloud-config# vim: syntax=yaml## Set your hostname here, the manage_etc_hosts will update the hosts file entries as wellhostname: black-pearlmanage_etc_hosts: true# don't write debian.org into apt mirrorsapt_preserve_sources_list: true# You could modify this for your own user informationusers:
- name: stefan # use any user name you likeprimary-group: usersshell: /bin/bashsudo: ALL=(ALL) NOPASSWD:ALLgroups: users,docker,adm,dialout,audiolugdev,netdev,videossh-import-id: Nonelock_passwd: truessh-authorized-keys:
- ssh-rsa AAAA.....NN stefan
Similar issue (not specific to SSH so I can create a separate issue if required) where user-data appears to be completely ignored. Something as simple as changing the hostname parameter (either before first boot with a fresh user-data file, or post-first-boot by modifying the present user-data file and rebooting) doesn't take.
Edit: Using 1.12.3 on RPi, tried on both Pi2 and Pi3
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to reproduce:
user-data
on boot partition:cloud-init
to finish/home/pirate/.ssh/authorized_keys
/root/.ssh/authorized_keys
with invalid content:The text was updated successfully, but these errors were encountered: