software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/002433.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Query on ChanServ/Nickserv behavior
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Query%20on%20ChanServ/Nickserv%20behavior&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="002429.html">
  11    <LINK REL="Next"  HREF="002434.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Query on ChanServ/Nickserv behavior</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Query%20on%20ChanServ/Nickserv%20behavior&In-Reply-To="
  17        TITLE="[IRCServices] Query on ChanServ/Nickserv behavior">achurch at achurch.org
  18        </A><BR>
  19     <I>Fri Nov  2 04:24:00 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002429.html">[IRCServices] Query on ChanServ/Nickserv behavior
  22 </A></li>
  23         <LI>Next message: <A HREF="002434.html">[IRCServices] Query on ChanServ/Nickserv behavior
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2433">[ date ]</a>
  27               <a href="thread.html#2433">[ thread ]</a>
  28               <a href="subject.html#2433">[ subject ]</a>
  29               <a href="author.html#2433">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;&gt;<i>I find this behavior rather odd.  Am I misunderstanding the purpose of
  35 </I>&gt;&gt;<i>being able to turn Secure off for NickServ?  The Help states &quot;with SECURE
  36 </I>&gt;&gt;<i>set, you must enter your password before you will be recognized as the
  37 </I>&gt;&gt;<i>owner of the nick, regardless of whether your address is on the access
  38 </I>&gt;&gt;<i>list.&quot;  This implies to me that if SECURE is NOT set, then NickServ will
  39 </I>&gt;&gt;<i>examine the access list and, if it should find a match, let ChanServ know
  40 </I>&gt;&gt;<i>that you're okay to op as you've been &quot;implicitly identified.&quot;
  41 </I>
  42      It sounds like the channel has SECURE set; this overrides nickname
  43 SECURE settings (for that channel) and requires an IDENTIFY whether or
  44 not the nickname has SECURE set.
  45
  46 &gt;<i>Related to this, I'd rather like an option to be opped on my channels
  47 </I>&gt;<i>as soon as I *have* identified, rather than having to issue OP
  48 </I>&gt;<i>commands just because the JOIN command beat my IDENTIFY command
  49 </I>&gt;<i>through the post.
  50 </I>
  51      This has been requested by a number of people and is being considered.
  52 (On the other hand, as long as you send /ns identify first this won't be a
  53 problem...)
  54
  55   --Andrew Church
  56     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
  57     <A HREF="http://achurch.org/">http://achurch.org/</A>
  58
  59 </PRE>
  60
  61 <!--endarticle-->
  62     <HR>
  63     <P><UL>
  64         <!--threads-->
  65         <LI>Previous message: <A HREF="002429.html">[IRCServices] Query on ChanServ/Nickserv behavior
  66 </A></li>
  67         <LI>Next message: <A HREF="002434.html">[IRCServices] Query on ChanServ/Nickserv behavior
  68 </A></li>
  69          <LI> <B>Messages sorted by:</B>
  70               <a href="date.html#2433">[ date ]</a>
  71               <a href="thread.html#2433">[ thread ]</a>
  72               <a href="subject.html#2433">[ subject ]</a>
  73               <a href="author.html#2433">[ author ]</a>
  74          </LI>
  75        </UL>
  76
  77 </body></html>