NetBSD Problem Report #18729

Received: (qmail 12289 invoked by uid 605); 19 Oct 2002 20:26:05 -0000
Message-Id: <20021019202602.DFF61A@proven.weird.com>
Date: Sat, 19 Oct 2002 16:26:02 -0400 (EDT)
From: woods@weird.com (Greg A. Woods)
Sender: gnats-bugs-owner@netbsd.org
Reply-To: woods@planix.com (Greg A. Woods)
To: gnats-bugs@gnats.netbsd.org
Subject: security/ssh should conflict with security/ssh2
X-Send-Pr-Version: 3.95

>Number:         18729
>Category:       pkg
>Synopsis:       security/ssh should conflict with security/ssh2
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Oct 19 20:27:00 +0000 2002
>Closed-Date:    Sun Oct 20 00:51:35 +0000 2002
>Last-Modified:  Wed Oct 23 04:27:01 +0000 2002
>Originator:     Greg A. Woods
>Release:        pkgsrc-current 2002/10/18
>Organization:
Planix, Inc.; Toronto, Ontario; Canada
>Environment:
System: NetBSD

>Description:

	security/ssh should conflict with security/ssh2

>How-To-Repeat:

>Fix:

Index: security/ssh/Makefile
===================================================================
RCS file: /cvs/master/m-NetBSD/main/pkgsrc/security/ssh/Makefile,v
retrieving revision 1.101
diff -c -r1.101 Makefile
*** security/ssh/Makefile	5 Sep 2002 00:13:41 -0000	1.101
--- security/ssh/Makefile	13 Sep 2002 19:24:29 -0000
***************
*** 18,24 ****
  HOMEPAGE=		http://www.cs.hut.fi/ssh/
  COMMENT=		Secure shell client and server (remote login program)

! CONFLICTS=		openssh-[0-9]* ssh6-[0-9]*

  CRYPTO=			YES
  LICENSE=		no-commercial-use
--- 18,24 ----
  HOMEPAGE=		http://www.cs.hut.fi/ssh/
  COMMENT=		Secure shell client and server (remote login program)

! CONFLICTS=		openssh-[0-9]* ssh6-[0-9]* ssh2-[0-9]*

  CRYPTO=			YES
  LICENSE=		no-commercial-use
>Release-Note:
>Audit-Trail:

From: Thomas Klausner <wiz@netbsd.org>
To: gnats-bugs@gnats.netbsd.org
Cc:  
Subject: pr/18729 CVS commit: pkgsrc/security/ssh
Date: Sun, 20 Oct 2002 03:49:57 +0300 (EEST)

 Module Name:	pkgsrc
 Committed By:	wiz
 Date:		Sun Oct 20 00:49:56 UTC 2002

 Modified Files:
 	pkgsrc/security/ssh: Makefile

 Log Message:
 Add CONLICT with ssh2 package. From Greg A. Woods in PR 18729.


 To generate a diff of this commit:
 cvs rdiff -r1.101 -r1.102 pkgsrc/security/ssh/Makefile

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: open->closed 
State-Changed-By: wiz 
State-Changed-When: Sat Oct 19 17:51:20 PDT 2002 
State-Changed-Why:  
Fixed, thanks. 

From: gabriel rosenkoetter <gr@eclipsed.net>
To: gnats-bugs@gnats.netbsd.org, netbsd-bugs@netbsd.org
Cc:  
Subject: Re: pkg/18729: security/ssh should conflict with security/ssh2
Date: Tue, 22 Oct 2002 15:31:31 -0400

 --9crTWz/Z+Zyzu20v
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 On Sat, Oct 19, 2002 at 04:26:02PM -0400, Greg A. Woods wrote:
 > 	security/ssh should conflict with security/ssh2

 Why?

 Unless the world has changed drastically since the last time I used
 FSecure SSH on a Unix-like system (admittedly, more than a little
 while ago), security/ssh installs itself as ssh[d]1[-*], then sym
 links to ssh[d,-*] to it. security/ssh2 installs itself as ssh[d]2[-*]
 and then sym links ssh[d,-*] to itself.

 If you install security/ssh2 first and then security/ssh1 second,
 you deserve what you get. Perhaps a warning in MESSAGE is in order,
 but I don't see why they need to conflict; the only overlapping=20
 files should be sym links (provided our patches aren't changing
 that install behavior).

 --=20
 gabriel rosenkoetter
 gr@eclipsed.net

 --9crTWz/Z+Zyzu20v
 Content-Type: application/pgp-signature
 Content-Disposition: inline

 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.7 (NetBSD)

 iD8DBQE9taeS9ehacAz5CRoRAkjPAJwJ/7McaZm6rSO88xhPttXm2+y/hgCdGCDB
 PV0gBMxmmpH3qsLeDUBa4bA=
 =iT53
 -----END PGP SIGNATURE-----

 --9crTWz/Z+Zyzu20v--

From: woods@weird.com (Greg A. Woods)
To: gnats-bugs@gnats.netbsd.org, netbsd-bugs@netbsd.org
Cc:  
Subject: Re: pkg/18729: security/ssh should conflict with security/ssh2
Date: Tue, 22 Oct 2002 17:06:11 -0400 (EDT)

 [ On Tuesday, October 22, 2002 at 15:31:31 (-0400), gabriel rosenkoetter wrote: ]
 > Subject: Re: pkg/18729: security/ssh should conflict with security/ssh2
 >
 > On Sat, Oct 19, 2002 at 04:26:02PM -0400, Greg A. Woods wrote:
 > > 	security/ssh should conflict with security/ssh2
 > 
 > Why?

 because it conflicts!  ;-)

 > Unless the world has changed drastically since the last time I used
 > FSecure SSH on a Unix-like system (admittedly, more than a little
 > while ago), security/ssh installs itself as ssh[d]1[-*], then sym
 > links to ssh[d,-*] to it. security/ssh2 installs itself as ssh[d]2[-*]
 > and then sym links ssh[d,-*] to itself.

 Yes, the world has changed drastically in that interval, especially the
 part directly surrounding SSH!  ;-)

 If you examine the security/ssh2 pkgsrc module you'll find that it is
 configured to provide internal ssh1 client compatability (the only kind
 that's even remotely sane to allow by default, though I'm not 100%
 certain that what's ended up in the package in the official pkgsrc is
 entirely and properly restricting any accidental use of any
 un-registered ssh1 files).  You'll also find that it installs and
 registers the filenames and symlink names that do not include any
 version identifier.

 I.e. security/ssh2 directly and unresolvably convlicts with security/ssh.

 > If you install security/ssh2 first and then security/ssh1 second,
 > you deserve what you get. Perhaps a warning in MESSAGE is in order,
 > but I don't see why they need to conflict; the only overlapping 
 > files should be sym links (provided our patches aren't changing
 > that install behavior).

 They must conflict unless neither installs the unversioned filenames and
 there's some pair of optional packages invented to install the symlinks
 that choose the default.  Such a combination of packages has no
 practical application though -- ssh1 is deprecated and should never be
 used in any new environment.  Those with ssh1 should be aggressively
 upgrading all of their servers and they can use the internal client
 compatability to continue to connect to whatever few sshd1 servers they
 have not yet upgraded (or cannot upgrade due to their existance in some
 closed environment that cannot be easily changed without vendor support).


 -- 
 								Greg A. Woods

 +1 416 218-0098;            <g.a.woods@ieee.org>;           <woods@robohack.ca>
 Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>

From: gabriel rosenkoetter <gr@eclipsed.net>
To: netbsd-bugs@netbsd.org, gnats-bugs@netbsd.org
Cc:  
Subject: Re: pkg/18729: security/ssh should conflict with security/ssh2
Date: Wed, 23 Oct 2002 00:25:53 -0400

 --rMWmSaSbD7nr+du9
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 On Tue, Oct 22, 2002 at 05:06:11PM -0400, Greg A. Woods wrote:
 > If you examine the security/ssh2 pkgsrc module

 =2E.. which I quite obviously didn't... ;^>

 > you'll find that it is configured to provide internal ssh1 client
 > compatability

 All you had to say. Argument withdrawn.

 --=20
 gabriel rosenkoetter
 gr@eclipsed.net

 --rMWmSaSbD7nr+du9
 Content-Type: application/pgp-signature
 Content-Disposition: inline

 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.7 (NetBSD)

 iD8DBQE9tiTQ9ehacAz5CRoRAmv6AJ4z3sWIpucQhfxWb6AS9HZkT9tmGwCeKjft
 DpH2Rr6TJvps9QRZ9jKzuTI=
 =uGey
 -----END PGP SIGNATURE-----

 --rMWmSaSbD7nr+du9--
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.