From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29524 invoked by alias); 22 Jul 2009 09:34:54 -0000 Received: (qmail 29513 invoked by uid 22791); 22 Jul 2009 09:34:53 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-ew0-f217.google.com (HELO mail-ew0-f217.google.com) (209.85.219.217) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 22 Jul 2009 09:34:45 +0000 Received: by ewy17 with SMTP id 17so67410ewy.2 for ; Wed, 22 Jul 2009 02:34:41 -0700 (PDT) Received: by 10.210.78.16 with SMTP id a16mr779074ebb.66.1248255281582; Wed, 22 Jul 2009 02:34:41 -0700 (PDT) Received: from ?192.168.2.99? (cpc2-cmbg8-0-0-cust61.cmbg.cable.ntl.com [82.6.108.62]) by mx.google.com with ESMTPS id 10sm860573eyd.7.2009.07.22.02.34.40 (version=SSLv3 cipher=RC4-MD5); Wed, 22 Jul 2009 02:34:40 -0700 (PDT) Message-ID: <4A66E038.1000808@gmail.com> Date: Wed, 22 Jul 2009 09:34:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: The Vulgar and Untrustworthy Cygwin-Talk Maiming List Subject: Re: Zone alarm, you have failed me for the first time... and the last. (BLODA news) References: <4A63E16D.2010503@gmail.com> <4A64E479.2000007@etr-usa.com> <4A665996.2060605@gmail.com> <4A665BB5.4050601@etr-usa.com> In-Reply-To: <4A665BB5.4050601@etr-usa.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Vulgar and Unprofessional Cygwin-Talk List Mail-Followup-To: cygwin-talk@cygwin.com X-SW-Source: 2009-q3/txt/msg00026.txt.bz2 Warren Young wrote: > Dave Korn wrote: >> Warren Young wrote: >>> Dave Korn wrote: >>>> Newer versions of ZA don't run on w2k >>> Is Win2K still running on old time zone data, or did MS finally cave to >>> the pressure to release that patch without requiring a $1000 payment? >> >> I have no idea. > > You would know if it did, if you're in an area of the world where the > DST rules changed after MS declared "no more patches" for such things. > In most of the US, for instance, your system time would have been off by > an hour for several weeks during the year for the past two years. If > your locale's DST rules did change recently and you didn't notice a time > problem, MS must have relented. There was a huge stink over this. Well I'm in the UK, I dunno if the rules have changed at all recently, and every once in a while I notice my PC has or hasn't got got a DST change right or wrong, but never more than twice a year. My love of w2k is based on it being the most lightweight version of the OS in years, and it having also had the longest time to get debugged and stable, but obviously it's not suitable for a corporate environment. It still WJFFM in a home environment and there's still /quite/ a lot of new software coming out that's compatible enough to run on it. >>> Expiration is not the same thing as revocation. >> >> I know. I was suggesting it should be, otherwise there's simply no >> point doing it at all. > > Sure there is. It benefits the CA -- more $$ -- That's precisely my idea of pointless: pointless churn for the sake of it! > and it benefits the > rest of us by encouraging people to keep their certs current. Huh? How does that help? > Which > cert would you trust more, one where the CA says it was current as of N > months ago (N < 12) or one where the CA says it was current 6 years ago > when it was first created? Well, I do maths, and in maths, what you just asked me was: > Which would you trust more, a statement from N months ago that a^y mod m > = b, or a statement from 6 years ago that c^y mod m = d ? Why would how long ago the statement was made have any bearing on its truth or falsity if maths hasn't changed in the mean time? cheers, DaveK