1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] RE: IRCServices Digest, Vol
16, Issue
6
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20RE%3A%20IRCServices%20Digest%2C%20Vol%2016%2C%20Issue%206&In-Reply-To=BLAZEeltyZZBClQhyCW000002d1%40BLAZE.wfsg.net">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"004227.html">
11 <LINK REL=
"Next" HREF=
"004229.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] RE: IRCServices Digest, Vol
16, Issue
6</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20RE%3A%20IRCServices%20Digest%2C%20Vol%2016%2C%20Issue%206&In-Reply-To=BLAZEeltyZZBClQhyCW000002d1%40BLAZE.wfsg.net"
17 TITLE=
"[IRCServices] RE: IRCServices Digest, Vol 16, Issue 6">ruldaen at wfsg.net
19 <I>Wed Apr
14 01:
34:
05 PDT
2004</I>
21 <LI>Previous message:
<A HREF=
"004227.html">[IRCServices] secure Identify Feature..
23 <LI>Next message:
<A HREF=
"004229.html">[IRCServices] secure Identify Feature..
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#4228">[ date ]
</a>
27 <a href=
"thread.html#4228">[ thread ]
</a>
28 <a href=
"subject.html#4228">[ subject ]
</a>
29 <a href=
"author.html#4228">[ author ]
</a>
34 <PRE>I really like this idea as well!!
36 -----Original Message-----
37 From:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-bounces at ircservices.za.net
</A>
38 [mailto:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-bounces at ircservices.za.net
</A>] On Behalf Of
39 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net
</A>
40 Sent: Tuesday, April
13,
2004 10:
03 PM
41 To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>
42 Subject: IRCServices Digest, Vol
16, Issue
6
44 Send IRCServices mailing list submissions to
45 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>
47 To subscribe or unsubscribe via the World Wide Web, visit
48 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
49 or, via email, send a message with subject or body 'help' to
50 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net
</A>
52 You can reach the person managing the list at
53 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-owner at ircservices.za.net
</A>
55 When replying, please edit your Subject line so it is more specific
56 than
"Re: Contents of IRCServices digest...
"
61 1. secure Identify Feature.. ( Dionisios K. )
62 2. RE: secure Identify Feature.. (Dionisios K.)
63 3. Re: secure Identify Feature.. (Craig Edwards)
64 4. RE: secure Identify Feature.. (M)
65 5. Re: RE: [IRCServices] secure Identify Feature.. (Craig McLure)
66 6. RE: RE: [IRCServices] secure Identify Feature.. (M)
67 7. Re: RE: RE: [IRCServices] secure Identify Feature.. (Craig McLure)
68 8. Re: RE: RE: [IRCServices] secure Identify Feature..
70 9. Re: RE: RE: [IRCServices] secure Identify Feature..
72 10. Re: RE: RE: [IRCServices] secure Identify Feature..
74 11. Re: RE: RE: [IRCServices] secure Identify Feature..
78 ----------------------------------------------------------------------
81 Date: Tue,
13 Apr
2004 13:
13:
46 +
0100 (BST)
82 From:
" Dionisios K.
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">vonitsa_net at yahoo.gr
</A>>
83 Subject: [IRCServices] secure Identify Feature..
84 To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>
85 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">20040413121346.62294.qmail at web86105.mail.ukl.yahoo.com
</A>>
86 Content-Type: text/plain; charset=iso-
8859-
7
89 A new command may be added to ircservices (or not..).
90 The command will be like this:
92 /cs set #channel restrictid on-off
94 If the option is
"on
" the /cs identify command will be
95 allowed only to channel accessed users even if someone
96 else have the password. If the option is
"off
" the /cs
97 identify command will be allowed to anyone who have
104 ------------------------------
107 Date: Tue,
13 Apr
2004 10:
48:
08 -
0700 (PDT)
108 From:
"Dionisios K.
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">vonitsa_net at yahoo.gr
</A>>
109 Subject: RE: [IRCServices] secure Identify Feature..
110 To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">Ircservices at ircservices.za.net
</A>
111 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">20040413174808.38288.qmail at web86106.mail.ukl.yahoo.com
</A>>
112 Content-Type: text/plain; charset=us-ascii
114 Sorry for my english.. A channel accessed user is a
115 user who have access to a channel.
118 Dionisios K. - VoNiTsA On GrNet
123 ------------------------------
126 Date: Tue,
13 Apr
2004 20:
26:
52 +
0100
127 From:
"Craig Edwards
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">brain at winbot.co.uk
</A>>
128 Subject: Re: [IRCServices] secure Identify Feature..
129 To:
"ircservices
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
130 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">200404131926.i3DJQqv02204 at brainbox.winbot.co.uk
</A>>
131 Content-Type: text/plain; charset=
"iso-
8859-
1"
133 i really like this idea, hope it gets put into
5.1 or whenever...
136 </I>><i>A new command may be added to ircservices (or not..).
137 </I>><i>The command will be like this:
139 </I>><i>/cs set #channel restrictid on-off
141 </I>><i>If the option is
"on
" the /cs identify command will be
142 </I>><i>allowed only to channel accessed users even if someone
143 </I>><i>else have the password. If the option is
"off
" the /cs
144 </I>><i>identify command will be allowed to anyone who have
145 </I>><i>the password.
147 </I>><i>Please reply:))
149 </I>><i>------------------------------------------------------------------
150 </I>><i>To unsubscribe or change your subscription options, visit:
151 </I>><i><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
156 ------------------------------
159 Date: Tue,
13 Apr
2004 21:
59:
58 +
0100
160 From:
"M
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>>
161 Subject: RE: [IRCServices] secure Identify Feature..
162 To:
"'IRC Services General Mailing List'
"
163 <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
164 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">E1BDV12-
0007Y1-
0X at anchor-post-
33.mail.demon.net
</A>>
165 Content-Type: text/plain; charset=
"US-ASCII
"
167 Isn't this already available: by default only the founder knows the password
168 so only that person can identify for it. If for some peculiar reason the
169 founder wants to share the password they can.
171 This
"option
" does not seem to create a benefit and merely adds unnecessary
176 ><i> -----Original Message-----
177 </I>><i> From:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-bounces at ircservices.za.net
</A>
178 </I>><i> [mailto:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-bounces at ircservices.za.net
</A>] On Behalf Of
179 </I>><i> Dionisios K.
180 </I>><i> Sent:
13 April
2004 13:
14
181 </I>><i> To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>
182 </I>><i> Subject: [IRCServices] secure Identify Feature..
185 </I>><i> A new command may be added to ircservices (or not..).
186 </I>><i> The command will be like this:
188 </I>><i> /cs set #channel restrictid on-off
190 </I>><i> If the option is
"on
" the /cs identify command will be
191 </I>><i> allowed only to channel accessed users even if someone else
192 </I>><i> have the password. If the option is
"off
" the /cs identify
193 </I>><i> command will be allowed to anyone who have the password.
195 </I>><i> Please reply:))
197 </I>><i> ------------------------------------------------------------------
198 </I>><i> To unsubscribe or change your subscription options, visit:
199 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
205 ------------------------------
208 Date: Tue,
13 Apr
2004 23:
50:
12 +
0100
209 From:
"Craig McLure
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">Craig at chatspike.net
</A>>
210 Subject: Re: RE: [IRCServices] secure Identify Feature..
211 To:
"<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>, IRC Services Gene
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>,
212 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
213 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mailman
.61.1081907989.777.ircservices at ircservices.za.net
</A>>
214 Content-Type: text/plain; charset=
"iso-
8859-
1"
216 This command would add things to make the channel more secure thou, If you
217 did give the channel founder password to people you trust, and you find its
218 being abused, you can simply remove that person from the access list, this
219 way you dont need to worry about changing the password and re-distributing
222 /****************************************
223 * Craig
"FrostyCoolSlug
" McLure
224 * InspIRCd -
<A HREF=
"http://www.inspircd.org">http://www.inspircd.org
</A> - REVIVED
225 * ChatSpike -
<A HREF=
"http://www.chatspike.net">http://www.chatspike.net
</A>
226 ****************************************/
229 /****************************************
230 * From - M
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>>
231 * To - 'IRC Services General Mailing List'
232 <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
233 * Sent -
2004-
04-
13 21:
59:
58
234 * Subject - RE: [IRCServices] secure Identify Feature..
235 ****************************************/
237 /****** - Begin Original Message - ******/
239 ><i>Isn't this already available: by default only the founder knows the
241 ><i>so only that person can identify for it. If for some peculiar reason the
242 </I>><i>founder wants to share the password they can.
244 </I>><i>This
"option
" does not seem to create a benefit and merely adds unnecessary
245 </I>><i>complexity.
250 </I>><i>------------------------------------------------------------------
251 </I>><i>To unsubscribe or change your subscription options, visit:
252 </I>><i><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
255 /******* - End Original Message - *******/
261 ------------------------------
264 Date: Wed,
14 Apr
2004 00:
08:
45 +
0100
265 From:
"M
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>>
266 Subject: RE: RE: [IRCServices] secure Identify Feature..
267 To:
"'IRC Services General Mailing List'
"
268 <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
269 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">E1BDX1f-
0001VX-
0X at anchor-post-
33.mail.demon.net
</A>>
270 Content-Type: text/plain; charset=
"US-ASCII
"
273 ><i> This command would add things to make the channel more secure
274 </I>><i> thou, If you did give the channel founder password to people
275 </I>><i> you trust, and you find its being abused, you can simply
276 </I>><i> remove that person from the access list, this way you dont
277 </I>><i> need to worry about changing the password and re-distributing it :)
279 The way to be secure is not to give out the founder password. You could
280 apply the same short sighted reason for a
"/ns set
281 letotherpeopleaccessmynick pass
" request.
283 The founder password is designed to give the channel founder access to
284 manage the ownership of the channel. There is no need to give out the
285 password to anyone, channel management through others is provided via op
288 If for some peculiar reason a channel founder wishes to share the password
289 then IMO that is their problem. The chances are that any user that would
290 require modifying the access list to
"fix
" this, would likely be attempted
291 too late since a rogue user could have merely taken ownership of the channel
292 thereby making the option and the founder password redundant and merely make
293 it a problem that administrators waste time on.
295 The founder can already provide access to whatever commands an op needs via
296 levels which is far more secure and already subject to access list
299 What function of founder status is required that warrants removing the
300 founder status by supporting sharing of it?
307 ------------------------------
310 Date: Wed,
14 Apr
2004 00:
39:
43 +
0000
311 From:
"Craig McLure
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">Craig at chatspike.net
</A>>
312 Subject: Re: RE: RE: [IRCServices] secure Identify Feature..
313 To:
"<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>, IRC Services Gene
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>,
314 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
315 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mailman
.62.1081907989.777.ircservices at ircservices.za.net
</A>>
316 Content-Type: text/plain; charset=
"iso-
8859-
1"
318 I read this mail, and read it again, and its absolutly right, with some
319 careful manipulation of the /cs levels command, along with /cs access, you
320 can basically give people 'Founder' privs without them being founder.
321 Another possible advantage to this command thou.. If for some weird reason,
322 someone finds your channel password, this command would prevent them from
323 doing anything with it, as they would not be able to log on as channel
324 founder (Unless they were on the access list). sometimes the distributation
325 of channel passwords may be present when the real founder cant get at the
326 channel for various reasons, and they give the password to the successor, or
327 someone else trustworthy. From where i'm sitting, I cant really see any
328 other real use for this function.
330 /****************************************
331 * Craig
"FrostyCoolSlug
" McLure
332 * InspIRCd -
<A HREF=
"http://www.inspircd.org">http://www.inspircd.org
</A> - REVIVED
333 * ChatSpike -
<A HREF=
"http://www.chatspike.net">http://www.chatspike.net
</A>
334 ****************************************/
337 /****************************************
338 * From - M
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>>
339 * To - 'IRC Services General Mailing List'
340 <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
341 * Sent -
2004-
04-
13 23:
08:
45
342 * Subject - RE: RE: [IRCServices] secure Identify Feature..
343 ****************************************/
345 /****** - Begin Original Message - ******/
347 ><i>Craig McLure wrote:
348 </I>>><i> This command would add things to make the channel more secure
349 </I>>><i> thou, If you did give the channel founder password to people
350 </I>>><i> you trust, and you find its being abused, you can simply
351 </I>>><i> remove that person from the access list, this way you dont
352 </I>>><i> need to worry about changing the password and re-distributing it :)
354 </I>><i>The way to be secure is not to give out the founder password. You could
355 </I>><i>apply the same short sighted reason for a
"/ns set
356 </I>><i>letotherpeopleaccessmynick pass
" request.
358 </I>><i>The founder password is designed to give the channel founder access to
359 </I>><i>manage the ownership of the channel. There is no need to give out the
360 </I>><i>password to anyone, channel management through others is provided via op
363 </I>><i>If for some peculiar reason a channel founder wishes to share the password
364 </I>><i>then IMO that is their problem. The chances are that any user that would
365 </I>><i>require modifying the access list to
"fix
" this, would likely be attempted
366 </I>><i>too late since a rogue user could have merely taken ownership of the
368 ><i>thereby making the option and the founder password redundant and merely
370 ><i>it a problem that administrators waste time on.
372 </I>><i>The founder can already provide access to whatever commands an op needs via
373 </I>><i>levels which is far more secure and already subject to access list
374 </I>><i>restrictions.
376 </I>><i>What function of founder status is required that warrants removing the
377 </I>><i>founder status by supporting sharing of it?
382 </I>><i>------------------------------------------------------------------
383 </I>><i>To unsubscribe or change your subscription options, visit:
384 </I>><i><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
387 /******* - End Original Message - *******/
393 ------------------------------
396 Date: Wed,
14 Apr
2004 09:
42:
30 JST
397 From:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A> (Andrew Church)
398 Subject: Re: RE: RE: [IRCServices] secure Identify Feature..
399 To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>
400 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">407c8f26.04340 at achurch.org
</A>>
401 Content-Type: text/plain; charset=ISO-
2022-JP
403 ><i>Another possible advantage to this command thou.. If for some weird
404 </I>><i>reason, someone finds your channel password, this command would prevent
405 </I>><i>them from doing anything with it, as they would not be able to log on as
406 </I>><i>channel founder (Unless they were on the access list).
408 It's always been my policy not to try and defend against user
409 stupidity;
"build idiot-proof software, and Nature will build a better
410 idiot
"--it's a losing battle. I realize that with the glut of online
411 services these days, it's next to impossible to memorize
"good
", distinct
412 passwords for everything, and I'll admit even I keep my less important
413 passwords stored in an encrypted file on my PC. Nonetheless, the password
414 itself should almost never be needed, since the founder can perform all
415 founder functions (except dropping) by identifying for their nick. If the
416 founder does choose to share the password, e.g. while going on vacation,
417 and said password is abused, as far as I'm concerned that's their fault,
418 and there's nothing Services should do about it.
421 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A>
422 <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
426 ------------------------------
429 Date: Tue,
13 Apr
2004 21:
12:
19 -
0400
430 From:
"David D. Wachtveitl
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">dwachtve at hotmail.com
</A>>
431 Subject: Re: RE: RE: [IRCServices] secure Identify Feature..
432 To:
"IRC Services General Mailing List
"
433 <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>,
"<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>, IRC Services
435 <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>,
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>,
436 <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">Craig at chatspike.net
</A>>
437 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">Sea2-DAV11p0mmhQZiC0002835a at hotmail.com
</A>>
438 Content-Type: text/plain; charset=
"iso-
8859-
1"
440 Also, it would prevent an
"over the shoulder
" viewer of the password the
441 ability to use it. I keep an access mask on my nick ident for this very
442 reason. I think it makes some sense to have this on the channel founder as
443 well (as an option). Of course, if for some reason you are the founder and
444 no longer have access to the mask you set for yourself, you could be sol
448 ----- Original Message -----
449 From:
"Craig McLure
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">Craig at chatspike.net
</A>>
450 To:
"<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>, IRC Services Gene
"
451 <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">,ircservices at ircservices.za.net
</A>>
452 Sent: Tuesday, April
13,
2004 8:
39 PM
453 Subject: Re: RE: RE: [IRCServices] secure Identify Feature..
456 ><i> I read this mail, and read it again, and its absolutly right, with some
457 </I>careful manipulation of the /cs levels command, along with /cs access, you
458 can basically give people 'Founder' privs without them being founder.
459 Another possible advantage to this command thou.. If for some weird reason,
460 someone finds your channel password, this command would prevent them from
461 doing anything with it, as they would not be able to log on as channel
462 founder (Unless they were on the access list). sometimes the distributation
463 of channel passwords may be present when the real founder cant get at the
464 channel for various reasons, and they give the password to the successor, or
465 someone else trustworthy. From where i'm sitting, I cant really see any
466 other real use for this function.
468 </I>><i> /****************************************
469 </I>><i> * Craig
"FrostyCoolSlug
" McLure
470 </I>><i> * InspIRCd -
<A HREF=
"http://www.inspircd.org">http://www.inspircd.org
</A> - REVIVED
471 </I>><i> * ChatSpike -
<A HREF=
"http://www.chatspike.net">http://www.chatspike.net
</A>
472 </I>><i> ****************************************/
475 </I>><i> /****************************************
476 </I>><i> * From - M
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net
</A>>
477 </I>><i> * To - 'IRC Services General Mailing List'
478 </I><<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
479 ><i> * Sent -
2004-
04-
13 23:
08:
45
480 </I>><i> * Subject - RE: RE: [IRCServices] secure Identify Feature..
481 </I>><i> ****************************************/
483 </I>><i> /****** - Begin Original Message - ******/
485 </I>><i> >Craig McLure wrote:
486 </I>><i> >> This command would add things to make the channel more secure
487 </I>><i> >> thou, If you did give the channel founder password to people
488 </I>><i> >> you trust, and you find its being abused, you can simply
489 </I>><i> >> remove that person from the access list, this way you dont
490 </I>><i> >> need to worry about changing the password and re-distributing it :)
492 </I>><i> >The way to be secure is not to give out the founder password. You could
493 </I>><i> >apply the same short sighted reason for a
"/ns set
494 </I>><i> >letotherpeopleaccessmynick pass
" request.
496 </I>><i> >The founder password is designed to give the channel founder access to
497 </I>><i> >manage the ownership of the channel. There is no need to give out the
498 </I>><i> >password to anyone, channel management through others is provided via op
499 </I>><i> >status.
501 </I>><i> >If for some peculiar reason a channel founder wishes to share the
503 ><i> >then IMO that is their problem. The chances are that any user that would
504 </I>><i> >require modifying the access list to
"fix
" this, would likely be
506 ><i> >too late since a rogue user could have merely taken ownership of the
508 ><i> >thereby making the option and the founder password redundant and merely
510 ><i> >it a problem that administrators waste time on.
512 </I>><i> >The founder can already provide access to whatever commands an op needs
514 ><i> >levels which is far more secure and already subject to access list
515 </I>><i> >restrictions.
517 </I>><i> >What function of founder status is required that warrants removing the
518 </I>><i> >founder status by supporting sharing of it?
523 </I>><i> >------------------------------------------------------------------
524 </I>><i> >To unsubscribe or change your subscription options, visit:
525 </I>><i> ><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
528 </I>><i> /******* - End Original Message - *******/
532 </I>><i> ------------------------------------------------------------------
533 </I>><i> To unsubscribe or change your subscription options, visit:
534 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
539 ------------------------------
542 Date: Wed,
14 Apr
2004 10:
42:
57 JST
543 From:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A> (Andrew Church)
544 Subject: Re: RE: RE: [IRCServices] secure Identify Feature..
545 To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>
546 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">407c9775.04373 at achurch.org
</A>>
547 Content-Type: text/plain; charset=ISO-
2022-JP
549 ><i>Also, it would prevent an
"over the shoulder
" viewer of the password the
550 </I>><i>ability to use it. I keep an access mask on my nick ident for this very
551 </I>><i>reason. I think it makes some sense to have this on the channel founder as
552 </I>><i>well (as an option). Of course, if for some reason you are the founder and
553 </I>><i>no longer have access to the mask you set for yourself, you could be sol
556 The same issue applies for nicks, since you can identify regardless of
557 whether you match an access mask or not--unless you set KILL IMMED on your
558 nick, in which case, as you say, you're SOL. The solution is to not let
559 people watch you type your password.
562 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A>
563 <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
567 ------------------------------
570 Date: Tue,
13 Apr
2004 21:
59:
09 -
0400
571 From:
"David D. Wachtveitl
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">dwachtve at hotmail.com
</A>>
572 Subject: Re: RE: RE: [IRCServices] secure Identify Feature..
573 To:
"IRC Services General Mailing List
"
574 <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
575 Message-ID:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">SEA2-DAV6wZKxnEzY0W00010f3c at hotmail.com
</A>>
576 Content-Type: text/plain; charset=
"ISO-
2022-JP
"
578 Well, except on nicks you have the option, on the channel founder you do
579 not, is that not the whole point trying to be made here? In this day and
580 age, it is getting to the point where you can barely go to the bathroom
581 without being
"watched
" in some manner. The real answer would be to crypt
582 the passwords (so they can't be snooped/sniffed) and to not allow them to be
583 seen on the screen. Knowing that is not going to happen, the current
584 suggestion would be a good solution.
588 ----- Original Message -----
589 From:
"Andrew Church
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A>>
590 To:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net
</A>>
591 Sent: Tuesday, April
13,
2004 9:
42 PM
592 Subject: Re: RE: RE: [IRCServices] secure Identify Feature..
595 ><i> >Also, it would prevent an
"over the shoulder
" viewer of the password the
596 </I>><i> >ability to use it. I keep an access mask on my nick ident for this very
597 </I>><i> >reason. I think it makes some sense to have this on the channel founder
599 ><i> >well (as an option). Of course, if for some reason you are the founder
601 ><i> >no longer have access to the mask you set for yourself, you could be sol
602 </I>><i> >also :P
604 </I>><i> The same issue applies for nicks, since you can identify regardless
606 ><i> whether you match an access mask or not--unless you set KILL IMMED on your
607 </I>><i> nick, in which case, as you say, you're SOL. The solution is to not let
608 </I>><i> people watch you type your password.
610 </I>><i> --Andrew Church
611 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A>
612 </I>><i> <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
614 </I>><i> ------------------------------------------------------------------
615 </I>><i> To unsubscribe or change your subscription options, visit:
616 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
621 ------------------------------
623 _______________________________________________
624 IRCServices mailing list
625 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">IRCServices at ircservices.za.net
</A>
626 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
629 End of IRCServices Digest, Vol
16, Issue
6
630 ******************************************
640 <LI>Previous message:
<A HREF=
"004227.html">[IRCServices] secure Identify Feature..
642 <LI>Next message:
<A HREF=
"004229.html">[IRCServices] secure Identify Feature..
644 <LI> <B>Messages sorted by:
</B>
645 <a href=
"date.html#4228">[ date ]
</a>
646 <a href=
"thread.html#4228">[ thread ]
</a>
647 <a href=
"subject.html#4228">[ subject ]
</a>
648 <a href=
"author.html#4228">[ author ]
</a>
projects / irc.git / blob