[IRCServices] Notice regarding Bahamut support

[Thomas J. Stensås]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 19 February 2003 19:23, Dmitry Agaphonov wrote:
> As for akills, placing an akill for *@216.201.160.2* or similar will not
> make the server to add it to its network bans.  So, Services should not
> allow such akills now for bahamut based networks.  Also, it would be nice
> to add CIDR akills support to Services.

This is wrong, adding an akill for *@216.201.160.2* will add it to the network 
wide list of akills. You can view it by using /stats a.

However one thing to be noted, and i have not checked IRC Services for this.
Bahamut 1.4.34 or .35 introduced sanity checking on akill expiry time.
Meaning that if the SetOn time + Expire time sent to the server is older than 
CurrentTime, the akill will be discarded as bogus. I seem to recall that in 
IRC Services 4.4 or about there akills was sent with the SetOn time correct, 
but with a static expiry time of 86400 * 2, which in many occations would 
lead to SetOn + (86400 * 2) being older the CurrTime if the akill gets sent 
out later than two days after it has been set.
If IRC Services now use the actual expiry time as the expiry time sent to the 
server this should not be a problem however. And this cant really be called a 
change in the protocol as its bugfix to disregard bogus akills.

- -- 
Yours Sincerely

Thomas Juberg Stensås

- -- What we do in life echoes in eternity

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+U9LTm5JSuDogRncRAsT8AJ0dcbmbH4Th6J6lLytMQvKpkV3NDwCgsyQu
1MRaF2Cwcw1+DOJr3oru1+o=
=HgXv
-----END PGP SIGNATURE-----