Re: New f29 install, windows 10 not detected / grub2-editenv nit

[Hans de Goede]

Hi,

On 09-01-19 19:16, Hans de Goede wrote:

Hi,

On 09-01-19 16:10, Richard Shaw wrote:

On Wed, Jan 9, 2019 at 8:57 AM Hans de Goede mailto:hdego...@redhat.com>> wrote:

    Hi,

    On 09-01-19 15:11, Richard Shaw wrote:
 > Following up on Windows 10 not being detected I have a strange (to me) 
issue...
 >
 > Windows 10 created an EFI partition
 >
 > Fedora did a EFI install but DID NOT install the EFI data to the EFI 
partition that Windows created and DID NOT create one of its own. The Fedora EFI 
files are installed to the plain /boot partition.
 >
 > Now I will say this is a somewhat older computer and has pretty early 
EFI support (EFI Ready). There's no configurable EFI options in the BIOS other 
than for CD/DVD booting.
 >
 > Thoughts?

    I believe this means that Fedora did not recognize your machine as using 
UEFI
    and is using classic BIOS boot instead. When you installed Fedora and
    booted from a CD or USB stick, you likely got the option to either boot
    Fedora in classic BIOS mode (probably marked in your BIOS boot menu as just "USB 
storage"
    or some such) and to boot it in UEFI mode (marked with EFI in the name 
somewhere),
    I think you probably picked the classic option, causing Fedora to do
    a classic install.


Ok... I thought the presence of /boot/efi/EFI meant it was booting UEFI but I 
checked my MythTV system which hasn't seen a fresh install since 2012 and it 
has those directories as well. It does have BIOS_BOOT since the main HD is gpt 
partitioned.

    Since you are getting what is most likely a classic BIOS grub version now
    when booting now your BIOS likely remembered that you booted in classic mode
    the last time and stuck with that.

    If Windows 10 expects to be loaded through UEFI then chainloading won't 
work.
    Take a look in your BIOS if you can turn EFI mode on, or try hitting F12 / 
F8
    (or some such) to get your BIOS boot menu. Probably you can choose between
    UEFI and classic booting your harddisk.


I'll double check but it treats the USB has a hard disk and I don't recall 
seeing a EFI option. The ONLY option related to EFI in the BIOS is for CD/DVD 
devices which is set, hence Win10 getting installed EFI using the disc. I may 
have to actually burn the ISO to disk to get it to boot in UEFI mode.


In that case it is probably easier to convert your existing install to UEFI:

1) Move /boot/efi contents to some place
2) Edit fstab mount the existing EFI system partition on /boot/efi
3) mount /boot/efi
4) move /boot/efi contents back in place
5) Run efibootmgr, doing something like:

efibootmgr -c -d /dev/sda -p 1 -L Fedora -l '\EFI\fedora\grubx64.efi'

This will tell your BIOS to add a "Fedora" entry to its UEFI boot menu.

You may need to adjust the /dev/sda and the partition "1" to match
your system. Also this assume your system and Fedora install are 64 bits,
UEFI is only supported with a 64 bit install. Perhaps that is why
your BIOS is not giving an EFI option for the USB disk ?

For some more info on how to convert a system to UEFI see:
https://oded.blog/2017/11/13/fedora-bios-to-uefi/

You may also want to use the -o option after running the -c
(for create) command to make Fedora the default.

Ugh I just realized that efibootmgr will only work if
you are already booted in UEFI mode. If you can get Windows
to boot again by trying to re-enable UEFI or some such
in the BIOS you can probably find a similar tool under
Windows. Sometimes UEFI BIOS also allow you to select an
EFI binary to execute, in that case you can navigate to
EFI\fedora\grubx64.efi and execute it directly or if
you can start an EFI commandline shell you can start
grubx64.efi from there.

Once you've booted Fedora in UEFI mode that way you can
use the efibootmgr command to permanently add Fedora to
the list of OS-es the UEFI part of your BIOS knows about.

If there is none of these options you may need to clear your mbr
or open fdisk and re-write the existing GPT table, so that you get
a dummy old style partition table (as is normally used with GPT)
that may kick the BIOS back into UEFI mode and give you Windows 10
again.

Note steps 1-4 are harmless (if done correct) and you will still
be able to boot in legacy mode regardless.


p.s.

Once you have Fedora booting in UEFI mode, re-run grub2-mkconfig and
now it will hopefully pickup the Windows install.

REgards,

Hans
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: cannot change password: Authentication token manipulation error

[Frédéric]

> > sudo touch /.autorelabel

I did that + reboot and now passwd works.
Thanks a lot!

F
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: New f29 install, windows 10 not detected / grub2-editenv nit

[Robin Laing]

