SSH pub key auth not working…
-
For every builder run, only one NanoBSD size is built. So depending on the size you need, it could take up to four builder runs for the proper size to be built.
-
Good to know ;)
Waiting for the 4g version. Today a 2g was released, so I guess tomorrow will be my time ;)
-
Still there….
With snap of 31st....
How long does this usually take?
Also the dashboard patch isn't in this release...
-
You'll need to edit and save admin to rewrite the authorized keys, what I fixed was removing some old code from 1.2.x that was deleting the keys where it shouldn't have been.
-
Thanks cmb! That did the trick ;) Happy New Year's Eve, now shutdown your computer ;-)
Cheers from Germany!
-
Hi cmb. I just updated to the latest snap and I had to edit and save admin again. After that it works. So another bug?
-
With every snap I need to do this again. Can someone please fix this?
-
Every firmware update it switches to a new partition, which will then not have your keys present. It probably needs a boot-time function to sync the keys.
-
Well I thought that all the config including such an important file would be taken over. This is a serious issue when you do a remote upgrade ;-)
-
I had thought the existing ssh keys were backed up and carried over, but that may not be the case. I haven't tried to do key-based auth on my ALIX running 2.0 yet.
-
On 1.2.3 they were…
-
I see what I was thinking of. The ssh host keys are backed up and restored on reboot/upgrade, but it may be missing some logic to handle the user keys.
-
Problem is still there with todays build :-(
Is this still an open ticket? This thing is huge! Think about remote updates….Should be easy to fix?!
-
Only appears to affect embedded, I've never seen it on full. Ticket opened.
http://redmine.pfsense.org/issues/show/317
