]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2004/003005.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2004 / 003005.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] possible bug in 5.0.28 and below?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20possible%20bug%20in%205.0.28%20and%20below%3F&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="003004.html">
11 <LINK REL="Next" HREF="003007.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] possible bug in 5.0.28 and below?</H1>
15 <B>CyberDems</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20possible%20bug%20in%205.0.28%20and%20below%3F&In-Reply-To="
17 TITLE="[IRCServices Coding] possible bug in 5.0.28 and below?">cyberdems at cyberdems.za.net
18 </A><BR>
19 <I>Wed Mar 31 00:28:22 PST 2004</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="003004.html">[IRCServices Coding] Bug using svs4-db in
22 svs5(autodeop/nojoin-level)
23 </A></li>
24 <LI>Next message: <A HREF="003007.html">[IRCServices Coding] possible bug in 5.0.28 and below?
25 </A></li>
26 <LI> <B>Messages sorted by:</B>
27 <a href="date.html#3005">[ date ]</a>
28 <a href="thread.html#3005">[ thread ]</a>
29 <a href="subject.html#3005">[ subject ]</a>
30 <a href="author.html#3005">[ author ]</a>
31 </LI>
32 </UL>
33 <HR>
34 <!--beginarticle-->
35 <PRE>I'm reporting this as a possible bug:
36
37 When a nickname is registered and AUTH is enabled
38
39 * Your nick is now XYZ
40 -&gt; PRIVMSG NickServ :REGISTER abc123xyz <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">your at email-address.com</A>
41 -NickServ- Nickname XYZ has been registered to you.
42 -NickServ- An authentication code for your nickname has been sent to
43 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">your at email-address.com.</A>
44 -NickServ- When you receive this message, type /msg NickServ AUTH code
45 (replace code with the authentication code in the message) to complete your
46 nickname registration.
47 -NickServ- Your password is abc123xyz -- remember this for later use.
48 -&gt; NICK ABC
49 * Your nick is now ABC
50 -&gt; NICK XYZ
51 * Your nick is now XYZ
52 * XYZ sets mode: +r
53 -&gt; WHOIS XYZ
54 and it contains: XYZ has identified for this nick
55
56 Notice I didn't identify, and yet i'm classified as identified with +r.
57
58 So in other words, the nickname is fully functional even though I have not
59 yet AUTH'ed, all it needs is a nickchange and it is concidered registered.
60 This could pose as fatal in situations involving spambots. For example: the
61 spambot registers its nick with a fake e-mail address, changes its nick, and
62 then changes it back, and its automatically registered, then it can privmsg
63 registered nicks with spam, join +R channels, etc. etc.
64
65 Hope this helps --
66 CyberDems
67 irc.rsachat.za.net
68
69
70
71 </PRE>
72
73 <!--endarticle-->
74 <HR>
75 <P><UL>
76 <!--threads-->
77 <LI>Previous message: <A HREF="003004.html">[IRCServices Coding] Bug using svs4-db in
78 svs5(autodeop/nojoin-level)
79 </A></li>
80 <LI>Next message: <A HREF="003007.html">[IRCServices Coding] possible bug in 5.0.28 and below?
81 </A></li>
82 <LI> <B>Messages sorted by:</B>
83 <a href="date.html#3005">[ date ]</a>
84 <a href="thread.html#3005">[ thread ]</a>
85 <a href="subject.html#3005">[ subject ]</a>
86 <a href="author.html#3005">[ author ]</a>
87 </LI>
88 </UL>
89
90 </body></html>