The 1Password Community forums are in read-only mode from Jan 28th - Feb 4th, 2025. Find out more.

Bug Report - Special characters in master password prevents sync using iCloud and WiFi Server

jasper_lawrence
jasper_lawrence
Community Member

I confirmed this by changing, after much frustration and confusion, including examining NAT/PnP on my router, my password on the Mac to 12345678 and making sure the iCloud archive had updated. Now I could sync the db to my newly configured iPhone and iPad. I also confirmed this solved my problem in WiFi server attempting to do the same thing. I had switched to using iCloud in an attempt to resolve it.

Deleting the iCloud archive did not fix the issue, it was only after I changed my master password that syncing worked. Once set up it doesn't seem to matter, but migrating the DB to a blank iDevice using either iCloud or WiFi server Sync the first time is impossible with my old Master Password.

My old password had included the following characters: 1@0\aqlp though not in that order. Changing the pword back between doing the iPad and iPhone restored the inability to sync a "clean" device, and so copy the 1Password DB from my Mac to my iDevice.

I am using the latest versions of iOS and Mac OS X, and all my devices are relatively recent purchases, the oldest the iPad Air, the iPhone is a 6.

So Mac OS X 10.10.5 (14F27), iOS 8.4.1 (12H321) on the iPad Air and iPhone 6. I got all my 1Passwords from an AppStore/Apple.


1Password Version: 5.3 (530029)
Extension Version: Not Provided
OS Version: OS X 10.10.5
Sync Type: iCloud or WiFi Server
Referrer: kb-search:password character bug icloud sync

Comments

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Greetings @jasper_lawrence,

    I tried altering my Master Password to the sequence of characters that you posted 1@0\aqlp in an attempt to replicate but my test Wi-Fi Sync (to a clean iOS device too) worked without issue. It would seem we'll need to work a bit more on pinning down the cause. It's surprising because before we posted the following article, Should I use special characters in my Master Password? we did test all the platforms to ensure this information was correct.

    Given we're discussing Master Passwords we can move this to email if you prefer.

  • jasper_lawrence
    jasper_lawrence
    Community Member
    edited August 2015

    I have changed my Master Password, so I am fine discussing it here. I used apql1@\0 as my password, and as I said could not get it to work for iCloud nor for WiFi server, I no longer use Dropbox, until I changed it to a simple 12345678.

    It is an odd one, after all the password worked and was accepted otherwise. If I had to I would guess it is the atmark or the forward slash since those have meanings in development languages and scripting languages, but I presume you escape or comment field contents on submission. So really I have zero idea what is going on or why.

    If you need more details from my OS or set up let me know, I am happy to oblige. I am for instance using pam.d and Yubikey for authentication to my Mac and for Admin access as well as Sudo, and for a while I thought it might be that, but never got around to disabling it to test it because simplifying the password solved it.

    Does Agilebits plan on adding a Google Authenticator function to 1Password by the way so I can dump these free and therefore of questionable duration tools like Google Authenticator and OTP Auth?

  • jasper_lawrence
    jasper_lawrence
    Community Member

    I am in Morocco by the way so on UK time, not sure where you are located.

  • littlebobbytables
    littlebobbytables
    1Password Alumni
    edited August 2015

    Hi @jasper_lawrence,

    1Password 5 on Mac and iOS and 1Password 4 for Windows all currently support TOTP in the form of RFC 6238 (Google Authenticator). We don't support certain propriety TOTP protocols so it depends on what a particular site is using I'm afraid. For more on this we have pages on Time-based One-Time Passwords (TOTP) for Mac and iOS.

    My first attempt at trying to replicate your issue still yielded no joy, I'm going to have to ponder and think of further testing to try I think. It's very odd.

This discussion has been closed.