On Sat, Oct 28, 2023 at 6:59 PM ToddAndMargo via users <
users@lists.fedoraproject.org> wrote:
>
> $ doas -u root "nvme smart-log /dev/nvme0n1"
> doas: Operation not permitted
>
I use:
% doas nvme smart-log /dev/nvme0n1
doas (@) password:
Smart Log for NVME device:nvme0n1 namespace-id:
c
On Sat, 2023-10-28 at 15:56 -0700, ToddAndMargo via users wrote:
> > > $ doas -u root "nvme smart-log /dev/nvme0n1"
> > > doas: Operation not permitted
> >
> > Try removing the quotes.
> >
> > poc
>
> $ doas -u root nvme smart-log /dev/nvme0n1
> doas: Operation not permitted
Does doas ask for y
On 10/29/23 04:00, George N. White III wrote:
On Sat, Oct 28, 2023 at 6:59 PM ToddAndMargo via users
mailto:users@lists.fedoraproject.org>>
wrote:
$ doas -u root "nvme smart-log /dev/nvme0n1"
doas: Operation not permitted
I use:
% doas nvme smart-log /dev/nvme0n1
doas (@) password:
On 10/29/23 04:02, Patrick O'Callaghan wrote:
On Sat, 2023-10-28 at 15:56 -0700, ToddAndMargo via users wrote:
$ doas -u root "nvme smart-log /dev/nvme0n1"
doas: Operation not permitted
Try removing the quotes.
poc
$ doas -u root nvme smart-log /dev/nvme0n1
doas: Operation not permitted
D
On Sun, 2023-10-29 at 04:06 -0700, ToddAndMargo via users wrote:
> On 10/29/23 04:02, Patrick O'Callaghan wrote:
> > On Sat, 2023-10-28 at 15:56 -0700, ToddAndMargo via users wrote:
> > > > > $ doas -u root "nvme smart-log /dev/nvme0n1"
> > > > > doas: Operation not permitted
> > > >
> > > > Try r
On Sun, 2023-10-29 at 04:04 -0700, ToddAndMargo via users wrote:
> I am trying to get around the password issue so I
> can just do a libnotify popup when I log into my
> desktop
I recall there's sudo configuration options for users and/or particular
commands that don't require a password.
"To ru
On 10/29/23 04:13, Robert Nichols wrote:
On 10/28/23 21:20, Robert Nichols wrote:
Yes, as long as the device is currently unlocked
Oops. I just realized that recovering the master key from the kernel works only
for LUKS1. Your device is using LUKS2, and and accessing the key from userspace
is
On Oct 29, 2023, at 11:00, Roberto Ragusa wrote:
>
> On 10/29/23 04:13, Robert Nichols wrote:
>>> On 10/28/23 21:20, Robert Nichols wrote:
>>> Yes, as long as the device is currently unlocked
>> Oops. I just realized that recovering the master key from the kernel works
>> only for LUKS1. Your d
On 10/29/23 20:16, Jonathan Billings wrote:
On Oct 29, 2023, at 11:00, Roberto Ragusa wrote:
On 10/29/23 04:13, Robert Nichols wrote:
On 10/28/23 21:20, Robert Nichols wrote:
Yes, as long as the device is currently unlocked
Oops. I just realized that recovering the master key from the kerne
On 10/29/23 12:47, Roberto Ragusa wrote:
On 10/29/23 20:16, Jonathan Billings wrote:
On Oct 29, 2023, at 11:00, Roberto Ragusa wrote:
On 10/29/23 04:13, Robert Nichols wrote:
On 10/28/23 21:20, Robert Nichols wrote:
Yes, as long as the device is currently unlocked
Oops. I just realized that
On 10/29/23 21:22, Samuel Sieb wrote:
As far as I can see in this thread, it consists in hostility against
the owner of the machine, which is risking something similar to
a ransomware event.Data availability is one of the aspects of security, so this
feature
is indeed a security issue.
That d
On 10/29/23 13:55, Roberto Ragusa wrote:
On 10/29/23 21:22, Samuel Sieb wrote:
As far as I can see in this thread, it consists in hostility against
the owner of the machine, which is risking something similar to
a ransomware event.Data availability is one of the aspects of
security, so this fe
On Oct 29, 2023, at 16:22, Samuel Sieb wrote:
>
> On 10/29/23 12:47, Roberto Ragusa wrote:
>>> On 10/29/23 20:16, Jonathan Billings wrote:
>>> On Oct 29, 2023, at 11:00, Roberto Ragusa wrote:
On 10/29/23 04:13, Robert Nichols wrote:
>> On 10/28/23 21:20, Robert Nichols wrote:
>>
On 10/29/23 22:01, Jonathan Billings wrote:
The point I’m making is that the decryption passphrase should not be accessible
to any root level process, be it a user with sudo or a compromised service.
This is why you should create a backup passphrase in a different keyslot and
store it somepla
F38
Yesterday I did a 'dnf update' when the machine had issues (I know, a bad idea).
During the update I noticed these failures (see below). Each time there was
some wait before proceeding.
I think that systemd was the cause as other cron jobs encountered this error:
Failed to retrieve
On 10/29/23 17:25, fed...@eyal.emu.id.au wrote:
F38
Yesterday I did a 'dnf update' when the machine had issues (I know, a
bad idea).
During the update I noticed these failures (see below). Each time there
was some wait before proceeding.
I think that systemd was the cause as other cron jobs
On 10/29/23 05:19, Tim via users wrote:
On Sun, 2023-10-29 at 04:04 -0700, ToddAndMargo via users wrote:
I am trying to get around the password issue so I
can just do a libnotify popup when I log into my
desktop
I recall there's sudo configuration options for users and/or particular
commands t
F38
Linux e7.eyal.emu.id.au 6.5.8-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Oct 20
15:53:48 UTC 2023 x86_64 GNU/Linux
I am looking at issues with my system which is ATM degraded (6/7 raid6 devices).
I am waiting for a replacement disk from seagate RMA.
Unrelated, I am trying to copy a director
On 30/10/2023 12.03, Samuel Sieb wrote:
On 10/29/23 17:25, fed...@eyal.emu.id.au wrote:
F38
Yesterday I did a 'dnf update' when the machine had issues (I know, a bad idea).
During the update I noticed these failures (see below). Each time there was
some wait before proceeding.
I think that sy
On Sun, Oct 29, 2023 at 9:49 PM ToddAndMargo via users
wrote:
>
> On 10/29/23 05:19, Tim via users wrote:
> > On Sun, 2023-10-29 at 04:04 -0700, ToddAndMargo via users wrote:
> >> I am trying to get around the password issue so I
> >> can just do a libnotify popup when I log into my
> >> desktop
>
On 10/29/23 20:06, fed...@eyal.emu.id.au wrote:
On 30/10/2023 12.03, Samuel Sieb wrote:
On 10/29/23 17:25, fed...@eyal.emu.id.au wrote:
F38
Yesterday I did a 'dnf update' when the machine had issues (I know, a
bad idea).
During the update I noticed these failures (see below). Each time
the
21 matches
Mail list logo
