ssh error
Hello, I recently upgraded from 5.2.1 to 5.3 and I ran into a problem that i can't seem to solve... I want to ssh from a local computer to my firewall running sshd. This used to work without any errors in the past but after the upgrade I get the following errors on both comps: Error on ssh computer: Warning: no access to tty (Bad file descriptor). Thus no job control in this shell. (This computer then locks the shell completely) Error on sshd computer (amadeus): Dec 1 2:16:17 amadeus sshd[11565]: error: openpty: No such file or directory Dec 1 2:16:17 amadeus sshd[11568]: error: session_pty_req: session 0 alloc failed (I've tried to ssh from the firewall comp to itself resulting in the same errors) The login process goes well and there are processes on the firewall showing that there is a connection. There's just no shell... I have device pty in my kernel. It used to work fine in 5.2.1 Thanks, Arno ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh error
Error on ssh computer: Warning: no access to tty (Bad file descriptor). Thus no job control in this shell. (This computer then locks the shell completely) Error on sshd computer (amadeus): Dec 1 2:16:17 amadeus sshd[11565]: error: openpty: No such file or directory Dec 1 2:16:17 amadeus sshd[11568]: error: session_pty_req: session 0 alloc failed (I've tried to ssh from the firewall comp to itself resulting in the same errors) Did you run mergemaster and allow it to do a MAKEDEV? -- Andy Harrison ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh error
On 02 dec 2004, at 14:45, Andy Harrison wrote: Error on ssh computer: Warning: no access to tty (Bad file descriptor). Thus no job control in this shell. (This computer then locks the shell completely) Error on sshd computer (amadeus): Dec 1 2:16:17 amadeus sshd[11565]: error: openpty: No such file or directory Dec 1 2:16:17 amadeus sshd[11568]: error: session_pty_req: session 0 alloc failed (I've tried to ssh from the firewall comp to itself resulting in the same errors) Did you run mergemaster and allow it to do a MAKEDEV? Isn't MAKEDEV only for systems prior to 5? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ssh error PRNG is not seeded
Hi, I've chosen do want to login via ssh=NO (can't exactly remember but it was a similar question) during setup of freebsd5.2, now, when I try to use scp or ssh client I get the following error message: PRNG is not seeded How can I solve the problem?! Many thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh error PRNG is not seeded
On Wed, Feb 04, 2004 at 05:04:24PM +0100, Didier WIROTH wrote: Hi, I've chosen do want to login via ssh=NO (can't exactly remember but it was a similar question) during setup of freebsd5.2, now, when I try to use scp or ssh client I get the following error message: PRNG is not seeded How can I solve the problem?! Have you built a custom kernel? You may have removed support for the (effectively mandatory) 'random' device; add it back or kldload the module. Kris pgp0.pgp Description: PGP signature
Re: ssh error PRNG is not seeded
On Wed, 4 Feb 2004 10:35:20 -0800 Kris Kennaway [EMAIL PROTECTED] wrote: On Wed, Feb 04, 2004 at 05:04:24PM +0100, Didier WIROTH wrote: Hi, I've chosen do want to login via ssh=NO (can't exactly remember but it was a similar question) during setup of freebsd5.2, now, when I try to use scp or ssh client I get the following error message: PRNG is not seeded How can I solve the problem?! Have you built a custom kernel? You may have removed support for the (effectively mandatory) 'random' device; add it back or kldload the module. Hm, I remember having this issue a few days ago and it magically disappeared, if memory serves; if not I had a slightly (few deay) kernel/world out of sync. But the kernel had random. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh error PRNG is not seeded
Hi, thanks for answering. I think, I've found the problem, I don't have a /dev/random device. I built a custom kernel and omitted device random, I've rebuilt the kernel with this device now, I will test this tomorrow and see it helps. Thanks Didier Messages d´origine De: Ion-Mihai Tetcu [EMAIL PROTECTED] Date: mercredi, février 4, 2004 8:02 pm Objet: Re: ssh error PRNG is not seeded On Wed, 4 Feb 2004 10:35:20 -0800 Kris Kennaway [EMAIL PROTECTED] wrote: On Wed, Feb 04, 2004 at 05:04:24PM +0100, Didier WIROTH wrote: Hi, I've chosen do want to login via ssh=NO (can't exactly remember but it was a similar question) during setup of freebsd5.2, now, when I try to use scp or ssh client I get the following error message: PRNG is not seeded How can I solve the problem?! Have you built a custom kernel? You may have removed support for the (effectively mandatory) 'random' device; add it back or kldload the module. Hm, I remember having this issue a few days ago and it magically disappeared, if memory serves; if not I had a slightly (few deay) kernel/world out of sync. But the kernel had random. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
