]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2004/004491.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2004 / 004491.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] NickServ enforcer bug when unlinking nicknames
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20NickServ%20enforcer%20bug%20when%20unlinking%20nicknames&In-Reply-To=">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="004492.html">
11 <LINK REL="Next" HREF="004494.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] NickServ enforcer bug when unlinking nicknames</H1>
15 <B>Bergee</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20NickServ%20enforcer%20bug%20when%20unlinking%20nicknames&In-Reply-To="
17 TITLE="[IRCServices] NickServ enforcer bug when unlinking nicknames">lordbergee at comcast.net
18 </A><BR>
19 <I>Tue Jul 13 16:32:11 PDT 2004</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="004492.html">[IRCServices] Ircservices + Unreal3.2.1
22 </A></li>
23 <LI>Next message: <A HREF="004494.html">[IRCServices] NickServ enforcer bug when unlinking nicknames
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#4491">[ date ]</a>
27 <a href="thread.html#4491">[ thread ]</a>
28 <a href="subject.html#4491">[ subject ]</a>
29 <a href="author.html#4491">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE> I recently experienced a minor bug on my network which is currently
35 running IRCServices 5.0.31 on Red Hat Linux 9.0 on an Intel Celeron 1.7
36 GHz processor.
37 A while ago I noticed that a NickServ Enforcer bot had been sitting on
38 a nickname for over an hour. Checking NickServ INFO returned that the
39 nickname was not registered. After a little investigating in the log
40 files I noticed that the nickname had very recently been unlinked by its
41 owner. With that in hand I've been able to consistently reproduce the
42 problem by taking the following steps: (This assumes of course that
43 your network does not have NSForceNickChange enabled.)
44 1) Register a nickname and enable automatic kill protection and then
45 link another nickname to your name.
46 2) Have another user use the nickname you just linked and wait for
47 NickServ to kill the user.
48 3) Unlink the other nickname from your main nickname and watch as the
49 NickServ enforcer bot doesn't ever release the nickname. If you attempt
50 to use NickServ release you will be told the nickname isn't being held.
51 Before reporting the problem, I upgraded to IRCServices 5.0.36 and it
52 is still reproducible. I believe that Services should simply remove the
53 enforcer bot holding a nickname if the user unlinks the nickname while
54 the enforcer is online.
55
56 Bergee
57
58
59 </PRE>
60
61 <!--endarticle-->
62 <HR>
63 <P><UL>
64 <!--threads-->
65 <LI>Previous message: <A HREF="004492.html">[IRCServices] Ircservices + Unreal3.2.1
66 </A></li>
67 <LI>Next message: <A HREF="004494.html">[IRCServices] NickServ enforcer bug when unlinking nicknames
68 </A></li>
69 <LI> <B>Messages sorted by:</B>
70 <a href="date.html#4491">[ date ]</a>
71 <a href="thread.html#4491">[ thread ]</a>
72 <a href="subject.html#4491">[ subject ]</a>
73 <a href="author.html#4491">[ author ]</a>
74 </LI>
75 </UL>
76
77 </body></html>