https://bugs.kde.org/show_bug.cgi?id=399268
Jan Grulich changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=399268
--- Comment #16 from Nate Graham ---
You are describing why it isn't *necessary*, but not why it is a *problem*.
I am suggesting that you store the hotel password in the wallet anyway, because
even though it may not feel *necessary*, doing so doesn't
https://bugs.kde.org/show_bug.cgi?id=399268
--- Comment #15 from Oleg Solovyov ---
(In reply to Nate Graham from comment #14)
> (In reply to Oleg Solovyov from comment #13)
> What's the *problem* with storing a hotel wifi password in the wallet?
It's unnecessary to store it in the wallet.
https://bugs.kde.org/show_bug.cgi?id=399268
--- Comment #14 from Nate Graham ---
(In reply to Oleg Solovyov from comment #13)
> (In reply to Nate Graham from comment #12)
> > (In reply to Oleg Solovyov from comment #11)
> >
> > What is the problem with just storing the hotel wifi password in
https://bugs.kde.org/show_bug.cgi?id=399268
--- Comment #13 from Oleg Solovyov ---
(In reply to Nate Graham from comment #12)
> (In reply to Oleg Solovyov from comment #11)
>
> What is the problem with just storing the hotel wifi password in the wallet?
> Why is this an issue?
I think it's
https://bugs.kde.org/show_bug.cgi?id=399268
--- Comment #12 from Nate Graham ---
(In reply to Oleg Solovyov from comment #11)
> What about that case?
> User tries to create a connection with an encrypted network provided by
> hotel which will be used for a day or two.
>
> There is no sense to
https://bugs.kde.org/show_bug.cgi?id=399268
--- Comment #11 from Oleg Solovyov ---
(In reply to Nate Graham from comment #10)
> > When KWallet is used [...] and kwallet creation is refused
>
> That said, if the user refuses to use KWallet, that's a pretty good sign
> that they don't care about
https://bugs.kde.org/show_bug.cgi?id=399268
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #10 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=399268
--- Comment #9 from Jan Grulich ---
(In reply to Christoph Feck from comment #8)
> But system-wide means unencrypted?
Yes. It's either that or not storing secrets at all and keep asking users to
configure KWallet.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=399268
--- Comment #8 from Christoph Feck ---
But system-wide means unencrypted?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399268
Jan Grulich changed:
What|Removed |Added
Resolution|NOT A BUG |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=399268
--- Comment #6 from Oleg Solovyov ---
(In reply to Jan Grulich from comment #5)
> So you suggest by default saving the secrets unencrypted to NM, which is not
> secure at all?
I suggest *checking* whether the secrets were saved in KWallet and
https://bugs.kde.org/show_bug.cgi?id=399268
Jan Grulich changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=399268
Oleg Solovyov changed:
What|Removed |Added
Resolution|NOT A BUG |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=399268
Jan Grulich changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=399268
Oleg Solovyov changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|NOT A BUG
https://bugs.kde.org/show_bug.cgi?id=399268
Jan Grulich changed:
What|Removed |Added
CC||jgrul...@redhat.com
Resolution|---
17 matches
Mail list logo