View Issue Details

IDProjectCategoryView StatusLast Update
0002464unrealircdpublic2005-04-08 11:47
Reporterw00t Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionopen 
Summary0002464: More comma fun in channel key setting
Description/mode #chan +k ,
/mode #chan +k test,pass

Looks like it's truncating on comma, useful to avoid join #1,#2 k1,k2 problems, but should it reject the whole thing?
3rd party modules

Activities

syzop

2005-04-07 23:24

administrator   ~0009714

uhm.. what exactly is the problem?
yes, it cuts the string off on comma, that's exactly what it is supposed to do :P.

w00t

2005-04-07 23:45

reporter   ~0009715

I would have thought it would have rejected the whole key on setting a key, that's all... It confused me when I went to set a key with a comma and then couldn't rejoin :P

syzop

2005-04-07 23:54

administrator   ~0009716

couldn't rejoin?
perhaps you can explain the problem a bit better, I'm lost ;).
because you report:
--
/mode #chan +k ,
/mode #chan +k test,pass
--
so I went type both commands, I noticed the 1st one does nothing, the second one truncates it.

[/me off to bed]

w00t

2005-04-08 02:44

reporter   ~0009717

Because the password was truncated and I wasn't informed of that appropriatly, I didn't notice, left, and couldn't rejoin until I was told of my misfortune :)

And uh, why'd this get marked private? :/

syzop

2005-04-08 11:47

administrator   ~0009718

I'm still lost.. why couldn't you rejoin if the password was truncated? You say 'and I wasn't informed of that appropriatly' but you were by the mode line, right? I doubt any decent client would rely on the +k info itself sent :P.

'And uh, why'd this get marked private? :/'
Because I went to bed and you were totally unclear about what the problem was, if it was serious then it should have been marked as private (like your report could have been [mis]read as: it says it didn't set any key but a NULL key was present and thus nobody was able to [re]join). Since it turns out to be nothing, it is unneeded.

Most likely this can be closed now.

Issue History

Date Modified Username Field Change
2005-04-07 23:07 w00t New Issue
2005-04-07 23:24 syzop Note Added: 0009714
2005-04-07 23:45 w00t Note Added: 0009715
2005-04-07 23:54 syzop Note Added: 0009716
2005-04-07 23:54 syzop View Status public => private
2005-04-08 02:44 w00t Note Added: 0009717
2005-04-08 11:47 syzop Note Added: 0009718
2005-04-08 11:47 syzop View Status private => public
2005-04-08 11:47 syzop Status new => closed