]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] Problems With TimeStamping On Bahamut-1.4.23 | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Problems%20With%20TimeStamping%20On%20Bahamut-1.4.23&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="001913.html"> | |
11 | <LINK REL="Next" HREF="001915.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] Problems With TimeStamping On Bahamut-1.4.23</H1> | |
15 | <B>Andrew Church</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Problems%20With%20TimeStamping%20On%20Bahamut-1.4.23&In-Reply-To=" | |
17 | TITLE="[IRCServices] Problems With TimeStamping On Bahamut-1.4.23">achurch at achurch.org | |
18 | </A><BR> | |
19 | <I>Sat May 26 04:40:03 PDT 2001</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001913.html">[IRCServices] Timestamping | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001915.html">[IRCServices] Problems With TimeStamping On Bahamut-1.4.23 | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1914">[ date ]</a> | |
27 | <a href="thread.html#1914">[ thread ]</a> | |
28 | <a href="subject.html#1914">[ subject ]</a> | |
29 | <a href="author.html#1914">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>><i>As i believe how services timestamping works, is that if services go = | |
35 | </I>><i>down, for say, an upgrade, when they come back a few minutes later, they = | |
36 | </I>><i>shouldnt ask for a password, | |
37 | </I> | |
38 | This is wrong. If a server on the network splits and comes back, | |
39 | users will not be asked to re-identify; however, if Services itself goes | |
40 | down, all timestamp information is lost. Securely recording timestamp | |
41 | information is a difficult task, and I will not be adding such a feature | |
42 | to Services. | |
43 | ||
44 | --Andrew Church | |
45 | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
46 | <A HREF="http://achurch.org/">http://achurch.org/</A> | |
47 | ||
48 | </PRE> | |
49 | ||
50 | <!--endarticle--> | |
51 | <HR> | |
52 | <P><UL> | |
53 | <!--threads--> | |
54 | <LI>Previous message: <A HREF="001913.html">[IRCServices] Timestamping | |
55 | </A></li> | |
56 | <LI>Next message: <A HREF="001915.html">[IRCServices] Problems With TimeStamping On Bahamut-1.4.23 | |
57 | </A></li> | |
58 | <LI> <B>Messages sorted by:</B> | |
59 | <a href="date.html#1914">[ date ]</a> | |
60 | <a href="thread.html#1914">[ thread ]</a> | |
61 | <a href="subject.html#1914">[ subject ]</a> | |
62 | <a href="author.html#1914">[ author ]</a> | |
63 | </LI> | |
64 | </UL> | |
65 | ||
66 | </body></html> |