On 09/01/2019 12:35, Richard Shaw wrote:
On Wed, Jan 9, 2019 at 12:16 PM Hans de Goede > wrote:




>> SNIP  <<





We'll see what happens. I've recovered from worse and my son doesn't 
have any critical data anyway.


When I had this problem, I just let my son pick Windows from the BIOS as 
it is on it's own drive as well as Linux.  As he uses Windows for gaming 
on this machine, I let it boot automatically into Windows instead of Fedora.


I am lazy this way.  :)

Robin
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[Robin Laing]

On 08/01/2019 17:52, George N. White III wrote:
On Tue, 8 Jan 2019 at 12:10, Alex > wrote:


Hi,
I need a gateway for our new office. I'd like it to run Fedora. What
are my options? I'd like to be able to do the following:

   - provide VPN back to the main office
   - provide basic masquerading of hosts on inside network
   - be small enough to fit on a shelf. Preferably fanless
   - web-based administration
   - ssh access


Have a look at https://www.pcengines.ch/apu2.htm  These offer 2 or 3 
ethernet

ports, small form factor, and fanless.  Fedora is not a good choice for this
role unless you are willing to devote time and effort to testing new 
versions

as they appear.  In that case you would want a couple systems so each new
release could be tested before going into serivice.   Pcengines has centos7
images for apu systems.

We're experienced admins, so a simple interface isn't specifically
necessary, but desired.

It's only for a few remote office workers, so it doesn't have to be
particularly powerful, but should be responsive enough to support
regular ssh and VPN activity.


Avoid USB NIC's.     Have a look at pfSense 


--
George N. White III




Working on this as well.

I have looked at pfSense and I am also looking at OPNsense

https://opnsense.org/   

I have a friend that uses pfsense for a small network at a resort and 
does remote admin when required.  For wireless he uses dedicated access 
points.  IPFire looks interesting but it looks like it wants to be more 
than a firewall/gateway.


https://www.ipfire.org/

The one point my friend mentions is using seperate network ports for the 
various vlans and combine at the firewall.  He prefers this method for 
his network.


I would look at a fanless solution as well.  We have had some Intel 
based units that have been major problems with heat.  Needed to be in 
cool rooms all the time.  Cannot remember the name though.


pfSense has a list of recommended hardware for throughput bandwidth.

http://pfsensesetup.com/pfsense-hardware-requirements/

It is interesting to read.

Have fun.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[John Harris]

On Wednesday, January 9, 2019 3:01:33 PM EST Samuel Sieb wrote:
> If you're suggesting to run Fedora off a USB port, then remember that 
> they also usually only have max 32MB of RAM as well. :-)

32-64 MiB, but that's fine. More than enough. You just can't use one of the 
standard images.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

signature.asc
Description: This is a digitally signed message part.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[Samuel Sieb]

On 1/9/19 11:51 AM, John Harris wrote:

On Wednesday, January 9, 2019 2:36:53 PM EST Samuel Sieb wrote:

I use Fedora for desktops, laptops, and servers in various places, but
in this case, Fedora is not suitable to run on a wifi router.  In a lot
of cases, there is only 8MB of flash to store the OS, or if you're
really lucky or willing to pay a lot more, you can get twice that.


While I'm not suggesting the use of Fedora on a stock residential router, most
of these routers also have a USB port.


If you're suggesting to run Fedora off a USB port, then remember that 
they also usually only have max 32MB of RAM as well. :-)



I second the suggestion of using such a device.  It's quiet, low power,
and easy config.  I have considered, but haven't got around to trying to
setup openvpn on one yet, so that's an unknown.  You could find a cheap,
openwrt supported router from a second-hand store to test out before
buying a better one.


I'd highly suggest using Wireguard rather than OpenVPN. I got around to
switching my personal systems the other day, and the benefits are immediately
noticeable. I can push gigabit over my home VPN. :)


I have been running openvpn for many years and my VPN network is 
widespread.  I only heard about Wireguard recently, but it's something I 
should look into.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[John Harris]

On Wednesday, January 9, 2019 2:36:53 PM EST Samuel Sieb wrote: 
> I use Fedora for desktops, laptops, and servers in various places, but 
> in this case, Fedora is not suitable to run on a wifi router.  In a lot 
> of cases, there is only 8MB of flash to store the OS, or if you're 
> really lucky or willing to pay a lot more, you can get twice that.

While I'm not suggesting the use of Fedora on a stock residential router, most 
of these routers also have a USB port.

> I second the suggestion of using such a device.  It's quiet, low power, 
> and easy config.  I have considered, but haven't got around to trying to 
> setup openvpn on one yet, so that's an unknown.  You could find a cheap, 
> openwrt supported router from a second-hand store to test out before 
> buying a better one.

