David Manouchehri

> This is not quite what is described here. Has the behaviour changed since this issue was created? Pretty sure I'm still having the same issue. This reproduces the error...

Confirmed, still having the issue. I started `wrangler tail -e production`, closed my laptop, ate lunch, and now there's no more logs showing up (yet wrangler hasn't exited or given...

I'm still having this issue on 3.31.0. I run into it multiple times per day. @petebacondarwin What OS are you testing on?

Awesome, thank you!

@petebacondarwin Which release should this be fixed in? I'm still having issues with dead logs sometimes.

You could still display a notification on the lock screen, it just wouldn't be able to show the contents. As soon as you unlock, it could decrypt. Is it common...

Indeed, I agree with you; there's probably some use cases I'm missing. For non-cached passphrase keys, do you think it's fair to assume that we can always put them in...

I was actually thinking of putting the entire private key into the keystore, not just the cached passphrase.

@nmikhailov Do we have a lot of users with fingerprint scanners?

Just to clarify, I'm suggesting we use the Keystone to protect the passphrase **cache** (meaning it has to be entered every _x_ amount of minutes/hours); I am _not_ suggesting that...