proshield (3.8.21) unstable; urgency=low * ProShield would say that AllowUnauthenticated was set, even when it was not (a bug). Resolved incorrect logic flow on this one. -- Tom Burton <86bccq802@sneakemail.com> Wed, 18 Feb 2009 20:16:23 -0500 proshield (3.8.20) unstable; urgency=low * Improved wording of notice added in last release. * Two other trivial phrasing changes. -- Tom Burton <86bccq802@sneakemail.com> Wed, 18 Feb 2009 18:55:25 -0500 proshield (3.8.19) unstable; urgency=low * Added note for Debian users that it's OK for them to remove that AllowUnauthenticated flag. -- Tom Burton <86bccq802@sneakemail.com> Sun, 30 Mar 2008 16:19:01 -0400 proshield (3.8.18) unstable; urgency=low * Removal of case statement in last release led to leftover punctuation. Bash scripts bail on syntax errors. Removed ";;"punctuation on line 743. * Also fixed an echoing of the allowunauthenticated line to the screen near line 366. -- Tom Burton <86bccq802@sneakemail.com> Sun, 30 Mar 2008 16:04:16 -0400 proshield (3.8.16) unstable; urgency=low * Due to Ubuntu bug #195419, removed ProShield dependency on the APT::Get::AllowUnauthenticated "true"; setting in /etc/apt/apt.conf. If machine has this set, will alert user and ask them if they would like ProShield to remove this flag. The bug would prevent users (particularly users of 7.04) from upgrading to a newer version of Ubuntu. Up until this release, ProShield has set this flag for new users, but after I myself was unable to upgrade a 7.04 box to 7.10, I found this bug. ProShield now specifies --allow-unauthenticated on the command-line to apt-get when it calls it for package operations. If user chooses to remove this flag, ProShield will also be helpful and remove any duplicate lines (sort | uniq) from /etc/apt/apt.conf, which I suspect ProShield puts when it touches /etc/apt/apt.conf upon first-run (the duplicate lines are a trivial thing though). -- Tom Burton <86bccq802@sneakemail.com> Sun, 30 Mar 2008 15:00:18 -0400 proshield (3.8.15) unstable; urgency=low * Fixed data-loss bug in code that is supposed to comment out source package lines in sources.list. Due to an extra grep, I believe since v3.8.0 the code would actually remove all binary repo lines and comment out all the source package lines. This is not what I intended. * Added stricter pattern for finding deb-src lines in sources.list. * Upon runtime program now says it is a GNU GPL program. -- Tom Burton <86bccq802@sneakemail.com> Tue, 11 Mar 2008 22:56:42 -0400 proshield (3.8.14) unstable; urgency=low * Last version excluded dhclient from packet sniffer check. dhcpd is now also excluded. -- Tom Burton <86bccq802@sneakemail.com> Thu, 10 Jan 2008 19:48:56 -0500 proshield (3.8.13) unstable; urgency=low * Excluded DHCP client (dhclient) from packet sniffer check. dhclient is normal and since this is how people in the real world get their IP's, we should not warn over this specific program. * Changed wording to indicate free disk space check checked all the partitions. -- Tom Burton <86bccq802@sneakemail.com> Fri, 04 Jan 2008 23:34:21 -0500 proshield (3.8.12) unstable; urgency=low * Primary upgrade method was broken in v3.8.10 and 3.8.11. Missing a dependency--->dpkg-dev, which provides dpkg-scanpackage, which we use for building the local apt respository for primary upgrade method. * Fixed bug that would make ProShield think both upgrade methods had failed (incorrectly). -- Tom Burton <86bccq802@sneakemail.com> Sat, 29 Dec 2007 16:21:56 -0500 proshield (3.8.11) unstable; urgency=low * When you sync the clock, it will now tell you the current time. * Gave more info about nis/portmap. * ProShield does not complain anymore if you are running Debian (since it works on Debian). * Changed where extra line is inserted during nis/portmap questions. * Improved wording in section that handles advising the user about direct root user logins via SSH. The bad behavior of killing current direct root logins when updating the SSHD config was fixed in v3.8.10. -- Tom Burton <86bccq802@sneakemail.com> Sat, 29 Dec 2007 15:13:31 -0500 proshield (3.8.10) unstable; urgency=low * Updated 'control' file with new approximation of package size. * Gave explanation of how to run ProShield as root (sudo). * Tweaked program header and updated copyright/active development year ranges. * Removed comment that gets added before #!/bin/bash to backup restore script. * Changed another section of code that used "ps fU root" instead of just "ps". This might cause some users to hang for a long time during backup creation. * Code to update SSH config to only use SSHv2 would killall sshd (bad!). Switch it to do a more graceful 'reload'. * ProShield will now allow you to tell it to never ask you again about fetching source package information. * Improved distribution detection and added dependency for lsb-release, which we really have been depending on since 3.8.0. * Added dependency for util-linux because we are now using 'mcookie' for pseudo-random hex data. Most systems should have this installed already. * Added dependency for mktemp. We've been dependent on this for like...ever. * Added MUID code. * Added failsafe secondary upgrade method. I'm sorry for all those who because of me got stuck in upgrade loops. This should fix it. * Jumped version to 3.8.10 because of important changes above. -- Tom Burton <86bccq802@sneakemail.com> Sun, 23 Dec 2007 03:43:15 -0500 proshield (3.8.6) unstable; urgency=low * I was shipping ".svn" directories since 3.8.0. This release and later should have no ".svn" directories. When you upgrade to this release, the extra ".svn" directories on your disk will be removed immediately by the package system. -- Tom Burton Sat, 22 Dec 2007 13:43:59 -0500 proshield (3.8.5) unstable; urgency=low * Adding "-all" to the package name broke the upgrade mechanism. Fixed it. Sorry that this was broken since 3.8.0. -- Tom Burton Wed, 19 Dec 2007 20:04:09 -0500 proshield (3.8.4) unstable; urgency=low * Implemented free disk space checker. Makes sure none of your partitions are getting full. * Fixed another part of the code that suffered from the same bug as fixed in v3.8.2. -- Tom Burton Mon, 17 Dec 2007 21:28:41 -0500 proshield (3.8.3) unstable; urgency=low * Fixed ProShield complaining package system was in a mess when it was not during an upgrade. -- Tom Burton Sun, 16 Dec 2007 22:42:28 -0500 proshield (3.8.2) unstable; urgency=low * Fix to ProShield potentially hanging at "Please wait while the Debian software repositories are queried (this may take a long time)..." forever. * Version number had to skip .1 because of bug with SF.net -- Tom Burton Sun, 16 Dec 2007 22:19:54 -0500 proshield (3.8.0) unstable; urgency=low * ProShield returns, updated against Ubuntu Linux (my current distro). * funcCheckConfigExist would fail if /etc/proshield did not exist. Make sure this directory and /etc/ exists. * Added check to see if system is Ubuntu. Warn, but allow user to continue if desired. * Fixed some parse errors that happened because of bitrot. * Section that disables direct root user logins for SSH would make config change and restart SSHD. If you were ssh'ed in, this would result in disconnected session and stopped ssh service. * When asked "y,n", starting to remove handling for "Y". * Section that removes usually unnecessary source package lines from sources.list has been changed to merely comment them out. Data loss is not good practice. -- Tom Burton Thu, 13 Dec 2007 21:27:21 -0500 proshield (3.7.47) unstable; urgency=low * ProShield should always be able to correctly calculate amount of space freed from apt cache cleaning. Previously, it would say "?? megs of space were freed" a lot. -- Tom Burton Fri, 23 Jun 2006 08:54:16 -0400 proshield (3.7.46) unstable; urgency=low * Changed ntpdate time server hostname to 1.pool.ntp.org from 0.pool.ntp.org. Sometimes 0.pool strangely doesn't exist (and thus can't sync time). According to their website, both 0,1,2 should work. -- Tom Burton Wed, 1 Mar 2006 20:34:18 -0500 proshield (3.7.45) unstable; urgency=low * Removed commented-out line #190. * It's February/March. Ended "transition period". Up until now, if a user of 3.7.37 or earlier ran any more recent version, it would say "There is a new config framework. Your old config is incompatible. You will be asked more questions this run, as your config/overrides are re-done." Now it will no longer say this. Users will just be transitioned with no notice. -- Tom Burton Thu, 23 Feb 2006 01:31:53 -0500 proshield (3.7.44e) unstable; urgency=low * Fix from 44c wouldn't work because config file isn't read until after that instruction line. Moved config file creation||read to right after version is displayed. Now it should work. -- Tom Burton Fri, 20 Jan 2006 14:45:41 -0500 proshield (3.7.44c) unstable; urgency=low * If user ran proshield -d for debug mode and then proshield upgraded, proshield would not say that it was in debug mode (at program beginning) when the new version ran, even though it was. Trivial bug, trivial fix. -- Tom Burton Fri, 20 Jan 2006 14:29:44 -0500 proshield (3.7.44) unstable; urgency=low * Added an over-ride for time syncronization. Some people use ntpd or just don't care I guess. -- Tom Burton Fri, 20 Jan 2006 14:03:43 -0500 proshield (3.7.43) unstable; urgency=low * Added SHA-1 checksum generation and validation for backup/restore features. If SHA-1 verification of backup archive fails when a user runs restore script, restore script will output text for user to read informing them of problem, possible causes and possible actions they can take. * Came up with a very clever way to improve the way I store the restore program that is stored inside the ProShield program. -- Tom Burton Mon, 16 Jan 2006 03:59:58 -0500 proshield (3.7.42) unstable; urgency=low * Added a configuration setting to keep track of if users were using custom backup directories. Although on next run of this version or later users will have to answer one or two extra backup questions, in the future updates can be rolled out silently to the default backup directory list, for those who are using default backup directory list. * Updated list of default backup directories to include /root/ and crontabs. -- Tom Burton Thu, 12 Jan 2006 16:23:35 -0500 proshield (3.7.41) unstable; urgency=low * Spelling error on lines 643 and 973. Insure-->Ensure. * In v3.7.39, I introduced some cleanup code. This code now uses rmdir instead of rm -rf. It's a better/safer way. * Removed one last instance of once/twice a week. -- Tom Burton Wed, 11 Jan 2006 18:49:51 -0500 proshield (3.7.40) unstable; urgency=low * Updated copyright notice in source code to read year 2006. Happy New Year. * Previously, if debug mode was specified on the command line, and then a new version of ProShield had been released, and the user opted to upgrade, the flag telling ProShield to run in debug mode was lost. Fixed it so that the flag is not lost when a user upgrades mid-run. -- Tom Burton Mon, 2 Jan 2006 06:17:29 -0500 proshield (3.7.39) unstable; urgency=low * Near the start of runtime, ProShield creates a safe (permissions and randomly named) temporarily directory in /tmp/. This folder is usually 5K-35K, but if ProShield detected a new version was out, and the user opted to upgrade, it neglected to remove the old temp folder. Fixed. * Trivial code housekeeping: Normalized all function names to start with lowercase "func". -- Tom Burton Sun, 1 Jan 2006 20:01:38 -0500 proshield (3.7.38.3) unstable; urgency=low * In the last release users would notice a non-threatening message about a file not found. ProShield was looking for a file but not silencing any output regarding it. Fixed. * Noticed some missing pretty word-wrapping for users who have never backed up before. -- Tom Burton Wed, 28 Dec 2005 17:48:45 -0500 proshield (3.7.38.2) unstable; urgency=low * Note to self: Do not even begin rollout of new version until all testing is complete. -- Tom Burton Wed, 28 Dec 2005 17:14:56 -0500 proshield (3.7.38) unstable; urgency=low * Reworked entire way ProShield stores and works with it's configuration settings. ProShield will no longer give out ugly over-ride commands for the user to run, but will ask smartly "would you like ProShield to never ask you again about this?". All config but the directories that ProShield backsup is stored in /etc/proshield/proshield.conf. * Changed "recommended interval" from "once/twice a week" to "once a week". -- Tom Burton Wed, 28 Dec 2005 16:40:00 -0500 proshield (3.7.37) unstable; urgency=low * Some users reported an unpleasant experience when asking ProShield to disable direct root user logins, whilest they were directly logged in as root. ProShield will now check to see if root is directly logged in if the user requests this change, and if so, will verbosely warn the user and present the choice again. -- Tom Burton Wed, 28 Dec 2005 05:04:44 -0500 proshield (3.7.36) unstable; urgency=low * Changed ProShield from using a simple string inequality/equality checker for it's auto-update routine to using a smart version checker that's infallible. Actually used "dpkg --compare-versions" for this, which was very convenient. * Sometimes a user won't want to apt-get upgrade, but will want to download the 'updates'. Provided this functionality as an option. -- Tom Burton Sun, 25 Dec 2005 23:27:50 -0500 proshield (3.7.35) unstable; urgency=low * Noticed a bug in the backup restore script that ProShield creates. It's trivial, an echoed "Restore complete" line wasn't going to be displayed. Fixed now. * Added debug mode (proshield -d). This entailed adding intelligent command-line option handling. Debug mode makes ProShield tarball it's temporary files right before it exits, and report this tarball to the user. -- Tom Burton Thu, 1 Dec 2005 16:34:50 -0500 proshield (3.7.34) unstable; urgency=low * More polishing, in order to get the proshield package ready for Debian. * Quite a few changes in DEBIAN/control file, including the description. * Improved COPYRIGHT file, including updating FSF's address. * The program's header had a reference to where the license was found. It should have pointed to /usr/share/common-licenses/ but it didn't. It does now. * I have discovered you can't upload to testing, but rather packages from unstable are copied to testing after a few weeks. So changed the 'distribution' from "testing" to "unstable". I currently believe that this is the most correct thing to do. * Apparently 1.pool.ntp.org sometimes is empty. 0 and 2 usually work when 1 doesn't, so I switched ProShield to use 0.pool.ntp.org. Weird that pool.ntp.org would break like this. -- Tom Burton Wed, 23 Nov 2005 21:38:28 -0500 proshield (3.7.33) unstable; urgency=low * As part of Debianization, started using this file for ChangeLog. Old changelog is archived and now located in "old-changelog.gz". * Forgot to run lintian before I released 3.7.32. As a result, one small error got through. This release is functionally the same to 3.7.32 except for no lintian errors or warnings. * This is the first version of ProShield that completely passes lintian! -- Tom Burton Thu, 10 Nov 2005 18:28:46 -0500