Most PRIVATE 2FA apps

Naomi Brockwell TV
17 Mar 202317:36

Summary

TLDREl uso de la Autenticación de Dos Factores (2FA) es fundamental para asegurar nuestras cuentas, añadiendo una capa adicional de seguridad. Sin embargo, algunos de los aplicativos de autenticación más conocidos recopilan más información sobre nuestras actividades de lo que muchos usuarios podrían imaginar. Este video explora qué tipo de información recopilan estos servicios, cómo podemos limitar la información que proporcionamos y presenta alternativas de aplicaciones de 2FA más privadas y de código abierto. Se analiza la recopilación de datos en aplicaciones populares como Authy y Microsoft Authenticator, y se comparan con soluciones más privadas como FreeOTP, Aegis y OTP. Además, se ofrecen consejos sobre cómo introducir manualmente la semilla secreta de 2FA para tener más control sobre la información que compartimos y se resalta la importancia de elegir aplicaciones de 2FA que respeten nuestra privacidad y seguridad.

Takeaways

  • 🔒 **Seguridad en cuentas:** El 2FA es esencial para proteger tus cuentas, añadiendo una segunda capa de verificación.
  • 📱 **Aplicaciones Autenticadoras:** Algunas aplicaciones de autenticación conocidas recolectan más datos de lo esperado.
  • 🕵️‍♂️ **Privacidad:** Es importante ser consciente de qué información recolectan estas aplicaciones y cómo pueden limitar esa recolección.
  • 📈 **Analytics en Aplicaciones:** Las aplicaciones utilizan sistemas de análisis, lo que podría no ser apropiado para herramientas de seguridad privada.
  • 📱 **Authy:** Una aplicación popular que recopila información personal y detalles de los servicios que utilizas.
  • ❌ **Opt-out Fallido:** A pesar de las opciones para desactivar el análisis, algunas aplicaciones siguen enviando datos.
  • 🤔 **Google Authenticator:** Parece no compartir información sobre el uso del servicio, aunque Google generalmente es conocido por rastrear a los usuarios.
  • 🌟 **Opciones Privadas:** Existen alternativas de código abierto más privadas, como FreeOTP y Aegis Authenticator, que no recopilan datos.
  • ⚙️ **OTP:** Una opción de código abierto y exclusiva de Android que, aunque no está mantenida activamente, aún es considerada segura.
  • ⚠️ **Cuidado con el Rastreo:** Es fundamental estar al tanto de cómo las aplicaciones de 2FA manejan tus datos personales.
  • 🔑 **Claves de Seguridad:** Las claves de seguridad son la forma más segura de 2FA y se recomienda su uso en lugar de aplicaciones.

