--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [IRCServices] secure Identify Feature..
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20secure%20Identify%20Feature..&In-Reply-To=E1BDWk5-0004J3-HD%40lon1-hub.mail.demon.net">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="004218.html">
+ <LINK REL="Next" HREF="004220.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[IRCServices] secure Identify Feature..</H1>
+ <B>M</B>
+ <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20secure%20Identify%20Feature..&In-Reply-To=E1BDWk5-0004J3-HD%40lon1-hub.mail.demon.net"
+ TITLE="[IRCServices] secure Identify Feature..">mark at ctcp.net
+ </A><BR>
+ <I>Tue Apr 13 16:08:45 PDT 2004</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="004218.html">[IRCServices] secure Identify Feature..
+</A></li>
+ <LI>Next message: <A HREF="004220.html">[IRCServices] secure Identify Feature..
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4219">[ date ]</a>
+ <a href="thread.html#4219">[ thread ]</a>
+ <a href="subject.html#4219">[ subject ]</a>
+ <a href="author.html#4219">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Craig McLure wrote:
+><i> This command would add things to make the channel more secure
+</I>><i> thou, If you did give the channel founder password to people
+</I>><i> you trust, and you find its being abused, you can simply
+</I>><i> remove that person from the access list, this way you dont
+</I>><i> need to worry about changing the password and re-distributing it :)
+</I>
+The way to be secure is not to give out the founder password. You could
+apply the same short sighted reason for a "/ns set
+letotherpeopleaccessmynick pass" request.
+
+The founder password is designed to give the channel founder access to
+manage the ownership of the channel. There is no need to give out the
+password to anyone, channel management through others is provided via op
+status.
+
+If for some peculiar reason a channel founder wishes to share the password
+then IMO that is their problem. The chances are that any user that would
+require modifying the access list to "fix" this, would likely be attempted
+too late since a rogue user could have merely taken ownership of the channel
+thereby making the option and the founder password redundant and merely make
+it a problem that administrators waste time on.
+
+The founder can already provide access to whatever commands an op needs via
+levels which is far more secure and already subject to access list
+restrictions.
+
+What function of founder status is required that warrants removing the
+founder status by supporting sharing of it?
+
+M.
+
+
+
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="004218.html">[IRCServices] secure Identify Feature..
+</A></li>
+ <LI>Next message: <A HREF="004220.html">[IRCServices] secure Identify Feature..
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4219">[ date ]</a>
+ <a href="thread.html#4219">[ thread ]</a>
+ <a href="subject.html#4219">[ subject ]</a>
+ <a href="author.html#4219">[ author ]</a>
+ </LI>
+ </UL>
+
+</body></html>
projects / irc.git / blobdiff