I'd highly suggest using Wireguard rather than OpenVPN. I got around to 
switching my personal systems the other day, and the benefits are immediately 
noticeable. I can push gigabit over my home VPN. :)

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

signature.asc
Description: This is a digitally signed message part.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[Samuel Sieb]

On 1/9/19 12:19 AM, John Harris wrote:

On Wednesday, January 9, 2019 3:14:25 AM EST Terry Barnaby wrote:

I know you asked for Fedora, but a standard, low cost router, running
OpenWRT, https://openwrt.org/, would likely be better for the tasks you
mention. OpenWRT is a minimal Linux system with the ability to install
extra packages. It has a simple to use WEB admin system and can do all
the things you mention.


I cannot think of any reason not to use ones distro of choice as their gateway
and/or VPN. I personally use a system Fedora (well, Fedora + Freed-ora-
freedom) for my router and VPN. OpenWRT is not inherently better than Fedora,
and there are many benefits of using Fedora over OpenWRT.


I use Fedora for desktops, laptops, and servers in various places, but 
in this case, Fedora is not suitable to run on a wifi router.  In a lot 
of cases, there is only 8MB of flash to store the OS, or if you're 
really lucky or willing to pay a lot more, you can get twice that.


I second the suggestion of using such a device.  It's quiet, low power, 
and easy config.  I have considered, but haven't got around to trying to 
setup openvpn on one yet, so that's an unknown.  You could find a cheap, 
openwrt supported router from a second-hand store to test out before 
buying a better one.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: New f29 install, windows 10 not detected / grub2-editenv nit

[Richard Shaw]

On Wed, Jan 9, 2019 at 12:16 PM Hans de Goede  wrote:

> Hi,
>
> On 09-01-19 16:10, Richard Shaw wrote:
> > On Wed, Jan 9, 2019 at 8:57 AM Hans de Goede  > wrote:
> >
> > I'll double check but it treats the USB has a hard disk and I don't
> recall seeing a EFI option. The ONLY option related to EFI in the BIOS is
> for CD/DVD devices which is set, hence Win10 getting installed EFI using
> the disc. I may have to actually burn the ISO to disk to get it to boot in
> UEFI mode.
>
> In that case it is probably easier to convert your existing install to
> UEFI:
>
> 1) Move /boot/efi contents to some place
> 2) Edit fstab mount the existing EFI system partition on /boot/efi
> 3) mount /boot/efi
> 4) move /boot/efi contents back in place
> 5) Run efibootmgr, doing something like:
>
> efibootmgr -c -d /dev/sda -p 1 -L Fedora -l '\EFI\fedora\grubx64.efi'
>
> This will tell your BIOS to add a "Fedora" entry to its UEFI boot menu.
>
> You may need to adjust the /dev/sda and the partition "1" to match
> your system. Also this assume your system and Fedora install are 64 bits,
> UEFI is only supported with a 64 bit install. Perhaps that is why
> your BIOS is not giving an EFI option for the USB disk ?
>

I've been 64 bits only for years...


For some more info on how to convert a system to UEFI see:
> https://oded.blog/2017/11/13/fedora-bios-to-uefi/
>
> You may also want to use the -o option after running the -c
> (for create) command to make Fedora the default.
>
> Ugh I just realized that efibootmgr will only work if
> you are already booted in UEFI mode. If you can get Windows
> to boot again by trying to re-enable UEFI or some such
> in the BIOS you can probably find a similar tool under
> Windows. Sometimes UEFI BIOS also allow you to select an
> EFI binary to execute, in that case you can navigate to
> EFI\fedora\grubx64.efi and execute it directly or if
> you can start an EFI commandline shell you can start
> grubx64.efi from there.
>

Worst case I can hopefully boot UEFI from the Live disc (instead of USB),
move all the data around, and then chroot before running efibootmgr.



> Once you've booted Fedora in UEFI mode that way you can
> use the efibootmgr command to permanently add Fedora to
> the list of OS-es the UEFI part of your BIOS knows about.
>
> If there is none of these options you may need to clear your mbr
> or open fdisk and re-write the existing GPT table, so that you get
> a dummy old style partition table (as is normally used with GPT)
> that may kick the BIOS back into UEFI mode and give you Windows 10
> again.
>
> Note steps 1-4 are harmless (if done correct) and you will still
> be able to boot in legacy mode regardless.
>

We'll see what happens. I've recovered from worse and my son doesn't have
any critical data anyway.

Thanks for the help!

Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[Michael Watters]

Look up Jetway devices.  They're small, fanless, and don't use a lot of
power.


On 1/8/19 11:09 AM, Alex wrote:
> Hi,
> I need a gateway for our new office. I'd like it to run Fedora. What
> are my options? I'd like to be able to do the following:
>
>   - provide VPN back to the main office
>   - provide basic masquerading of hosts on inside network
>   - be small enough to fit on a shelf. Preferably fanless
>   - web-based administration
>   - ssh access
>
> We're experienced admins, so a simple interface isn't specifically
> necessary, but desired.
>
> It's only for a few remote office workers, so it doesn't have to be
> particularly powerful, but should be responsive enough to support
> regular ssh and VPN activity.
>
> Thanks,
> Alex
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: New f29 install, windows 10 not detected / grub2-editenv nit

[Hans de Goede]

Hi,

On 09-01-19 16:10, Richard Shaw wrote:

On Wed, Jan 9, 2019 at 8:57 AM Hans de Goede mailto:hdego...@redhat.com>> wrote:

Hi,

On 09-01-19 15:11, Richard Shaw wrote:
 > Following up on Windows 10 not being detected I have a strange (to me) 
issue...
 >
 > Windows 10 created an EFI partition
 >
 > Fedora did a EFI install but DID NOT install the EFI data to the EFI 
partition that Windows created and DID NOT create one of its own. The Fedora EFI 
files are installed to the plain /boot partition.
 >
 > Now I will say this is a somewhat older computer and has pretty early 
EFI support (EFI Ready). There's no configurable EFI options in the BIOS other 
than for CD/DVD booting.
 >
 > Thoughts?

I believe this means that Fedora did not recognize your machine as using 
UEFI
and is using classic BIOS boot instead. When you installed Fedora and
booted from a CD or USB stick, you likely got the option to either boot
Fedora in classic BIOS mode (probably marked in your BIOS boot menu as just "USB 
storage"
or some such) and to boot it in UEFI mode (marked with EFI in the name 
somewhere),
I think you probably picked the classic option, causing Fedora to do
a classic install.


Ok... I thought the presence of /boot/efi/EFI meant it was booting UEFI but I 
checked my MythTV system which hasn't seen a fresh install since 2012 and it 
has those directories as well. It does have BIOS_BOOT since the main HD is gpt 
partitioned.

Since you are getting what is most likely a classic BIOS grub version now
when booting now your BIOS likely remembered that you booted in classic mode
the last time and stuck with that.

If Windows 10 expects to be loaded through UEFI then chainloading won't 
work.
Take a look in your BIOS if you can turn EFI mode on, or try hitting F12 / 
F8
(or some such) to get your BIOS boot menu. Probably you can choose between
UEFI and classic booting your harddisk.


I'll double check but it treats the USB has a hard disk and I don't recall 
seeing a EFI option. The ONLY option related to EFI in the BIOS is for CD/DVD 
devices which is set, hence Win10 getting installed EFI using the disc. I may 
have to actually burn the ISO to disk to get it to boot in UEFI mode.


In that case it is probably easier to convert your existing install to UEFI:

1) Move /boot/efi contents to some place
2) Edit fstab mount the existing EFI system partition on /boot/efi
3) mount /boot/efi
4) move /boot/efi contents back in place
5) Run efibootmgr, doing something like:

efibootmgr -c -d /dev/sda -p 1 -L Fedora -l '\EFI\fedora\grubx64.efi'

This will tell your BIOS to add a "Fedora" entry to its UEFI boot menu.

You may need to adjust the /dev/sda and the partition "1" to match
your system. Also this assume your system and Fedora install are 64 bits,
UEFI is only supported with a 64 bit install. Perhaps that is why
your BIOS is not giving an EFI option for the USB disk ?

For some more info on how to convert a system to UEFI see:
https://oded.blog/2017/11/13/fedora-bios-to-uefi/

You may also want to use the -o option after running the -c
(for create) command to make Fedora the default.

Ugh I just realized that efibootmgr will only work if
you are already booted in UEFI mode. If you can get Windows
to boot again by trying to re-enable UEFI or some such
in the BIOS you can probably find a similar tool under
Windows. Sometimes UEFI BIOS also allow you to select an
EFI binary to execute, in that case you can navigate to
EFI\fedora\grubx64.efi and execute it directly or if
you can start an EFI commandline shell you can start
grubx64.efi from there.

Once you've booted Fedora in UEFI mode that way you can
use the efibootmgr command to permanently add Fedora to
the list of OS-es the UEFI part of your BIOS knows about.

If there is none of these options you may need to clear your mbr
or open fdisk and re-write the existing GPT table, so that you get
a dummy old style partition table (as is normally used with GPT)
that may kick the BIOS back into UEFI mode and give you Windows 10
again.

Note steps 1-4 are harmless (if done correct) and you will still
be able to boot in legacy mode regardless.

Regards,

Hans
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: New f29 install, windows 10 not detected / grub2-editenv nit

[Richard Shaw]

On Wed, Jan 9, 2019 at 8:57 AM Hans de Goede  wrote:

