Limit concurrent connections

Rich Turner rich at storix.com
Sat Jun 17 00:52:05 WST 2006


This seems to be working just fine. Thanks for the help.

I must admit I am not that verse with C programming. Can you tell me what I 
just did by commenting out "m_close(svr_ses.childpipe)" in svr-auth.c. I 
would like to know what I did so that if something odd happens I may be able 
to relate it to the change I made.

Also, the error message that I receive when a second client attempts to 
connect is "dbclient: connection to root at rich-laptop:22 exited: Failed to get 
remote version". I would prefer that the error message indicate that I have 
exceeded the maximum number of concurrent connections. I have found in 
common.session.c where I can change the text, but I do not want to change it 
if this would be a valid error for another reason other than maximum 
connections exceeding. Under what circumstances would I get this error?

On Friday 16 June 2006 09:21, Matt Johnston wrote:
> On Fri, Jun 16, 2006 at 09:02:50AM -0700, Rich Turner wrote:
> > I have looked through options.h and could not find where I could define
> > the total number of concurrent client connections that are allowed to be
> > connected to the dropbear server. I would like to limit the number of
> > authorized connections to 1. Is this possible?
> >
> > I do see in options.h the ability to limit the number unauthorized
> > clients, but nothing to limit the number of authorized clients.
>
> There isn't a setting for this by default. You can achieve
> it by setting MAX_UNAUTH_CLIENTS 1, then commenting out the
> "m_close(svr_ses.childpipe)" call near the bottom of
> svr-auth.c. It seems to work here, you might want to test it
> a bit though. Let me know how it goes.
>
> Cheers,
> Matt



More information about the Dropbear mailing list