Q & A

  • ¿Por qué es esencial el uso del 2FA para proteger las cuentas?

    -El 2FA es esencial porque agrega un segundo método de verificación a la cuenta, lo que impide que alguien, incluso si tiene acceso a tu contraseña, pueda acceder a tu cuenta sin el segundo factor de autenticación.

  • ¿Cómo funciona un aplicativo de autenticación 2FA?

    -Un aplicativo de autenticación 2FA utiliza una semilla secreta proporcionada por el sitio web, la combina con la hora actual y la alimenta a un algoritmo que genera un código corto cada 30 segundos. Este código debe ser ingresado en el sitio web de la cuenta para autenticarse.

  • ¿Por qué debería preocuparme por la privacidad de mi información si utilizo un aplicativo de autenticación 2FA?

    -Algunos aplicativos de autenticación 2FA recopilan más información sobre tus actividades de lo que podrías imaginar, lo que podría afectar tu privacidad si esa información se envía de vuelta a los servidores de la aplicación.

  • ¿Qué información recolectan algunos de los aplicativos de autenticación 2FA más populares?

    -Algunos aplicativos recopilan información sensible como el tipo de dispositivo, versión del sistema operativo, información sobre los servicios que utilizas y detalles de las cuentas que tienes, lo que podría vincular tus servicios con tu identidad.

  • ¿Qué es Google Firebase y cómo se relaciona con la recopilación de datos en aplicaciones de autenticación 2FA?

    -Google Firebase es un servicio común utilizado para sistemas de análisis en aplicaciones, que recopila datos que a menudo son no maliciosos pero que podrían no ser apropiados para una herramienta de seguridad como un aplicativo de autenticación 2FA.

  • ¿Qué es Authy y qué tipo de información recolecta?

    -Authy es un aplicativo de autenticación 2FA popular que recolecta una gran cantidad de información del usuario, incluyendo su dirección de correo electrónico, número telefónico, información del dispositivo y detalles sobre los servicios que utiliza.

  • ¿Por qué podría ser problemático que un aplicativo de autenticación 2FA recopile información analítica?

    -La recopilación de información analítica puede ser problemática porque va en contra de la privacidad esperada de una herramienta de seguridad. Los usuarios conscientes de la privacidad no desearía ver análisis en una aplicación de autenticación, y si los análisis son incluidos, deberían ser anónimos e imposibles de vincular con una identidad personal.

  • ¿Qué es Microsoft Authenticator y qué tipo de información recolecta?

    -Microsoft Authenticator es otro aplicativo de autenticación 2FA popular que requiere permiso para recopilar datos del usuario antes de su uso. Recopila información sobre el dispositivo, versión del sistema operativo, información del proveedor de servicios de móviles y datos de uso general.

  • ¿Por qué podría ser preocupante el uso de Google Authenticator en términos de privacidad?

    -A pesar de que no se detectó comunicación de la actividad dentro de la aplicación con los servidores de Google, la empresa tiene un historial de rastrear a los usuarios, lo que podría preocupar a los usuarios que valoran su privacidad.

  • ¿Cuáles son algunas alternativas de código abierto para aplicaciones de autenticación 2FA que son más privadas?

    -Algunas alternativas de código abierto y más privadas incluyen FreeOTP, Aegis Authenticator y OTP. Estas opciones son respetadas en la comunidad y no recopilan datos personales del usuario.

  • ¿Cómo puedo disminuir la cantidad de datos que envío si no confío en una aplicación de autenticación 2FA?

    -Puedes introducir manualmente la semilla secreta en lugar de escanear un código QR, lo que te permite controlar exactamente qué información proporciona a la aplicación y también te permite hacer una copia de esa semilla, lo que es esencial para la recuperación en caso de pérdida de la aplicación.

  • ¿Qué medidas adicionales se recomiendan para mejorar la privacidad y seguridad al usar 2FA?

    -Se recomienda utilizar un lector de claves de seguridad en lugar de una aplicación 2FA, ya que son la forma más segura de 2FA. También es importante descargar la aplicación desde un sitio web legítimo y no desde copias o aplicaciones parecidas que podrían ser fraudulentas.

Outlines

00:00

🔒 Seguridad y privacidad en las apps de autenticación de 2FA

Este párrafo aborda la importancia del 2FA (autenticación de dos factores) para proteger las cuentas y cómo algunas apps de autenticación recopilan más información de lo necesario. Se discute la recopilación de datos personales por parte de apps populares como Authy y la preocupación por la privacidad. Además, se ofrecen consejos sobre cómo usar estas apps de manera más privada y se exploran alternativas más privadas y de código abierto.

05:01

📱 Análisis de la privacidad en apps de autenticación de Microsoft y Google

Se examina la política de privacidad y la recopilación de datos de las apps de autenticación de Microsoft y Google. Se menciona que Microsoft Authenticator requiere el consentimiento para recopilar datos y cómo, a pesar de las opciones para desactivar el análisis, la app sigue enviando información. Por otro lado, Google Authenticator no parece comunicar el comportamiento del usuario a los servidores de Google, aunque hay advertencias sobre la reputación de Google en el seguimiento de usuarios.

10:03

🛡️ Alternativas de código abierto para aplicaciones de autenticación de 2FA

Este párrafo presenta varias opciones de aplicaciones de autenticación de 2FA de código abierto que son más privadas, como Free OTP, Aegis Authenticator y OTP. Se describen sus características, como el soporte para múltiples cuentas, escáner de código QR integrado y almacenamiento encriptado de secretos TOTP. Se destaca que, aunque son de código abierto, es importante verificar su reputación y estar al tanto de posibles seguimientos no deseados.

15:04

📝 Consejos para una mejor privacidad en el uso del 2FA

Se proporcionan recomendaciones para utilizar el 2FA de manera más privada. Incluye la opción de ingresar manualmente la semilla secreta en lugar de escanear un código QR, lo que permite al usuario controlar la información que la aplicación conoce. También se sugiere la utilización de claves de seguridad en lugar de aplicaciones, ya que son la forma más segura de 2FA. Finalmente, se destaca la importancia de descargar aplicaciones desde fuentes legítimas y el valor de la comunidad en la selección de soluciones de 2FA privadas.

Mindmap

Keywords

💡Autenticación de dos factores (2FA)

La Autenticación de dos factores, o 2FA, es un método de seguridad que requiere dos formas de identificación para acceder a una cuenta. En el video, se destaca como esencial para proteger las cuentas, añadiendo una capa adicional de seguridad más allá de la simple contraseña. Se menciona que incluso si alguien obtiene tu contraseña, el 2FA actúa como una barrera adicional para evitar el acceso no autorizado.

💡Aplicaciones de autenticación

Las aplicaciones de autenticación son programas que implementan el 2FA, generalmente proporcionando códigos de autenticación temporales. En el video, se exploran varias aplicaciones populares y cómo algunas de ellas recopilan más datos de los que es necesario, afectando la privacidad del usuario.

💡Secret seed

El 'secret seed' es una cadena de caracteres o un código QR que contiene una clave secreta utilizada por las aplicaciones de autenticación para generar códigos de seguridad. Se menciona en el video que este código es crucial para la generación de los códigos de autenticación y que nunca debe ser compartido con servidores de la aplicación.

💡Análisis de tráfico de red

El análisis de tráfico de red es el proceso de examinar las comunicaciones entre una aplicación y sus servidores para detectar qué información se envía. En el contexto del video, se utiliza para evaluar qué datos personales y de análisis recopilan las aplicaciones de autenticación.

💡Google Firebase y App Center

Google Firebase y App Center son servicios de análisis que permiten a los desarrolladores rastrear el uso de sus aplicaciones. Aunque no son malicious en sí mismos, el video cuestiona su uso en aplicaciones de seguridad y privacidad, como las de autenticación, donde se espera que los datos sean privados.

💡Authy

Authy es una aplicación de autenticación de dos factores popular que, según el video, recopila una gran cantidad de información personal del usuario, incluido el ID de sesión, información del dispositivo y detalles sobre los servicios que utiliza el usuario. Esto se menciona como un problema de privacidad para aquellos que valoran la confidencialidad.

💡Microsoft Authenticator

Microsoft Authenticator es otra aplicación de autenticación discutida en el video. Se destaca que esta aplicación requiere explícitamente el consentimiento del usuario para recopilar datos, lo que podría ser un problema para quienes buscan aplicaciones que respeten la privacidad.

💡Google Authenticator

Google Authenticator es un programa de autenticación que, a pesar de la reputación de Google en términos de recopilación de datos, parece no enviar información de actividad del usuario a los servidores de Google, según el análisis del video. Sin embargo, se advierte que los usuarios deben tener precaución debido al historial de seguimiento de usuarios de Google.

💡Aplicaciones de código abierto

Las aplicaciones de código abierto son aquellas donde el código fuente está disponible para su inspección y modificación por parte de la comunidad. En el video, se presentan como una alternativa más privada a las aplicaciones de autenticación propietarias, siempre y cuando estén bien verificadas y tengan una reputación sólida.

💡Seguridad de la clave de seguridad

Una clave de seguridad, o 'security key', es un dispositivo físico que puede ser utilizado como método de 2FA. Se menciona en el video como la forma más segura de autenticación de dos factores, ya que ofrece un nivel adicional de protección contra ataques informáticos.

💡Privacidad

La privacidad es un tema central del video, donde se discute cómo las aplicaciones de autenticación pueden comprometer la privacidad del usuario al recopilar datos personales. Se aboga por la elección de aplicaciones que respeten y protejan la privacidad del usuario, y se ofrecen soluciones para reducir la cantidad de información que se comparte.

Highlights

2FA es esencial para asegurar tus cuentas, añadiendo un segundo método de verificación.

Algunas aplicaciones de autenticación recopilan más información sobre tus actividades de lo que podrías imaginar.

Authy recopila información sensible, incluyendo los servicios que utilizas y los tipos de cuentas que tienes.

Microsoft Authenticator exige permitir la recopilación de datos antes de su uso y mantiene un seguimiento de la información del dispositivo y del proveedor de servicios.

Google Authenticator no parece recopilar información sobre el comportamiento dentro de la aplicación.

Existen alternativas de código abierto más privadas, como FreeOTP y Aegis Authenticator, que no recopilan datos personales.

FreeOTP y Aegis no tienen rastreadores y se han confirmado como opciones seguras.

Cuando se introduce la semilla secreta en la aplicación, se puede hacer manualmente o escaneando un código QR.

Es posible editar la información en el código QR para evitar que se recopile información adicional.

La entrada manual de la semilla también permite hacer una copia de ella, lo que es esencial en caso de pérdida de la aplicación 2FA.

Se recomienda el uso de claves de seguridad en lugar de aplicaciones 2FA, ya que son la forma más segura de autenticación.

Es importante ser consciente de las aplicaciones que están recopilando datos personales y poder tomar decisiones informadas.

La elección de una aplicación 2FA depende de la postura personal de privacidad y seguridad de cada individuo.

Se debe tener cuidado al descargar una aplicación 2FA y asegurarse de que no sea malware o una aplicación no deseada.

Es posible optar por una aplicación que no recopila información personal, y existen muchas opciones establecidas y reputadas.

Descargar la aplicación correcta es crucial, ya que hay muchos imitadores que pueden ser engañosos.

Siempre que sea posible, se debe optar por usar una clave de seguridad en lugar de una aplicación 2FA.

Transcripts

play00:00

2fa is essential for securing your

play00:02

accounts it's where you add a second

play00:04

verification method for your account so

play00:06

that even if someone gets access to your

play00:08

password there's still a barrier

play00:10

stopping them from accessing your

play00:12

account one popular 2fa method is an

play00:15

authenticator app but some of the most

play00:17

well-known authenticator apps are

play00:20

actually collecting more data about your

play00:22

activities than you may realize in this

play00:24

video we're going to dive into what kind

play00:26

of information they're collecting how to

play00:28

give these apps less information when

play00:30

you use them and we're also going to

play00:32

explore some more private 2fa apps that

play00:34

are also open source let's quickly recap

play00:37

how 2fa authenticators or trtp apps work

play00:40

basically in your account settings you

play00:43

might have an option to add 2fa via an

play00:45

authenticator app when you select this

play00:47

option the website will give you a

play00:49

secret seed either in the form of a long

play00:51

string of digits or in the form of a QR

play00:54

code that has that long string of digits

play00:56

embedded in it you need to somehow enter

play00:58

the code into the app and there are two

play01:01

options either you enter it manually or

play01:03

you scan the code talal and Tommy form

play01:05

the security and privacy research Duo

play01:07

misc and they explain to us that your

play01:09

2fa app will take this seed combine it

play01:12

with the current time and feed it into

play01:14

an algorithm that spits out a new short

play01:16

code every 30 seconds or so which you'll

play01:19

type into the account website meanwhile

play01:21

the account you're securing like your

play01:23

Twitter or email will also have a copy

play01:26

of that secret on their servers when you

play01:28

try to authenticate they'll feed their

play01:30

secret into an algorithm on their end

play01:32

combined with the current time and also

play01:34

spit out a code if the codes match then

play01:37

you're in if not it would just reject

play01:39

your call the 2fa app servers shouldn't

play01:41

ever get access to your secret seed

play01:43

really all the apps should be doing is

play01:46

just some computation locally on the

play01:48

device involving your seed in the

play01:50

current time and spitting out codes for

play01:52

you the app can functionally operate

play01:54

perfectly without internet but it turns

play01:57

out that some 2fa apps are doing more

play01:59

than this sending all kinds of

play02:01

information back to their servers in our

play02:03

last video we showed you some malware

play02:05

2fa apps that were actually stealing

play02:08

your secret seed so that hackers could

play02:09

access your 2fa codes too in this video

play02:12

we're going to talk about a different

play02:14

threat apps that aren't stealing your

play02:16

codes but are collecting extra data

play02:19

around your activities which a privacy

play02:21

conscious person should be aware of it

play02:23

is pretty much industry standard at this

play02:25

point that each app has its own

play02:27

analytics system they often use common

play02:30

services such as Google Firebase there's

play02:33

app center for Microsoft these analytics

play02:35

aren't necessarily nefarious but are

play02:37

they appropriate for something like a

play02:39

2fa app when it comes to security tools

play02:41

like authenticator apps anything you

play02:44

would consider to be pretty private we

play02:46

don't want to see analytics in it and if

play02:49

there are analytics we want the option

