]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2003/003770.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2003 / 003770.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Set Secure
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Set%20Secure&In-Reply-To=3e9c7197.10447%40mail.achurch.org">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="003769.html">
11 <LINK REL="Next" HREF="003772.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Set Secure</H1>
15 <B>Stefan Funke</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Set%20Secure&In-Reply-To=3e9c7197.10447%40mail.achurch.org"
17 TITLE="[IRCServices] Set Secure">bundy at usage.de
18 </A><BR>
19 <I>Tue Apr 15 14:49:54 PDT 2003</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="003769.html">[IRCServices] Set Secure
22 </A></li>
23 <LI>Next message: <A HREF="003772.html">[IRCServices] Set Secure
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#3770">[ date ]</a>
27 <a href="thread.html#3770">[ thread ]</a>
28 <a href="subject.html#3770">[ subject ]</a>
29 <a href="author.html#3770">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>On 2003-04-16 (05:51, +0900), Andrew Church &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>&gt; wrote:
35
36 &gt;<i> &gt;Hello everybody;
37 </I>&gt;<i> &gt;
38 </I>&gt;<i> &gt;I think chanserv set secure option isnt working well.
39 </I>&gt;<i> &gt;
40 </I>&gt;<i> &gt;As services says
41 </I>&gt;<i> &gt;-ChanServ- Enables or disables ChanServ's security features for a
42 </I>&gt;<i> &gt; -ChanServ- channel. When SECURE is set, only users who have registered
43 </I>&gt;<i> &gt; -ChanServ- their nicknames with NickServ and IDENTIFY'd with their
44 </I>&gt;<i> &gt; -ChanServ- password will be given privileges on the channel as
45 </I>&gt;<i> &gt; -ChanServ- controlled by the access list.
46 </I>&gt;<i> &gt;
47 </I>&gt;<i> &gt;it seems good but when a founder makes autoop levels 0 then any un
48 </I>&gt;<i> &gt;registered nickname can be op. So there is a problem here because chanserv
49 </I>&gt;<i> &gt;doesnt check if nick is a registered or not when we set autoop level 0.
50 </I>&gt;<i> &gt;
51 </I>&gt;<i> &gt;Any idea?
52 </I>&gt;<i>
53 </I>&gt;<i> Services is performing exactly as the help messages state. Any
54 </I>&gt;<i> nickname not on the access list automatically has an access level of 0; if
55 </I>&gt;<i> you set the auto-op level to 0, then obviously, any nickname not on the
56 </I>&gt;<i> access list will be auto-opped. If this wasn't your intention, then the
57 </I>&gt;<i> solution is simple: Don't set the auto-op level to 0.
58 </I>
59 Not really - cs &quot;secure on&quot; means that only registered and identified
60 nicks (users in status 3) get an op. That means together with AutoOp level
61 0 everyone with (nick)status 3 will get an OP. Others will fit in any
62 other level or won't get another umode.
63
64 However, that whats fits in my logic ;-)
65
66 - Stefan
67
68
69 --
70 Work is for people who don't have Internet access.
71 </PRE>
72
73 <!--endarticle-->
74 <HR>
75 <P><UL>
76 <!--threads-->
77 <LI>Previous message: <A HREF="003769.html">[IRCServices] Set Secure
78 </A></li>
79 <LI>Next message: <A HREF="003772.html">[IRCServices] Set Secure
80 </A></li>
81 <LI> <B>Messages sorted by:</B>
82 <a href="date.html#3770">[ date ]</a>
83 <a href="thread.html#3770">[ thread ]</a>
84 <a href="subject.html#3770">[ subject ]</a>
85 <a href="author.html#3770">[ author ]</a>
86 </LI>
87 </UL>
88
89 </body></html>