]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] Panic / Segmentation fault? | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Panic%20/%20Segmentation%20fault%3F&In-Reply-To=E14JMhx-0003T6-00%40gadolinium.btinternet.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="001123.html"> | |
11 | <LINK REL="Next" HREF="001131.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] Panic / Segmentation fault?</H1> | |
15 | <B>ben at desync.com</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Panic%20/%20Segmentation%20fault%3F&In-Reply-To=E14JMhx-0003T6-00%40gadolinium.btinternet.com" | |
17 | TITLE="[IRCServices] Panic / Segmentation fault?">ben at desync.com | |
18 | </A><BR> | |
19 | <I>Thu Jan 18 18:29:32 PST 2001</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001123.html">[IRCServices] Panic / Segmentation fault? | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001131.html">[IRCServices] Panic / Segmentation fault? | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1127">[ date ]</a> | |
27 | <a href="thread.html#1127">[ thread ]</a> | |
28 | <a href="subject.html#1127">[ subject ]</a> | |
29 | <a href="author.html#1127">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>On Thu, Jan 18, 2001 at 09:31:52PM -0000, Dr. K. Hawkes wrote: | |
35 | ><i> I must say this is a bad idea for DB's with unencrypted passwords, but | |
36 | </I>><i> apart from that I like that idea, would save me alot of pain and worry, my | |
37 | </I>><i> backups are a cron'd FTP to a remote location. Although for some odd | |
38 | </I>><i> reason, the DB's don't like going to the remote location and seem | |
39 | </I>><i> corrupted, this is being worked on ATM. | |
40 | </I> | |
41 | "Oh no someone will get the passwords" shouldn't be a valid concern since anyone with access to the DBs can do that whether they're plain text or not. Maybe secure your files instead? | |
42 | ||
43 | ><i> Just my 0.2p. | |
44 | </I>><i> | |
45 | </I>><i> Quinn | |
46 | </I> | |
47 | -ben | |
48 | ||
49 | ||
50 | ||
51 | </PRE> | |
52 | ||
53 | <!--endarticle--> | |
54 | <HR> | |
55 | <P><UL> | |
56 | <!--threads--> | |
57 | <LI>Previous message: <A HREF="001123.html">[IRCServices] Panic / Segmentation fault? | |
58 | </A></li> | |
59 | <LI>Next message: <A HREF="001131.html">[IRCServices] Panic / Segmentation fault? | |
60 | </A></li> | |
61 | <LI> <B>Messages sorted by:</B> | |
62 | <a href="date.html#1127">[ date ]</a> | |
63 | <a href="thread.html#1127">[ thread ]</a> | |
64 | <a href="subject.html#1127">[ subject ]</a> | |
65 | <a href="author.html#1127">[ author ]</a> | |
66 | </LI> | |
67 | </UL> | |
68 | ||
69 | </body></html> |