From: Julien Lepiller <julien@lepiller.eu>
To: jbranso@dismail.de, 39660@debbugs.gnu.org
Subject: bug#39660: openvpn-client-service does not support auth-user-pass
Date: Fri, 21 Feb 2020 12:27:11 -0500 [thread overview]
Message-ID: <9BF96819-AE31-4DA1-9D0D-44B749992914@lepiller.eu> (raw)
In-Reply-To: <8636b33lyj.fsf@dismail.de>
Le 21 février 2020 12:10:44 GMT-05:00, Joshua Branson via Bug reports for GNU Guix <bug-guix@gnu.org> a écrit :
>
>Julien and I discussed on irc that guix currently does not have a
>method of generating my config file. Here is just an updated list of
>the options that I (and possibly others) may need or want.
>
>#+BEGIN_SRC org
>These are all the options that my config file has. If the box does
>not have an X, then we should add this in the service definition.
>
>- [ ] "persist-key"
>- [ ] "persist-tun"
We already have both of them. Are they not documented? They should be persist-key? and persist-tun? respectively.
>- [ ] "remote-random"
>- [ ] "pull"
>- [X] "comp-lzo no"
>- [ ] "tls-client" does tls-auth provide this option???
tls-auth and tls-client are different options. tls-client replaces the client directive we currently generate for all openvpn-client-configuration.
>- [ ] "verify-x509-name Server name-prefix"
>- [ ] "ns-cert-type server" This is possibly deprecated?
>- [ ] "key-direction 1" This is another way of specifying tls-auth?
>- [X] "route-method exe" This is only useful on Windows.
>- [ ] "route-delay 2"
>- [X] "tun-mtu 1500" The documentation says most cases...I should
> leave this to it's default parameter. So unless needed, we probably
> shouldn't need to add it to guix.
>
>- The next two options only make sense when we are using the protocol
> udp. We should probably specify them someway that you can only use
> them if protocol is upd. Something like:
>
> #+BEGIN_SRC scheme
> (proto udp
> (upd-options
> (fragment 1300)
> (mssfix 1200))
> #+END_SRC
>
>- [X] "fragment 1300"
>- [X] "mssfix 1200"
>
>
>- [ ] "cipher AES-256-CBC"
>- [X] keysize 256 deprecated. Do not need. and my key size is the
>cipher size anyway. The documentation does not reccommend manually
>changing your keysize.
>- [X] auth SHA512 I have no idea where this is in the documentation
>- [X] sndbuf 524288 The documentation says that the default should
>work.
>- [X] rcvbuf 524288 as above
>- [X] auth-user-pass login.conf
>#+END_SRC
>
>We should also probably allow a file option. Some users may have a
>working file. Perhaps we should support this:
>
>#+BEGIN_SRC scheme
>(openvpn-client-service
> #:file "/path/to/openvpn.conf")
>#+END_SRC
>
>Joshua
next prev parent reply other threads:[~2020-02-21 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 14:43 bug#39660: openvpn-client-service does not support auth-user-pass Joshua Branson via Bug reports for GNU Guix
2020-02-19 3:14 ` Julien Lepiller
2020-02-21 17:10 ` Joshua Branson via Bug reports for GNU Guix
2020-02-21 17:27 ` Julien Lepiller [this message]
2020-02-23 19:33 ` bug#39660: (no subject) Joshua Branson
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9BF96819-AE31-4DA1-9D0D-44B749992914@lepiller.eu \
--to=julien@lepiller.eu \
--cc=39660@debbugs.gnu.org \
--cc=jbranso@dismail.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).