Hi.
On Mon, 02 Jun 2025 22:45:48 +0700 Frederic Muller wrote:
> On 02/06/2025 21:45, francis.montag...@inria.fr wrote:
>> AFAIK sudo cannot be configured to authenticate with SSH keys.
> of course it can.
Effectively, a search shows that this is possible by configuring sudo
with pam_ssh_agent_au
On Mon, 2025-06-02 at 11:50 -0500, Ranjan Maitra via users wrote:
> passwordless sudo seems quite risky to me (and seems to defeat the
> purpose of sudo).
Yes, and no...
If I "sudo something" the password I'm going to type is my own, which I
already know. Though it does offer an "are you sure" m
On one Fedora 42 machine after update get this.
wine notepad
002c:err:seh:NtRaiseException Unhandled exception code
c005 flags 0 addr 0x6fc4c133
0034:err:seh:NtRaiseException Unhandled exception code
c005 flags 0 addr 0x6fc4c133
003c:err:seh:NtRaiseException Unhandled exception co
On Mon Jun02'25 10:45:48PM, Frederic Muller wrote:
> From: Frederic Muller
> Date: Mon, 2 Jun 2025 22:45:48 +0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: ssh forward agent
>
> On 02/06/2025 21:45, francis.montag...@inria.fr wrote:
> > Hi.
On 02/06/2025 21:45, francis.montag...@inria.fr wrote:
Hi.
On Mon, 02 Jun 2025 21:32:41 +0700 Frederic Muller wrote:
I copied the old .ssh from my backup so it's all the same files and I do
manage to ssh to the server, just not sudo su.
This is thus a change in the sudo configurations, not SS
Hi.
On Mon, 02 Jun 2025 21:32:41 +0700 Frederic Muller wrote:
> I copied the old .ssh from my backup so it's all the same files and I do
> manage to ssh to the server, just not sudo su.
This is thus a change in the sudo configurations, not SSH.
AFAIK sudo cannot be configured to authenticate wi
Hi!
Is there something that changed in F42 making forward agent no longer
working? I'm logging in using SSH key to a VPS to which I usually log in
without any problem.
I then sudo su, but it's asking for a password.
My config is as such:
Host myhost
Hostname thatsite.com
ForwardAgen
On Mon, 2025-06-02 at 15:28 +0200, François Patte wrote:
> Le 02/06/2025 à 15:20, George N. White III a écrit :
> > journalctl --no-hostaname -b
>
> journalctl : option non reconnue (not known) '--no-hostaname'
It's a typo.
man journalctl:
...
--no-hostname
Do not show the host
Le 02/06/2025 à 15:09, François Patte a écrit :
Bonjour,
I upgraded to f42 from f40 using the dnf system upgrade, everything
seems to be alright, except the default background which is missing on
the logging screen (black) and also when users are logged (white).
I use lightdm and all files
Le 02/06/2025 à 15:20, George N. White III a écrit :
journalctl --no-hostaname -b
journalctl : option non reconnue (not known) '--no-hostaname'
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lis
On Mon, Jun 2, 2025 at 10:10 AM François Patte
wrote:
> Bonjour,
>
> I upgraded to f42 from f40 using the dnf system upgrade, everything seems
> to be alright, except the default background which is missing on the
> logging screen (black) and also when users are logged (white).
>
> I use lightdm
Bonjour,
I upgraded to f42 from f40 using the dnf system upgrade, everything
seems to be alright, except the default background which is missing on
the logging screen (black) and also when users are logged (white).
I use lightdm and all files in /etc/lightdm and /usr/share/background
seem to
12 matches
Mail list logo
