On 2021-07-12 07:37, Wade Garrett wrote:
> On 7/12/21 5:53 AM, Unbreakable Disease wrote:
>> My 50-year old brain isn't capable of memorizing that many passwords
>> anymore, so I use KeePassXC. I keep basically everything here
>> including my financial passwords and credit card data, with the
>> exception of passwords that I would have to remember anyway (full-disk
>> encryption, login, primary e-mail passwords, etc.)
>>
>> Overall, it's much easier to remember and much harder to forget 10
>> complicated passwords that you use everyday than 100+ simple passwords
>> you use every month or even less.
>>
>> I can't speak about Windows version of KeePass, because with the
>> exception of playing games not available on Macintosh, I haven't used
>> one since Windows 95 days.
>
> I'd like to use a password manager but I'm not comfortable with that
> data being on some server somewhere- allegedly encrypted or not.

256 bit AES encryption not good enough for you?

>
> If there's one that keeps the data just on the local machine, I'd be
> interested.

1Password has that option as well as using a local server.

>
> I keep a spreadsheet with my PWs on my FileVault-encrypted iMac hard
> drive and copy/paste to logins that need to stay secure- financial,
> vendors, healthcare, etc.

Not very secure. Of course it's your house and that has some security.

But far better to use a manager - even if only on your machine.

>
> I always log out before leaving the house.

My computer does that for me ... well, might be a few minutes after I
leave...

--
"...there are many humorous things in this world; among them the white
man's notion that he is less savage than the other savages."
-Samuel Clemens

Alan Browne <bitbucket@blackhole.com> writes:
> On 2021-07-12 07:37, Wade Garrett wrote:
[...]
>> I'd like to use a password manager but I'm not comfortable with that
>> data being on some server somewhere- allegedly encrypted or not.
>
> 256 bit AES encryption not good enough for you?

The weak link is not the encryption algorithm, but the key used to
decrypt the data.

[...]

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */

In article <87r1fu18j7.fsf@nosuchdomain.example.com>, Keith Thompson
<Keith.S.Thompson+u@gmail.com> wrote:

> >> I'd like to use a password manager but I'm not comfortable with that
> >> data being on some server somewhere- allegedly encrypted or not.
> >
> > 256 bit AES encryption not good enough for you?
>
> The weak link is not the encryption algorithm, but the key used to
> decrypt the data.

that's up to you to choose something complex.

hint: don't use 'password123'

In message <87r1fu18j7.fsf@nosuchdomain.example.com> Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
> Alan Browne <bitbucket@blackhole.com> writes:
>> On 2021-07-12 07:37, Wade Garrett wrote:
> [...]
>>> I'd like to use a password manager but I'm not comfortable with that
>>> data being on some server somewhere- allegedly encrypted or not.
>>
>> 256 bit AES encryption not good enough for you?

> The weak link is not the encryption algorithm, but the key used to
> decrypt the data.

Which the user chooses.

Have you done any actual research into this or have you just read
know-nothing clickbait shit?

--
And the three men I admire most, the father son and the holly ghost
they caught the last train for the coast...

Lewis <g.kreme@kreme.dont-email.me> writes:
> In message <87r1fu18j7.fsf@nosuchdomain.example.com> Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
>> Alan Browne <bitbucket@blackhole.com> writes:
>>> On 2021-07-12 07:37, Wade Garrett wrote:
>> [...]
>>>> I'd like to use a password manager but I'm not comfortable with that
>>>> data being on some server somewhere- allegedly encrypted or not.
>>>
>>> 256 bit AES encryption not good enough for you?
>
>> The weak link is not the encryption algorithm, but the key used to
>> decrypt the data.
>
> Which the user chooses.

Yes, of course.

> Have you done any actual research into this or have you just read
> know-nothing clickbait shit?

Be less rude. If I'm wrong, say so and tell us what's right.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
> Alan Browne <bitbucket@blackhole.com> writes:
>> On 2021-07-12 07:37, Wade Garrett wrote:
> [...]
>>> I'd like to use a password manager but I'm not comfortable with that
>>> data being on some server somewhere- allegedly encrypted or not.
>>
>> 256 bit AES encryption not good enough for you?
>
> The weak link is not the encryption algorithm, but the key used to
> decrypt the data.

