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 7/22/20 5:58 PM, Jack Craig wrote:
what is the current wisdom on debugging this fedora 32 freeze failure type?
You'll first need to provide some information.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to u
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
On Mon, Jul 20, 2020 at 10:10 AM Greg Woods wrote:
>
>
> What used to happen when I switched to a different computer is that I can
> use the new computer using the first monitor, the mouse and the keyboard,
> just as usual. The second monitor, unaffected by the KVM switch, will
> continue to show
Glad it worked out for you.
I don't know why your Sane is so different from mine.
I cannot find the "Bind X and Y resolutions" option in
Window - Show Advanced Options or Preferences - Setup.
But your Sane works and mine works, so everybody is happy.
Mike
On 7/22/20 6:40 PM, Stephen Morris
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
what is the current wisdom on debugging this fedora 32 freeze failure type?
thx, jackc...
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.f
On 22/7/20 9:09 pm, Mike Flannigan wrote:
Sure thing.
The 'xsane.rc' file at
~/.sane/xsane
is copied here:
http://www.mflan.com/temp/xsane.rc
There is also a 'xsane.mdf' file in there, but
I don't think you need that.
There is also a 'CANON:Canoscan9000FMarkII.drc'
file in there and it is copi
On Wed, Jul 22, 2020, 23:50 Bob Goodwin wrote:
>
>
> On 2020-07-21 21:19, Ed Greshko wrote:
> > OK, and do verify that the changes were made to /etc/nsswitch.conf.
> Just because paranoia is
> > at times not a bad thing.:-) :-)
> °
> I did that immediately after activating the change.
>
> The im
Thanks Robin, I wasn't sure it was me or a bug that need reporting.
On Wed, Jul 22, 2020 at 1:45 PM Robin Lee
wrote:
>
>
> Terry Polzin 于2020年7月23日 周四上午1:34写道：
>
>> I've been dealing with this issue on a couple of my Fedora 32 machines.
>> It appears that the upgrade of icedtea-web
>> from icedt
Terry Polzin 于2020年7月23日 周四上午1:34写道：
> I've been dealing with this issue on a couple of my Fedora 32 machines.
> It appears that the upgrade of icedtea-web
> from icedtea-web-1.8.2-3.fc31.x86_64 to
> icedtea-web-2.0.0-pre.0.3.alpha13.patched1.fc32.x86_64 breaks the
> alternatives link to javaws.x8
I've been dealing with this issue on a couple of my Fedora 32 machines.
It appears that the upgrade of icedtea-web
from icedtea-web-1.8.2-3.fc31.x86_64 to
icedtea-web-2.0.0-pre.0.3.alpha13.patched1.fc32.x86_64 breaks the
alternatives link to javaws.x86_64.
I have to downgrade icedtea-web to be abl
On 2020-07-21 21:19, Ed Greshko wrote:
OK, and do verify that the changes were made to /etc/nsswitch.conf. Just
because paranoia is
at times not a bad thing.:-) :-)
°
I did that immediately after activating the change.
The important thing is that I am able to print and satisfy the need for
On 7/22/20 07:57, Mauricio Tavares wrote:
> On Wed, Jul 22, 2020 at 6:14 AM Daniel Walsh wrote:
>> On 7/21/20 20:54, Gordon Messmer wrote:
>>> On 7/21/20 4:46 PM, Mauricio Tavares wrote:
What is the argument I need to properly pass a PCI or PCIe
device to a podman container at run
On Wed, Jul 22, 2020 at 6:14 AM Daniel Walsh wrote:
>
> On 7/21/20 20:54, Gordon Messmer wrote:
> > On 7/21/20 4:46 PM, Mauricio Tavares wrote:
> >>What is the argument I need to properly pass a PCI or PCIe
> >> device to a podman container at runtime (podman-run)?
> >
> >
> > Assuming tha
Sure thing.
The 'xsane.rc' file at
~/.sane/xsane
is copied here:
http://www.mflan.com/temp/xsane.rc
There is also a 'xsane.mdf' file in there, but
I don't think you need that.
There is also a 'CANON:Canoscan9000FMarkII.drc'
file in there and it is copied here:
http://www.mflan.com/temp/CANON:Ca
On 7/21/20 20:54, Gordon Messmer wrote:
> On 7/21/20 4:46 PM, Mauricio Tavares wrote:
>> What is the argument I need to properly pass a PCI or PCIe
>> device to a podman container at runtime (podman-run)?
>
>
> Assuming that it's supported by the OS running podman, I believe you
> can mount
25 matches
Mail list logo
