<div dir="ltr"><div><div>And since it is a rpi... you can just pop out the sdcard, and put in a different computer and see which ssh-key is in the second-partition at user-data/*/.ssh/authorized_keys if you are really curious (although since you are on windows, reading that partition which is ext4 might be more difficult). </div> </div></div><div class="gmail_extra"> <div class="gmail_quote">On Fri, Feb 3, 2017 at 9:25 AM, Luca Dionisi <<a href="mailto:luca.dionisi@gmail.com" target="_blank">luca.dionisi@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just a couple of hints. 1. Double check username. It might be different than that of the email you use to signon at Ubuntu. E.g. my mail is <a href="mailto:luca.dionisi@gmail.com">luca.dionisi@gmail.com</a> while user on my RPi is luca-dionisi. 2. Try flag "-v" with ssh. Check the id_rsa* files that it tries with. <div class="HOEnZb"><div class="h5"> On Fri, Feb 3, 2017 at 4:08 PM, George Gundry <<a href="mailto:george.gundry@4dml.com">george.gundry@4dml.com</a>> wrote: > I followed the instructions here: > <a href="https://developer.ubuntu.com/core/get-started/raspberry-pi-2-3" rel="noreferrer" target="_blank">https://developer.ubuntu.com/core/get-started/raspberry-pi-2-3</a> > > I have created a Ubuntu SSO account > > uploaded my SSH public key, > > used Win32DiskImager to burn the Ubuntu Core Pi3 image > ubuntu-core-16-pi3.img to an SD card, > > booted the Pi3 connected to Ethernet, > > correctly get the “Press Enter to Configure” message, > > pass Network Config, > > entered my SSO account, > > got the ”Contacting Store” message, > > got the success reply back from the store saying the key had been stored on > the Pi and I can use ssh <username>@<ip address> > > Try to connect to pi over ssh as instructed, private key auth fails … > > Things I have tried: > > Different terminal emulators – putty; Remote Terminal; TokenShell/MD; > command line ssh from another Pi; forcing use of specific private key with > -I option > > Different SSH key pairs – known good pair that we use elsewhere; new keygen > generated keys with passphrase; new keygen generated keys without passphrase > > Different Pi’s – Work and home > > Different Ubuntu SSO accounts – created a new account from scratch, same > result. > > In desperation, I tried to load 16.04 LTS, and this was successful so I am > confident the kit (Pi, SD card, network connection) is good. > > Nothing I have tried makes any difference, the private key is never accepted > by the Ubuntu Core device. > > I am keen to investigate migrating our IoT product from Raspbian Lite to > Core, but can’t seem to get beyond step one ! > > > > </div></div>> -- > Snapcraft mailing list > <a href="mailto:Snapcraft@lists.snapcraft.io">Snapcraft@lists.snapcraft.io</a> > Modify settings or unsubscribe at: > <a href="https://lists.ubuntu.com/mailman/listinfo/snapcraft" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snapcraft</a> > -- Snapcraft mailing list <a href="mailto:Snapcraft@lists.snapcraft.io">Snapcraft@lists.snapcraft.io</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snapcraft" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snapcraft</a> </blockquote></div> </div>