> Hi,
>
> On 09-01-19 15:11, Richard Shaw wrote:
> > Following up on Windows 10 not being detected I have a strange (to me)
> issue...
> >
> > Windows 10 created an EFI partition
> >
> > Fedora did a EFI install but DID NOT install the EFI data to the EFI
> partition that Windows created and DID NOT create one of its own. The
> Fedora EFI files are installed to the plain /boot partition.
> >
> > Now I will say this is a somewhat older computer and has pretty early
> EFI support (EFI Ready). There's no configurable EFI options in the BIOS
> other than for CD/DVD booting.
> >
> > Thoughts?
>
> I believe this means that Fedora did not recognize your machine as using
> UEFI
> and is using classic BIOS boot instead. When you installed Fedora and
> booted from a CD or USB stick, you likely got the option to either boot
> Fedora in classic BIOS mode (probably marked in your BIOS boot menu as
> just "USB storage"
> or some such) and to boot it in UEFI mode (marked with EFI in the name
> somewhere),
> I think you probably picked the classic option, causing Fedora to do
> a classic install.
>

Ok... I thought the presence of /boot/efi/EFI meant it was booting UEFI but
I checked my MythTV system which hasn't seen a fresh install since 2012 and
it has those directories as well. It does have BIOS_BOOT since the main HD
is gpt partitioned.



> Since you are getting what is most likely a classic BIOS grub version now
> when booting now your BIOS likely remembered that you booted in classic
> mode
> the last time and stuck with that.
>
> If Windows 10 expects to be loaded through UEFI then chainloading won't
> work.
> Take a look in your BIOS if you can turn EFI mode on, or try hitting F12 /
> F8
> (or some such) to get your BIOS boot menu. Probably you can choose between
> UEFI and classic booting your harddisk.
>

I'll double check but it treats the USB has a hard disk and I don't recall
seeing a EFI option. The ONLY option related to EFI in the BIOS is for
CD/DVD devices which is set, hence Win10 getting installed EFI using the
disc. I may have to actually burn the ISO to disk to get it to boot in UEFI
mode.

Thanks,
Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: New f29 install, windows 10 not detected / grub2-editenv nit

[Hans de Goede]

Hi,

On 09-01-19 15:11, Richard Shaw wrote:

Following up on Windows 10 not being detected I have a strange (to me) issue...

Windows 10 created an EFI partition

Fedora did a EFI install but DID NOT install the EFI data to the EFI partition 
that Windows created and DID NOT create one of its own. The Fedora EFI files 
are installed to the plain /boot partition.

Now I will say this is a somewhat older computer and has pretty early EFI 
support (EFI Ready). There's no configurable EFI options in the BIOS other than 
for CD/DVD booting.

Thoughts?


I believe this means that Fedora did not recognize your machine as using UEFI
and is using classic BIOS boot instead. When you installed Fedora and
booted from a CD or USB stick, you likely got the option to either boot
Fedora in classic BIOS mode (probably marked in your BIOS boot menu as just "USB 
storage"
or some such) and to boot it in UEFI mode (marked with EFI in the name 
somewhere),
I think you probably picked the classic option, causing Fedora to do
a classic install.

Since you are getting what is most likely a classic BIOS grub version now
when booting now your BIOS likely remembered that you booted in classic mode
the last time and stuck with that.

If Windows 10 expects to be loaded through UEFI then chainloading won't work.
Take a look in your BIOS if you can turn EFI mode on, or try hitting F12 / F8
(or some such) to get your BIOS boot menu. Probably you can choose between
UEFI and classic booting your harddisk.

If you've not customized Fedora a lot yet, it is probably best to
re-install Fedora and make sure you pick the UEFI boot option this time.

Regards,

Hans
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[Oleg Cherkasov]

On 08.01.2019 17:09, Alex wrote:

Hi,
I need a gateway for our new office. I'd like it to run Fedora. What
are my options? I'd like to be able to do the following:

   - provide VPN back to the main office
   - provide basic masquerading of hosts on inside network
   - be small enough to fit on a shelf. Preferably fanless
   - web-based administration
   - ssh access

We're experienced admins, so a simple interface isn't specifically
necessary, but desired.

It's only for a few remote office workers, so it doesn't have to be
particularly powerful, but should be responsive enough to support
regular ssh and VPN activity.



I had been using https://www.ipfire.org/ in a past and later switched to 
pfSense so I would really recommend IPFire if you want to have full 
control on firewall on low level and simple decent setup/conf interface 
as well.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[John Harris]

On Wednesday, January 9, 2019 9:05:56 AM EST Chris Adams wrote:
> It's the difference between using a multitool and a purpose-built tool.
> Sure, your Leatherman or Gerber can strip wires and screw in a switch,
> but a good pair of wire strippers and assorted size screwdrivers will
> usually be more convenient (and quicker) to use.

I cannot think of a more dishonest comparison. A multitool cannot be easily 
reconfigured to meet a given purpose. A multitool could not be made to be as 
ergonomic and efficient of a screwdriver as a real screwdriver, for example. 
With Fedora, you can configure the system to be anything you could ever need.

> OpenWrt is a light-weight system designed for router setups.  It has an
> integrated web UI (for those that want it) that can configure and
> monitor traffic, and all configuration normally needed is in a small set
> of config files in one directory and in a common format (makes
> management much easier for occasional edits).

Sure, and if you're alright with throwing up something in a system you're 
unfamiliar with, or you don't have time to properly manage yet another system, 
maybe it's a good idea.

> There are things that OpenWrt does easily that Fedora doesn't do at all;
> for example, the web UI on OpenWrt includes real-time traffic graphs.  I
> don't know of anything that can provide that in Fedora.

There are several packages that you could install to show you real-time 
statistics of your system's network interfaces (including virtual interfaces). 
Cockpit is one which the Fedora Server folks put in their default image.

> Also, OpenWrt uses much less resources than any general-purpose OS
> install, so costs less.

This isn't necessarily true. It would depend heavily on what you install, and 
how you configure it. Out of box? Sure.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

signature.asc
Description: This is a digitally signed message part.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: New f29 install, windows 10 not detected / grub2-editenv nit

[Richard Shaw]

Following up on Windows 10 not being detected I have a strange (to me)
issue...

Windows 10 created an EFI partition

Fedora did a EFI install but DID NOT install the EFI data to the EFI
partition that Windows created and DID NOT create one of its own. The
Fedora EFI files are installed to the plain /boot partition.

Now I will say this is a somewhat older computer and has pretty early EFI
support (EFI Ready). There's no configurable EFI options in the BIOS other
than for CD/DVD booting.

Thoughts?

Do I just need to add a manual option and chainload Win10?

Thanks,
Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[Chris Adams]

Once upon a time, John Harris  said:
> I cannot think of any reason not to use ones distro of choice as their 
> gateway 
> and/or VPN. I personally use a system Fedora (well, Fedora + Freed-ora-
> freedom) for my router and VPN. OpenWRT is not inherently better than Fedora, 
> and there are many benefits of using Fedora over OpenWRT.

It's the difference between using a multitool and a purpose-built tool.
Sure, your Leatherman or Gerber can strip wires and screw in a switch,
but a good pair of wire strippers and assorted size screwdrivers will
usually be more convenient (and quicker) to use.

OpenWrt is a light-weight system designed for router setups.  It has an
integrated web UI (for those that want it) that can configure and
monitor traffic, and all configuration normally needed is in a small set
of config files in one directory and in a common format (makes
management much easier for occasional edits).

There are things that OpenWrt does easily that Fedora doesn't do at all;
for example, the web UI on OpenWrt includes real-time traffic graphs.  I
don't know of anything that can provide that in Fedora.

Also, OpenWrt uses much less resources than any general-purpose OS
install, so costs less.
-- 
Chris Adams 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[Chris Adams]

Once upon a time, Samuel Sieb  said:
> On 1/8/19 11:15 AM, Chris Adams wrote:
> >Once upon a time, Tom Horsley  said:
> >>Intel sells boxes they call NUCs.
> >
> >NUC only has one ethernet port built-in, although newer models also have
> >a Thunderbolt port, which should drive a decent speed network.
> 
> The servers I run usually only have 1 Ethernet port.  I use a
> managed switch with vlan support to provide as many ports as I need.

That's fine for servers, but would add significant cost and additional
management and bandwidth overhead for a router.  I have gigabit Internet
service; hairpinning all the traffic through a single port turns a
full-duplex service into half-duplex.

-- 
Chris Adams 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[John Harris]

On Wednesday, January 9, 2019 7:48:24 AM EST wwp wrote:
> True, but you may also fail at upgrading (see the users ML) and it
> means possibly fail every 6 months ;-). You cannot be serious in
> recommending Fedora for a server in production, just because it has
> up-to-date software without mentioning that it would bring fresh fixes,
> yes, but also fresh bugs. And that's not what I'd recommend to
> handle a server in production, unless you are both the user and the
> admin and it's your own home/office and your responsibility only
> involves you and no real cost if something goes wrong. Or, unless your
> hardware requires kernel (and more) support that is only found in
> Fedora, which is another important detail (for instance, you might fail
> w/ CentOS7 or Redhat7 on fresh hardware).

I would definitely suggest Fedora for production servers, but this is another 
conversation entirely. I'd be happy to discuss this with you in a separate 
thread.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

signature.asc
Description: This is a digitally signed message part.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[wwp]

Hello,


