Project

General

Profile

Bug #995

Bogus client prevents new client to connect

Added by David Demelier 10 months ago. Updated 10 months ago.

Status:
Closed
Priority:
Urgent
Category:
irccd
Target version:
Start date:
02/13/2019
Due date:
% Done:

100%

Estimated time:
1.00 h
Spent time:
MFD after:
MFD revision:
Branch:
default
Bookmark:
@
Platform:

Description

If a client does not answer a password enabled transport, the service will wait until the client has given a password to add a new client

  1. create a transport with a password
  2. use telnet/openssl to connect and do nothing
  3. use telnet/openssl again -> you don't get hello from irccd

Solution:

  1. remove the auth/greetings process from the service/acceptor and put directly in the client. #

Associated revisions

Revision 831:7b012c42660c (diff)
Added by David Demelier 10 months ago

irccd: move authentication part from transport_server, closes #995 @2h

If a server requires a password and a client does not provide, the server
is unable to accept a new client.

Move the authentication/greetings part from the server into the client to let
the transport_service processing input.

History

#1

Updated by David Demelier 10 months ago

  • Target version set to 3.0.0
#2

Updated by David Demelier 10 months ago

  • % Done changed from 0 to 100
  • Status changed from New to Resolved
#3

Updated by David Demelier 10 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF