Re: Dropbear difficulties due to outdated version?

James, What I suggested was not to recompile dropbear for the VPS, but download and compile the same version of dropbear *on your computer* (or whatever is the machine you are using to connect to the VPC from). Then use dbclient instead of ssh to connect to the VPS. If you can write on the VPC,

Re: Dropbear difficulties due to outdated version?

I know I am not directly answering your question, but have you thought of building dropbear v2017.75 on your PC and use dbclient to connect (instead of ssh) to your VPS ? If you must use openssh, I would look into the ssh client settings to see if there is some sort of configurable parameters that

Re: restrict access

I've used successfully (well, at least I believe it's successful) sshblack ( http://www.pettingers.org/code/sshblack.html) to block those pesky robots through iptables. To get it to work correctly It's not as obvious as it seems... and there are some limitations, but once you are familiar with it,

Re: Cannot Connect to Dropbear Server of Openwrt in QEMU

FYI, the firewall rules on OpenWRT are defined in: /etc/config/firewall As far as I remember by default port 22 is blocked on wan, so make sure there is a section as follow: -- config rule option target 'ACCEPT' option src 'wan' option proto 'tcp'

Re: Dropbear server exit when idle?

I don't think you should have this functionality in Dropbear. This is specific to your use case. You can still do it with a bash script. At boot the script can check the /var/log/secure file to see if there is any activity on dropbear (poll the file size every few seconds)... Reset the internal

Re: Tunnelling support?

Russel, dropbear fully support tunneling. Both local (with -L) and reverse (with -R). I have been using for quite some time now. If you expect your local port (6) to be reached from other machines, make sure to use the -g option as well. I think your problem is on the server side, on the ssh

Re: Getting dbclient to time out when network goes down with reverse proxy usage

for free for non-commercial products, but requires to pay for a license for commercial use. I don't remember exactly the name of the one we looked at (that was few years ago). Regards, Fabrizio On Sat, Jul 5, 2014 at 2:14 AM, Jesse Molina je...@opendreams.net wrote: Fabrizio Bertocci contacted me

Re: Timeout dead connections

I remember reporting this problem and sending a patch long time ago (for version 0.52). The problem with the keep-alive (if I remember correctly) was that every time dropbear was sending the keep-alive message, it was also resetting the timeout counter... so dropbear or dbclient never detect the

Re: Timeout dead connections

reset by SSH_MSG_IGNORE packets. If the network cable has been pulled out, shouldn't the OS send a TCP RST packet eventually after some traffic and close the connection? Cheers, Matt On Wed, Mar 27, 2013 at 11:41:40AM -0400, Fabrizio Bertocci wrote: I remember reporting this problem

Re: Starting Dropbear

Dropbearkey only generates the keys, is not the real server. You need to start the server on one machine (use dropbear), and the client from another machine. Well... Get help page from dropbear for a list of arguments. You need to provide at least your dsa or rsa keys to start the server side

Multiple auth requests?

Hi guys, I'm working on a project that uses dropbear, and I'm modifying the code to add a custom lookup mechanism for pub/priv keys that uses a database instead of a file. While debugging it, I've noticed that the server sometimes receives message type 50 (that I understand it means auth. request)