]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/002121.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2003 / 002121.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] 2 feature requests
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%202%20feature%20requests&In-Reply-To=BAY8-DAV26ZaendgjvM0000135e%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="002117.html">
11 <LINK REL="Next" HREF="002118.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] 2 feature requests</H1>
15 <B>Andrew Church</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%202%20feature%20requests&In-Reply-To=BAY8-DAV26ZaendgjvM0000135e%40hotmail.com"
17 TITLE="[IRCServices Coding] 2 feature requests">achurch at achurch.org
18 </A><BR>
19 <I>Fri Jul 25 22:25:58 PDT 2003</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="002117.html">[IRCServices Coding] 2 feature requests
22 </A></li>
23 <LI>Next message: <A HREF="002118.html">[IRCServices Coding] 2 feature requests
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#2121">[ date ]</a>
27 <a href="thread.html#2121">[ thread ]</a>
28 <a href="subject.html#2121">[ subject ]</a>
29 <a href="author.html#2121">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE> I'm not seriously considering SSL because I assume that if you're
35 running Services and the ircd on separate machines, it's because you don't
36 have enough CPU power to run them both, and adding SSL processing wouldn't
37 help that condition. If you do want to encrypt the data, I'd assume you
38 could use tunnelling software to do it. (Poor man's tunnel:
39 ssh -L localport:remotehost:remoteport remotehost)
40
41 The suggestion of making SENDPASS generate a new password has been
42 suggested before, and I'm considering it as a possibility for 5.1.
43
44 --Andrew Church
45 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
46 <A HREF="http://achurch.org/">http://achurch.org/</A>
47
48 &gt;<i>Hello,
49 </I>&gt;<i>
50 </I>&gt;<i>On our network we're currently taking a look on how we can make things more
51 </I>&gt;<i>secure. And while doiung that we came up with a couple of ideas to improve
52 </I>&gt;<i>IRCServices.
53 </I>&gt;<i>
54 </I>&gt;<i>One of the things we did is link all of our servers through SSL, and gave
55 </I>&gt;<i>clients the option to connect through SSL as well. Now the only thing on our
56 </I>&gt;<i>net that isn't connected through SSL is Services.
57 </I>&gt;<i>Are there any plans to add this to IRCServices? I didn't see anything about
58 </I>&gt;<i>it in the TODO.
59 </I>&gt;<i>
60 </I>&gt;<i>The second idea is about the encrypted passwords. As stated in the
61 </I>&gt;<i>IRCServices documentation SENDPASS and GETPASS won't work with encryption
62 </I>&gt;<i>enabled because of the way md5 works.
63 </I>&gt;<i>This introduces the problem that users will have to contact an Oper in case
64 </I>&gt;<i>they lose their password.
65 </I>&gt;<i>Would it be possible to, when encryption is enabled, change the behaviour of
66 </I>&gt;<i>SENDPASS so that it won't send the user's password (because this is not
67 </I>&gt;<i>possible), but generate a new random password for the user and send that to
68 </I>&gt;<i>the user's e-mail address instead?
69 </I>&gt;<i>
70 </I>&gt;<i>Grtz,
71 </I>&gt;<i>Rodecker
72 </I>&gt;<i>------------------------------------------------------------------
73 </I>&gt;<i>To unsubscribe or change your subscription options, visit:
74 </I>&gt;<i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
75 </I></PRE>
76
77 <!--endarticle-->
78 <HR>
79 <P><UL>
80 <!--threads-->
81 <LI>Previous message: <A HREF="002117.html">[IRCServices Coding] 2 feature requests
82 </A></li>
83 <LI>Next message: <A HREF="002118.html">[IRCServices Coding] 2 feature requests
84 </A></li>
85 <LI> <B>Messages sorted by:</B>
86 <a href="date.html#2121">[ date ]</a>
87 <a href="thread.html#2121">[ thread ]</a>
88 <a href="subject.html#2121">[ subject ]</a>
89 <a href="author.html#2121">[ author ]</a>
90 </LI>
91 </UL>
92
93 </body></html>