On 2020-07-23 20:45, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>>
>> What also needs to be documented, or I need to get better at searching, is
>> what are the possible values
>> for "option" when doing a modify of vpn.secrets and flags=1.
>>
>> "help" was of no "help".
>>
>> Error: failed to
Ed Greshko writes:
What also needs to be documented, or I need to get better at searching, is
what are the possible values
for "option" when doing a modify of vpn.secrets and flags=1.
"help" was of no "help".
Error: failed to modify vpn.secrets: 'help' is not valid; use
=.
I was able t
Ed Greshko writes:
On 2020-07-23 10:49, Sam Varshavchik wrote:
> This means the password is stored in the user's key ring on a per-
user basis.
>
> I haven't tried changing this via nmcli. But, will investigate.
FWIW
nmcli connection modify US-East-NJ vpn.secrets "password=something"
W
On 2020-07-23 10:49, Sam Varshavchik wrote:
> This means the password is stored in the user's key ring on a per-user basis.
>
> I haven't tried changing this via nmcli. But, will investigate.
FWIW
nmcli connection modify US-East-NJ vpn.secrets "password=something"
Works just fine for a log
On 2020-07-23 10:49, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>> On 2020-07-23 10:25, Sam Varshavchik wrote:
>> > vpn.data: auth = SHA512, ca = PEMFILEPATH,
>> > cipher = AES-256-CBC, comp-lzv = no-by-default, connection-type =
>> > password, dev = tun, mssfix =
Ed Greshko writes:
On 2020-07-23 10:25, Sam Varshavchik wrote:
>
vpn.data: auth = SHA512, ca = PEMFILEPATH, cipher = AES-256-
CBC, comp-lzv = no-by-default, connection-
type = password, dev = tun, mssfix = 1450, password-
flags = 1, ping = 15, ping-restart = 0,
Ed Greshko writes:
On 2020-07-23 10:15, Ed Greshko wrote:
> On 2020-07-23 09:20, Sam Varshavchik wrote:
>> Some searching around found some hits suggesting that my
/etc/NetworkManager/system-connections/CONNECTIONNAME should have a [vpn-
secrets] section, but mine does not. If I add it, run "
On 2020-07-23 10:25, Sam Varshavchik wrote:
> vpn.data: auth = SHA512, ca = PEMFILEPATH,
> cipher = AES-256-CBC, comp-lzo = no-by-default, connection-type = password,
> dev = tun, mssfix = 1450, password-flags = 1, ping = 15, ping-restart = 0,
> remote = OP_ADDRESS,
Ed Greshko writes:
On 2020-07-23 09:45, Ed Greshko wrote:
> On 2020-07-23 09:20, Sam Varshavchik wrote:
>> I'm trying to save an OpenVPN password via nmcli, in Fedora 32. I believe
I should be executing:
>>
>> nmcli connection modify CONNECTIONNAME vpn.secrets "password=[PASSWORD]"
>>
>> So I
On 2020-07-23 10:15, Ed Greshko wrote:
> On 2020-07-23 09:20, Sam Varshavchik wrote:
>> Some searching around found some hits suggesting that my
>> /etc/NetworkManager/system-connections/CONNECTIONNAME should have a
>> [vpn-secrets] section, but mine does not. If I add it, run "nmcli connection
On 2020-07-23 09:20, Sam Varshavchik wrote:
> Some searching around found some hits suggesting that my
> /etc/NetworkManager/system-connections/CONNECTIONNAME should have a
> [vpn-secrets] section, but mine does not. If I add it, run "nmcli connection
> reload", "nmcli connection modify", that j
On 2020-07-23 09:45, Ed Greshko wrote:
> On 2020-07-23 09:20, Sam Varshavchik wrote:
>> I'm trying to save an OpenVPN password via nmcli, in Fedora 32. I believe I
>> should be executing:
>>
>> nmcli connection modify CONNECTIONNAME vpn.secrets "password=[PASSWORD]"
>>
>> So I execute this as root
On 2020-07-23 09:20, Sam Varshavchik wrote:
> I'm trying to save an OpenVPN password via nmcli, in Fedora 32. I believe I
> should be executing:
>
> nmcli connection modify CONNECTIONNAME vpn.secrets "password=[PASSWORD]"
>
> So I execute this as root, and this initially produces very promising no
I'm trying to save an OpenVPN password via nmcli, in Fedora 32. I believe I
should be executing:
nmcli connection modify CONNECTIONNAME vpn.secrets "password=[PASSWORD]"
So I execute this as root, and this initially produces very promising noises
in /var/log/messages:
Jul 22 20:41:35 jack
14 matches
Mail list logo
