Your message dated Sun, 22 Aug 2010 19:17:47 +0000
with message-id <e1ong39-0007du...@franck.debian.org>
and subject line Bug#587583: fixed in strongswan 4.4.1-2
has caused the Debian Bug report #587583,
regarding strongswan 4.4.0-2 does not work here: charon seems not to ignore all 
incoming requests/answers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
587583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: strongswan
Version: 4.4.0-2
Severity: grave

charon seems no ignore all incoming ikev2-request.

I downgraded both machines to strongswan 4.3.2-1.3 and all worked again.

I further left one with 4.3.2-1.3 and upgraded the other to 4.4.0-2. Whereas 
4.3.2-1.3 logs and answer packets sent by 4.4.0-2, the latter neither logs 
request nor anwers from 4.3.2-1.0.



Regards,

-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts



--- End Message ---
--- Begin Message ---
Source: strongswan
Source-Version: 4.4.1-2

We believe that the bug you reported is fixed in the latest version of
strongswan, which is due to be installed in the Debian FTP archive:

libstrongswan_4.4.1-2_amd64.deb
  to main/s/strongswan/libstrongswan_4.4.1-2_amd64.deb
strongswan-dbg_4.4.1-2_amd64.deb
  to main/s/strongswan/strongswan-dbg_4.4.1-2_amd64.deb
strongswan-ikev1_4.4.1-2_amd64.deb
  to main/s/strongswan/strongswan-ikev1_4.4.1-2_amd64.deb
strongswan-ikev2_4.4.1-2_amd64.deb
  to main/s/strongswan/strongswan-ikev2_4.4.1-2_amd64.deb
strongswan-nm_4.4.1-2_amd64.deb
  to main/s/strongswan/strongswan-nm_4.4.1-2_amd64.deb
strongswan-starter_4.4.1-2_amd64.deb
  to main/s/strongswan/strongswan-starter_4.4.1-2_amd64.deb
strongswan_4.4.1-2.debian.tar.gz
  to main/s/strongswan/strongswan_4.4.1-2.debian.tar.gz
