software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2004/002864.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Re: IRCServices-Coding Digest, Vol 12, Issue 7
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Re%3A%20IRCServices-Coding%20Digest%2C%20Vol%2012%2C%20Issue%207&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="002863.html">
  11    <LINK REL="Next"  HREF="002865.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Re: IRCServices-Coding Digest, Vol 12, Issue 7</H1>
  15     <B>Craig Edwards</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Re%3A%20IRCServices-Coding%20Digest%2C%20Vol%2012%2C%20Issue%207&In-Reply-To="
  17        TITLE="[IRCServices Coding] Re: IRCServices-Coding Digest, Vol 12, Issue 7">brain at brainbox.winbot.co.uk
  18        </A><BR>
  19     <I>Sat Jan 10 07:11:13 PST 2004</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="002863.html">[IRCServices Coding] feature: nickserv high security
  22 </A></li>
  23         <LI>Next message: <A HREF="002865.html">[IRCServices Coding] feature: nickserv high security
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#2864">[ date ]</a>
  27               <a href="thread.html#2864">[ thread ]</a>
  28               <a href="subject.html#2864">[ subject ]</a>
  29               <a href="author.html#2864">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Apart from the still getting killed bit, &quot;/ns set kill immed&quot; will do this.
  35
  36 &gt;&gt;<i>Here's another idea that might be useful:
  37 </I>&gt;&gt;<i>Having an additional tag for nickserv set secure, (like &quot;high&quot; or some other name), meaning increased security regulations applied according to which you may only use INDETIFY command if you match an entry from the nickserv access list.
  38 </I>&gt;&gt;<i>Possibly also that under this feature you will still get killed (if set) even if matching an entry in the access list.
  39 </I>&gt;&gt;<i>This should be similar to the hostmask directive under the o:line some ircd's have.
  40 </I>&gt;&gt;<i>
  41 </I>&gt;&gt;<i>PHANTOm
  42 </I>&gt;&gt;<i>
  43 </I>&gt;&gt;<i>
  44 </I>&gt;<i>So, how do you propose people identify to change the access list?
  45 </I>&gt;<i>Say(like charter likes to do to me), your 'static' ip changes.
  46 </I>
  47
  48
  49
  50 </PRE>
  51
  52 <!--endarticle-->
  53     <HR>
  54     <P><UL>
  55         <!--threads-->
  56         <LI>Previous message: <A HREF="002863.html">[IRCServices Coding] feature: nickserv high security
  57 </A></li>
  58         <LI>Next message: <A HREF="002865.html">[IRCServices Coding] feature: nickserv high security
  59 </A></li>
  60          <LI> <B>Messages sorted by:</B>
  61               <a href="date.html#2864">[ date ]</a>
  62               <a href="thread.html#2864">[ thread ]</a>
  63               <a href="subject.html#2864">[ subject ]</a>
  64               <a href="author.html#2864">[ author ]</a>
  65          </LI>
  66        </UL>
  67
  68 </body></html>