Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
I just upgraded a number of packages (including openssh) and found myself locked out of funplug.
It took me a while to realize that the cause was that the upgraded openssh package overwrote /ffp/start/sshd.sh, thereby changing it's mode back to 644.
So, would it make sense to add some logic to funpkg to preserve the executability state of files in /ffp/start when doing upgrades?
Offline
puterboy wrote:
So, would it make sense to add some logic to funpkg to preserve the executability state of files in /ffp/start when doing upgrades?
Yes, it's on my todo-list. For critical stuff, like ssh or telnet, you can also add chmod to /ffp/etc/fun_plug.local.
Offline
That's a good idea - I will do so
Offline
Another problem that I just discovered inadvertently is that upgrading ffp-base (or busybox) leaves telnet on in the default no password required state -- which means that anyone has automatic root access to telnet even if they think that they had shut off the service or commented out the line:
telnetd_flags="-l /ffp/bin/sh"
Maybe it would be best to at least not have the default be an open root access telnet in the upgraded packages.
Again, I know that I can "solve" this (temporarily) using fun_plug.local...
Offline
puterboy wrote:
Maybe it would be best to at least not have the default be an open root access telnet in the upgraded packages.
Again, I know that I can "solve" this (temporarily) using fun_plug.local...
Yes, and the solution is to not overwrite telnetd.sh on package upgrade. Not overwriting it will also preserve the file permission bits.
Offline
Pages: 1