projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices] Bug in mode locked keys in 5.0.6 | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Bug%20in%20mode%20locked%20keys%20in%205.0.6&In-Reply-To=200212280226.gBS2QBC28531%40localhost.localdomain"> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="003422.html"> | |
| 11 | <LINK REL="Next" HREF="003423.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices] Bug in mode locked keys in 5.0.6</H1> | |
| 15 | <B>Trevor Talbot</B> | |
| 16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Bug%20in%20mode%20locked%20keys%20in%205.0.6&In-Reply-To=200212280226.gBS2QBC28531%40localhost.localdomain" | |
| 17 | TITLE="[IRCServices] Bug in mode locked keys in 5.0.6">quension at softhome.net | |
| 18 | </A><BR> | |
| 19 | <I>Tue Dec 31 23:12:01 PST 2002</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="003422.html">[IRCServices] Bug in mode locked keys in 5.0.6 | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="003423.html">[IRCServices] bahamut/Services crash | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#3431">[ date ]</a> | |
| 27 | <a href="thread.html#3431">[ thread ]</a> | |
| 28 | <a href="subject.html#3431">[ subject ]</a> | |
| 29 | <a href="author.html#3431">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>On Friday, Dec 27, 2002, at 18:25 US/Pacific, Craig Edwards wrote: | |
| 35 | ||
| 36 | ><i> We've just discovered a bug in ircservices 5.0.6 where a channel can | |
| 37 | </I>><i> be joined which has a key modelocked, and not only does it allow the | |
| 38 | </I>><i> client to enter, it also shows them the key, if the room is empty. | |
| 39 | </I>><i> In the following test, the channel is registered with the mode lock | |
| 40 | </I>><i> "+ntk mykey", and is empty. Guest2088478498 is not on any access | |
| 41 | </I>><i> lists for the channel. | |
| 42 | </I>><i> | |
| 43 | </I>><i> *** services.chatspike.net changes topic to '(ChanServ)' | |
| 44 | </I>><i> *** ChanServ sets mode: +ntrk-o mykey Guest2088478498 | |
| 45 | </I> | |
| 46 | ><i> A little discussion led us to think that a good fix for this would | |
| 47 | </I>><i> be to treat keyed channels in the same way as +O channels, unless | |
| 48 | </I>><i> the correct key is supplied in the JOIN raw, if +k is mode locked, | |
| 49 | </I>><i> kick out the user before the locked modes and topic are set by | |
| 50 | </I>><i> chanserv/services.* | |
| 51 | </I> | |
| 52 | The key in the join command is not passed to other servers, so | |
| 53 | services would never receive it. | |
| 54 | ||
| 55 | -- Quension | |
| 56 | ||
| 57 | ||
| 58 | </PRE> | |
| 59 | ||
| 60 | <!--endarticle--> | |
| 61 | <HR> | |
| 62 | <P><UL> | |
| 63 | <!--threads--> | |
| 64 | <LI>Previous message: <A HREF="003422.html">[IRCServices] Bug in mode locked keys in 5.0.6 | |
| 65 | </A></li> | |
| 66 | <LI>Next message: <A HREF="003423.html">[IRCServices] bahamut/Services crash | |
| 67 | </A></li> | |
| 68 | <LI> <B>Messages sorted by:</B> | |
| 69 | <a href="date.html#3431">[ date ]</a> | |
| 70 | <a href="thread.html#3431">[ thread ]</a> | |
| 71 | <a href="subject.html#3431">[ subject ]</a> | |
| 72 | <a href="author.html#3431">[ author ]</a> | |
| 73 | </LI> | |
| 74 | </UL> | |
| 75 | ||
| 76 | </body></html> |