On Wed, 09 Jan 2019 07:37:53 -0500 John Harris  wrote:

[snip]
> > 4. Fedora's aggressive new "feature" release cycle is painful for such 
> > low level infrastructure.  
> 
> Nope. Fedora has releases about every 6 months. This means your systems will 
> just about always have the latest and greatest stable code.
[snip]

True, but you may also fail at upgrading (see the users ML) and it
means possibly fail every 6 months ;-). You cannot be serious in
recommending Fedora for a server in production, just because it has
up-to-date software without mentioning that it would bring fresh fixes,
yes, but also fresh bugs. And that's not what I'd recommend to
handle a server in production, unless you are both the user and the
admin and it's your own home/office and your responsibility only
involves you and no real cost if something goes wrong. Or, unless your
hardware requires kernel (and more) support that is only found in
Fedora, which is another important detail (for instance, you might fail
w/ CentOS7 or Redhat7 on fresh hardware).


Regards,

-- 
wwp


pgprjH3NLfti1.pgp
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[John Harris]

On Wednesday, January 9, 2019 4:33:25 AM EST Terry Barnaby wrote:
> 1. Fedora is big and bloated for small/low powered hardware that can be 
> used for this task and low energy usage is important in my opinion for 
> 24/7 systems.

I've successfully run Fedora (certainly not the images published, but still 
Fedora) on embedded devices without issue. Additionally, using Fedora doesn't 
inherently make your system use more energy than it otherwise would.

> 2. Fedora is complex for such a task.

Not really. It's more complex, because of your point 3, but not by a lot. It 
also has a lot of flexibility in comparison to things like OpenWRT.

> 3. Fedora hasn't a simple web interface to manage the particular 
> functionality that a simple router like device needs.

Sure.

> 4. Fedora's aggressive new "feature" release cycle is painful for such 
> low level infrastructure.

Nope. Fedora has releases about every 6 months. This means your systems will 
just about always have the latest and greatest stable code.

> 5. Other Linux systems have been designed to easily install on small 
> router like hardware easily and be easily used. As long as it is 
> OpenSource and Linux most of someone's knowledge of Fedora will be 
> applicable.

Fedora, as with many other GNU/Linux systems, is a general purpose operating 
system. As I said earlier, you can certainly install it on embedded devices 
such as routers. I'd be careful doing so, however, and look into the 
peripherals and their support in mainline before doing so. It is possible that 
you'll have to run Fedora from a custom kernel.

Little of ones knowledge of Fedora is really relevant to Linux.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

signature.asc
Description: This is a digitally signed message part.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: sudo

[Ulf Volmer]

On 09.01.19 10:13, Patrick Dupre wrote:
>>  $ mount /mnt/USB
> 
> The problem is that it tries to mount at boot even if the drive is off

Add noauto as option to your fstab line.
This and other options are documented in 'man fstab'.

best regards
Ulf
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[Terry Barnaby]

On 09/01/2019 08:19, John Harris wrote:

On Wednesday, January 9, 2019 3:14:25 AM EST Terry Barnaby wrote:

I know you asked for Fedora, but a standard, low cost router, running
OpenWRT, https://openwrt.org/, would likely be better for the tasks you
mention. OpenWRT is a minimal Linux system with the ability to install
extra packages. It has a simple to use WEB admin system and can do all
the things you mention.

I cannot think of any reason not to use ones distro of choice as their gateway
and/or VPN. I personally use a system Fedora (well, Fedora + Freed-ora-
freedom) for my router and VPN. OpenWRT is not inherently better than Fedora,
and there are many benefits of using Fedora over OpenWRT.

I agree there are pros in using a system you know and use on as many 
things as possible. I use Fedora on multiple servers, workstation, 
webservers, backup servers etc. However there are a few cons in use 
Fedora for such tasks, my particular cons for this task are:


1. Fedora is big and bloated for small/low powered hardware that can be 
used for this task and low energy usage is important in my opinion for 
24/7 systems.


2. Fedora is complex for such a task.

3. Fedora hasn't a simple web interface to manage the particular 
functionality that a simple router like device needs.


4. Fedora's aggressive new "feature" release cycle is painful for such 
low level infrastructure.


5. Other Linux systems have been designed to easily install on small 
router like hardware easily and be easily used. As long as it is 
OpenSource and Linux most of someone's knowledge of Fedora will be 
applicable.


Terry
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: sudo

[Patrick Dupre]

