Re: Is there any way to kill a seahorse?
- From: Adam Tauno Williams <awilliam whitemice org>
- To: seahorse-list gnome org
- Subject: Re: Is there any way to kill a seahorse?
- Date: Fri, 13 Apr 2012 08:50:00 -0400
Quoting Bruce Korb <bkorb gnu org>:
On 04/11/12 19:11, Michael Stephenson wrote:
So suddenly you care about security again?>
There are two flavors of security: Physical and electronic.
now. Everything else is stopped at the router.
It doesn't actually work that way. Your machine communicates with
other hosts all the time, and those hosts *can* use the out-bound
connections you create. But this isn'tthe forum to discuss basic
network security; just know that I've sat through numerous
presentations and demos about how to exploit machines that do not
permit inbound connections - it is often easier than you think.
robotic intruder is going to guess my /path/to/my/password/db.txt
In the end, I do not want to have passwords demanded of me
by some I-know-better-than-you-do password manager,
either when I login or when I visit web sites.
So when applications and websites demand passwords of you - you
cut-n-paste them from a text file? How is that easier [or more
secure] than entering a password at login and permitting the rest of
your passwords to be stored in an encrypted database accessed via a
consitent API?
You can do it your way - but it does *not* make any sense.
And I have no idea what "I-know-better-than-you-do password manager"
implies other than it knows to encrypt the data and allow you to
control access to it.
In your confused head you want rid of this system because
it is inconvenient, having to enter a password all the time.
In your confused head, you are certain you know better than
Yes.
me and you coded your software on that presumption.
That presumption is wrong 100% of the time.
Nope.
Anyway, my thanks to Stef. gnome-keyring is gone!
See, gnome-keyring is optional! :)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]