On Mon, 27 May 2024, Curt wrote:
On 2024-05-26, Tim Woodall wrote:
Anyone got any ideas how to disable this?
If you have ~/.alpine.passfile apparently it will keep asking, but maybe
you don't, in which case I'm stumped.
Thanks, no that file doesn't exist. I'm a bit stumped too - and
On 2024-05-26, Tim Woodall wrote:
>
> Anyone got any ideas how to disable this?
>
>
If you have ~/.alpine.passfile apparently it will keep asking, but maybe
you don't, in which case I'm stumped.
I start alpine with the following alias
alias pine='alpine -p
\{imap202.home.woodall.me.uk/norsh/tls/user=tim\}remote_pinerc'
and after entering my password I get:
Preserve password on DISK for next login? [y]:
I don't want to do this. My googling suggested that I could set
[X
Welcome to TNG eWallet Careline Support! We have received your inquiry and
happy to assist you.
In order for us to assist you further, please sign up an account by clicking
the link at the bottom of this email.
Upon signed up, a ticket number will be sent to you in a separate email and our
Am 25.04.2024 schrieb David Mehler :
> Since changing systems to Debian 12.5 I can't send, though checking
> the password with a manual login to Dovecot works fine.
Sending mails is SMTP and therefore postfix on your machine.
It can use PAM for auth. Do you use PAM?
Hello,
I have a quick question. Can Debian, and/or it's
Postfix/Dovecot/MySQL/MariaDB packages support the argon2 password
hashing scheme? I had a previously-working e-mail setup on a *BSD
system, utilizing the argon2ID scheme with Dovecot, Postfix, and MySQL.
Since changing systems
On 22 Mar 2024 20:01 -0400, from ler...@gmail.com (Lee):
> The IPv4 address space is only 32 bits long. Scanning 2^32 = about
> 4,000,000,000 addresses for an open port is easily doable.
> The IPv6 address space is a bit harder... Let's just say that 7/8th
> of the IPv6 address space is
On 22 Mar 2024 17:26 +0500, from avbe...@gmail.com (Alexander V. Makartsev):
> This is because of how IPv4 network address translation (NAT) works, to
> allow multiple LAN hosts to connect to Internet with single IP address
> assigned by Internet Service Provider (ISP).
A NAT router might
On Fri, Mar 22, 2024 at 9:02 AM Jan Krapivin wrote:
>
> The thing that bothers me are words: "any computer (and a fortiori any
> server) connected to the Internet is regularly targeted by automated
> connection attempts"
Change it to "any computer (and a fortiori any server) >>using IPv4
and
On 22.03.2024 14:57, Jan Krapivin wrote:
чт, 21 мар. 2024 г. в 22:34, Alexander V. Makartsev :
This conclusion seems less than optimal to me.
By condemning yourself to type 12+ character password every time
you 'sudo' would really hurt accessibility and usability of your
home
On Fri, 22 Mar 2024 12:57:20 +0300
Jan Krapivin wrote:
> чт, 21 мар. 2024 г. в 22:34, Alexander V. Makartsev
> :
>
> > This conclusion seems less than optimal to me.
> > By condemning yourself to type 12+ character password every time you
> > 'sudo' would really hurt
чт, 21 мар. 2024 г. в 22:34, Alexander V. Makartsev :
> This conclusion seems less than optimal to me.
> By condemning yourself to type 12+ character password every time you
> 'sudo' would really hurt accessibility and usability of your home computer
> and for no good reason.
>
On 20.03.2024 20:28, Jan Krapivin wrote:
I must mention that "32 characters" is only my guess.
In the Handbook it is said: "The root user's password should be long
(12 characters or more) and impossible to guess."
Also, i must again say that in my case we speak just
>
> You don't need a threat model to understand why writing a password on a
> paper is generally a bad practice.
>
> But since you invest this much energy on defending a bad practice, I'll
> let you keep the trend alone.
>
I have written down key passwords which I keep in
On Wed, Mar 20, 2024 at 3:50 PM Pierre-Elliott Bécue wrote:
>
> De : Lee
> À : Pierre-Elliott Bécue
> Cc : Debian Users ML
> Date : 20 mars 2024 20:40:52
> Objet : Re: Root password strength
>
> > On Wed, Mar 20, 2024 at 1:47 PM Pierre-Elliott Bécue wrote:
> >
On Wed, Mar 20, 2024 at 2:34 PM Pierre-Elliott Bécue wrote:
>
> Jeffrey Walton wrote on 20/03/2024 at 19:16:16+0100:
>
> [...]
> >> Noone asks someone to remember more than two or three passwords. The
> >> rest belongs to a password manager.
> >
> >
De : Lee
À : Pierre-Elliott Bécue
Cc : Debian Users ML
Date : 20 mars 2024 20:40:52
Objet : Re: Root password strength
> On Wed, Mar 20, 2024 at 1:47 PM Pierre-Elliott Bécue wrote:
>>
>> Brad Rogers wrote on 20/03/2024 at 18:39:30+0100:
>>> On Wed, 20 Mar 2024 1
On Wed, Mar 20, 2024 at 1:47 PM Pierre-Elliott Bécue wrote:
>
> Brad Rogers wrote on 20/03/2024 at 18:39:30+0100:
> > On Wed, 20 Mar 2024 17:09:31 +0100
> > Pierre-Elliott Bécue wrote:
> >
> > Hello Pierre-Elliott,
> >
> >>Most of the tim
John Hasler wrote on 20/03/2024 at 19:35:42+0100:
> Pierre-Elliott Bécue writes:
>> My home sees plenty different people coming in. Some I trust, some I
>> trust less. Also videocalls is a nice way to get a paper password
>> recorded (and yes it happens).
>
> I keep m
tomas writes:
> Actually, I use between pwgen -n 8 (user pw) and pwgen -n 16 (LUKS
> encryption).
-n is the default for pwgen. Note that this slightly reduces the size
of the search space. Unfortunately many sites require it.
> I memorize the most important of them.
I memorize the ones I use
a rather bad cybersecurity approach.
>
> I use password generators and vaults for all my passwords. Nothing
> wrong with my cyber-security.
When you state that something like "writing down" a password is
reasonable in one's home as if this actual home were a heaven of safety,
I b
Pierre-Elliott Bécue writes:
> My home sees plenty different people coming in. Some I trust, some I
> trust less. Also videocalls is a nice way to get a paper password
> recorded (and yes it happens).
I keep my passwords in a small book the size of a passport and I secure
it the same way
03/2024 at 16:58:01+0100:
>> >> >>
>> >> >> > Pierre-Elliott Bécue writes:
>> >> >> >> A phrase you will easily remember but that would be hardcore to
>> >> >> >> guess
>> >> >> >> t
On Wed, 20 Mar 2024 18:46:04 +0100
Pierre-Elliott Bécue wrote:
Hello Pierre-Elliott,
>You have a rather bad cybersecurity approach.
I use password generators and vaults for all my passwords. Nothing
wrong with my cyber-security.
Also note that I put 'written down' in single quo
Michael Kjörling <2695bd53d...@ewoof.net> wrote on 20/03/2024 at 19:04:10+0100:
> On 20 Mar 2024 18:46 +0100, from p...@debian.org (Pierre-Elliott Bécue):
>>>> Most of the time, writing down a password is a very bad idea.
>>>
>>> Not in your own home.
writes:
> >> >> >> A phrase you will easily remember but that would be hardcore to guess
> >> >> >> through social engineering is perfect.
> >> >> >
> >> >> > Better is a random string that you write down. When peo
On 20 Mar 2024 17:07 +0100, from p...@debian.org (Pierre-Elliott Bécue):
> Let's stop to overcomplexify, the best course of action for passwords
> you need to remember are passphrases, and to this matter, Randall nailed
> the matter properly.
If you're referring to https://xkcd.com/936/ I believe
On 20 Mar 2024 18:46 +0100, from p...@debian.org (Pierre-Elliott Bécue):
>>> Most of the time, writing down a password is a very bad idea.
>>
>> Not in your own home. And in any event, it depends where one keeps that
>> 'written down' password.
>>
>> A
On Wed, Mar 20, 2024 at 11:02:41AM -0500, John Hasler wrote:
> Use one of the password generating programs such as pwgen to produce a
> 12 character random password. Write it down.
Actually, I use between pwgen -n 8 (user pw) and pwgen -n 16 (LUKS encryption).
I memorize the most imp
Brad Rogers wrote on 20/03/2024 at 18:39:30+0100:
> On Wed, 20 Mar 2024 17:09:31 +0100
> Pierre-Elliott Bécue wrote:
>
> Hello Pierre-Elliott,
>
>>Most of the time, writing down a password is a very bad idea.
>
> Not in your own home. And in any event, it depends wher
eering is perfect.
>> >> >
>> >> > Better is a random string that you write down. When people try to
>> >> > generate phrases that meet those requirements they usually fail.
>> >>
>> >> Writing down a password is a ba
On Wed, 20 Mar 2024 17:09:31 +0100
Pierre-Elliott Bécue wrote:
Hello Pierre-Elliott,
>Most of the time, writing down a password is a very bad idea.
Not in your own home. And in any event, it depends where one keeps that
'written down' password.
And if it *does* become an issue at h
When people try to
> >> > generate phrases that meet those requirements they usually fail.
> >>
> >> Writing down a password is a bad idea.
> >
> > I don't think that's true anymore. The threat being mitigated is the
> > network attacker. The netw
John Hasler wrote on 20/03/2024 at 17:21:20+0100:
> Pierre-Elliott Bécue writes:
>> Writing down a password is a bad idea.
>
> Why?
Because anyone falling on the paper with the password can do a lot of
harm. Because you can't control what this paper will become with
certainty, wh
member but that would be hardcore to guess
>> >> through social engineering is perfect.
>> >
>> > Better is a random string that you write down. When people try to
>> > generate phrases that meet those requirements they usually fail.
>>
>> Writing dow
On 20/03/2024 23:19, Jeffrey Walton wrote:
The network attacker cannot (yet) reach through a
monitor and read a sticky note.
It may be visible during a video call performed from a smartphone.
Pierre-Elliott Bécue writes:
> Writing down a password is a bad idea.
Why?
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
rfect.
> >
> > Better is a random string that you write down. When people try to
> > generate phrases that meet those requirements they usually fail.
>
> Writing down a password is a bad idea.
I don't think that's true anymore. The threat being mitigated is the
network
John Hasler wrote on 20/03/2024 at 17:02:41+0100:
> Use one of the password generating programs such as pwgen to produce a
> 12 character random password. Write it down.
Most of the time, writing down a password is a very bad idea.
--
PEB
signature.asc
Description: PGP signature
nerate phrases that meet those requirements they usually fail.
Writing down a password is a bad idea.
Managing passwords through a password-store (eg pass, keepassxc,
whatever tool you prever) is a great idea, but you first need to unlock
your disk that hopefully you encrypted and then your ses
Use one of the password generating programs such as pwgen to produce a
12 character random password. Write it down.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 20 Mar 2024 10:58 -0500, from j...@sugarbit.com (John Hasler):
>> A phrase you will easily remember but that would be hardcore to guess
>> through social engineering is perfect.
>
> Better is a random string that you write down. When people try to
> generate phrases that meet those
Pierre-Elliott Bécue writes:
> A phrase you will easily remember but that would be hardcore to guess
> through social engineering is perfect.
Better is a random string that you write down. When people try to
generate phrases that meet those requirements they usually fail.
--
John Hasler
about 3.6*10^38
> _years_ to go through. A widely agreed-upon figure for the age of the
> universe is around 1.4*10^10 years. Therefore such a password would
> take, very roughly, 10^28 times the age of the universe to brute
> force.
>
> Of course, with only 32 characters actually c
I must mention that "32 characters" is only my guess.
In the Handbook it is said: "The root user's password should be long (12
characters or more) and impossible to guess."
Also, i must again say that in my case we speak just about a humble home
desktop, without a "&
rs),
32 characters is equivalent to about 203 bits. (82^32 ~ 2^203 or,
expressed differently, log_2(82^32) ~ 203.)
At a rate of 2^50 guesses per second, that will take about 3.6*10^38
_years_ to go through. A widely agreed-upon figure for the age of the
universe is around 1.4*10^10 years. Therefore suc
Jan Krapivin wrote on 19/03/2024 at 15:42:55+0100:
> I read Debian Administrator's handbook now. And there are such words:
>
> The root user's password should be long (12 characters or more) and
> impossible to guess. Indeed, any computer (and a fortiori any server)
. It is wise to avoid gratuitous rotation schemes.
I will be the last ne to advocate any gratuitous rotation scheme (key
or password or anything).
My point is giving users enough wits and power (and competent help) to
make good decisions and to implement them.
If my laptop gets stolen, I'll definit
On Wed, Mar 20, 2024 at 7:03 AM Michael Kjörling <2695bd53d...@ewoof.net> wrote:
>
> On 20 Mar 2024 15:46 +0800, from jeremy.ard...@gmail.com (jeremy ardley):
> > Regarding certificates, I issue VPN certificates to be installed on each
> > remote device. I don't use public key.
>
> What exactly is
jeremy ardley wrote:
>
> On 20/3/24 19:03, Michael Kjörling wrote:
> > On 20 Mar 2024 15:46 +0800, fromjeremy.ard...@gmail.com (jeremy ardley):
> > > [users are locked out from uploading their public key using ssh-copy-id]
> > So the private keys aren't private, thereby invalidating a lot of
>
On 20 Mar 2024 12:17 +0100, from to...@tuxteam.de:
>>> For ssh use I issue secret keys to each user and maintain matching public
>>> keys in LDAP servers [...]
>
>> So the private keys aren't private, thereby invalidating a lot of
>> assumptions inherent in public key cryptography.
>
> We are
On 20 Mar 2024 19:21 +0800, from jeremy.ard...@gmail.com (jeremy ardley):
>>> Regarding certificates, I issue VPN certificates to be installed on each
>>> remote device. I don't use public key.
>>
>> What exactly is this "certificate" that you speak of? In typical
>> usage, it means a public key
On 20/3/24 19:03, Michael Kjörling wrote:
On 20 Mar 2024 15:46 +0800, fromjeremy.ard...@gmail.com (jeremy ardley):
Regarding certificates, I issue VPN certificates to be installed on each
remote device. I don't use public key.
What exactly is this "certificate" that you speak of? In typical
On Wed, Mar 20, 2024 at 11:03:16AM +, Michael Kjörling wrote:
> On 20 Mar 2024 15:46 +0800, from jeremy.ard...@gmail.com (jeremy ardley):
> > Regarding certificates, I issue VPN certificates to be installed on each
> > remote device. I don't use public key.
>
> What exactly is this
On 20 Mar 2024 15:46 +0800, from jeremy.ard...@gmail.com (jeremy ardley):
> Regarding certificates, I issue VPN certificates to be installed on each
> remote device. I don't use public key.
What exactly is this "certificate" that you speak of? In typical
usage, it means a public key plus some
On 20/3/24 13:32, to...@tuxteam.de wrote:
How will a "VPN" with a "certificate" (whatever that means in this > context) be more secure than a SSH (assuming key pair
authentication, > not password)? > > They are doing the same dance (key
exchange, ke
ed in sshd via pam.
> >
> > How will a "VPN" with a "certificate" (whatever that means in this context)
> > be more secure than a SSH (assuming key pair authentication, not password)?
>
> This may be more theoretical, but... IPSec uses
> Encrypt-then-A
xt)
> be more secure than a SSH (assuming key pair authentication, not password)?
This may be more theoretical, but... IPSec uses
Encrypt-then-Authenticate (EtA), which is provably secure under random
models. In fact, I believe IPSec is IND-CCA2 secure (Ciphertext
Indistinguishability), which is a str
> further enhancement of security is to use 2-factor authentication - which is
> supported in sshd via pam.
How will a "VPN" with a "certificate" (whatever that means in this context)
be more secure than a SSH (assuming key pair authentication, not password)?
They are doing the
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> For most values of "you", most attackers don't care about _your_
> account, or _your_ system; they care about _any_ account, or _any_
> system. Actually targeted attacks do happen, but very rarely compared
> to what might be thought of as
On 19/3/24 23:02, Greg Wooledge wrote:
On Tue, Mar 19, 2024 at 05:42:55PM +0300, Jan Krapivin wrote:
The root user's password should be long (12 characters or more) and
impossible to guess. Indeed, any computer (and a fortiori any server)
connected to the Internet is regularly targeted
On Tue, Mar 19, 2024 at 03:49:06PM +, debian-u...@howorth.org.uk wrote:
> Dan Ritter wrote:
> > Check whether you are running ssh:
> >
> > /sbin/service ssh status
>
> It's not called ssh; it is sshd
> Also nowadays it's more usual to say
>
> $ systemctl status sshd
On Debian, the
On 19 Mar 2024 17:42 +0300, from daydreamer199...@gmail.com (Jan Krapivin):
> The thing is my password is very easy now, and i haven't thought about
> *"automated
> connection attempts"*, that sounds rather... scary? My password is easy
> because i am not afraid of
Dan Ritter wrote:
> Jan Krapivin wrote:
> > I read Debian Administrator's handbook now. And there are such
> > words:
> >
> > The root user's password should be long (12 characters or more) and
> > impossible to guess.
> ...
>
>
> > The thin
Greg Wooledge writes:
> On Tue, Mar 19, 2024 at 05:42:55PM +0300, Jan Krapivin wrote:
>> The root user's password should be long (12 characters or more) and
>> impossible to guess. Indeed, any computer (and a fortiori any server)
>> connected to the Internet is regularly
Am Tue, 19 Mar 2024 17:42:55 +0300
schrieb Jan Krapivin :
> The thing is my password is very easy now
The simplest thin is to change that now.
, and i haven't thought about *"automated connection attempts"*,
> that sounds rather... scary?
Those attempts happen if a server so
Jan Krapivin wrote:
> I read Debian Administrator's handbook now. And there are such words:
>
> The root user's password should be long (12 characters or more) and
> impossible to guess.
...
> The thing is my password is very easy now, and i haven't thought about
> *"
On Tue, Mar 19, 2024 at 05:42:55PM +0300, Jan Krapivin wrote:
> The root user's password should be long (12 characters or more) and
> impossible to guess. Indeed, any computer (and a fortiori any server)
> connected to the Internet is regularly targeted by automated connection
&
~$ /sbin/service ssh status*
*Unit ssh.service could not be found.*
*@deb:~$ sudo /sbin/service ssh status*
*[sudo] password for ***: *
*Unit ssh.service could not be found.*
> Do you have some kind of remote access enabled or do you intend to in
> the near future?
>
No and no. Its just a simple home PC.
>
> If not, then you do not need to worry. Even less if you have a firewall
> to block any service that might appear by mistake.
>
I have UFW (gufw) enabled.
Jan Krapivin (12024-03-19):
> The thing is my password is very easy now, and i haven't thought about
> *"automated
> connection attempts"*, that sounds rather... scary? My password is easy
> because i am not afraid of direct physical access to the computer.
Hi.
Do you ha
I read Debian Administrator's handbook now. And there are such words:
The root user's password should be long (12 characters or more) and
impossible to guess. Indeed, any computer (and a fortiori any server)
connected to the Internet is regularly targeted by automated connection
attempts
On Tue, Mar 5, 2024 at 11:30 AM Jeffrey Walton wrote:
>
> On Tue, Mar 5, 2024 at 11:22 AM genti pp wrote:
> >
> > I want to install debian 12 but I need to try it first.
> > Having Debian 12 live iso it asks me for username and password. Please tell
> > me the corr
Hello.
Default login and password for the Debian live is user / live
2024-03-05, an, 18:22 genti pp rašė:
>
> Hello!
> I want to install debian 12 but I need to try it first.
> Having Debian 12 live iso it asks me for username and password. Please tell
> me the correct username
On Tue, Mar 5, 2024 at 11:22 AM genti pp wrote:
>
> I want to install debian 12 but I need to try it first.
> Having Debian 12 live iso it asks me for username and password. Please tell
> me the correct username and password so I can try it.
I usually use 'sudo su -' from the
On Tue, Mar 05 2024 at 02:28:08 PM, genti pp wrote:
> Hello!
> I want to install debian 12 but I need to try it first.
> Having Debian 12 live iso it asks me for username and password. Please tell
> me the correct username and password so I can try it.
> Thank you in advance!
Hello!
I want to install debian 12 but I need to try it first.
Having Debian 12 live iso it asks me for username and password. Please tell
me the correct username and password so I can try it.
Thank you in advance!
. 2024 kl 14:12 skrev Оксана Патакі >:
> >
> > yes login is debian but he need password and i dont use ssh
> >
> > вт, 6 лют. 2024, 06:44 користувач Luna Jernberg
> пише:
> >>
> >> -- Forwarded message -
> >> Från: Joost van B
yes login is debian but he need password and i dont use ssh
вт, 6 лют. 2024, 06:44 користувач Luna Jernberg
пише:
> -- Forwarded message -
> Från: Joost van Baal-Ilić
> Date: tis 6 feb. 2024 kl 06:31
> Subject: Re: Fwd: Openstack images default password
> To
:
>
> yes login is debian but he need password and i dont use ssh
>
> вт, 6 лют. 2024, 06:44 користувач Luna Jernberg пише:
>>
>> -- Forwarded message -
>> Från: Joost van Baal-Ilić
>> Date: tis 6 feb. 2024 kl 06:31
>> Subject: Re: Fwd: Ope
-- Forwarded message -
Från: Joost van Baal-Ilić
Date: tis 6 feb. 2024 kl 06:31
Subject: Re: Fwd: Openstack images default password
To: Luna Jernberg
Hi Luna,
off-list reply (feel free to quote me): i don't think our openstack images come
with a default password; they do
У меня есть вопрос а почему А пароль не Откуда взять потому что я просто
взял образ АРМ 64 хотел запустить на qemu
On 28/01/2024 00:07, Curt wrote:
(Anyway, this is what my personal robot explained to me and may be subject to
imperfection and error.)
I find it over-sophisticated and, being put after the recipe, extremely
unfriendly to those who get it in search engine results. Unfortunately
bootup(7) is
[ Sorry, didn't read the actual post, just answering the Subject: ]
What makes you think initrd will be satisfied with a sound?
Stefan
at is
almost what I want, but the small gap is blocking: cryptsetup might ask
for the password several times (if the user types it wrong), and the
sound must be played again too in that case.
Regards,
--
Nicolas George
Curt (12024-01-27):
> (Anyway, this is what my personal robot explained to me and may be subject to
> imperfection and error.)
I started explaining all the ways this answer is obviously nonsensical,
but I got fed up and deleted it.
If I wanted the answers from a stupid AI, I could have asked
xecution context
parameters that are not native to the service manager into dynamically
generated unit files, symlinks or unit file drop-ins, so that they
can extend the unit file hierarchy the service manager subsequently
loads and operates on.
> > And what should I put in the time
uess that path should've been /usr/local/lib/systemd/system-generators/*.
https://manpages.debian.org/testing/systemd/systemd.generator.7.en.html
> And what should I put in the timer file to express “when a password is
> asked”?
> In fact, what relation do you see between a timer and c
On Fri 26 Jan 2024 at 16:13:26 (+0100), Nicolas George wrote:
> Hi.
>
> Yet another strange question. Is there a supported¹ way to have
> cryptsetup play a specific sound when it asks the password for the root
> partition from the initrd?
>
> I think brttty (braill
Curt (12024-01-26):
> A play-sound.timer unit file in /usr/lib/systemd/system-generators/initrd
> directory.
I see no mention of this directory on the web. Where did yo find the
idea of using it, I want to check the doc.
And what should I put in the timer file to express “when a pa
On 2024-01-26, Nicolas George wrote:
> Curt (12024-01-26):
>> I guess a systemd timer unit constitutes a hack.
>
> A systemd timer in the initrd? Can you elaborate?
>
A play-sound.timer unit file in /usr/lib/systemd/system-generators/initrd
directory.
A play-sound.service file in the same
Curt (12024-01-26):
> I guess a systemd timer unit constitutes a hack.
A systemd timer in the initrd? Can you elaborate?
--
Nicolas George
On 2024-01-26, Nicolas George wrote:
> Hi.
>
> Yet another strange question. Is there a supported¹ way to have
> cryptsetup play a specific sound when it asks the password for the root
> partition from the initrd?
>
> I think brttty (braille) is already running at th
Hi.
Yet another strange question. Is there a supported¹ way to have
cryptsetup play a specific sound when it asks the password for the root
partition from the initrd?
I think brttty (braille) is already running at this point (no occasion
to test yet), but a recognizable sound would be something
On 07.01.24 18:07, David Wright wrote:
On Sat 06 Jan 2024 at 20:04:57 (+0100), Richard Rosner wrote:
I just tried out systemd-boot. What I noticed, it doesn't ask for my
decryption password to decrypt both my LUKS2 encrypted root and swap
partition. This kinda defeats the purpose of encrypted
On Sat 06 Jan 2024 at 20:04:57 (+0100), Richard Rosner wrote:
> I just tried out systemd-boot. What I noticed, it doesn't ask for my
> decryption password to decrypt both my LUKS2 encrypted root and swap
> partition. This kinda defeats the purpose of encrypted drives. How do
> I have
I just tried out systemd-boot. What I noticed, it doesn't ask for my
decryption password to decrypt both my LUKS2 encrypted root and swap
partition. This kinda defeats the purpose of encrypted drives. How do I
have systemd-boot forget and never again remember my credentials
On Sun, Dec 17, 2023 at 01:39:34AM +0100, Kevin Price wrote:
> Am 14.12.23 um 23:01 schrieb David Sawyer:
> > I use the password that I wrote down it is not accepted.
>
> Keyboard layout? We've seen that with the kernel that comes with 12.4.0.
> --
Hi Kevin,
There is no
That is a good pointer, I will start experimenting with kdbrate and see
if anything improves.
I did come up with the following contraption which helps at least seeing
what is going on and so far
it seems that the password is 1 char short on invalid attempt and it is
usually the last char
> RemainAfterExit=yes
> ExecStart=/usr/sbin/zfs load-key -a
> StandardInput=tty-force
>
> [Install]
> WantedBy=zfs-mount.service
>
>
> I have a very weird issue that.. if I type too fast the password is
> wrong. I know this sounds weird but it's true..
>
> I
1 - 100 of 3643 matches
Mail list logo
