software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001491.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Re: While talking about NickServ...
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Re%3A%20While%20talking%20about%20NickServ...&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="001490.html">
  11    <LINK REL="Next"  HREF="001492.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Re: While talking about NickServ...</H1>
  15     <B>Countersync of AGNPH (and #agnph)</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Re%3A%20While%20talking%20about%20NickServ...&In-Reply-To="
  17        TITLE="[IRCServices] Re: While talking about NickServ...">countersync at hotmail.com
  18        </A><BR>
  19     <I>Sat Feb 24 14:16:01 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001490.html">[IRCServices] Re: While talking about NickServ...
  22 </A></li>
  23         <LI>Next message: <A HREF="001492.html">AW: [IRCServices] Re: While talking about NickServ...
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1491">[ date ]</a>
  27               <a href="thread.html#1491">[ thread ]</a>
  28               <a href="subject.html#1491">[ subject ]</a>
  29               <a href="author.html#1491">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>From: &quot;Lonewolf&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">lonewolf at lagnet.org.za</A>&gt;
  35 &gt;<i> On Fri, Feb 23, 2001 at 11:09:29PM -0800, Countersync of AGNPH (and
  36 </I>#agnph) wrote:
  37 &gt;<i> &gt; Please do not forget that it is rare for a user to hide their email
  38 </I>&gt;<i> &gt; address.
  39 </I>&gt;<i>
  40 </I>&gt;<i> Set &quot;NSDefHideEmail&quot; in your services.conf file.  This stops the
  41 </I>&gt;<i> possibility of would-be spammers from harvesting e-mail addresses from
  42 </I>&gt;<i> your NickServ database too.
  43 </I>&gt;<i>
  44 </I>&gt;<i> &gt; Especially if they actually want to be contacted.  Perhaps the
  45 </I>&gt;<i> &gt; addition of a 'secure' email address that the user is instructed to
  46 </I>&gt;<i> &gt; set and not to share anywhere else is a good idea?
  47 </I>&gt;<i>
  48 </I>&gt;<i> Seems a terrible fiddle to add _another_ e-mail address; bound to
  49 </I>&gt;<i> confuse most users too.  If they want to be contacted, they should set
  50 </I>&gt;<i> their NickServ URL to a web page which has their preferred contact
  51 </I>&gt;<i> details.
  52 </I>
  53 Actually, I was suggesting it as a way to limit confusion.  If they know
  54 that the address is to be used explicitly for the secure return of their
  55 passwords they are less likely to compromise their own security.  The fact
  56 is that a user may want to keep an email address public.  This would allow
  57 the user to have their current (and probably known) email address under the
  58 old system, and a new address just for nickserv to send their password to.
  59 Leaving it blank would automatically make nickserv use the other mailing
  60 address, and leaving both blank would disable the feature.  Or at least,
  61 that sounds like the most simple way of setting it up to me.
  62
  63 Additionally were the services to have some type of split key encryption
  64 module in the future the entry could be encoded with the public key, and
  65 only decoded with the services private key.  It's still almost as vulnerable
  66 to attack as the other methods, but if services had a separate account on
  67 the same, or different server who's files might not be compromised by an
  68 attack it could provide just slightly more security.  It is a bit complex
  69 for the small increase.  Especially since root could likely read both the
  70 private key and pass, thus separating the services and protecting root
  71 security would be big concerns.
  72
  73
  74
  75 </PRE>
  76
  77 <!--endarticle-->
  78     <HR>
  79     <P><UL>
  80         <!--threads-->
  81         <LI>Previous message: <A HREF="001490.html">[IRCServices] Re: While talking about NickServ...
  82 </A></li>
  83         <LI>Next message: <A HREF="001492.html">AW: [IRCServices] Re: While talking about NickServ...
  84 </A></li>
  85          <LI> <B>Messages sorted by:</B>
  86               <a href="date.html#1491">[ date ]</a>
  87               <a href="thread.html#1491">[ thread ]</a>
  88               <a href="subject.html#1491">[ subject ]</a>
  89               <a href="author.html#1491">[ author ]</a>
  90          </LI>
  91        </UL>
  92
  93 </body></html>