NetBSD Problem Report #53864
From www@NetBSD.org Sun Jan 13 06:24:48 2019
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id 76F417A181
for <gnats-bugs@gnats.NetBSD.org>; Sun, 13 Jan 2019 06:24:48 +0000 (UTC)
Message-Id: <20190113062447.A79437A1F5@mollari.NetBSD.org>
Date: Sun, 13 Jan 2019 06:24:47 +0000 (UTC)
From: rlntlss83@gmail.com
Reply-To: rlntlss83@gmail.com
To: gnats-bugs@NetBSD.org
Subject: netcat could use OpenSSL
X-Send-Pr-Version: www-1.0
>Number: 53864
>Category: bin
>Synopsis: netcat could use OpenSSL
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jan 13 06:25:00 +0000 2019
>Originator: rlntlss
>Release: 8.0
>Organization:
independent
>Environment:
8.0 amd64
>Description:
netcat compiles with -ltls (currently commented out), which is not in base, but openssl is. It looks pretty trivial to support SSL via OpenSSL in netcat.
What I don't know is if netcat is being tracked as a part of OpenSSH. If that's the case, it might be better to leave it as is..
>How-To-Repeat:
>Fix:
the crypto is currently #ifdef'd out. One could leave the tls stuff in, but #else if defined CRYPTO_OPENSSL to add the OpenSSL stuff -- that way no one would lose the libtls stuff if they are currently using it.
(Contact us)
$NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.