play02:50

to disable analytics for me it's very

play02:52

sensitive that the app would send for

play02:54

example the services that you're dealing

play02:56

with so if you have an Amazon account

play02:58

Twitter account Facebook account and

play03:00

then it would link the services that you

play03:02

use with your identity the misc team

play03:04

analyzed the network traffic from the

play03:06

most popular 2fa apps to find out what

play03:08

information each was collecting and

play03:10

which app was the most private we would

play03:12

see if the app is sharing more

play03:14

information more analytics than it is

play03:16

required let's start with authy a

play03:18

popular 2fa authenticator app that it

play03:20

turns out collects a lot of information

play03:23

from you to be able to use authi you

play03:25

have to supply your email this is the

play03:28

first thing that they request when you

play03:29

open the app for the first time you need

play03:31

to give your phone number and you need

play03:32

to verify your phone number and when you

play03:34

create your account they give you an ID

play03:36

called S auth ID the user can see that

play03:39

this ID belongs to them after the

play03:41

verification of course this ID is going

play03:43

to be tied with your email and your

play03:46

phone number then there's the analytics

play03:48

that's sent to all these servers and

play03:50

there's a lot device information like

play03:52

device type OS version but there's also

play03:55

more sensitive information they are

play03:57

collecting information about the

play03:59

services that you use and they know

play04:01

which accounts types you already have

play04:03

Google is the service of the token that

play04:06

we scanned during this experiment and of

play04:08

course

play04:10

can't go using whether it's Google or

play04:12

Twitter or something else with your user

play04:15

ID this data analytics that we see in

play04:17

here this is not anonymous because it is

play04:19

associated with the Sid and the SIDS

play04:22

associated with the email and the phone

play04:24

number which are already personal

play04:26

information they are able to keep track

play04:28

of what their own users are doing within

play04:30

their own apps we don't think security

play04:32

tools such as authenticators should be

play04:34

using analytics and if the vendor really

play04:36

wants to add analytics we believe it

play04:38

should be anonymous in this case we can

play04:40

see that these analytics events do

play04:42

contain a unique identifier that can be

play04:45

tied back to the user's account with

play04:47

authy at least give the option for users

play04:49

to disable analytics and all fee doesn't

play04:51

there was no option in the app to turn

play04:53

this off now do we think that authy is

play04:55

using this information for some Grand

play04:57

conspiracy of linking all the platforms

play04:59

someone uses together in a giant

play05:01

centralized database probably not if I

play05:03

were to speculate they just really want

play05:05

to know overall what are the more more

play05:07

popular accounts how are users using

play05:10

their app and so on typically analytics

play05:12

it's not malicious it's just something

play05:14

that

play05:15

is pretty much industry standard at this

play05:17

point we just have strong opinions about

play05:19

which apps should be using analytics and

play05:22

how analytics should be anonymous and

play05:24

not user identifiable but even if there

play05:27

is no Grand conspiracy I'd prefer that

play05:30

an app not know which platforms I'm

play05:32

using or what my phone number and email

play05:34

address are authy is a very talkative

play05:37

app meaning it sends data back to its

play05:39

servers frequently if you're privacy

play05:41

conscious it might not be the best app

play05:43

for you now let's look at Microsoft

play05:45

authenticator another popular 2fa app

play05:48

the first thing to note about Microsoft

play05:49

authenticator is that they mandate you

play05:51

allow Microsoft to collect your data

play05:53

before you can use their authenticator

play05:55

if you decline to share your data they

play05:58

tell you that you can't use the app not

play06:00

a great start so what data do they want

play06:02

from you there's information about your

play06:04

device OS version they're even

play06:06

collecting which mobile operator you use

play06:08

so they mapping who your sell provider

play06:11

is yes they're using something called

play06:13

App Center to collect this starter which

play06:16

is an Analytics tool developed by

play06:18

Microsoft this is one of the standard

play06:20

things that App Center collects it does

play06:22

collect carrier information there's also

play06:24

General usage data as in your behavior

play06:26

each button clicked how you use the app

play06:28

and on top of that Microsoft 2 collects

play06:32

which platforms you're using you can see

play06:34

here in the analytics proton which is

play06:36

the account linked in this test

play06:38

Microsoft is also contradictory

play06:40

regarding whether all these analytics

play06:42

are personally identifiable according to

play06:44

the app's privacy label data collected

