No luck, I'm afraid. In fact, it appears Dropbear ignores the log message priority. I will try creating a pcap file next.
Thanks, Adrian On 09/24/13, at 1:45 PM, Dustin Oprea <[email protected]> wrote: > If this is from syslog, syslog might not be configured to allow all logging. > That being said, try running the server directly (not as a service). It looks > like both the server and the client send errors to STDERR. The server log > routine (in svr-session.c): > > if (!svr_opts.usingsyslog || havetrace) > { > struct tm * local_tm = NULL; > timesec = time(NULL); > local_tm = localtime(×ec); > if (local_tm == NULL > || strftime(datestr, sizeof(datestr), "%b %d %H:%M:%S", > local_tm) == 0) > { > /* upon failure, just print the epoch-seconds time. */ > snprintf(datestr, sizeof(datestr), "%d", (int)timesec); > } > fprintf(stderr, "[%d] %s %s\n", getpid(), datestr, printbuf); > } > > It looks like error, warning, info, and debug logging all go into STDERR. In > this case, it looks like a majority of the messages are LOG_INFOs. > > > > Dustin > > On Tue, Sep 24, 2013 at 12:06 PM, Adrian Baerlocher <[email protected]> > wrote: > Logging from the server doesn't provide much help (the disconnect occurs from > client timeout): > > dropbear[37646]: Child connection from 127.0.0.1:56535 > dropbear[37646]: Exit before auth: Disconnect received > > I'll try creating a pcap file next. > > Thanks, > Adrian > > > On 09/24/13, at 11:49 AM, Andreas Schneider <[email protected]> wrote: > > > On Tuesday 24 September 2013 10:04:27 Adrian Baerlocher wrote: > >> Does anyone know of any compatibility issues with Dropbear > >> (dropbear_2013.58)? I'm seeing libssh (0.5.5) time out after exchanging > >> banners. I'm able to connect via OpenSSH, however. > > > > Could you turn on debugging on the server and find out what's going wrong? > > If > > this doesn't give any hint then probably creating a pcap file will help. > > > > http://git.libssh.org/projects/libssh.git/tree/include/libssh/pcap.h > > > > > > -- andreas > > > > -- > > Andreas Schneider GPG-ID: F33E3FC6 > > www.cryptomilk.org [email protected] > > > > > > > >
