public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Catastrophic bug in the firefox 'ProfileManager' function
Date: Wed, 22 Jul 2015 23:18:18 +0100	[thread overview]
Message-ID: <201507222318.30379.michaelkintzios@gmail.com> (raw)
In-Reply-To: <55AFE45F.4040108@gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 3027 bytes --]

On Wednesday 22 Jul 2015 19:43:43 Dale wrote:

> So, don't use something that is within your browser but then go and type
> that password . . . in your browser?  Yea, that'll work.  Heck, if I
> really wanted something that secure, I'd unplug the ethernet cable and
> turn off my modem.  Then I might be secure.

LOL!  No, I meant that you decrypt your passwd containing text file, sql file, 
localc file, or whatever file you use.  Then you use something like cat, or 
less, or localc to view/search it.  It can all be scripted so that you run a 
single command alias in a terminal and it asks you for your gpg passphrase, 
before it opens the file for you.

A terminal is unlikely to suffer from XSS, javascript injection, sql 
injection, et al. but a browser could.  Then you can copy & paste whichever 
account passwd you needed into a browser, but this will NOT be your master 
passphrase.  Even if the passwd you paste into a browser ends up being 
compromised, it will only be one passwd and a single account, rather than your 
master passphrase and all your accounts.


> Just how many of these sticks do I need?  Are we looking at a dozen or
> more which will have to be all kept up to date as well?  Come on, be
> realistic here.  I doubt anyone is going to spend the time to do all that.

You need more than one, if you want to keep your passwds file stored off your 
machine.  I keep mine on a PC which is air-gapped and a second copy on a USB 
stick.  You may need a third copy kept at different premises, if you want to 
guard against DR.


> But with Lastpass, I don't have to worry about that.  I can go to my
> brothers house, put my email and password in Lastpass and carry on with
> life.  No need for a USB stick at all or having to wonder when was the
> last time I updated the passwords on it either.
> 
> I'm trying to be realistic here.  I try to be as secure as I can but
> within REASON.  As I mentioned above, if I really need and must be that
> secure, I'd unplug the ethernet cable and turn off my modem.  Then I
> wouldn't have to worry about it unless someone broke into my home.  Of
> course, I wouldn't have the benefit of using the internet either.

Sure, security and convenience are not always best bedfellows.  We are 
discussing about hypothetical risks here and different users' risk tolerances.  
If you encrypt the file separately with a strong key before you upload it, and 
this encryption key is different to your authentication key on the Lastpass 
website, then the risk of your encrypted file being cracked is rather low.  
When people discovered that their Lastpass account had been compromised, this 
did not necessarily mean that their encrypted file had been compromised too.  
However, I don't know exactly what the security architecture of Lastpass is to 
comment on the specifics.  All I'm saying is that I wouldn't trust storing my 
passwds on the cloud for the sake of convenience.

YMMV.  :-)

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-07-22 22:18 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 23:18 [gentoo-user] Catastrophic bug in the firefox 'ProfileManager' function walt
2015-07-20 23:59 ` wabenbau
2015-07-21  0:20 ` Dale
2015-07-21  1:17   ` Rich Freeman
2015-07-21  1:40     ` Dale
2015-07-21  7:53       ` Mick
2015-07-21  9:38         ` Neil Bothwick
2015-07-21 10:27           ` wraeth
2015-07-21 10:41             ` Neil Bothwick
2015-07-21 11:09               ` wraeth
2015-07-21 13:59                 ` Neil Bothwick
2015-07-21 19:35                   ` Chris Spackman
2015-07-21 20:31                     ` covici
2015-07-21 23:51                       ` Neil Bothwick
2015-07-22  2:05                         ` covici
2015-07-22  3:00                           ` wraeth
2015-07-22  9:28                             ` Neil Bothwick
2015-07-22  9:26                           ` Neil Bothwick
2015-07-22 20:15                             ` covici
2015-07-23  0:34                               ` wraeth
2015-07-21 17:35         ` Dale
2015-07-21 20:20           ` Mick
2015-07-22  0:32             ` Dale
2015-07-22 17:41               ` Mick
2015-07-22 18:43                 ` Dale
2015-07-22 22:18                   ` Mick [this message]
2015-07-22 23:09                     ` Dale
2015-07-23 23:24                       ` [gentoo-user] Re: [gone O/T] " Mick
2015-07-24  9:38                         ` Dale
2015-07-21 23:52           ` [gentoo-user] " Neil Bothwick
2015-07-22  0:34             ` Dale
2015-07-21 22:51         ` [gentoo-user] " walt
2015-07-21  1:45 ` [gentoo-user] " Jc García
2015-07-21  4:14 ` [gentoo-user] " »Q«
2015-07-22  0:23 ` [gentoo-user] " Volker Armin Hemmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201507222318.30379.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox