-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optional password export #4700
Optional password export #4700
Conversation
Currently IntelliJ IDEA/Android Studio can't be configured to define the import order for Kotlin files. AFAIK this will be fixed soon. In the meantime you can use the Thanks for including the screenshot of the modified export screen. I don't quite like the idea of simply including a "Passwords" entry in the list. The option to include passwords when exporting accounts feels more like a modifier to the selection, not like something that belongs in the list of objects to export. I currently don't know how a good UI that satisfies these points could look like. |
8a3f20d
to
8bc7517
Compare
7abcc6f
to
0fc2cb1
Compare
The password import works, but a folder sync is missing and only After sync folders, it works properly. @cketti I need your advise. Please can you point me to the place and what's to do then, to do this automatic after import |
Enabling an account via |
0fc2cb1
to
45cb4e3
Compare
45cb4e3
to
7d645da
Compare
After fix build after project restructure, I'm a little bit tired about maintain this PR. I see it as a nice feature to prevent from password-hell after device change. |
@cketti Any change to get this merged ? |
I was thinking more along the lines of something like this: Yes, the option would be unchecked by default. All of that is intentional. Exporting plain text passwords is dangerous. The only reason I'm even considering this is because someone else is willing to do the work and it's much more work to add a way to support exporting passwords in a secure way (that probably means encrypting all of them using a master password). This way at least users that are knowledgeable enough and accept the risks have the option of exporting passwords. Why all the fuss? I believe that it is our job as developers to keep the user's data safe. The average user is not a tech expert and doesn't have the knowledge required to make a proper risk assessment. And they shouldn't have to. It is our job. Merging an incomplete feature and then finishing things later is totally acceptable in some situations. Adding something dangerous and then adding the safety switch later (maybe? worst case is I'll have to do the work myself; on a feature I don't think is a great idea in the first place) is not something I'm keen on doing. |
Sorry, all is just to make thing not/bad working |
There is nothing incomplete, simply added like other switches before. |
Because #4696 was declined on less reflected doubts, maybe we can optional export the passwords