On Tue, Oct 20, 2015 at 12:28 AM, emigrant <[email protected]> wrote: > The same problem, src via cvs.
Failed at a different step, with a different error is the same problem? NOTE: Please describe EXACTLY what you did in the lead up to an error. If you don't, then people will have to guess or reconstruct it from what you do provide. That requires more of their time than it would have taken if you just described what you did, and you should treat other people's time as at least as valuable as your own. > sshd patch001 > > (…) > cc -o sshd sshd.o auth-rhosts.o auth-passwd.o sshpty.o sshlogin.o servconf.o > serverloop.o auth.o auth2.o auth-options.o session.o auth-chall.o > auth2-chall.o groupaccess.o auth-bsdauth.o auth2-hostbased.o auth2-kbdint.o > auth2-none.o auth2-passwd.o auth2-pubkey.o monitor_mm.o monitor.o > monitor_wrap.o sftp-server.o sftp-common.o roaming_common.o roaming_serv.o > sandbox-systrace.o -L/usr/src/usr.bin/ssh/sshd/../lib/obj -lssh -lutil > -L/usr/src/usr.bin/ssh/sshd/../lib/obj -lssh -lutil -lcrypto -lutil -lz > sshd.o: In function `main': > sshd.c:(.text+0x4ae4): undefined reference to `do_authentication' You failed to mention, and indeed cut out all the compilation lines that would have shown it, that you decided to enable SSHv1 support. Indeed, you build sshd, then decided you wanted SSHv1 support and enabled it but didn't do "make clean" from /usr/src/usr.bin/ssh/ If you change ssh compilation options, you must recompile *all* of ssh, including the library. You *do* know that sshv1 is even less secure than the 1024 bit primes that people have been panicing about in the last week or so, right? Philip Guenther