strongswan_4.4.1-2.dsc
  to main/s/strongswan/strongswan_4.4.1-2.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 587...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Mayrhofer <rm...@debian.org> (supplier of updated strongswan package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 21 Aug 2010 23:28:47 +0200
Source: strongswan
Binary: strongswan libstrongswan strongswan-dbg strongswan-starter 
strongswan-ikev1 strongswan-ikev2 strongswan-nm
Architecture: source amd64
Version: 4.4.1-2
Distribution: unstable
Urgency: low
Maintainer: Rene Mayrhofer <rm...@debian.org>
Changed-By: Rene Mayrhofer <rm...@debian.org>
Description: 
 libstrongswan - strongSwan utility and crypto library
 strongswan - IPsec VPN solution metapackage
 strongswan-dbg - strongSwan library and binaries - debugging symbols
 strongswan-ikev1 - strongSwan Internet Key Exchange (v1) daemon
 strongswan-ikev2 - strongSwan Internet Key Exchange (v2) daemon
 strongswan-nm - strongSwan plugin to interact with NetworkManager
 strongswan-starter - strongSwan daemon starter and configuration file parser
Closes: 587583 593313
Changes: 
 strongswan (4.4.1-2) unstable; urgency=low
 .
   * Recompiled with dpkg-buildpackage instead of svn-buildpackage to
     make the clean target work. I am still looking for the root cause of
     this quilt 3.0 format and svn-buildpackage incompatibility.
     Closes: Bug#593313: strongswan: FTBFS because clean rule fails
   * Removed the --enable-socket-* configure options again. Having multiple
     socket variants for charon would force to explicitly enable one (in case
     of pluto co-existance the socket-raw) in strongswan.conf. Disabling the
     other variants for now at build-time relieves us from changing the
     default config file and might be more future-proof concerning future
     upstream changes to configure options.
     Really closes: #587583
Checksums-Sha1: 
 23fc6432fe511b1188e16c824cb006642df0e21a 1676 strongswan_4.4.1-2.dsc
 267f42620530af15afc55997a9edfcce17a56132 364208 
strongswan_4.4.1-2.debian.tar.gz
 9817d115badc2a233ab10f9fb378215d518b1e07 423168 libstrongswan_4.4.1-2_amd64.deb
 12e6147b7f34889672c9ec4aec9ebb49685a2de2 4349144 
strongswan-dbg_4.4.1-2_amd64.deb
 831ef92b48811803aabc4a39234da57761160a07 270762 
strongswan-starter_4.4.1-2_amd64.deb
 c7feb5316efd6565733e7da4a1c602f2e3e10379 355348 
strongswan-ikev1_4.4.1-2_amd64.deb
 ab499358df6517e20f9abf88f6e8ab22aad3303a 272946 
strongswan-ikev2_4.4.1-2_amd64.deb
 45d00aa3e5a06613a400185e9293572a0b55b306 51022 strongswan-nm_4.4.1-2_amd64.deb
Checksums-Sha256: 
 1efee6c951cba761fa87ed1ca3d0684769b5c003701daf83b0f3d1e4b045270d 1676 
strongswan_4.4.1-2.dsc
 85b02811c8e099c843a7b7b8fcbab71d9d78b3966706ab516170ec2af50b3cd4 364208 
strongswan_4.4.1-2.debian.tar.gz
 4f778dad03b52f2331a34d8e64fdc1ddd70f164ff9d52d915699df0f5a1cb664 423168 
libstrongswan_4.4.1-2_amd64.deb
 5b895e943563c1ed8fb345809803a9ae3e8d589200ddf704132ec4e7802744fc 4349144 
strongswan-dbg_4.4.1-2_amd64.deb
 fe19b33fa0e6221355fc904b2ef5e23c17496ad2929284151f6fdd0c9d64d427 270762 
strongswan-starter_4.4.1-2_amd64.deb
 969129e4818026fa5c3a99e1b0e6260a74d7b56347ca971df360b1392b6b8f71 355348 
strongswan-ikev1_4.4.1-2_amd64.deb
 5ec596abfa3e652de50a8cebaaef4e5af96645c1be689caf0ec1021189188ab8 272946 
strongswan-ikev2_4.4.1-2_amd64.deb
 cea6e2af2123f5b3b81980080ad84d183dbc41015389937f6fcc366babbca11c 51022 
strongswan-nm_4.4.1-2_amd64.deb
Files: 
 cde8b348db78bc1ff7ca8c90b2582f86 1676 net optional strongswan_4.4.1-2.dsc
 214f09d9d7e0cad5a80ffa2d63c350d5 364208 net optional 
strongswan_4.4.1-2.debian.tar.gz
 455ee947436e6ae71d34c657fb516ad7 423168 net optional 
libstrongswan_4.4.1-2_amd64.deb
 b054145c8816b3e7380617a33bfdf54d 4349144 debug extra 
strongswan-dbg_4.4.1-2_amd64.deb
 779530f9e9e6a8c439a1b7c19cd302be 270762 net optional 
strongswan-starter_4.4.1-2_amd64.deb
 37817a7f739029a3de67a48e494352d0 355348 net optional 
strongswan-ikev1_4.4.1-2_amd64.deb
 6d7cdeffd3e9f7ac68d4557a98144b3f 272946 net optional 
strongswan-ikev2_4.4.1-2_amd64.deb
 6f2fda2faf8882677500383f6b1a53a6 51022 net optional 
strongswan-nm_4.4.1-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkxwUTcACgkQq7SPDcPCS94+LwCg1w1XboWD/boEDmUzP/mK8EnS
2PIAniGksKpdQLlZsHAfz6WPRSXamGya
=toFK
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to