play06:46

is linked to your real identity but then

play06:49

in the app settings it says that the

play06:51

data collected is non-identifying let's

play06:53

take a look at the actual identifiers

play06:55

they collect so that we can figure out

play06:57

which one is true first there's the Sid

play06:59

which is an ID that changes with each

play07:01

session that would suggest that it might

play07:04

be randomly generated and not personally

play07:06

identifiable but they also collect

play07:08

something called your shared device

play07:10

identifier which is a persistent ID that

play07:13

would allow them to aggregate analytic

play07:15

across sessions if Microsoft links the

play07:18

shared device identifier ID to the

play07:20

user's identity then all these analytics

play07:22

become identifiable but as you notice

play07:24

there is an option for you to turn data

play07:27

sharing off what happens if we toggle

play07:29

that off we switched the analytics off

play07:31

and we run the experiment again and we

play07:33

saw that this information is being sent

play07:35

nonetheless now the amount of data was

play07:36

was reduced for example the app stopped

play07:39

sending General usage data like she

play07:41

clicked here scrolled here Etc and they

play07:44

stopped sending which platform you're

play07:45

using like proton Twitter Etc but they

play07:48

are indeed still sharing data like your

play07:51

device information your phone carrier

play07:53

and they're even still collecting your

play07:55

persistent shared device identifier that

play07:58

was the interesting part about the

play08:00

Microsoft authenticator because you

play08:01

switch the usage data off yet it sends

play08:04

this thing these apps they're still

play08:06

sending analytics even though the user

play08:08

has opted out from analytics this is

play08:10

still a lot of information for no

play08:12

analytics so if you're one of those

play08:13

great busy people who thinks that opting

play08:16

out of data sharing should actually opt

play08:18

you out of data sharing Microsoft

play08:20

authenticator probably isn't the best

play08:22

choice for you now let's look at Google

play08:24

Authenticator this was a tricky one when

play08:26

analyzing the app traffic to the misc

play08:28

team it appeared that Google was not

play08:30

collecting activity from within the app

play08:32

your behavior inside the app was not

play08:35

being communicated to Google servers we

play08:37

couldn't detect anything about what kind

play08:39

of service you're scanning or how many

play08:41

services for example if you add multiple

play08:43

accounts one from Amazon the other one

play08:45

from Google another from Twitter

play08:46

Mastodon it would not share this

play08:48

information with Google Google did send

play08:50

some things like crash reports but other

play08:52

than that we were surprised to see that

play08:54

actually it doesn't seem to send

play08:56

anything indeed surprising behavior for

play08:58

a company that is renowned for

play09:00

collecting as much data about users as

play09:02

it can and it also seems to contradict

play09:04

what is self-disclosed in their privacy

play09:06

label if you were to look at the Privacy

play09:08

label on the App Store they do mention

play09:10

that the dual link usage data and

play09:13

identify some Diagnostics during account

play09:14

and hence to a user's identity but

play09:17

Exodus privacy confirmed that they too

play09:19

found no trackers in Google

play09:20

Authenticator they did say that they did

play09:22

a static analysis of Google

play09:23

authenticators APK which stands for

play09:26

Android package kit and is the file

play09:27

format used by Android to distribute and

play09:30

install applications and in this

play09:31

analysis found tracker signatures but

play09:34

this is not proof of activity of these

play09:36

trackers on the other side of things the

play09:38

application could contain trackers that

play09:40

Exodus privacy doesn't know about yet

play09:42

they do associate this thing with a

play09:44

cookie ID which is shared among all the

play09:47

Google apps that you have installed on

play09:49

your iPhone and there might be other

play09:50

tracking methods that we're missing

play09:52

there are ways to do this especially if

play09:54

you have multiple Google apps installed

play09:56

on your phone so while Google

play09:57

Authenticator actually seems okay tread

play10:00

carefully because Google has a terrible

play10:02

track record when it comes to tracking

play10:04

users now let's look at some more

play10:06

private alternatives for your 2fa app we

play10:08

explored a bunch of Open Source options

play10:10

to see how they compare free OTP is a

play10:13

popular open Source trtp app developed

play10:16

by Red Hat it's available for both

play10:18

Android and iOS devices and supports

play10:20

multiple accounts free OTP is available

play10:23

on the Google Play Store F Droid and

play10:25

Apple App Store there's also a fork of

play10:27

