From: kotoko <kotoko@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Add support for pkcs11 in strongswan
Date: Thu, 16 Mar 2023 18:11:09 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42811@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
New issue by kotoko on void-packages repository
https://github.com/void-linux/void-packages/issues/42811
Description:
<!--
if you are creating a bug report or package request, please fill out one of the forms here:
https://github.com/void-linux/void-packages/issues/new/choose
Don't request an update of a package, We have a script for that:
https://repo-default.voidlinux.org/void-updates/void-updates.txt
However, a quality pull request may help.
-->
I have working vpn configuration using certificate that is stored on smartcard on linux mint. I am trying to setup same vpn on void linux. I think the problem is in strongswan that does not have plugin enabled. When I looked at [1] I see there is no plugin `pkcs11` enabled. According to [2] it is necessary to add option `--enable-pkcs11` before compilation.
Please add support for pkcs11 in strongswan.
[1] https://raw.githubusercontent.com/void-linux/void-packages/e21993428f6776a1730f92f23a3189c7c13becc8/srcpkgs/strongswan/template
[2] https://docs.strongswan.org/docs/5.9/plugins/pkcs11.html
next reply other threads:[~2023-03-16 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 17:11 kotoko [this message]
2023-03-28 12:45 ` abenson
2023-03-28 18:25 ` kotoko
2023-03-29 14:45 ` [ISSUE] [CLOSED] " abenson
2023-04-01 16:27 ` kotoko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42811@inbox.vuxu.org \
--to=kotoko@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).