forked from shupp/VegaDNS
-
Notifications
You must be signed in to change notification settings - Fork 0
/
UPGRADE
73 lines (36 loc) · 2.32 KB
/
UPGRADE
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
** UPGRADING FROM 0.11.2 OR LOWER PLEASE READ ** 4/4/2013
You SHOULD run the ALTER statements in records_update.sql:
mysql -u <user> -p<pass> <db_name> < records_update.sql
These provide even longer `val` columns for things like SPF/TXT records
** UPGRADING FROM 0.9.10 OR LOWER PLEASE READ ** 3/20/2010
You MUST run the ALTER statements in srv_support.sql:
mysql -u <user> -p<pass> <db_name> < srv_support.sql
These provide additional columns for SRV records
You SHOULD run the ALTER statements in records_update.sql:
mysql -u <user> -p<pass> <db_name> < records_update.sql
These provide longer `val` columns for things like SPF/TXT records
** UPGRADING FROM 0.9.8 OR LOWER PLEASE READ ** 2/4/2005
The smarty core code has been moved. You will need to remove the old templates
to avoid errors by issuing:
sudo rm /usr/local/apache/vegadns/templates_c/*
** UPGRADING FROM 0.9b1 OR LOWER PLEASE READ ** 9/23/2004
You should remove the "> /dev/null" from your cron entry of update-data.sh.
update-data.sh now provides some errors, and you want to get them.
** UPGRADING FROM 0.7 OR LOWER PLEASE READ ** 5/19/2004
As of version 0.8, passwords are no longer stored as plain text, but rather as
md5 hashes. In order for your old passwords to work, you need to run the md5upgrade patch, which is located in the md5upgrade directory of your VegaDNS source.
NOTE: The md5upgrade script was removed after 0.11.3. Grab the 0.11.3 source if you still need this:
https://github.com/shupp/VegaDNS/archive/0.11.3.zip
To upgrade, just point your browser to:
http://your-server/vegadns-x.x/md5upgrade/index.php
(replacing your-server with your hostname, and x.x with your new version)
This script will verify that your accounts table does not have the correct
Password field length. It will then provide you with an upgrade link. When
you follow this link, the Password field length will be changed for the
accounts table, and then each password will be replaced with the corresponding
md5 hash. Once this is complete, your users will be able to log in
successfully.
Also note that since passwords are no longer stored in clear text, if you
forget your password, the system will generate a new one for you upon request.
Bill Shupp
hostmaster@shupp.org