[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded freeswan 1.95-1 (m68k) to non-us

Hash: SHA1

Format: 1.7
Date: Mon, 11 Feb 2002 00:23:18 +0100
Source: freeswan
Binary: kernel-patch-freeswan freeswan
Architecture: m68k
Version: 1.95-1
Distribution: unstable
Urgency: high
Maintainer: buildd m68k user account <buildd@ax.westfalen.de>
Changed-By: Rene Mayrhofer <rene.mayrhofer@vianova.at>
 freeswan   - IPSEC utilities for FreeSWan
Closes: 119637 120252 122115 122116 128000 128117 128471 129392
 freeswan (1.95-1) unstable; urgency=HIGH
   This release has urgency HIGH because it makes the package usable again.
   (The last upstream release is unusable.)
   * New upstream release.
     This release should make freeswan usable again, but the major changes
     seem to have happened in the x509 patches (which I include in the
     newest version in this package). The patched pluto is now able to read
     its RSA private key directly from a x509 file in PEM or DER format
     (please look at /usr/share/doc/freeswan/ipsec.secrets.template.x509 for
     details) instead of having to extract the key and store it in
     ipsec.secrets. Of cource, this makes my previously introduced
     extractrsakey.sh script useless, sigh.... Although I have invested some
     time in the previous solution, this one is definitely cleaner.
     Entering the private key file in ipsec.secrets automatically will be done
     by a future package, this one only creates new x509 certificates as
     before, but does not change ipsec.secrets (I have to release quickly).
     Closes: #129392, 120252
     I hope this also fixes the problem with the validity date of x509
     certificates. Since I was unable to reproduce the problem, I am closing
     the bug report. Please reopen it if it still does not work for you (but
     the I need more details for reproducing).
     Closes: #128117
   * The kernel-patch-freeswan should work with current kernels, at least on
     my system it does. If it does not compile for you, please send me
     a detailed report with the kernel version *and* the kernel configuration
     you are using.
     Closes: #128000, #122115, #122116
   * Made the postinst script a bit more robust against failures when starting
     freeswan (the kernel module might not be available yet).
     Closes: #128471
   * As far as I see it, the makefiles for patching the kernel have to be
     called from within the kernel patch directory. The KERNELSRC variable
     is responsible for changing files in the right directory (and that one
     gets set to the current working directory, which should be the kernel
     source dir when calling the apply script). Therefore I think the
     PATCHDIR variable is set correctly. If it does not work in some cases,
     then please send me a report where it does not work this way.
     For now, closing the bug report since it seems to work on all of my
     Closes: #119637
 8331dd5530f27f3e80ac0d5f2594e954 1604724 non-US/main optional freeswan_1.95-1_m68k.deb
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org


Reply to: