Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi All,
I've funplugged by DNS-323 and all this while been logging in through ssh. I formatted my notebook recently and my rsa key has change. Due to this, I'm unable to access through ssh/sftp anymore.
Would like to know if anyone has a solution to this problem. If I can run the telnet script, I should be able to change the authorized_keys to the new ones. However, I'm out of ideas on how to get this script running.
I taught of create an add-on pack that runs the telnet script or replace the authorized_keys totally but I couldn't find a way to create the binary file.
If on there's a crontab menus on the web GUI, this can also be done.
Hope to hear solutions from you guys, thanks!
Offline
Reactivate telnet: http://dns323.kood.org/forum/p19176-Tod … tml#p19176
Offline
Most ssh clients can be set up to fall back to password authentication if the key authentication fails. If you are using putty, you might look at that in the config panels. This would work if there is a password on the account and you remember it.
I suppose it is also possible that you configured the sshd daemon on the server (the 323) to accept only key authentication, in which case you are stuck without the keys in place.
After you generate your public/private pair on the reformatted laptop, you could try copying the public key to the 323 disk via a Windows share or whatever. Then, assuming that you can edit your fun_plug file via the share or ftp, add a line to the fun_plug to append the public key file to the authorized key file. If you put the public key file in the "Volume_1" share, or the top-level dir of the data disk, then something like:
cat /mnt/HD_a2/public_key >> /home/root/.ssh/authorized_keys
You would have to change the filespec on the right to wherever the authorized_key file is. And you'll have to recall exactly where that is. Recall that /home/root does not persist across a reboot, so you probably have put the keys someplace else that persists. If you have a way of making a share to access this persistent location, you might be able to add the new public key directly via the share and not have to hack it with a fun_plug.
Offline