--SNIs70sCzqvszXB4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Ben Collver writes:
> On Sat, Jan 22, 2005 at 04:41:43PM +0100, Lasse Kliemann wrote:
> > * Hubert Feyrer writes:
> > > On Sat, 22 Jan 2005, Lasse Kliemann wrote:
> > > >What do you intend to use them for?
> > >=20
> > > Verify (manually) that the binary pkgs are not modified.
> >=20
> > Modified by whom?
> >=20
> > He who can modify the binary packages can also modify the checksums, un=
less you=20
> > take extra precautions via file permissions and ownerships. But then, y=
ou can=20
> > protect the binary packages against modification from the start.
> >=20
> > Or am I missing something?
> > What is the exact scenario that you have in mind?
>=20
> How about corruption introduced by someone else's failing disks, or over
> the network itself?

Ok, in connection with a distribution of the binary packages over possibly=
=20
noisy channels or their storage on bad hardware, this makes sense.

--=20
Lasse Kliemann
      private homepage: http://plastictree.net
   NO software patents: http://swpat.ffii.org
do NOT use M$ products: http://plastictree.net/articles/noms

--SNIs70sCzqvszXB4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iD8DBQFB8oxZ1gObwed86AkRAuhVAKDJ86aKs7qqLMGW5tTsCkib6aVDWQCfYeiV
7zFLPzJ++vTrZk7fMkytwR4=
=aG4k
-----END PGP SIGNATURE-----

--SNIs70sCzqvszXB4--