From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37374) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eZIjV-0001qt-SB for guix-patches@gnu.org; Wed, 10 Jan 2018 10:56:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eZIjS-0002nU-Q8 for guix-patches@gnu.org; Wed, 10 Jan 2018 10:56:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:43289) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eZIjS-0002nB-G3 for guix-patches@gnu.org; Wed, 10 Jan 2018 10:56:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eZIjS-0003i8-As for guix-patches@gnu.org; Wed, 10 Jan 2018 10:56:02 -0500 Subject: [bug#30037] [PATCH] gnu: whois: Remove bundled mkpasswd. Resent-Message-ID: References: <20180109010138.29740-1-me@tobias.gr> <20180109065157.j4ffqj7rye5wwike@abyayala> <65a6b7e7-afca-cc9e-d1b7-cf23038800d4@tobias.gr> <20180110145554.bdnge6atptnrsg7c@abyayala> From: Tobias Geerinckx-Rice Message-ID: <6615f0ce-9417-8a15-686e-7d8656b7ad3f@tobias.gr> Date: Wed, 10 Jan 2018 16:57:53 +0100 MIME-Version: 1.0 In-Reply-To: <20180110145554.bdnge6atptnrsg7c@abyayala> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LcKFgLj8HljV4AhjpBnpmIfHu1mSmesgk" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: ng0@n0.is Cc: 30037@debbugs.gnu.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --LcKFgLj8HljV4AhjpBnpmIfHu1mSmesgk Content-Type: multipart/mixed; boundary="iUCkqMsODhtS5isrKRND6hz4ZHjINroQl"; protected-headers="v1" From: Tobias Geerinckx-Rice To: ng0@n0.is Cc: 30037@debbugs.gnu.org Message-ID: <6615f0ce-9417-8a15-686e-7d8656b7ad3f@tobias.gr> Subject: Re: [bug#30037] [PATCH] gnu: whois: Remove bundled mkpasswd. References: <20180109010138.29740-1-me@tobias.gr> <20180109065157.j4ffqj7rye5wwike@abyayala> <65a6b7e7-afca-cc9e-d1b7-cf23038800d4@tobias.gr> <20180110145554.bdnge6atptnrsg7c@abyayala> In-Reply-To: <20180110145554.bdnge6atptnrsg7c@abyayala> --iUCkqMsODhtS5isrKRND6hz4ZHjINroQl Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable ng0, ng0 wrote on 10/01/18 at 15:55: > What if someone under account root install 'whois' into their=20 > profile. [together with expect, source of The Other Mkpasswd.] > Wouldn't they have 2 mkpasswd now in their path of exectuables and=20 > encounter a collision? Presumably. > Should we rename it for the sake of namespace collisions reduction? I don't think this case warrants manual intervention. Whois' mkpasswd encrypt()s a given passwd and prints the result. Expect's generates a random string that satisfies some criteria. Neither are what I'd call day-to-day system administration tools. I'd rather give users deterministic control over any collision, but now who's bikeshedding (with no intention to write the code)... :-) Kind regards, T G-R --iUCkqMsODhtS5isrKRND6hz4ZHjINroQl-- --LcKFgLj8HljV4AhjpBnpmIfHu1mSmesgk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCWlY4AQ0cbWVAdG9iaWFz LmdyAAoJEA2w/4hPVW15NZgA/iFQaugadf9UOPUjJZd3dqjsTc1GpiT1hW3qisrG 4bIVAP4/mV2Cfk0NK170aOAQoEez0lzQaMrC9EKgr3wNlReiBg== =7h/d -----END PGP SIGNATURE----- --LcKFgLj8HljV4AhjpBnpmIfHu1mSmesgk--