>>>>> "Christophe" == Christophe Kalt <kalt@xxxxxxxxxxx> writes:
Christophe> If this is such an issue, then it shows that changing K
Christophe> lines behaviour was a mistake: instead one should have
Christophe> written a few scripts to help manage the ircd.conf and
Christophe> at the same time generate web pages users can refer to
Christophe> find out why they cannot access the server.
For various reasons this isn't practical -- it would be very difficult
to determine which K-Line (or ban) was applied to a certain user based
purely on, for example, CGI environment variables. At the very least,
it should be possible to return an ID or cookie so that you can say
something to the effect of "Please visit
http://www.example.com/klines/cookie to see why you are not permitted
to use this server."
There just needs to be a way to return some form of ban- or
k-line-specific information, especially since some servers have
hundreds of k-lines (it wouldn't surprise me if some have more).
- Andrew
--
#!/usr/bin/env python
print(lambda s:s+"("+`s`+")")\
('#!/usr/bin/env python\012print(lambda s:s+"("+`s`+")")\\\012')
print(lambda x:x%`x`)('print(lambda x:x%%`x`)(%s)')
Attachment:
pgp00001.pgp
Description: PGP signature