it called free OTP plus that allows you

play10:29

to export or import settings to Google

play10:31

Drive has a more modern UI and also

play10:33

allows biometric or pin authentication

play10:36

to secure the app Exodus privacy said

play10:38

that they found zero trackers in freeotp

play10:41

and the misc team confirmed that they

play10:43

couldn't detect any network traffic

play10:44

according to the privacy policy of

play10:46

freeotp they do not collect any data

play10:49

from your mobile device and permissions

play10:50

are very narrow in how they're used free

play10:53

OTP seems like a solid choice for an

play10:55

authenticator app next we have Aegis

play10:57

authenticator another open source totp

play11:00

app this is only available for Android

play11:02

but has some good qualities including a

play11:04

built-in QR code scanner Aegis

play11:06

authenticator is available on both the

play11:08

Google Play Store and F Droid and the

play11:10

totp secrets are stored in an encrypted

play11:13

Vault for added secure ready Aegis also

play11:15

has biometric support and integration

play11:17

with Guardian projects Ripple which

play11:19

allows you to delete the Vault if you

play11:21

hit the panic button which is a really

play11:23

cool feature Exodus privacy reports that

play11:25

they found zero trackers in Aegis and

play11:27

the misc team confirmed in their testing

play11:29

that Aegis doesn't send any trackers the

play11:31

Aegis privacy policy states that they

play11:33

don't collect any data from your device

play11:35

and that the usage of the camera

play11:36

permissions is narrow Aegis is another

play11:39

solid choice for an authenticator app if

play11:41

you're on Android and OTP is another

play11:43

free and open source totp app and as its

play11:46

name implies it is also Android

play11:48

exclusive one thing to note is that it's

play11:50

no longer actively maintained as the

play11:52

developer doesn't have time but many

play11:54

still say that it's a good choice for an

play11:56

authenticator app and it also has zero

play11:59

trackers and doesn't collect any data

play12:01

use unmaintained code at your own risk

play12:03

we also looked at 2fas another open

play12:05

source two-factor authenticator that is

play12:08

available for both IOS and Android but

play12:10

according to Exodus privacy reports it

play12:12

does contain trackers the misc team

play12:15

confirmed this that it sends for example

play12:17

frequent Google analytics data but

play12:19

according to them it's nothing really

play12:21

sensitive in terms of all the different

play12:23

2fa product choices now that you have

play12:25

more information about how they do or

play12:27

don't use your data you can pick the app

play12:29

that you feel best aligns with your

play12:31

personal privacy and security stance and

play12:34

this is going to vary from person to

play12:35

person some people will choose to go

play12:37

with the most well-known products

play12:39

because they want to avoid any

play12:41

lesser-known apps that might be scams if

play12:43

they're not too bothered by analytics

play12:45

data then it's not necessarily a lower

play12:49

security option for them if you're more

play12:51

careful you really don't want any

play12:53

analytics data then yes something like

play12:54

an open source solution that you trust

play12:56

that you vetted that others have vetted

play12:59

would be a better option because you

play13:01

know that they're not sending analytics

play13:03

data because you can actually see what

play13:05

the app is doing and just because

play13:06

something is open source it doesn't make

play13:08

it immediately trusted so don't just

play13:10

choose an app because it says that it's

play13:12

open source make sure that it's well

play13:14

vetted and has a good reputation there

play13:16

are many open source options out there

play13:19

the thing is that once you publish your

play13:20

app to the store it's very hard to

play13:22

verify that the code which is open

play13:24

source is the same as the code that you

play13:26

submitted to the store the final part of

play13:28

this video is on how to decrease the

play13:30

amount of data you send off regardless

play13:32

of which app you choose when you first

play13:34

input into your 2fa app the string of

play13:37

random digits that is your secret seed

play13:39

you can choose to type it in manually or

play13:41

to scan a code that has the seed

play13:43

embedded in it that's secret seed it's

play13:45

long it's hard to type and stuff so this

play13:47

is why they use QR code it's very

play13:49

convenient to just scan with the camera

play13:51

and then you get the C to your app so if

play13:53

you trust the app and you want to let it

play13:55

access your camera scanning might be a

play13:57

good option but there's actually all

play13:58

kinds of other data that might have been

play14:00

added to that QR code you can't tell

play14:03

just by looking at a QR code what data

play14:05

or instructions are actually embedded in

