On Sat 23 Dec 2017 at 18:43:38 +0100, to...@tuxteam.de wrote:
> On Sat, Dec 23, 2017 at 03:14:25PM +, Curt wrote:
> > On 2017-12-23, Hans wrote:
>
> [...]
>
> > > And I suppose, guessing 15 digits will cause a loong time [...]
>
> > (Assuming all 95 printable ascii characters) link to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Dec 23, 2017 at 03:14:25PM +, Curt wrote:
> On 2017-12-23, Hans wrote:
[...]
> > And I suppose, guessing 15 digits will cause a loong time [...]
> (Assuming all 95 printable ascii characters) link to % time savings:
[...]
> An in
On 2017-12-23, Hans wrote:
>
> But 1 percent longer for each added digit sounds not much. However, when it
> comes to more digits, let's say 16 (WPA2 often uses 16 digits with only
> letters and numbers), then the time to crack will increase rapidely.
>
> If I understood you correct, and please
Am Samstag, 23. Dezember 2017, 13:57:59 CET schrieb Anders Andersson:
Hi Anders,
this is an interesting point, you showed. I suppose, 10 digits will be mostly
be used by poeple, maybe less.
But 1 percent longer for each added digit sounds not much. However, when it
comes to more digits, let's
On Fri, Dec 22, 2017 at 10:25 PM, Richard Hector wrote:
> On 21/12/17 22:16, Curt wrote:
>> On 2017-12-20, Richard Hector wrote:
>>>
>>> On 21/12/17 02:02, Curt wrote:
Also, I'm uncertain whether suppression of the asterisk-echo qualifies
as "security by obscurity"
>>>
>>> I think most
On Sat 23 Dec 2017 at 10:25:10 +1300, Richard Hector wrote:
> On 21/12/17 22:16, Curt wrote:
> > On 2017-12-20, Richard Hector wrote:
> >>
> >> On 21/12/17 02:02, Curt wrote:
> >>> Also, I'm uncertain whether suppression of the asterisk-echo qualifies
> >>> as "security by obscurity"
> >>
> >> I
On 21/12/17 22:16, Curt wrote:
> On 2017-12-20, Richard Hector wrote:
>>
>> On 21/12/17 02:02, Curt wrote:
>>> Also, I'm uncertain whether suppression of the asterisk-echo qualifies
>>> as "security by obscurity"
>>
>> I think most people accept that obscurity is quite reasonable for
>> passwords
On 2017-12-21, wrote:
>
> On Wed, Dec 20, 2017 at 01:02:51PM +, Curt wrote:
>
> [...]
>
>> Now we want to change the default. Give them the moon, and they want the
>> stars, too!
>
> Who is "them"? "Not us"?
>
> Perhaps you're trying to construe a conflict where, actually there
> isn't one.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Dec 20, 2017 at 01:02:51PM +, Curt wrote:
[...]
> Now we want to change the default. Give them the moon, and they want the
> stars, too!
Who is "them"? "Not us"?
Perhaps you're trying to construe a conflict where, actually there
isn't o
On 2017-12-20, Richard Hector wrote:
>
> On 21/12/17 02:02, Curt wrote:
>> Also, I'm uncertain whether suppression of the asterisk-echo qualifies
>> as "security by obscurity"
>
> I think most people accept that obscurity is quite reasonable for
> passwords ...
>
> Richard
>
Wonderful, Dick, howe
On 21/12/17 02:02, Curt wrote:
> Also, I'm uncertain whether suppression of the asterisk-echo qualifies
> as "security by obscurity"
I think most people accept that obscurity is quite reasonable for
passwords ...
Richard
signature.asc
Description: OpenPGP digital signature
On 2017-12-20, root kea wrote:
> On Wed, Dec 20, 2017 at 3:18 AM, Jonathan Dowland wrote:
>> On Wed, Dec 20, 2017 at 12:15:36AM +0530, root kea wrote:
>
>>> And I just filed a bug report [0]. if anybody interested they can
>>> follow the discussion there.
>>>
>>> [0] https://bugs.debian.org/cgi-b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Dec 20, 2017 at 10:54:25AM +, Curt wrote:
> On 2017-12-20, wrote:
> >
> > On Tue, Dec 19, 2017 at 02:07:34PM -0800, Don Armstrong wrote:
> >> On Wed, 20 Dec 2017, root kea wrote:
> >> > I want *default* password agent to be consistent wit
On Wed, Dec 20, 2017 at 3:18 AM, Jonathan Dowland wrote:
> On Wed, Dec 20, 2017 at 12:15:36AM +0530, root kea wrote:
>> And I just filed a bug report [0]. if anybody interested they can
>> follow the discussion there.
>>
>> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884788
>
>
> In thi
On 2017-12-20, wrote:
>
> On Tue, Dec 19, 2017 at 02:07:34PM -0800, Don Armstrong wrote:
>> On Wed, 20 Dec 2017, root kea wrote:
>> > I want *default* password agent to be consistent with traditional *Nix
>> > password handling. And that is echoing NOTHING at all.
>>
>> You can just recompile sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Dec 19, 2017 at 02:07:34PM -0800, Don Armstrong wrote:
> On Wed, 20 Dec 2017, root kea wrote:
> > I want *default* password agent to be consistent with traditional *Nix
> > password handling. And that is echoing NOTHING at all.
>
> You can jus
On Wed, 20 Dec 2017, root kea wrote:
> I want *default* password agent to be consistent with traditional *Nix
> password handling. And that is echoing NOTHING at all.
You can just recompile systemd-ask-password and set ASK_PASSWORD_SILENT
true. This probably should be a command-line option, though
On Wed, Dec 20, 2017 at 12:15:36AM +0530, root kea wrote:
I am amazed that at times I had to defend not wanting stars(*) getting
echoed on terminal on *Linux* box. That should have been other way
around. That is the onus to defend should be on the one who wants
stars(*) being echoed on Terminal.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Dec 20, 2017 at 12:15:36AM +0530, root kea wrote:
> On Tue, Dec 19, 2017 at 11:58 PM, wrote:
>
> > So you might try to write your own agent, or file a wishlist
> > bug.
>
> I want *default* password agent to be consistent with traditional *
On Tue, Dec 19, 2017 at 11:58 PM, wrote:
> So you might try to write your own agent, or file a wishlist
> bug.
I want *default* password agent to be consistent with traditional *Nix
password handling. And that is echoing NOTHING at all.
I am amazed that at times I had to defend not wanting sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Dec 19, 2017 at 11:04:38PM +0530, root kea wrote:
[...]
> Thanks for the apt-file tip. I was hoping to find systemd-ask-password
> command execution in this file so that I could omit `--echo` switch
> (I'm thinking it's there as user input is
On Tue, Dec 19, 2017 at 1:58 AM, wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, Dec 19, 2017 at 12:42:57AM +0530, root kea wrote:
>> Now I just need to find out from where this `systemd-ask-password` is
>> executed and then edit it's command by omitting the `--echo` flag
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Caradoc-Davies wrote:
> On 19/12/17 02:41, Roberto C. Sánchez wrote:
>> Whether stars are echoed or nothing is echoed, the passphrase remains
>> concealed.
>
> Not true if the passphrase is "**".
Wait, how'd you know my pass is "hunter2017"
On 19/12/17 02:41, Roberto C. Sánchez wrote:
On Mon, Dec 18, 2017 at 06:41:00PM +0530, root kea wrote:
I am using LUKS on LVM on Debian Stretch. I have encrypted /home and
swap partition. When initram gets loaded it asks for password to
decrypt swap partition. That passowrd doesn't get printed t
On 19/12/17 02:11, root kea wrote:
I am using LUKS on LVM on Debian Stretch. I have encrypted /home and
swap partition. When initram gets loaded it asks for password to
decrypt swap partition. That passowrd doesn't get printed to screen.
No stars. Nothing.
But After which Kernel gets loaded (I th
to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, Dec 19, 2017 at 12:42:57AM +0530, root kea wrote:
>> I don't know why but this email didn't get delivered to my mailbox
>> even after I'm being in "To" field. I couldn't even find this email in
>> spam. Thankful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Dec 19, 2017 at 12:42:57AM +0530, root kea wrote:
> I don't know why but this email didn't get delivered to my mailbox
> even after I'm being in "To" field. I couldn't even find this email in
> spam. Thankfully, I decided to check debian-users
I don't know why but this email didn't get delivered to my mailbox
even after I'm being in "To" field. I couldn't even find this email in
spam. Thankfully, I decided to check debian-users archives and found
this mail there!
As I have copy pasted mail by hand please excuse the poor formatting.
> O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Dec 18, 2017 at 10:17:07AM -0500, Cindy-Sue Causey wrote:
[...]
> Is it possible to pre-populate that field somehow in a way that
> doesn't change when any given user's moniker (username, account name,
> alias) is chosen? I'm imagining it to
On 12/18/17, Cindy-Sue Causey wrote:
> On 12/18/17, to...@tuxteam.de wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On Mon, Dec 18, 2017 at 02:53:27PM +0100, Jeroen Mathon wrote:
>>
>> Don't forget to cc root kea, (s)he isn't on list. And oh, don't
>> top post... pretty please :
On 12/18/17, to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, Dec 18, 2017 at 02:53:27PM +0100, Jeroen Mathon wrote:
>
> Don't forget to cc root kea, (s)he isn't on list. And oh, don't
> top post... pretty please :-)
>
>> I have never seen any stars in my Luks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Dec 18, 2017 at 02:53:27PM +0100, Jeroen Mathon wrote:
Don't forget to cc root kea, (s)he isn't on list. And oh, don't
top post... pretty please :-)
> I have never seen any stars in my Luks screen.
>
> As long as it decrypts the drive i see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Dec 18, 2017 at 06:41:00PM +0530, root kea wrote:
> Hello!
>
> I am using LUKS on LVM on Debian Stretch. I have encrypted /home and
> swap partition. When initram gets loaded it asks for password to
> decrypt swap partition. That passowrd does
I have never seen any stars in my Luks screen.
As long as it decrypts the drive i see no real issue here.
On 12/18/2017 02:41 PM, Roberto C. Sánchez wrote:
> On Mon, Dec 18, 2017 at 06:41:00PM +0530, root kea wrote:
>> Hello!
>>
>> I am using LUKS on LVM on Debian Stretch. I have encrypted /home
On Mon, Dec 18, 2017 at 06:41:00PM +0530, root kea wrote:
> Hello!
>
> I am using LUKS on LVM on Debian Stretch. I have encrypted /home and
> swap partition. When initram gets loaded it asks for password to
> decrypt swap partition. That passowrd doesn't get printed to screen.
> No stars. Nothing.
Hello!
I am using LUKS on LVM on Debian Stretch. I have encrypted /home and
swap partition. When initram gets loaded it asks for password to
decrypt swap partition. That passowrd doesn't get printed to screen.
No stars. Nothing.
But After which Kernel gets loaded (I think) and it asks password fo
36 matches
Mail list logo
