]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002790.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2002 / 002790.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Services 4.5.39 released
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%204.5.39%20released&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="002791.html">
11 <LINK REL="Next" HREF="002792.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Services 4.5.39 released</H1>
15 <B>Andrew Church</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%204.5.39%20released&In-Reply-To="
17 TITLE="[IRCServices] Services 4.5.39 released">achurch at achurch.org
18 </A><BR>
19 <I>Wed Feb 27 14:29:00 PST 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="002791.html">[IRCServices] README Question
22 </A></li>
23 <LI>Next message: <A HREF="002792.html">[IRCServices] How can it be?? (4.5.38)
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#2790">[ date ]</a>
27 <a href="thread.html#2790">[ thread ]</a>
28 <a href="subject.html#2790">[ subject ]</a>
29 <a href="author.html#2790">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE> Services 4.5.39 has been released, and can be downloaded from:
35
36 <A HREF="ftp://ftp.esper.net/ircservices/ircservices-4.5.39.tar.gz">ftp://ftp.esper.net/ircservices/ircservices-4.5.39.tar.gz</A>
37 <A HREF="ftp://ftp.esper.net/ircservices/ircservices-4.5.39.diff.gz">ftp://ftp.esper.net/ircservices/ircservices-4.5.39.diff.gz</A>
38
39 ftp.ircservices.za.net and the mirrors should have it shortly.
40
41 This release fixes a minor security issue with MemoServ, which could
42 allow a user to receive new-memo messages for another user without needing
43 to identify or be on a nickname access list; in particular, if the other
44 user has two or more nicks linked together, then a malicious user could use
45 one of the nicks and receive notices from MemoServ when memos were sent to
46 the other user (the real nickname owner), because MemoServ failed to check
47 that the user was recognized (on the access list) or identified before
48 sending the notice. While such malicious users could not actually read the
49 memos, they could find out who was sending them, which could be considered
50 an invasion of privacy; therefore, I recommend upgrading at your earliest
51 convenience.
52
53 And yes, work on Services 5.0 is progressing. I should have a beta
54 out any day now, if people would just stop finding new bugs... ;)
55
56 Changes in version 4.5.39
57 -------------------------
58 2002/02/27 Fixed minor security hole allowing users to find out when
59 nicknames not their own receive memos.
60 2002/02/15 Fixed ChanServ LIST syntax error message for Services
61 admins. Reported by Mark Hetherington &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">mark at ctcp.net</A>&gt;
62
63 --Andrew Church
64 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
65 <A HREF="http://achurch.org/">http://achurch.org/</A>
66
67 </PRE>
68
69 <!--endarticle-->
70 <HR>
71 <P><UL>
72 <!--threads-->
73 <LI>Previous message: <A HREF="002791.html">[IRCServices] README Question
74 </A></li>
75 <LI>Next message: <A HREF="002792.html">[IRCServices] How can it be?? (4.5.38)
76 </A></li>
77 <LI> <B>Messages sorted by:</B>
78 <a href="date.html#2790">[ date ]</a>
79 <a href="thread.html#2790">[ thread ]</a>
80 <a href="subject.html#2790">[ subject ]</a>
81 <a href="author.html#2790">[ author ]</a>
82 </LI>
83 </UL>
84
85 </body></html>