Zinggi

Pretty sure you mean this one: https://thedailywtf.com/articles/The-Speedup-Loop

In JS, my preferred way of handling json is heavily inspired by the elm json decoding way.

I want my decoders to essentially do 2 things:

1. Transform received data into a data structure that is best suited for my app. This might involve converting lists to objects, objects to sets, parse dates etc.

2. Only succeed on valid data

This way, my application never has to deal with bad data. Also, I get to design the data structures I use, not the APIs I use. By only validating and not transforming, you are pushing more advanced validation further away from where the data was received (since you'll need to transform the data at some point anyway).

As for libraries, I want composable parsers. For TS I'd probably use: https://github.com/paperhive/fefe/

You shouldn't validate json. You should parse it, e.g. transform it into your desired data structure if it comes in in a valid shape.

https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-va...

I really like Elms way of Json decoding for this.

You might be interested in lamdera. It abstracts away database access, data transport and data encoding between client end server. Here is a talk about it: https://www.youtube.com/watch?v=nSrucNcwlA8

If you're interested, you can probably get an invite from @supermario on the elm slack, or on: https://lamdera.app/

Disclaimer: I'm not affiliated with the project, but I've met Mario in person and he's a cool dude with great ideas ;)

Thank you! Well put.

> the Android app requires no device permissions

That's not true, it just uses the new way to ask for permissions. E.g. when you want to scan a QR code it requires the camera permission. But it only asks at that moment, not upfront as older android apps used to do

Yep, from a user perspective it definitely looks like 2FA.

In terms of technology it's of course completely different.

Ah ok, got it. If you are already using KeePass than there is no reason to use NoKey, KeePass is great!

> Not everyone has a million devices.

I don't think that's fair. With 3 devices you're perfectly ok. Or even with only 2, if you also use a "key box" (gives you one "device" more at the cost of having to remember a password).

But wouldn't you agree that your brain + NoKey instead of a piece of paper as a backup would be more secure? And more convenient, as you don't have to type your passwords anymore.

I don't wanna push you, just wanna give you some things to think about. As long as you use strong and unique passwords everywhere you're good.

Also, it's not a big problem if one of your devices dies, as long as you paired enough devices you won't lose any passwords.

Exactly. Or even 3 if you make use of security level 3.

The only exception is at the start when there are no passwords stored yet.

When pairing a new device (or in this case a new browser), that device doesn't automatically get any keys! When adding a new device, to complete the setup you also have to be able to unlock a password group, for which you need another device that already has keys.

In short, a new device doesn't have the same power as the others from the start, first new keys have to be generated which can only happen if you are able to unlock your passwords.

So just don't setup both the Firefox and Chrome extension and you're golden.

Yes, but it's a very bad idea. If you'd do this, you could unlock your passwords with a single device by confirming on Firefox or vice-versa on Chrome. This of course also means that if someone steals this device, they can unlock it too.

So don't do it.

Oh, than I misunderstood, sorry. You're absolutely correct.

Thanks. I was always wondering why others don't do this more often. I find it much easier to remember and type in a few words compared to a long number.

> Doesn't this increase your attack surface greatly though?

That's true. I suppose it's a trade off between protection against lost vs. smaller attack surface.

> Since there's no master key, one has to only compromise the OS to get at everything

That's wrong, compromising one device doesn't give an attacker anything useful. Only if two or more devices have been compromised can passwords be decrypted. But in any case, I think if your device is compromised you might be in bigger troubles anyway. E.g. if an attacker controls your device, ransomeware might be easier and more lucrative to them than going after more devices to hunt for passwords.

You lose access to your passwords, that's the consequence of that approach.

That's why it's a very good idea to pair as many devices as you can, e.g. an old phone, your work PC, etc.

This way you're pretty save from any loss.

In general, if you save your passwords with security level N (meaning you need N devices to unlock), if you lose all but N-1 devices, you lose access. You can also add a "key box", which gives you one more "device", but requires you to remember a password.

Hi all!

This is my first time posting something to HN, so please be kind.

I wanted to show what I’ve been working on for the last 6 months:

NoKey, a password manager without a master password. Instead, you can unlock your passwords by confirming from another device. E.g. if you need a password on your PC, you only have to confirm this on your phone. No need to remember any passwords!

The vast majority of the code is written in Elm and it’s fully open source.

There is a browser extension for Chrome and Firefox and an Android app. The application is only useful with at least two devices, so to really test it out, you’ll have to install it on two devices. There is no iOS version and the web app doesn’t work on Safari either (it's missing some stuff from the Web Crypto API), sorry!

Any feedback or questions are greatly appreciated!