Hacker Newsnew | past | comments | ask | show | jobs | submit | PranavBerry's commentslogin

Location: India

Remote: Yes

Willing to relocate: No (can work remotely according to another time zone)

Technologies:

Python (FastAPI, Flask, Django)

JavaScript/TypeScript (React, React Native, Node.js)

Machine Learning (Numpy, Scikit-Learn, Pandas, Keras)

PostgreSQL/MySQL

Docker

Résumé/CV: https://www.linkedin.com/in/pranav-berry-00809719b/

Email: berrypranav@gmail.com

I'm also ok with an internship role before discussing further.


Remote: Yes

Willing to relocate: No (but can work remotely according to another time zone)

Technologies:

JavaScript/TypeScript (React, React Native, Node.js)

Python (FastAPI, Flask, Django)

Machine Learning (Numpy, Scikit-Learn, Pandas, Keras)

PostgreSQL/MySQL

Docker

Résumé/CV: https://www.linkedin.com/in/pranav-berry-00809719b/

Email: berrypranav@gmail.com


Location: India

Remote: Yes

Willing to relocate: No (but can work remotely according to another time zone)

Technologies:

JavaScript/TypeScript (React, React Native, Node.js)

Python (FastAPI, Flask, Django)

Machine Learning (Numpy, Scikit-Learn, Pandas, Keras)

PostgreSQL/MySQL

Docker

Résumé/CV: https://www.linkedin.com/in/pranav-berry-00809719b/

Email: berrypranav@gmail.com

I'm also ok with an internship role or working on something as a sample before discussing further.


>If I'm a common person with one phone

I had not thought about that but I think I can add push notifications if this is a problem. So on your phone you just tap the login with my authenticator button and approve the push notification in my authenticator app.

>how do I get my account back?

You can optionally add a recovery email.


> FIDO Alliance is doing with WebAuthn

Yes I looked into it, but it looks like WebAuthn does not support multiple devices (let me know if I am wrong).

What if I want to login from two different devices? I don't think that is possible with WebAuthn, but using my authenticator you can login to multiple devices. You will also be able to add a recovery email address to my authenticator to recover your accounts if you phone gets damaged/lost.


Yes it is. I can plug my Yubikey into as many laptops as I would like.

> You will also be able to add a recovery email address to my authenticator to recover your accounts if you phone gets damaged/lost.

This worries me. That means I have to trust you to not leak my 2FA. Authy does this already and so I don’t use Authy. All my 2FA is on my Yubikey.


> plug my Yubikey into as many laptops as I would like.

What if you don't own a physical key?

> I have to trust you to not leak my 2FA. Authy does this already and so I don’t use Authy

This is optional. You can choose not to have a recovery email. Just curious though, what do you do if your Yubikey gets stolen/damaged/lost?


I have a backup Yubikey as well as backup codes stored in an encrypted file and backed up to several different devices.


>As for QR codes, those can be copied The QR code are unique for every login attempt. After you scan the QR code and enter your phone's pin, my authenticator will send a request to my server. If everything is ok you will be logged in. Sorry I did not get what you mean by this? Do you mean that someone could copy and use the same QR again?

>I will never use digital face/touch ID for anything I do not save any biometrics on my server. They are stored locally on your phone, my app just uses the native system used to unlock your phone. That being said, you can just use your phone's pin if you don't like to use biomterics.


Do you mean that someone could copy and use the same QR again?

A person intercepting traffic or spoofing a site can copy/tamper/replace the QR code just as they can plain text or binary blobs. QR is just a presentation structure that makes it easier for a camera to translate something into data. For this to be useful there would have to be a boot-strapped chain of custody and chain of trust already installed on the device scanning the QR code meaning you know where that trust came from and you can verify it against a trusted source. If this is not what you meant then where is the end user getting the certs used in this QR code from? Are you embedding the certs in the application? How do people know the application has not been copied/tampered with?


>intercepting traffic or spoofing a site can copy/tamper/replace the QR code

Will this be a problem with HTTPS?

When you open a page, a request will be made to my server to generate a unique login attempt, the id of this unique login attempt will be shown in the QR code. When you scan it and enter your phone's pin, my authenticator generates a signature of the login attempt id, your username on that website and the current time. My server verifies the signature and logs you in if everything is ok.

Have you logged in to the Discord/Reddit/Whatsapp websites by scanning the QR code shown there from their mobile app? My concept is the same but using my authenticator app, websites which do not have a native app can also offer a QR code login.


I've seen people use QR with those sites and it doesn't make sense to me. So using a bank as example, I barely trust them to get this right. Now I am inserting your company into the chain of trust? Why am I trusting one more party to get all of this right? Or is this a solution you are selling to each vendor and they are implementing your service on prem? Is your service going to be audited by independent third parties that vendors choose? How do people verify that your application is the legitimate version? How does the bank know if someone has tampered with your application? Why is my bank trusting your application?


>Is your service going to be audited by independent third parties that vendors choose?

Yes I am planning to do that.

>How do people verify that your application is the legitimate version? How does the bank know if someone has tampered with your application?

I will use SafetyNet to check that the device is not rooted/jailbroken and that the signature is being made from my app.


> SMS based 2fa has many other problems

What are these problems? It will be great if you can list some of them, I'd like to read more in detail.


>agree with password-less.

Does my idea sounds like something you would use? Will you download a authenticator app to avoid using user/pass?


I already have a Msft Authenticator and a Google one installed on my phone, if you can make it work with one of these already that would be fine.


>have a Msft Authenticator and a Google one I think you can just add all accounts to one authenticator.

>make it work with one of these These authenticators, have no support for QR codes so this would not be possible.


I'm not sure as a user I'll use another Authenticator app just for a random website.

It has to be for something worth the trouble (work, bank, etc...)


Got it, but there will still be a network effect.

You will just have to download it once and can add and manage accounts on a lot of websites.


> TOTP and similar already solve the "phone is present but offline" issue.

Thanks a lot, this invalidates my idea and I will not work further on it.


> How will a website be able to scan my phone's screen?

Using your webcam. However from the comments it seems that there are a lot of devices without a webcam so my idea will not work.


My laptop doesn't have a webcam, and even if it did, I wouldn't permit my web browser address to it unless I really needed to. A website that asks me to access the webcam just to log in isn't going to appeal to me.

I've no idea how typical I am in this regard, though.

Could you turn the idea on its head? Could the website display the QR code and the phone scan it, as per WhatsApp and many others? Or perhaps the phone just displays the note ubiquitous "random raccoon" type wordset for the user to enter into the website?

I'm probably missing the point of your idea.


>the website display the QR code and the phone scan it I'm exploring that right now, thx a lot.

>I'm probably missing the point of your idea.

It was mainly a way to do 2FA with a phone but no SMS/internet on phone. However it looks like TOPTs solve this probelem.


> I'm exploring that right now, thx a lot.

No problem, good luck :) Is good to see someone experimenting in this area and asking for advice to stay on track.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: