search for: stopspazzing

I would like to suggest adding a fallback in the event that somehow the sshd_config port number is invalid. Example: Port != (1<= or >=65535) By default fall by to port 22, and spit out an error. Same would go for if the new port is already in use, fall back to port 22 and spit out an error. Why is this a good idea? Would be a good idea because people are human and make mistakes, and you

...l partitions" patch. The following patch broke the recovery console hack: chain.c32: add option to set hidden sectors; load boot sector for NTLDR http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=commit;h=033fb123375ce6af905dcb2408fa0df74960e066 You can download a small image: http://ubcd.stopspazzing.com/downloads/cmdcons.img.gz You can test it in qemu: $ qemu -boot c -hda cmdcons.img syslinux.cfg file: UI menu.c32 LABEL 1 MENU LABEL Recovery console (RC) original patch (working) COM32 chain_g.c32 APPEND cmldr=/cmldr LABEL 2 MENU LABEL Recovery console (for fixing chain.c32 3.86-pr...

...u fixed the problem and selected a valid non-standard port." Is there any reason something like this isn't implemented already? Could it be implemented? On Thu, Jul 30, 2015 at 2:02 PM Ron Frederick <ronf at timeheart.net> wrote: > On Jul 30, 2015, at 1:30 PM, Stop Spazzing <stopspazzing at gmail.com> wrote: > > I would like to suggest adding a fallback in the event that somehow the > sshd_config port number is invalid. > > Example: > Port != (1<= or >=65535) > > By default fall by to port 22, and spit out an error. Same would go for if > the ne...