I have attached an example configuration where the pfSense server leftid
is configured with keyid:-prefix and therefor in unable to authenticate
an IPsec connection from a client where rightid does not contain
keyid:-prefix.
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "ipsec_client.secrets"
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1451091/+attachment/4420801/+files/ipsec_client.secrets
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Attachment added: "ipsec_sever.secrets"
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1451091/+attachment/4420802/+files/ipsec_sever.secrets
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
When using PSK in pfSense you are required to select identifier type.
Looking at it from a security perspective it seems better to explicit
define identifier type rather then auto detect type.
** Attachment added: "pfsense_ipsec_keyid.png"
https://bugs.launchpad.net/ubuntu/+source/strongswan/+
** Attachment added: "ipsec_server.conf"
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1451091/+attachment/4420800/+files/ipsec_server.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Attachment added: "ipsec_client.conf"
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1451091/+attachment/4420799/+files/ipsec_client.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
The current version of Strongswan (5.1.2) does not work with newer versions of
pfSense (Strongswan 5.3.2 based).
When using IPsec IKEv2/PSK the identity type is now prefixed leftid and rightid
for better matching.
The change requires at least Strongswan 5.2.2 but newest upstream is 5.3.2.
Source
** Summary changed:
- new upstream version 5.2.1
+ new upstream version 5.2.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451091
Title:
new upstream version 5.2.2
To manage notifications about
Public bug reported:
This happened during resume to login screen.
Ubuntu 3.13.0-23.45-generic 3.13.8
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-23-generic 3.13.0-23.45
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86
Public bug reported:
It fails with a generic error about using 3rd party packages, but who
doesn't install extra packages?
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-release-upgrader-core 1:0.205.4
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-1
*** This bug is a duplicate of bug 862185 ***
https://bugs.launchpad.net/bugs/862185
I can't open bug #862185 so I don't know if the duplicate mark is
correct.
Opening: https://bugs.launchpad.net/bugs/862185
Lost something?
This page does not exist, or you may not have permission to see it.
I
*** This bug is a duplicate of bug 862185 ***
https://bugs.launchpad.net/bugs/862185
$ lsb_release -rd
Description:Ubuntu precise (development branch)
Release:12.04
$ apt-cache policy gitg
gitg:
Installed: 0.2.4-0ubuntu1
Candidate: 0.2.4-0ubuntu1
Version table:
*** 0.2.4-0u
12 matches
Mail list logo