play14:07

it but if you really want to you can

play14:09

actually just use any QR code scanner

play14:12

app and see what's actually in the QR

play14:13

code in a typical QR code for one of

play14:16

these 2fa apps there's usually standard

play14:18

information about your account that will

play14:20

allow the app to easily autofill the

play14:22

descriptions your username normally is

play14:24

included inside the QR code your data

play14:27

and login screen and service and issue

play14:29

and all these things they are inside the

play14:31

the QR code this is optional data for

play14:34

you so that you know that this C that

play14:36

you're scanning to which account it

play14:37

belongs and which issuer has issued this

play14:40

code but you can change it you can

play14:41

delete it it's no problem it is really

play14:43

optional so if you're using an app that

play14:45

you know will send this information back

play14:47

to their service you can actually edit

play14:49

the information in the QR code and

play14:51

create a new one before scanning it into

play14:53

the app or another option is just typing

play14:56

in the seed manually in which case no

play14:58

other information will be Auto filled

play15:00

you'll have to type it in manually too

play15:01

when you enter the code manually they

play15:03

prompt you to ask you what is this code

play15:06

for because you would be confused if you

play15:07

only have the secrets they do pile up

play15:09

after a while of using them by inputting

play15:12

this information manually you can choose

play15:14

exactly what information you want the

play15:16

app to have in theory if you have your

play15:18

own way of distinguishing between the

play15:20

various codes and the various accounts

play15:22

that you have that would be one way to

play15:24

obfuscate that this code belongs to

play15:26

Twitter that code belongs to Instagram

play15:28

and so on instead of having that

play15:30

information in the QR code itself this

play15:32

would result in a marginal difference in

play15:34

privacy but that difference might be

play15:36

important a privacy conscious people who

play15:38

choose to opt out of this data

play15:40

collection but importantly manually

play15:42

inputting your seed also allows you to

play15:44

easily make a copy of that seed which is

play15:46

essential in case you ever lose your 2fa

play15:49

app so I highly recommend manual input

play15:51

anyway so here are our main takeaways

play15:53

when using 2fa one you should absolutely

play15:56

have 2fa on your accounts whenever you

play15:58

can two be careful which 2fa app you

play16:01

download because some of them are

play16:03

outright malware three out of the

play16:05

legitimate apps you have the option to

play16:07

choose one that doesn't collect Donna

play16:08

about you and there are a lot of

play16:10

established and well-regarded options

play16:12

for you to choose from four whichever

play16:14

app you choose make sure you download

play16:16

the right thing there are lots of

play16:18

copycats out there that will pay to be

play16:21

the first option in search results when

play16:23

in doubt find the real app from their

play16:25

legitimate website first and link to the

play16:27

App Store from there and five wherever

play16:29

possible opt to use a security key as

play16:32

your 2fa method instead of an app

play16:34

because security keys are the most

play16:36

secure form of 2fa out there we have a

play16:38

whole video explaining how they work if

play16:40

you want to take a look 2fa is an

play16:42

essential part of your privacy and

play16:44

security setup and it's important people

play16:46

know that they can make more private

play16:48

choices with these if you were to ask

play16:49

them do you want to be tracked most

play16:51

people would say no they don't want to

play16:53

be tracked by knowing which Tech in our

play16:55

lives is tracking us and collecting our

play16:57

data we can make more informed decisions

play16:59

about which products and services we

play17:01

decide to use you can make the choice

play17:04

that's right for you nbtv is funded by

play17:06

community support if you'd like to

play17:08

support our free educational content

play17:10

please visit nbtv.media support or check

play17:14

out our eBook The Beginner's

play17:15

introduction to privacy which also

play17:17

supports the channel or even just liking

play17:19

sharing commenting on and subscribing to

play17:21

our content also really helps us thank

play17:24

you so much for watching through till

play17:25

the end click here to receive your

play17:27

access code to Twitter well I don't

play17:29

remember requesting an access code to

play17:30

Twitter but let me click on this random

play17:32

link anyway

Rate This

5.0 / 5 (0 votes)

Étiquettes Connexes
Autenticación de 2FAPrivacidad DigitalSeguridad de CuentaApps de AutenticaciónOpen SourceGoogle AuthenticatorMicrosoft AuthenticatorAuthyAnálisis de RedPrivacidad de DatosCódigo QR
Besoin d'un résumé en anglais ?