Maybe, but the homeless crackhead shambling through the lot at 3am like a zombie doesn't give a fuck and will kick that thing as hard as he can muster.
Move it anyway; at least it will have a chance instead of painting a massive target on it with those cones.
I keep vaultwarden behind a vpn so it's not exposed directly to the net. You don't need a constant connection to the server; that's only needed to add/change vault items.
This does require some planning though; it's easy to lock yourself out of your accounts when you're away, if you don't incorporate a backdoor of some kind to let yourself in in an emergency. (lost your device while away from home for example)
My normal vpn connection requires a private key and a password that's stored in my vault to decrypt it. I've setup a method for retrieving a backup set of keys using a series of usernames, emails, passwords, and undocumented paths (these are the only passwords I actually memorize); allowing me to reach vaultwarden where I can retrieve my vault with the data needed to login to everything else properly.
Usually that does the trick for me too; but this morning it just would not cooperate no matter what I tried.
Seems to be playing ball again, for now.
I have a feeling this is more to do with Android/Google not wanting to give up control more than anything. If googles stuff always works, but third party stuff is mysteriously always glitchy; users are going to gravitate to google and their ever growing monopoly...
Glued on panels and a skeleton like Swiss cheese.
I wonder how quickly you could break into one with your bare hands. Just rip a panel off and reach into the interior to open.
He never defined how short 'short' is. He also never said you'd be able to use it for anything else after, lol
Found the best option:
There's a quick setting button you can add to the notification tray. It opens the vault and asks which item to auto fill in the app you just had open. :)
I was pointed in the direction of that menu: there's an 'autofill' button in there that will open the vault and ask you which item to use. This is so much better than android thinking about whether it should popup!
Thank you! You gave me the hint I needed.
I didn't know there was a quick setting button (the buttons in the notification tray) and have been struggling to find the accessibility options people have mentioned.
That button in the tray seems so much more reliable. Thanks again!
I had tried that; if I disable inline, I have no autofill at all.
Using SwiftKey, but I get the same results with the built in Samsung keyboard too :/
What type of auto fill do you use/works for you?
Looking into this more I've realized there are three options, but only one has ever worked for me. (talking strictly about the Bitwarden android app)
The standard 'autofill services', which is supposed to provide a popup on screen near the item to be auto filled has never worked for me. Sometimes it will flash onscreen for a fraction of a second, but always disappears before you could possibly touch or even read it.
'inline autofill' is what I have been using. It replaces the word suggestions on the keyboard with autofill options. It's what stopped working today, then seems to have come back; both unexplainably...
Finally there's the 'use accessibility' option, but the only bitwarden accessibility options I can find in android are these:
Each with 'select action' > 'bitwarden'. No other configuration, no options to choose what to do with Bitwarden, just 'bitwarden'.
When enabled the selected action enables/disables bitwarden as an autofill service to be used in the standard Android autofill services as above. I can't find anything at all in accessibility that actually triggers autofill to fill things.
I've always had all three of these autofill options enabled, but inline is the only thing that's ever actually functioned. Even still, that has been flakey, with it often not appearing in the keyboard until I move the cursor between fields several times or switch apps and come back. Today is the first time it's outright refused to show up no matter what troubleshooting I tried.
It's fixed itself and started working again, but I habe no idea why. I didn't change anything between now and when I made this post.
I tried. I couldn't get it to work again, so wanted to look at other options alongside looking for help/solutions.
But just as it decided to stop working, despite my efforts; it's suddenly started working again.
Sigh...
Most of my web services are behind my vpn, but there are a couple I expose publicly for friends/family to use. Things like emby, ombi, and some generic file sharing with file browser.
One of these has a long custom path setup in nginx which, instead of proxying to the named service, will ask for http basic auth credentials. Use the correct host+path, then provide the correct user+pass, and you'll be served an openvpn configuration file which includes an encrypted private key. Decrypt that and you've got backdoor vpn access.