id_rsa.pub
or id_dsa.pub
you have keys set up already, so you can skip the generating keys step (or delete these files with rm id*
and make new keys)./home/pi/.ssh/id_rsa
) by just hitting Enter
.Enter
, then type it again when prompted. Leave the field empty for no passphrase..ssh
directory:id_rsa
and id_rsa.pub
:id_rsa
file is your private key. Keep this on your computer.id_rsa.pub
file is your public key. This is what you share with machines you want to connect to. When the machine you try to connect to matches up your public and private key, it will allow you to connect.authorized_keys
file on the Pi, sending it over SSH:ssh-copy-id
is not available on your system, you can copy the file manually over SSH:ssh: connect to host <IP-ADDRESS> port 22: Connection refused
and you know the IP-ADDRESS
is correct, then you probably haven't enabled SSH on your Pi. Run sudo raspi-config
in the Pi's terminal window, enable SSH, and then try to copy the files again.ssh <USER>@<IP-ADDRESS>
and you should connect without a password prompt.ssh-agent
then execute the following command:rm ~/.ssh/id*
and follow the instructions again.scp
command (secure copy). See the SCP guide for more information.start.elf
, a firmwware blob for the VideoCore IV processor used byall Raspberry Pi models, was posted toredditby /u/fuck_the_mpeg_laon 03-03-2017:start.elf
(latest as of time of writing) results in the following diff:start.elf
, we can find the is_licensed
routineat address 0xEC96290
by jumping to the file offset given to us by xxd
beforehand. The relevant code sections are available insub_EC96290.asm and is_licensed.asm.0xEE86680
for MPEG-2 and 0xEE869E0
for VC-1)that point to the .bss
segment are checked to determine the return value ofis_licensed
. There are no other obvious references to these locations instart.elf
, so memory-breakpoint debugging (TBD) is probably needed.