S/KEY sequence?

[Barry Hamill]

Thanks again for the many responses.

Several people assumed wrongly that I hadn't rebooted, so I didn't try those suggestions. LGI_CALLOUTS (whatever that is) says current=1, default=0. If I'm feeling lucky, I may try that suggestion.

Multinet configure /access ; show server-access replies "?Not confirmed." That can't be good. I tried setting that to 127.0.0.1, but still got the "S/KEY sequence not found" thing. Grrr.

I changed the default-method to plaintext-passwords, and for obvious reasons, the s/key thing went away. I'm debating now how much more time to spend on this - any system is hackable, but this one is pretty invisible to the world beyond my WAN; no one is going to log into it except from behind my firewall or connected via VPN. Anyone got any strong feelings about plaintext passwords?