Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Future ntsec-detection problem in sshd (Re: winsup/cygwin
	ChangeLog security.cc)
From: Robert Collins <rbcollins@cygwin.com>
To: cygwin@cygwin.com
In-Reply-To: <20020727161323.GH16216@redhat.com>
References: <20020725170413.3469.qmail@sources.redhat.com>
	<005d01c23417$27a656e0$0100a8c0@wdg.uk.ibm.com>
	<20020726102233.V3921@cygbert.vinschen.de>
	<021301c234eb$a8d6bf00$0100a8c0@wdg.uk.ibm.com>
	<20020727111609.O3921@cygbert.vinschen.de>
	<013001c23570$993c7280$0100a8c0@wdg.uk.ibm.com> 
	<20020727161323.GH16216@redhat.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-nZ0Ns6Nx4q3YnVnIHz7e"
Date: 28 Jul 2002 10:45:20 +1000
Message-Id: <1027817120.9602.34.camel@lifelesswks>
Mime-Version: 1.0

--=-nZ0Ns6Nx4q3YnVnIHz7e
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2002-07-28 at 02:13, Christopher Faylor wrote:

> Breaking backwards compatibility gratuitously is not desirable.
>=20
> In this case however, this could be implemented as a "cygwin_internal" fu=
nction
> anyway, which would mean not having to worry about loading the function.
>=20
> However, checking the cygwin api version should be sufficient too.  That'=
s
> what it is there for.

What about a /proc entry?

Rob

--=-nZ0Ns6Nx4q3YnVnIHz7e
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEABECAAYFAj1DPqAACgkQI5+kQ8LJcoKz/gCeIBhUGcMd6spQGue6r6iYDPy5
s/oAnjSy2pcgLRTxog1C4+AUPypOFKQc
=dvE5
-----END PGP SIGNATURE-----

--=-nZ0Ns6Nx4q3YnVnIHz7e--