Problems found locating distfiles:
Package f-prot-antivirus6-fs-bin: missing distfile fp-NetBSD.x86.32-fs-6.2.3.tar.gz
Package f-prot-antivirus6-ws-bin: missing distfile fp-NetBSD.x86.32-ws-6.2.3.tar.gz
Package libidea: missing distfile libidea-0.8.2b.tar.gz
Package openssh: missing distfile openssh-7.1p1-hpn-20150822.diff.bz2
Package uvscan: missing distfile vlp4510e.tar.Z
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
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.
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.
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.
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.
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.
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.
