Sorry about that. The patch is correct, I'll put up a new
release in a couple of days (wait to see if there are any
more glaring bugs).
Cheers,
Matt
On Tue, Apr 16, 2013 at 11:13:48PM +0200, Hans Harder wrote:
> I get compile errors with the new version, because I compile this in a
> uclib enviro
I get compile errors with the new version, because I compile this in a
uclib environment without zlib.
I use ./configure --disable-zlib
In common-kex.c I run into compile errors.
common-kex.o(.text+0x203): In function `switch_keys':
: undefined reference to `gen_new_zstream_recv'
common-kex.o(.te
Found the problem...
In my energetic effort to reduce the size of the server,
I had #undef DROPBEAR_MD5_HMAC
in my options.h file.
With that defined, the fingerprints now match.
All better now.
Sorry for the noise!
Ed
Ok, more information...
I see that if I use an ssh client that connects to an s
Ok, more information...
I see that if I use an ssh client that connects to an ssh server, I do
get the expected
fingerprints. I also see that if I use the dbclient with the db server
I get the
expected fingerprint. The problem occurs when I try to use the ssh
client to connect
to the db serv
I'm confused, so I'd like to re-phrase my question (below) a bit...
Assume I start up a dropbear server on a machine (ignore my embedded case).
I do that with the following commands...
dropbearkey -t dss -f dropbear_dss_host_key
dropbearkey -t rsa -f dropbear_rsa_host_key
dropbear -F -r
Matt,
Answers embedded...
Ed
Hi,
I'm pretty sure there'd be interest in such a port, even if
there are no immediate takers. I guess it depends how much
effort you want to put in - a separate tarball (or hg
branch ease of merging future versions) might be enough for other
people to get going. It
Hi,
I now have the dropbearkey code integrated into my embedded stuff.
I assume the idea is to call this function each time the server starts up.
Then each time the server starts, future client connections will reject the
server connection until $HOME/.ssh/known_hosts is purged of that server's
k
Hi,
I'm pretty sure there'd be interest in such a port, even if
there are no immediate takers. I guess it depends how much
effort you want to put in - a separate tarball (or hg
branch ease of merging future versions) might be enough for other
people to get going. It doesn't sound like the changes
Fabrizio,
Don't ignore CPU horsepower needs.
Ed
Hmm interesting... now, 77K is kind of 'at reach'...
Depending on the chip I am going to finalize the project, but probably
with some help from some external RAM & flash I might give it a shot.
Thanks a lot for your reports!
Fabrizio
On Mon, Apr
