d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add notes pointing out that bsdiff does not store file hashes and

Browse Source 
bspatch thus does not verify file hashes, and that consequently it
is recommended that users store hashes separately and verify files
before and after running bspatch.

Requested by:	BugMagnet
MFC after:	1 week
This commit is contained in:
cperciva 2009-10-30 11:13:00 +00:00
parent f2a32c79ab
commit 299d516f33
2 changed files with 40 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
usr.bin/bsdiff/bsdiff/bsdiff.1
View File

@ -65,5 +65,24 @@ an absolute minimum working set size of 8 times the size of
.Ar oldfile .
.Sh SEE ALSO
.Xr bspatch 1
.Sh BUGS
The
.Nm
utility does not store the hashes of
.Ar oldfile
or
.Ar newfile
in
.Ar patchfile .
As a result, it is possible to apply a patch to the wrong file; this
will usually produce garbage.
It is recommended that users of
.Nm
store the hashes of
.Ar oldfile
and
.Ar newfile
and compare against them before and after applying
.Ar patchfile .
.Sh AUTHORS
.An Colin Percival Aq cperciva@FreeBSD.org

21
usr.bin/bsdiff/bspatch/bspatch.1
View File

@ -61,5 +61,26 @@ but can tolerate a very small working set without a dramatic loss
of performance.
.Sh SEE ALSO
.Xr bsdiff 1
.Sh BUGS
The
.Nm
utility does not verify that
.Ar oldfile
is the correct source file for
.Ar patchfile .
Attempting to apply a patch to the wrong file will usually produce
garbage; consequently it is strongly recommended that users of
.Nm
verify that
.Ar oldfile
matches the source file from which
.Ar patchfile
was built, by comparing cryptographic hashes, for example.
Users may also wish to verify after running
.Nm
that
.Ar newfile
matches the target file from which
.Ar was built.
.Sh AUTHORS
.An Colin Percival Aq cperciva@FreeBSD.org