[PATCH] Compilation fix when ENABLE_CLI_AGENTFWD undefined

Hello, (I just subscribed to the list, so the following points might already have been addressed; sorry if it's the case.) Here is a patch for dropbear-0.53.1 that fixes a compilation and linking issue that currently comes up when ENABLE_CLI_AGENTFWD is not defined at all. Only the

Re: [solaris] library -lc: not found

$ make PROGRAMS=scp STATIC=1 gcc -L/usr/local/lib -R/usr/local/lib -static -o scp scp.o progressmeter.o atomicio.o scpmisc.o compat.o ld: fatal: library -lc: not found As Matt said, you cannot make static programs on Solaris. Solaris does not ship with a libc.a, only a libc.so. This would

dropbear hangs instead of returning failure on a long command

Hello Matt (and list), When given a command that exceeds MAX_CMD_LEN, the dropbear server just hangs and does nothing (it stays on select() in the main loop until the client closes the connection, which may never happen). It happens whether or not a pty is requested. I've only tested it with

dbclient reports integrity errors with GitHub

Hello, dropbear-2015.67, compiled with a recent (last week) musl libc, statically linked. The problem also occurs with dropbear-2014.66. Since a few days ago (but I'm not sure when it started; in any case it's less than a month ago), every git pull and push over SSH from/to GitHub fails

Re: dbclient reports integrity errors with GitHub

On 23/04/2015 02:03, Matt Johnston wrote: I think its because their version of libssh ignores one of the protocol flags, fixed in libssh 0.6.4. I'll send an email to github. https://git.libssh.org/projects/libssh.git/commit/?id=eb86fd8cdfd69f46c60bf0885a2125285e4a22b3 Thanks for your quick

Re: server limits commands to MAX_CMD_LEN

On 01/07/2015 19:24, Tim Broberg wrote: Yes, I have had to scp scripts to the target and run them in place for large commands specifically because of dropbear. I've run into the same issue and just recompiled dropbear with increased limits. 8k is enough for me (but 4k is not enough, so Matt,

Re: Dropbear SSH integrity error

On 12/11/2015 10:28, Zbynek Michl wrote: # ssh d...@demo.mt.lv ssh: Connection to d...@demo.mt.lv:22 exited: Integrity error (bad packet size -22146333) Hi Zbynek, I had the same problem earlier this year with GitHub: git over ssh worked with an OpenSSH client, but not with a dropbear

Re: Dropbear Digest, Vol 171, Issue 1

I can't compile DB 2020.79 with uClibc-ng (1.0.32, looking at the 1.0.34 sources nothing has changed) unless I add "#define _GNU_SOURCE" on top of "dbrandom.c" (it is required by sys/random.h, line 11