1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] Suggestion
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&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=
"001638.html">
11 <LINK REL=
"Next" HREF=
"001634.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] Suggestion
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To="
17 TITLE=
"[IRCServices] Suggestion">achurch at achurch.org
19 <I>Mon Mar
19 00:
01:
01 PST
2001</I>
21 <LI>Previous message:
<A HREF=
"001638.html">[IRCServices] Suggestion
23 <LI>Next message:
<A HREF=
"001634.html">[IRCServices] Suggestion
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#1631">[ date ]
</a>
27 <a href=
"thread.html#1631">[ thread ]
</a>
28 <a href=
"subject.html#1631">[ subject ]
</a>
29 <a href=
"author.html#1631">[ author ]
</a>
34 <PRE>>><i>I think it would be nice to see a
"Last modif by
" when useing
"/msg
35 </I>>><i>chanserv access #channel list
".
37 </I>><i> I'm not sure of the value of this compared to the amount of
38 </I>><i>bookkeeping it would take.
40 </I>>><i>And another thing...this is more a question then a suggestion.
41 </I>>><i>We have problems with users takeing others nickname password.
42 </I>>><i>We enforced the use of an email adress when registering a nickname, but
43 </I>>><i>of course, first thing when somebody take a password is to change that
44 </I>>><i>address. So we don't have any sure way to check if the new password goes
45 </I>>><i>to the right address.
47 </I>>><i>And I was thinking...I know it may sound silly...but can we have a
48 </I>>><i>duplicate db with emails that can be changed just by services admins? Or
49 </I>>><i>any other way to secure this thing? Ideas? Suggestions? Thanx a lot.
51 </I>><i> Since users having their passwords taken almost certainly means they
52 </I>><i>chose an easy-to-guess password, the right solution is to educate the
53 </I>><i>users. I don't see why Services should have to run through hoops to try
54 </I>><i>and solve this problem. (Of course, if your server is being
55 </I>><i>packet-sniffed, then you have other problems altogether.)
57 Another thought just occurred to me: since Services logs the
58 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">user at host
</A> mask used to register a nick, you can check your logs for the
59 mask in use when the nick was registered, and compare that with the one
60 in use currently. I do think it would be reasonable to record the E-mail
61 address used with the REGISTER (or SET EMAIL) command, so I'll look into
65 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A> | New address - please note.
66 <A HREF=
"http://achurch.org/">http://achurch.org/
</A> |
メールアドレスが変わりました。
75 <LI>Previous message:
<A HREF=
"001638.html">[IRCServices] Suggestion
77 <LI>Next message:
<A HREF=
"001634.html">[IRCServices] Suggestion
79 <LI> <B>Messages sorted by:
</B>
80 <a href=
"date.html#1631">[ date ]
</a>
81 <a href=
"thread.html#1631">[ thread ]
</a>
82 <a href=
"subject.html#1631">[ subject ]
</a>
83 <a href=
"author.html#1631">[ author ]
</a>