Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: Ideas re problem reporting From: Robert Collins To: luke.kendall@cisra.canon.com.au Cc: cygwin@cygwin.com In-Reply-To: <20030716090612.1AE0834381@nevin.research.canon.com.au> References: <20030716090612.1AE0834381@nevin.research.canon.com.au> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-2V0reM6px1/8Yd1A3XrS" Message-Id: <1058346866.731.13.camel@localhost> Mime-Version: 1.0 Date: 16 Jul 2003 19:14:26 +1000 --=-2V0reM6px1/8Yd1A3XrS Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2003-07-16 at 19:06, luke.kendall@cisra.canon.com.au wrote: > On 16 Jul, Robert Collins wrote: > > However, a registry entry won't correct this: only the user knows=20 > > exactly what tool they used, unless we go down some insane DRM style=20 > > path - and I won't be taking setup down that path.=20 >=20 > You mean, even if setup just recorded whether it had just completed a > full, or a default, or some intermediate install - there would be > nothing to stop a naughty user from faking the same entry manually? Exactly. Rob --=20 GPG key available at: . --=-2V0reM6px1/8Yd1A3XrS Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/FRdxI5+kQ8LJcoIRAr16AKCcE9ncYtT6zwf82R7g1E7i3GoPQACfdFeu xqhaiaYmya9dkqJqGnmNKfY= =xmeN -----END PGP SIGNATURE----- --=-2V0reM6px1/8Yd1A3XrS--