Groups | Search | Server Info | Login | Register

Groups > alt.os.linux.mandrake > #56

Re: keepassx updating

Cross-posted to 2 groups.

Show all headers | View raw

On 2018-05-18 07:25, Bobbie Sellers wrote:

>     So soon enough widespread facial recognition capacity
> should be enough to access your own devices and your cloud
> storage from that initial facial recognition.  With maybe
> special coding for identical people like tattoos in shades
> difficult for people to even notice but easily seen with
> optical filtration on the software.  Most identicals would
> be twins but Triplets and so forth are real now but in the
> future it might have to deal with cloned people.
> 
>     So don't make your problem too insoluble because
> tech will solve it soon enough and give us fresh new problems
> at a different level.

That has a security issue.

At the end, there will be a file that stores (securely) some map or
signatures of your face. Or your fingerprint, or eye blood vessels,
whatever. And it will have to be stored at each site where you identify
yourself.

Now, suppose one of these is compromised, and the bad guys gain access
to your face data and clone it. After all, it is just a file somewhere.
Even if it is a rom.

From that point, they can gain access to your data by using another
compromised device, that instead of looking at your face, looks at or
loads data generated from that file they got on the previous step.
Perhaps the bud guy wears a good enough head mask. Even a robotized face
clone. They can access your private data stored on the cloud, or gain
access to your house, whatever.

You may find this out, but hey, you can not change your face.


The idea is not mine, I saw it mentioned about fingerprint readers on
phones.


-- 
Cheers, Carlos.

Back to alt.os.linux.mandrake | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

keepassx updating William Unruh <unruh@invalid.ca> - 2018-05-15 16:24 +0000
  Re: keepassx updating Dan Purgert <dan@djph.net> - 2018-05-15 17:00 +0000
  Re: keepassx updating Mike Easter <MikeE@ster.invalid> - 2018-05-15 10:01 -0700
    Re: keepassx updating William Unruh <unruh@invalid.ca> - 2018-05-15 17:15 +0000
      Re: keepassx updating Mike Easter <MikeE@ster.invalid> - 2018-05-15 10:58 -0700
        Re: keepassx updating Mike Easter <MikeE@ster.invalid> - 2018-05-15 11:09 -0700
          Re: keepassx updating William Unruh <unruh@invalid.ca> - 2018-05-15 20:45 +0000
            Re: keepassx updating stepore <linshine@here.now> - 2018-05-15 21:45 -0700
              Re: keepassx updating "Carlos E.R." <robin_listas@es.invalid> - 2018-05-16 13:14 +0200
                Re: keepassx updating stepore <linshine@here.now> - 2018-05-16 21:57 -0700
                Re: keepassx updating "Carlos E.R." <robin_listas@es.invalid> - 2018-05-17 14:41 +0200
                Re: keepassx updating stepore <linshine@here.now> - 2018-05-17 17:50 -0700
                Re: keepassx updating Dan Purgert <dan@djph.net> - 2018-05-18 01:17 +0000
                Re: keepassx updating William Unruh <unruh@invalid.ca> - 2018-05-18 03:04 +0000
                Re: keepassx updating stepore <linshine@here.now> - 2018-05-17 21:46 -0700
                Re: keepassx updating "Carlos E.R." <robin_listas@es.invalid> - 2018-05-18 13:23 +0200
        Re: keepassx updating William Unruh <unruh@invalid.ca> - 2018-05-15 20:43 +0000
          Re: keepassx updating Bobbie Sellers <bliss@mouse-potato.com> - 2018-05-17 22:25 -0700
            Re: keepassx updating "Carlos E.R." <robin_listas@es.invalid> - 2018-05-18 13:31 +0200
  Re: keepassx updating theta <theta@nowhere.blah> - 2018-05-30 15:46 +0000
  Re: keepassx updating Bud Frede <frede@mouse-potato.com> - 2018-06-27 08:54 -0400
  Re: keepassx updating wimpunk <wimpunk+news@gmail.com> - 2018-06-27 18:25 +0200
    Re: keepassx updating William Unruh <unruh@invalid.ca> - 2018-06-28 12:25 +0000
      Re: keepassx updating Bud Frede <frede@mouse-potato.com> - 2018-06-30 09:56 -0400

csiph-web