projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
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="> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="002114.html"> | |
| 11 | <LINK REL="Next" HREF="002116.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] 2 feature requests</H1> | |
| 15 | <B>Martin Pels</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%202%20feature%20requests&In-Reply-To=" | |
| 17 | TITLE="[IRCServices Coding] 2 feature requests">martinpels at hotmail.com | |
| 18 | </A><BR> | |
| 19 | <I>Thu Jul 24 03:02:41 PDT 2003</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="002114.html">[IRCServices Coding] Why does IRC Services take mode +r when | |
| 22 | linking to the hub? | |
| 23 | </A></li> | |
| 24 | <LI>Next message: <A HREF="002116.html">[IRCServices Coding] 2 feature requests | |
| 25 | </A></li> | |
| 26 | <LI> <B>Messages sorted by:</B> | |
| 27 | <a href="date.html#2115">[ date ]</a> | |
| 28 | <a href="thread.html#2115">[ thread ]</a> | |
| 29 | <a href="subject.html#2115">[ subject ]</a> | |
| 30 | <a href="author.html#2115">[ author ]</a> | |
| 31 | </LI> | |
| 32 | </UL> | |
| 33 | <HR> | |
| 34 | <!--beginarticle--> | |
| 35 | <PRE>Hello, | |
| 36 | ||
| 37 | On our network we're currently taking a look on how we can make things more | |
| 38 | secure. And while doiung that we came up with a couple of ideas to improve | |
| 39 | IRCServices. | |
| 40 | ||
| 41 | One of the things we did is link all of our servers through SSL, and gave | |
| 42 | clients the option to connect through SSL as well. Now the only thing on our | |
| 43 | net that isn't connected through SSL is Services. | |
| 44 | Are there any plans to add this to IRCServices? I didn't see anything about | |
| 45 | it in the TODO. | |
| 46 | ||
| 47 | The second idea is about the encrypted passwords. As stated in the | |
| 48 | IRCServices documentation SENDPASS and GETPASS won't work with encryption | |
| 49 | enabled because of the way md5 works. | |
| 50 | This introduces the problem that users will have to contact an Oper in case | |
| 51 | they lose their password. | |
| 52 | Would it be possible to, when encryption is enabled, change the behaviour of | |
| 53 | SENDPASS so that it won't send the user's password (because this is not | |
| 54 | possible), but generate a new random password for the user and send that to | |
| 55 | the user's e-mail address instead? | |
| 56 | ||
| 57 | Grtz, | |
| 58 | Rodecker | |
| 59 | </PRE> | |
| 60 | ||
| 61 | <!--endarticle--> | |
| 62 | <HR> | |
| 63 | <P><UL> | |
| 64 | <!--threads--> | |
| 65 | <LI>Previous message: <A HREF="002114.html">[IRCServices Coding] Why does IRC Services take mode +r when | |
| 66 | linking to the hub? | |
| 67 | </A></li> | |
| 68 | <LI>Next message: <A HREF="002116.html">[IRCServices Coding] 2 feature requests | |
| 69 | </A></li> | |
| 70 | <LI> <B>Messages sorted by:</B> | |
| 71 | <a href="date.html#2115">[ date ]</a> | |
| 72 | <a href="thread.html#2115">[ thread ]</a> | |
| 73 | <a href="subject.html#2115">[ subject ]</a> | |
| 74 | <a href="author.html#2115">[ author ]</a> | |
| 75 | </LI> | |
| 76 | </UL> | |
| 77 | ||
| 78 | </body></html> |