]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices Coding] SENDPASS with encryption... | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20SENDPASS%20with%20encryption...&In-Reply-To=BAY8-DAV4556jq2qmlM0001ae7a%40hotmail.com"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="002879.html"> | |
11 | <LINK REL="Next" HREF="002878.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices Coding] SENDPASS with encryption...</H1> | |
15 | <B>Aragon Gouveia</B> | |
16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20SENDPASS%20with%20encryption...&In-Reply-To=BAY8-DAV4556jq2qmlM0001ae7a%40hotmail.com" | |
17 | TITLE="[IRCServices Coding] SENDPASS with encryption...">aragon at phat.za.net | |
18 | </A><BR> | |
19 | <I>Wed Feb 4 13:08:25 PST 2004</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="002879.html">[IRCServices Coding] SENDPASS with encryption... | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="002878.html">[IRCServices Coding] SENDPASS with encryption... | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#2880">[ date ]</a> | |
27 | <a href="thread.html#2880">[ thread ]</a> | |
28 | <a href="subject.html#2880">[ subject ]</a> | |
29 | <a href="author.html#2880">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Or why not just email some kind of random unique cookie which is then msg'd | |
35 | to nickserv to reset and obtain the new password. Kinda like the auth | |
36 | system for authorising new registrations... | |
37 | ||
38 | That'll also take care of the insecure nature of emailing passwords. More | |
39 | and more ircds are supporting ssl client connections. Getting the new | |
40 | password over irc is favourable in that regard. | |
41 | ||
42 | ||
43 | Regards, | |
44 | Aragon | |
45 | ||
46 | ||
47 | |<i> By Martin Pels <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">martinpels at hotmail.com</A>> | |
48 | </I>|<i> [ 2004-02-04 22:54 +0200 ] | |
49 | </I>><i> I'm looking forward to this module. It is what kept us from switching to | |
50 | </I>><i> encrypted passwords. | |
51 | </I>><i> | |
52 | </I>><i> Here's some ideas on the abuse problem: | |
53 | </I>><i> * Only allow usage of the command from hosts that are in the nickname's | |
54 | </I>><i> accesslist | |
55 | </I>><i> * Send the nick!<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">user at host</A> of the user that issued the command in the E-mail | |
56 | </I>><i> (it won't prevent abuse, but at least you'll know who's been playing around) | |
57 | </I>><i> * Give a notice to services operators/admins each time the command is issued | |
58 | </I>><i> * Limit the amount of times the command can be used successively | |
59 | </I>><i> | |
60 | </I>><i> Hope this helps. | |
61 | </I>><i> | |
62 | </I>><i> Grtz, | |
63 | </I>><i> Martin | |
64 | </I>><i> | |
65 | </I>><i> ----- Original Message ----- | |
66 | </I>><i> From: "Craig McLure" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">Craig at chatspike.net</A>> | |
67 | </I>><i> To: "ircservices-coding" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>> | |
68 | </I>><i> Sent: Wednesday, February 04, 2004 4:47 PM | |
69 | </I>><i> Subject: [IRCServices Coding] SENDPASS with encryption... | |
70 | </I>><i> | |
71 | </I>><i> | |
72 | </I>><i> > I've been working on a module that allows use of sendpass whilst using | |
73 | </I>><i> encrypted passwords (i'll contribute the source to Andy when complete for | |
74 | </I>><i> inclusion in services), it will work by changing the users password, and | |
75 | </I>><i> mailing them that.. but i cant find around other users using it miliciously | |
76 | </I>><i> to aggrovate others.. | |
77 | </I>><i> > | |
78 | </I>><i> > anyone got any idea on how this can be resolved? thanks :) | |
79 | </I>><i> > | |
80 | </I>><i> > /**************************************** | |
81 | </I>><i> > * Craig "FrostyCoolSlug" McLure | |
82 | </I>><i> > * InspIRCd - <A HREF="http://www.inspircd.org">http://www.inspircd.org</A> | |
83 | </I>><i> > * ChatSpike - <A HREF="http://www.chatspike.net">http://www.chatspike.net</A> | |
84 | </I>><i> > ****************************************/ | |
85 | </I>><i> > | |
86 | </I>><i> > ------------------------------------------------------------------ | |
87 | </I>><i> > To unsubscribe or change your subscription options, visit: | |
88 | </I>><i> > <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
89 | </I>><i> > | |
90 | </I>><i> ------------------------------------------------------------------ | |
91 | </I>><i> To unsubscribe or change your subscription options, visit: | |
92 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
93 | </I> | |
94 | </PRE> | |
95 | ||
96 | <!--endarticle--> | |
97 | <HR> | |
98 | <P><UL> | |
99 | <!--threads--> | |
100 | <LI>Previous message: <A HREF="002879.html">[IRCServices Coding] SENDPASS with encryption... | |
101 | </A></li> | |
102 | <LI>Next message: <A HREF="002878.html">[IRCServices Coding] SENDPASS with encryption... | |
103 | </A></li> | |
104 | <LI> <B>Messages sorted by:</B> | |
105 | <a href="date.html#2880">[ date ]</a> | |
106 | <a href="thread.html#2880">[ thread ]</a> | |
107 | <a href="subject.html#2880">[ subject ]</a> | |
108 | <a href="author.html#2880">[ author ]</a> | |
109 | </LI> | |
110 | </UL> | |
111 | ||
112 | </body></html> |