all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: ng0@n0.is
Cc: 30037@debbugs.gnu.org
Subject: [bug#30037] [PATCH] gnu: whois: Remove bundled mkpasswd.
Date: Wed, 10 Jan 2018 16:57:53 +0100	[thread overview]
Message-ID: <6615f0ce-9417-8a15-686e-7d8656b7ad3f@tobias.gr> (raw)
In-Reply-To: <20180110145554.bdnge6atptnrsg7c@abyayala>


[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]

ng0,

ng0 wrote on 10/01/18 at 15:55:
> What if someone under account root install 'whois' into their 
> profile.

[together with expect, source of The Other Mkpasswd.]

> Wouldn't they have 2 mkpasswd now in their path of exectuables and 
> 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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 248 bytes --]

  reply	other threads:[~2018-01-10 15:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  1:01 [bug#30037] [PATCH] gnu: whois: Remove bundled mkpasswd Tobias Geerinckx-Rice
2018-01-09  1:04 ` Tobias Geerinckx-Rice
2018-01-09  6:51 ` ng0
2018-01-09 16:46   ` Tobias Geerinckx-Rice
2018-01-10 14:55     ` ng0
2018-01-10 15:57       ` Tobias Geerinckx-Rice [this message]
2018-01-09 13:36 ` Ludovic Courtès
2018-01-09 16:46   ` Tobias Geerinckx-Rice
2018-01-09 17:05     ` Marius Bakke
2018-01-10 14:46       ` ng0
2018-01-10 15:26         ` bug#30037: " Tobias Geerinckx-Rice
2018-01-10 17:17           ` [bug#30037] " ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6615f0ce-9417-8a15-686e-7d8656b7ad3f@tobias.gr \
    --to=me@tobias.gr \
    --cc=30037@debbugs.gnu.org \
    --cc=ng0@n0.is \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.