> On 1/8/19 8:38 AM, Ulf Volmer wrote:
> > On 08.01.19 10:57, Patrick Dupre wrote:
> > 
> >> With visudo, I did
> >> pdupre  localhost=/usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB/
> > 
> >> sudo /usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB
> > 
> > When you allow a specific command for sudo, you *must* use *exactly* the
> > same command. In this case the slash at the end is missing.
> > 
> > 'sudo -l' may be helpful.
> 
> You could also add an appropriate line to /etc/fstab and make sure the
> "user" option is specified. Then any non-root user can mount that
> filesystem. A line such as:
> 
>   /dev/mapper/VolGrpUsr_DK0-home /mnt/USB ext4 defaults,user 0 0
> 
> in /etc/fstab should permit any user to:
> 
>   $ mount /mnt/USB

The problem is that it tries to mount at boot even if the drive is off



> and accomplish what you want (assuming, of course, that /mnt/USB has
> appropriate permissions for the user). Not necessarily secure, but...
> --
> - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
> - AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
> --
> -  Never eat anything larger than your head  -
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[John Harris]

On Wednesday, January 9, 2019 3:14:25 AM EST Terry Barnaby wrote:
> I know you asked for Fedora, but a standard, low cost router, running 
> OpenWRT, https://openwrt.org/, would likely be better for the tasks you 
> mention. OpenWRT is a minimal Linux system with the ability to install 
> extra packages. It has a simple to use WEB admin system and can do all 
> the things you mention.

I cannot think of any reason not to use ones distro of choice as their gateway 
and/or VPN. I personally use a system Fedora (well, Fedora + Freed-ora-
freedom) for my router and VPN. OpenWRT is not inherently better than Fedora, 
and there are many benefits of using Fedora over OpenWRT.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

signature.asc
Description: This is a digitally signed message part.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Smallest Fedora box to use as gateway/firewall/VPN

[Terry Barnaby]

I know you asked for Fedora, but a standard, low cost router, running 
OpenWRT, https://openwrt.org/, would likely be better for the tasks you 
mention. OpenWRT is a minimal Linux system with the ability to install 
extra packages. It has a simple to use WEB admin system and can do all 
the things you mention.


I use cheap (£20 second hand on ebay) TP-Link TL-WDR3600 v1 routers and 
OpenWRT 18.06 at work and home. This particular router has 5 x 1Gbit 
Ethernet ports, Wifi (2.4 and 5GHz), 2 USB ports and has efficient use 
of power. Can connect to cable/FTTP/FTTC "modems" if needed etc. There 
are many other hardware platforms that would work with OpenWRT but this 
one works well and has a good amount of FLASH/RAM.


Terry

On 08/01/2019 16:09, Alex wrote:

Hi,
I need a gateway for our new office. I'd like it to run Fedora. What
are my options? I'd like to be able to do the following:

   - provide VPN back to the main office
   - provide basic masquerading of hosts on inside network
   - be small enough to fit on a shelf. Preferably fanless
   - web-based administration
   - ssh access

We're experienced admins, so a simple interface isn't specifically
necessary, but desired.

It's only for a few remote office workers, so it doesn't have to be
particularly powerful, but should be responsive enough to support
regular ssh and VPN activity.

Thanks,
Alex
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: cannot change password: Authentication token manipulation error

[Frédéric]

> Why do you need to set the LANG?

to get the error message in English to post to this list.

> Have you checked the journal for any messages?

I guess this is what matters:
AVC avc:  denied  { create } for  pid=6267 comm="passwd"
name="nshadow" scontext=unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:etc_t:s0 tclass=file permissive=0

Jan 09 09:05:16 gamma su[6232]: (to root) fred on pts/0
Jan 09 09:05:16 gamma audit[6232]: CRED_ACQ pid=6232 uid=1000
auid=1000 ses=6
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su"
hostname=gamma addr=? terminal=pts/0 res=success'
Jan 09 09:05:16 gamma su[6232]: pam_systemd(su-l:session): Cannot
create session: Already running in a session
Jan 09 09:05:16 gamma su[6232]: pam_unix(su-l:session): session opened
for user root by (uid=1000)
Jan 09 09:05:16 gamma audit[6232]: USER_START pid=6232 uid=1000
auid=1000 ses=6
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:session_open
grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_xauth
acct="root" exe="/usr/bin/su" hostname=gam>
Jan 09 09:05:44 gamma audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Jan 09 09:06:04 gamma audit[6267]: AVC avc:  denied  { create } for
pid=6267 comm="passwd" name="nshadow"
scontext=unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:etc_t:s0 tclass=file permissive=0
Jan 09 09:06:04 gamma audit[6267]: USER_CHAUTHTOK pid=6267 uid=0
auid=1000 ses=6 subj=unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023
msg='op=PAM:chauthtok grantors=? acct="root" exe="/usr/bin/passwd"
hostname=gamma addr=? terminal=pts/0 res=failed'
Jan 09 09:06:04 gamma passwd[6267]: gkr-pam: couldn't update the login
keyring password: no old password was entered


> Also, what is the result of "echo $?" run right after the passwd attempt?

1
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org