Glen Huang

12:14 strongSwan Feature #3423: Specify which certificates to send with send_certreq?: Thanks for the quick reply.
I didn't realize config was not yet matched when an initiator tried connect.
Howeve...
12:07 strongSwan Feature #3422: Allow multiple local.id to be specified in a single connection?: > You can use [[StrongswanConf#Referencing-other-Sections|section referencing]] or includes to simplify configuration...
09:53 strongSwan Feature #3423 (Closed): Specify which certificates to send with send_certreq?: When authenticate with certificates in a StrongSwan responder, I have CA certificates that are meant to authenticate ...
09:46 strongSwan Feature #3422 (Feedback): Allow multiple local.id to be specified in a single connection?: I have a StrongSwan server that wants to accept clients that can send different IDr. Due to local.id not being a list...

10:00 strongSwan Issue #3367: Docs on windows client: Oh, the container contains both the CA certificate and entity certificate.
Sorry for missing that.
It all makes...
09:49 strongSwan Issue #3367: Docs on windows client: Thanks for the quick reply.
> I think it already does.
If you mean [[Win7Certs]], I think it only says how to i...
08:46 strongSwan Issue #3367 (Closed): Docs on windows client: The doc on storing windows 7 machine certificate & certificate requirements, if I understand them correctly, makes it...

13:28 strongSwan Bug #3357: Avoid log message if mixed PKIs (RSA/ECDSA) are used with the openssl plugin: Tobias Brunner wrote:
> > So if I don't use CRLs or OCSP, I guess I can safely remove the x509 and pkcs1 plugins?
>...
13:23 strongSwan Issue #3359: unique = keep seems to behave like replace: Tobias Brunner wrote:
> > > As can be seen in the log message, that's because of the @INITIAL_CONTACT@ notify.
> > ...
13:07 strongSwan Issue #3359: unique = keep seems to behave like replace: > As can be seen in the log message, that's because of the @INITIAL_CONTACT@ notify.
So @INITIAL_CONTACT@ can make...

Also available in: Atom

strongSwan