IOS Problem loading usernames from mpsites file
I've been using the IOS version successfully for some time now. It just stopped importing usernames from the mpsites file. I wrongfully bought the option to generate usernames when I purchased the biometrics option. Now the app generates random usernames but I do not want that. Problem 1, there doesn't seem to be any way to turn this off in the app. If I reinstall the app and do not restore previous purchases, it goes away but I also no longer have biometrics, which I want. Problem 2 is that the app still does not import user names from my mpsites file.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Maarten Billemo... on 17 Jun, 2020 03:31 PM
Hi Bill,
Thanks for bringing this to my attention. I will look into both of those concerns.
https://gitlab.com/MasterPassword/MasterPassword/-/issues/354
2 Posted by wjbi on 27 Aug, 2020 04:08 PM
Hi Maarten,
How are things going with a fix for this issue? The IOS version of
Masterpassword still does not import user login names from the mpsites
file. Instead the app fills in the randomly generated login names that of
course do not work. Thanks for this great app and all the time you have
put into it. I use it on all my devices - android, IOS, windows, linux
ubuntu and mint.
---------- Forwarded message ---------
3 Posted by Bill B on 29 Aug, 2020 01:20 PM
Thanks Maartin, I used my MasterPassword java applet in Linux to create user login names that were AES encrypted exportable and exported the new data into a new mpsites file. Now the user login names are imported to IOS as before. Something must have changed with the latest release of the IOS app, because it was accepting clear text user login names before the latest update.
Just a few observations and comments on these files. As I mentioned I use MPassword on all my devices, and, unfortunately, I have just about every OS out there - Windows (my wife), Android, IOS (my wife), and several versions of Linux (Ubuntu and Mint, but started with Fedora). So the same list of sites needs to be kept up to date on each machine for this method of password protection to work. Prior to this change, I used my android device, which does not encrypt user login names, to generate both the json and mpsites files to cover all android devices and IOS and the Linux java applet. I needed to create and maintain a second list on the windows machine, which cannot use either of the other two because they do not maintain the notes section of the windows app. I would loose all my notes for each site. The windows app is exactly the same as the Fedora app you developed that got me hooked on MasterPassword. It's very robust and my favorite of all of them. Since the IOS change, I now need to maintain 3 lists. One for Android, One for Windows, and One for IOS/Linux Java applet (since these two require encrypted user login names that are only generated in the Linux Java applet. BTW, my Linux java applet never did carry the user names from the beginning, and I wondered why. It's working now along with the IOS device using the encrypted names. I rebuilt the list one site at a time.
So, this is a long winded user scenario I know, but I am thinking that I am not the only one with multiple devices using MasterPassword. I really love the app and recommend it to everyone I know when the subject of passwords comes up. The bottom line is that it would really be nice to have to maintain only one file list of all user sites that could be loaded into each app for each OS rather than keeping up with multiple files. I have confused myself a number of times by not remembering which device I used to create and save a new site and if I remembered to export a new file, create the other device files and import them into all the machines.
While this is food for thought, I also realize it would be a very difficult accomplishment at best, since the various apps are done by different developers. You have an outstanding app here that I think tops anything on the market today. I love it. and it saved my sanity, as I currently maintain about 190 sites in the app. Things were really getting out of hand when I used paper. If it could be simplified for use on multiple platforms with a single file to maintain, I think it would be unsurpassed by any other system on the market. It already is in terms of everything else. This would put it over the top, if it's even practical to do.
Thanks again for your help and all the hard work you and everyone else on the team puts into this.
Support Staff 4 Posted by Maarten Billemo... on 03 Sep, 2020 08:50 PM
A fix for this issue is rolling out in 2.9.7 on iOS and macOS.
Support Staff 5 Posted by Maarten Billemo... on 03 Sep, 2020 08:54 PM
Bill:
I'm not sure I understand the situation 100%, could you clarify each of the applications you are using on the various platforms, so I can make sure I understand which apps you're working with? Most importantly: which ones are using official Master Password apps (ie. apps you can get by following the links on https://masterpassword.app), and which ones are using third-party apps?
Ideally, an export file from any of the apps should work on all others – if you're having issues using export files between apps, the best I can recommend for me to investigate, is for you to create a user "Test" with a master password "test", on each of the apps you use, export from each of those apps, and include the export files you receive from all of the apps here for inspection along with a detailed explanation of what you expect to be able to do + how that expectation falls through.
Thanks!
6 Posted by Bill on 10 Nov, 2020 11:11 PM
Hi Maarten, you sent me a request for some sample files containing dummy
sites and usernames so you could analyze why the various masterpass apps
I use on several different operating systems will not work with the same
master file imported to each one. Well, you already nailed it in your
request to me when you asked me if I use all your official apps from the
masterpassapp website. It turns out I do not. I'm using your official
java applet on my Linux machines and your official IOS app for my wife's
Iphone. They both load from the same file. However, I am using the
android version from the google app store for my android phone and
tablets. I think the developer is devland. I use a robust windows
version that I got off the internet from I don't remember where. I
think I sent you a copy of the *.exe file a while back at your request.
So that's why they require different files to import sites, usernames
and data. Until I read through more of your discussion items on the
official website, I didn't realize that these are not official versions
and so they differ, being from different independent developers using
the open source license for the algorithm. I was thinking that you
controlled them all. I really like the android version I'm using from
the google play store, so I'll keep using it for a while. I tried the
one on your official website, but it's pretty basic at this time. I
could not figure out how to import the sites/usernames file. I think I
saw a comment from you that you will be working on upgrading the app, so
I will keep an eye out for that. I am curious as to what happened to
the version I used on Fedora a long time ago that has the same exact
look and feel as the windows version I use today. I thought it was an
official app that you developed, but I do not see it on the
masterpasswordapp site. In any event as long as I am using different
apps from different developers, I guess I need to live with maintaining
3 different files. Sorry for taking your time on this. I should have
realized the issue before bothering you with it. In any event you and
your team have done excellent work in the development of the algorithm
and official apps. I have nearly 200 sites in the app to date. It's a
real lifesaver, since every site one visits wants an account created to
do anything. Thanks again.