There’s lots of possible weak links.

- The key may be stored insecurely.
- If the key is derived from a password then the user may choose a weak
password.
- It’s easy to make a bad choice of KDF.
- The choice of cipher mode matters.
- For some cipher modes, how you choose the parameters matters.
- Some ciphers (including AES) are prone to side channels.

How much each of these matters is situational, but “256 bit AES
encryption” is not a complete description and may indeed not be good
enough, depending on the missing details.

--
https://www.greenend.org.uk/rjk/

In message <8735s99z9w.fsf@LkoBDZeT.terraraq.uk> Richard Kettlewell <invalid@invalid.invalid> wrote:
> Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
>> Alan Browne <bitbucket@blackhole.com> writes:
>>> On 2021-07-12 07:37, Wade Garrett wrote:
>> [...]
>>>> I'd like to use a password manager but I'm not comfortable with that
>>>> data being on some server somewhere- allegedly encrypted or not.
>>>
>>> 256 bit AES encryption not good enough for you?
>>
>> The weak link is not the encryption algorithm, but the key used to
>> decrypt the data.

> There’s lots of possible weak links.

> - The key may be stored insecurely.

The key is not stored at all. The key is the password that that the user
selects.

> - If the key is derived from a password then the user may choose a weak
> password.

Nothing anyone can do about that.

> - It’s easy to make a bad choice of KDF.
> - The choice of cipher mode matters.

Which is why these tools are audited by third parties and you should
only use tools that have been audited.

> - For some cipher modes, how you choose the parameters matters.

Ibid.

> - Some ciphers (including AES) are prone to side channels.

Ibid.

> How much each of these matters is situational, but “256 bit AES
> encryption” is not a complete description and may indeed not be good
> enough, depending on the missing details.

Ibid.

--
you cannot code around infinite implementations of OCD -John C Welch

On 2021-07-19 14:08, Keith Thompson wrote:
> Alan Browne <bitbucket@blackhole.com> writes:
>> On 2021-07-12 07:37, Wade Garrett wrote:
> [...]
>>> I'd like to use a password manager but I'm not comfortable with that
>>> data being on some server somewhere- allegedly encrypted or not.
>>
>> 256 bit AES encryption not good enough for you?
>
> The weak link is not the encryption algorithm, but the key used to
> decrypt the data.

First off there is a difference between a "key" and a "password".

If the password is "a", the key will still be extremely strong at 256
bits and would look completely different to the key for password "b".
Of course that is not a recommendation.

As to passwords, it's trivial to make strong and easy to remember
passwords with a few misspelled words, mixed case, some symbols and digits.

--
"...there are many humorous things in this world; among them the white
man's notion that he is less savage than the other savages."
-Samuel Clemens

Alan Browne <bitbucket@blackhole.com> writes:
> On 2021-07-19 14:08, Keith Thompson wrote:
>> Alan Browne <bitbucket@blackhole.com> writes:
>>> On 2021-07-12 07:37, Wade Garrett wrote:
>> [...]
>>>> I'd like to use a password manager but I'm not comfortable with that
>>>> data being on some server somewhere- allegedly encrypted or not.
>>>
>>> 256 bit AES encryption not good enough for you?
>> The weak link is not the encryption algorithm, but the key used to
>> decrypt the data.
>
> First off there is a difference between a "key" and a "password".

Sure (but sometimes they can be the same, right?).

> If the password is "a", the key will still be extremely strong at 256
> bits and would look completely different to the key for password "b".
> Of course that is not a recommendation.

Are you talking about a key being algorithmically derived from the
password? If the string "a" is all the information you need to unlock
an encrypted file, then an attacker is going to be able to unlock it,
whether it first has to be translated to a 256-bit key or not. (Or I'm
missing something.)

> As to passwords, it's trivial to make strong and easy to remember
> passwords with a few misspelled words, mixed case, some symbols and
> digits.

Sure. It's also easy for a password to leak in any of a number of ways.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */