View Issue Details

IDProjectCategoryView StatusLast Update
0000727unrealircdpublic2003-11-20 19:46
Reporteriguy Assigned Tosyzop  
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Product Version3.2-beta14 
Summary0000727: Connect Allow blocks to Listen blocks
DescriptionI have a need of requiring folks to either connect via SSL (which means no password needed) or if you are connecting via the non-SSL port that you MUST password connect.

There are a variety of passworded allow blocks that are used currently but they are exclusive. There is no easy way to make a default password on only the port 6667 or whatever.
3rd party modules

Activities

syzop

2003-02-14 17:28

administrator   ~0001564

IMO it would be more logical to have an ssl option somewhere in the allow block (which means the user has to be connected via ssl in order to use that allow block </badenglish>). What do you think? Is the listen block thing more usefull? And if so, when?

iguy

2003-02-14 17:36

reporter   ~0001565

However you guys wish to implement it. :)

I'm really needing a way to restrict stuff to ports, connection types. Etc.

syzop

2003-04-11 18:27

administrator   ~0002267

I don't know if it's enough for you but I've now added allow::options::ssl and allow::options::nopasscont
*paste from docs*
ssl - only match if this client is connected via SSL
nopasscont - continue matching if no password was given (so you can put clients in special classes if they supply a password).

iguy

2003-04-15 12:29

reporter   ~0002334

That might just do it. Only allow clients to a given allow block with SSL.

Thanks. I assume this is in CVS and I'll check out CVS one of these days and test it.

Issue History

Date Modified Username Field Change
2003-04-11 18:27 syzop Note Added: 0002267
2003-04-15 12:29 iguy Note Added: 0002334
2003-04-15 13:25 syzop Status new => resolved
2003-04-15 13:25 syzop Resolution open => fixed
2003-04-15 13:25 syzop Assigned To => syzop
2003-11-20 19:46 syzop Status resolved => closed