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] secure Identify Feature.. | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20secure%20Identify%20Feature..&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="004220.html"> | |
| 11 | <LINK REL="Next" HREF="004223.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices] secure Identify Feature..</H1> | |
| 15 | <B>David D. Wachtveitl</B> | |
| 16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20secure%20Identify%20Feature..&In-Reply-To=" | |
| 17 | TITLE="[IRCServices] secure Identify Feature..">dwachtve at hotmail.com | |
| 18 | </A><BR> | |
| 19 | <I>Tue Apr 13 18:12:19 PDT 2004</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="004220.html">[IRCServices] secure Identify Feature.. | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="004223.html">[IRCServices] secure Identify Feature.. | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#4222">[ date ]</a> | |
| 27 | <a href="thread.html#4222">[ thread ]</a> | |
| 28 | <a href="subject.html#4222">[ subject ]</a> | |
| 29 | <a href="author.html#4222">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>Also, it would prevent an "over the shoulder" viewer of the password the | |
| 35 | ability to use it. I keep an access mask on my nick ident for this very | |
| 36 | reason. I think it makes some sense to have this on the channel founder as | |
| 37 | well (as an option). Of course, if for some reason you are the founder and | |
| 38 | no longer have access to the mask you set for yourself, you could be sol | |
| 39 | also :P | |
| 40 | ||
| 41 | ||
| 42 | ----- Original Message ----- | |
| 43 | From: "Craig McLure" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">Craig at chatspike.net</A>> | |
| 44 | To: "<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net</A>, IRC Services Gene" | |
| 45 | <<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>> | |
| 46 | Sent: Tuesday, April 13, 2004 8:39 PM | |
| 47 | Subject: Re: RE: RE: [IRCServices] secure Identify Feature.. | |
| 48 | ||
| 49 | ||
| 50 | ><i> I read this mail, and read it again, and its absolutly right, with some | |
| 51 | </I>careful manipulation of the /cs levels command, along with /cs access, you | |
| 52 | can basically give people 'Founder' privs without them being founder. | |
| 53 | Another possible advantage to this command thou.. If for some weird reason, | |
| 54 | someone finds your channel password, this command would prevent them from | |
| 55 | doing anything with it, as they would not be able to log on as channel | |
| 56 | founder (Unless they were on the access list). sometimes the distributation | |
| 57 | of channel passwords may be present when the real founder cant get at the | |
| 58 | channel for various reasons, and they give the password to the successor, or | |
| 59 | someone else trustworthy. From where i'm sitting, I cant really see any | |
| 60 | other real use for this function. | |
| 61 | ><i> | |
| 62 | </I>><i> /**************************************** | |
| 63 | </I>><i> * Craig "FrostyCoolSlug" McLure | |
| 64 | </I>><i> * InspIRCd - <A HREF="http://www.inspircd.org">http://www.inspircd.org</A> - REVIVED | |
| 65 | </I>><i> * ChatSpike - <A HREF="http://www.chatspike.net">http://www.chatspike.net</A> | |
| 66 | </I>><i> ****************************************/ | |
| 67 | </I>><i> | |
| 68 | </I>><i> | |
| 69 | </I>><i> /**************************************** | |
| 70 | </I>><i> * From - M <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net</A>> | |
| 71 | </I>><i> * To - 'IRC Services General Mailing List' | |
| 72 | </I><<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>> | |
| 73 | ><i> * Sent - 2004-04-13 23:08:45 | |
| 74 | </I>><i> * Subject - RE: RE: [IRCServices] secure Identify Feature.. | |
| 75 | </I>><i> ****************************************/ | |
| 76 | </I>><i> | |
| 77 | </I>><i> /****** - Begin Original Message - ******/ | |
| 78 | </I>><i> | |
| 79 | </I>><i> >Craig McLure wrote: | |
| 80 | </I>><i> >> This command would add things to make the channel more secure | |
| 81 | </I>><i> >> thou, If you did give the channel founder password to people | |
| 82 | </I>><i> >> you trust, and you find its being abused, you can simply | |
| 83 | </I>><i> >> remove that person from the access list, this way you dont | |
| 84 | </I>><i> >> need to worry about changing the password and re-distributing it :) | |
| 85 | </I>><i> > | |
| 86 | </I>><i> >The way to be secure is not to give out the founder password. You could | |
| 87 | </I>><i> >apply the same short sighted reason for a "/ns set | |
| 88 | </I>><i> >letotherpeopleaccessmynick pass" request. | |
| 89 | </I>><i> > | |
| 90 | </I>><i> >The founder password is designed to give the channel founder access to | |
| 91 | </I>><i> >manage the ownership of the channel. There is no need to give out the | |
| 92 | </I>><i> >password to anyone, channel management through others is provided via op | |
| 93 | </I>><i> >status. | |
| 94 | </I>><i> > | |
| 95 | </I>><i> >If for some peculiar reason a channel founder wishes to share the | |
| 96 | </I>password | |
| 97 | ><i> >then IMO that is their problem. The chances are that any user that would | |
| 98 | </I>><i> >require modifying the access list to "fix" this, would likely be | |
| 99 | </I>attempted | |
| 100 | ><i> >too late since a rogue user could have merely taken ownership of the | |
| 101 | </I>channel | |
| 102 | ><i> >thereby making the option and the founder password redundant and merely | |
| 103 | </I>make | |
| 104 | ><i> >it a problem that administrators waste time on. | |
| 105 | </I>><i> > | |
| 106 | </I>><i> >The founder can already provide access to whatever commands an op needs | |
| 107 | </I>via | |
| 108 | ><i> >levels which is far more secure and already subject to access list | |
| 109 | </I>><i> >restrictions. | |
| 110 | </I>><i> > | |
| 111 | </I>><i> >What function of founder status is required that warrants removing the | |
| 112 | </I>><i> >founder status by supporting sharing of it? | |
| 113 | </I>><i> > | |
| 114 | </I>><i> >M. | |
| 115 | </I>><i> > | |
| 116 | </I>><i> > | |
| 117 | </I>><i> >------------------------------------------------------------------ | |
| 118 | </I>><i> >To unsubscribe or change your subscription options, visit: | |
| 119 | </I>><i> ><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
| 120 | </I>><i> >. | |
| 121 | </I>><i> | |
| 122 | </I>><i> /******* - End Original Message - *******/ | |
| 123 | </I>><i> | |
| 124 | </I>><i> | |
| 125 | </I>><i> | |
| 126 | </I>><i> ------------------------------------------------------------------ | |
| 127 | </I>><i> To unsubscribe or change your subscription options, visit: | |
| 128 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
| 129 | </I>><i> | |
| 130 | </I> | |
| 131 | ||
| 132 | </PRE> | |
| 133 | ||
| 134 | <!--endarticle--> | |
| 135 | <HR> | |
| 136 | <P><UL> | |
| 137 | <!--threads--> | |
| 138 | <LI>Previous message: <A HREF="004220.html">[IRCServices] secure Identify Feature.. | |
| 139 | </A></li> | |
| 140 | <LI>Next message: <A HREF="004223.html">[IRCServices] secure Identify Feature.. | |
| 141 | </A></li> | |
| 142 | <LI> <B>Messages sorted by:</B> | |
| 143 | <a href="date.html#4222">[ date ]</a> | |
| 144 | <a href="thread.html#4222">[ thread ]</a> | |
| 145 | <a href="subject.html#4222">[ subject ]</a> | |
| 146 | <a href="author.html#4222">[ author ]</a> | |
| 147 | </LI> | |
| 148 | </UL> | |
| 149 | ||
| 150 | </body></html> |