Date: Mon, 29 May 2000 10:02:08 -0700 (PDT) From: Eric S <eric@cybernut.com> To: FreeBSD-gnats-submit@freebsd.org Subject: ports/18879: New ports - lsh 0.9.10 Message-ID: <200005291702.e4TH28w15360@cybernut.com>
next in thread | raw e-mail | index | archive | help
>Number: 18879 >Category: ports >Synopsis: New ports - lsh 0.9.10 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon May 29 10:10:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Eric Schwertfeger >Release: FreeBSD 4.0-RELEASE i386 >Organization: >Environment: >Description: [This is my first port submission in quite some time, I'm pretty sure I'm following all the guidelines, but not certain. portlint likes it, at least] lsh is a client that can connect to the corresponding lshd server. It uses the SECSH protocol, which means that it is compatible with SSH 2.0, except for file transfer, which is not part of SECSH. SECSH uses compression and encryption algorithms that are unencumbered, and lsh itself is GPL. lsh is not as feature-rich as OpenSSH, as it doesn't currently support password-protected keyrings, the SSH 1.X protocols, TCP wrappers, etc. On the other hand, it doesn't require OpenSSL, and doesn't take a lot of work to avoid patented algorithms. Port author's notes on usage and common problems can be found at WWW: http://gz.geekazoid.com/lsh/ >How-To-Repeat: >Fix: # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # lsh # lsh/Makefile # lsh/patches # lsh/patches/patch-aa # lsh/patches/patch-ab # lsh/patches/patch-ac # lsh/files # lsh/files/md5 # lsh/pkg # lsh/pkg/PLIST # lsh/pkg/COMMENT # lsh/pkg/DESCR # echo c - lsh mkdir -p lsh > /dev/null 2>&1 echo x - lsh/Makefile sed 's/^X//' >lsh/Makefile << 'END-of-lsh/Makefile' X# New ports collection makefile for: lsh secure shell X# Date created: 29 MAY 2000 X# Whom: eric X# X# $FreeBSD$ X XPORTNAME= lsh XPORTVERSION= 0.9.10 XCATEGORIES= security net XMASTER_SITES= ftp://ftp.lysator.liu.se/pub/security/lsh/ XDISTNAME= ${PORTNAME}-${PORTVERSION} X XMAINTAINER= eric@cybernut.com X XGNU_CONFIGURE= yes XINSTALL_TARGET= install X XRESTRICTED= "Crypto: export-controlled" X Xpost-install: X strip ${PREFIX}/bin/lsh X strip ${PREFIX}/bin/lsh_keygen X strip ${PREFIX}/bin/lsh_writekey X strip ${PREFIX}/bin/sexp_conv X strip ${PREFIX}/bin/srp-gen X strip ${PREFIX}/sbin/lshd X strip ${PREFIX}/sbin/lsh_proxy X.if !defined(NOPORTDOCS) X install-info --section="Miscellaneous" \ X --entry="* LSH: (lsh). lsh secure remote shell documentation." \ X ${PREFIX}/info/lsh.info ${PREFIX}/info/dir X.endif X X.include <bsd.port.mk> END-of-lsh/Makefile echo c - lsh/patches mkdir -p lsh/patches > /dev/null 2>&1 echo x - lsh/patches/patch-aa sed 's/^X//' >lsh/patches/patch-aa << 'END-of-lsh/patches/patch-aa' X--- configure.orig Sun Jan 9 09:43:03 2000 X+++ configure Sun Jan 9 22:12:24 2000 X@@ -4666,12 +4666,14 @@ X echo $ac_n "checking for BSD pty names""... $ac_c" 1>&6 X echo "configure:4668: checking for BSD pty names" >&5 X X+first=`ls /dev/pty* | cut -c 9-9 | uniq | tr -d '\n'` X+second=`ls /dev/pty* | cut -c 10-10 | sort | uniq | tr -d '\n'` X cat >> confdefs.h <<EOF X-#define PTY_BSD_SCHEME_FIRST_CHARS "`ls /dev/pty* | cut -c 9-9 | uniq | tr -d '\n'`" X+#define PTY_BSD_SCHEME_FIRST_CHARS "$first" X EOF X X cat >> confdefs.h <<EOF X-#define PTY_BSD_SCHEME_SECOND_CHARS "`ls /dev/pty* | cut -c 10-10 | sort | uniq | tr -d '\n'`" X+#define PTY_BSD_SCHEME_SECOND_CHARS "$second" X EOF X X END-of-lsh/patches/patch-aa echo x - lsh/patches/patch-ab sed 's/^X//' >lsh/patches/patch-ab << 'END-of-lsh/patches/patch-ab' X--- configure.in.orig Sun Jan 9 09:42:52 2000 X+++ configure.in Sun Jan 9 22:17:49 2000 X@@ -544,8 +544,10 @@ X AC_MSG_CHECKING(for BSD pty names) X X dnl FIXME: What is most portable, tr -d '\n' or tr -d '\012' ? X-AC_DEFINE_UNQUOTED(PTY_BSD_SCHEME_FIRST_CHARS, "`ls /dev/pty* | cut -c 9-9 | uniq | tr -d '\n'`") X-AC_DEFINE_UNQUOTED(PTY_BSD_SCHEME_SECOND_CHARS, "`ls /dev/pty* | cut -c 10-10 | sort | uniq | tr -d '\n'`") X+first=`ls /dev/pty* | cut -c 9-9 | uniq | tr -d '\n'` X+second=`ls /dev/pty* | cut -c 10-10 | sort | uniq | tr -d '\n'` X+AC_DEFINE_UNQUOTED(PTY_BSD_SCHEME_FIRST_CHARS, "$first") X+AC_DEFINE_UNQUOTED(PTY_BSD_SCHEME_SECOND_CHARS, "$second") X X dnl FIXME: How can we test if the bsd scheme is likely to work? X AC_DEFINE(PTY_BSD_SCHEME) END-of-lsh/patches/patch-ab echo x - lsh/patches/patch-ac sed 's/^X//' >lsh/patches/patch-ac << 'END-of-lsh/patches/patch-ac' X--- src/lsh-authorize.orig Sun Feb 6 09:39:43 2000 X+++ src/lsh-authorize Sun Apr 16 13:32:57 2000 X@@ -1,4 +1,4 @@ X-#! /bin/sh X+#!/bin/sh X X usage () { X echo Usage: $0 key-file X@@ -29,7 +29,7 @@ X exit 0 X fi X X-create_dir () { X+create-dir () { X if mkdir $1 2>/dev/null; then X echo Created $1 X chmod $2 $1 || exit 1 X@@ -37,22 +37,27 @@ X } X X # Create directories X-create_dir ~/.lsh 0700 X-create_dir ~/.lsh/authorized_keys_sha1 0700 X+create-dir ~/.lsh 0700 X+create-dir ~/.lsh/authorized_keys_sha1 0700 X X-SEXP_CONV=`PATH=$PATH:. \type -path sexp_conv` X+PATH=$PATH:`dirname $0` X X-if [ -z $SEXP_CONV ] ; then X- echo "Can't find the sexp_conv program" X- exit 1 X-fi X+SEXP_CONV="sexp_conv" X X while [ $# != 0 ]; do X- hash=`$SEXP_CONV < $1 --once --hash sha1 --raw-hash` X- if [ -z $hash ] ; then X- echo $0: File $1 not found. X- else X+ if [ -f $1 ]; then X+ hash=`$SEXP_CONV < $1 --once --hash sha1 --raw-hash` X+ if [ $? = 127 ]; then X+ echo "Can't find the sexp_conv program" X+ exit 1 X+ fi X+ if [ -z "$hash" ] ; then X+ echo $0: File $1 not readable. X+ else X $SEXP_CONV < $1 -o canonical --once > ~/.lsh/authorized_keys_sha1/$hash X+ fi X+ else X+ echo $0: File $1 not found. X fi X shift X done END-of-lsh/patches/patch-ac echo c - lsh/files mkdir -p lsh/files > /dev/null 2>&1 echo x - lsh/files/md5 sed 's/^X//' >lsh/files/md5 << 'END-of-lsh/files/md5' XMD5 (lsh-0.9.10.tar.gz) = b09d691cdbb8f82091bf6343a1bb7ace END-of-lsh/files/md5 echo c - lsh/pkg mkdir -p lsh/pkg > /dev/null 2>&1 echo x - lsh/pkg/PLIST sed 's/^X//' >lsh/pkg/PLIST << 'END-of-lsh/pkg/PLIST' Xbin/lsh Xbin/lsh_keygen Xbin/lsh_writekey Xbin/sexp_conv Xbin/lsh-authorize Xbin/srp-gen Xsbin/lshd Xsbin/lsh_proxy X@unexec install-info --delete --section="Miscellaneous" --entry="* LSH: (lsh). lsh secure remote shell documentation." %D/info/jed.info %D/info/dir Xinfo/lsh.info X@exec install-info --section="Miscellaneous" --entry="* LSH: (lsh). lsh secure remote shell documentation." %D/info/jed.info %D/info/dir END-of-lsh/pkg/PLIST echo x - lsh/pkg/COMMENT sed 's/^X//' >lsh/pkg/COMMENT << 'END-of-lsh/pkg/COMMENT' XA secure (encrypted) remote shell compatible with ssh 2.0 END-of-lsh/pkg/COMMENT echo x - lsh/pkg/DESCR sed 's/^X//' >lsh/pkg/DESCR << 'END-of-lsh/pkg/DESCR' Xlsh is a client that can connect to the corresponding lshd server. It uses Xthe SECSH protocol, which means that it is compatible with SSH 2.0, except Xfor file transfer, which is not part of SECSH. X XSECSH uses compression and encryption algorithms that are unencumbered, and Xlsh itself is GPL. X Xlsh is not as feature-rich as OpenSSH, as it doesn't currently support Xpassword-protected keyrings, the SSH 1.X protocols, TCP wrappers, etc. XOn the other hand, it doesn't require OpenSSL, and doesn't take a lot of Xwork to avoid patented algorithms. X XPort author's notes on usage and common problems can be found at XWWW: http://gz.geekazoid.com/lsh/ END-of-lsh/pkg/DESCR exit >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005291702.e4TH28w15360>