summaryrefslogtreecommitdiff
path: root/security/fsh
AgeCommit message (Collapse)AuthorFilesLines
2009-06-14Remove @dirrm entries from PLISTsjoerg1-2/+1
2009-02-09Switch to Python 2.5 as default. Bump revision of all packages that havejoerg1-2/+2
changed runtime dependencies now.
2008-06-12Add DESTDIR support.joerg1-1/+3
2007-12-12Reset maintainer on his request.wiz1-2/+2
2006-04-07List the info files directly in the PLIST and honor PKG{INFO,MAN}DIR.jlam2-3/+4
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg1-2/+2
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-2/+2
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
2005-03-20Extend "fshcompat.py" to work with python24, using patch submitted byfredb3-2/+44
lukem in PR pkg/29704. Reviewed by recht.
2005-02-24Add RMD160 digests.agc1-1/+2
2004-03-09Remove info files entries from PLIST.seb1-2/+1
2003-08-09USE_NEW_TEXINFO is unnecessary now.seb1-2/+1
2003-08-04Convert to USE_NEW_TEXINFO.seb2-5/+4
2003-07-21COMMENT should start with a capital letter.martti1-2/+2
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-03-05Update fsh to 1.2. Changes since 1.1:jschauma3-6/+7
Use Bugzilla for bug reporting. * README: Mention Bugzilla. * fsh.texi (Bugs): Mention Bugzilla. Port to Python 2.2. (Bug 332). * fshcompat.py: New module, that finds some constants in os, fcntl, FCNTL or thin air depending on Python version. * fshlib.py: Use fshcompat instead of FCNTL. * infshd.py: Ditto. * Makefile.am (pkgdata_DATA): Added fshcompat.py.
2002-09-21Strip the ".buildlink" from the names of the python application andjlam1-2/+2
extension Makefile fragments, because they really don't have anything to do with the buildlink[12] frameworks. Change all the Makefiles that use application.buildlink.mk and extension.buildlink.mk to use application.mk and extension.mk instead.
2002-02-18Introduce new framework for handling info files generation and installation.seb2-5/+5
Summary of changes: - removal of USE_GTEXINFO - addition of mk/texinfo.mk - inclusion of this file in package Makefiles requiring it - `install-info' substituted by `${INSTALL_INFO}' in PLISTs - tuning of mk/bsd.pkg.mk: removal of USE_GTEXINFO INSTALL_INFO added to PLIST_SUBST `${INSTALL_INFO}' replace `install-info' in target rules print-PLIST target now generate `${INSTALL_INFO}' instead of `install-info' - a couple of new patch files added for a handful of packages - setting of the TEXINFO_OVERRIDE "switch" in packages Makefiles requiring it - devel/cssc marked requiring texinfo 4.0 - a couple of packages Makefiles were tuned with respect of INFO_FILES and makeinfo command usage See -newly added by this commit- section 10.24 of Packages.txt for further information.
2002-01-18use python buildlinkdrochner1-3/+4
2001-11-01Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-09-27Mechanical changes to 375 files to change dependency patterns of the formjlam1-2/+2
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the packages whose base package name is "foo", and not those named "foo-bar". A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also change dependency examples in Packages.txt to reflect this.
2001-07-13Update my email address.fredb1-2/+2
2001-04-19Move to sha1 digests, add distfile sizes.agc1-2/+3
2001-04-17+ move the distfile digest/checksum value from files/md5 to distinfoagc1-1/+1
+ move the patch digest/checksum values from files/patch-sum to distinfo
2001-02-17Update to new COMMENT style: COMMENT var in Makefile instead of pkg/COMMENT.wiz2-2/+2
2000-12-14Update to 1.1 because of a possible security problem:wiz3-5/+6
The socket creation code in fshd was not paranoid enough. There were are at least two possible attacks: - If a malicious user has symlinked /tmp/fshd-<UID> to another file, fshd will chmod 0700 that file. - A race condition made it possible for an attacker to create an unsafe socket directory, so that the attacker can access an fshd tunnel. The attacker must alread have a local shell on the computer where fsh or fshd is invoked. Other changes: New timeout option, fixed to work with openssh2, now also usable if you have to enter a password to connect, and some others.
2000-01-14Initial import of fsh-1.0, "fast remote command execution". The authorfredb5-0/+41
states that the motivation for this program was to speed up cvs work, but it works just as well with "rsync" and other programs that use ssh for the transport. This is a set of python scripts: "fsh" uses ssh, (or optionally rsh or lsh) to start and set up a connection to "fshd" on the remote host, also includes "fcp", and docs in "info" format.