Happy π Day! This morning at 10am (and in quite a snow storm in the northeast US, hope everyone else is warm and safe) we are releasing Codebook for macOS 3.2.2, a maintenance update that includes an upgrade for the Password Generator. When Diceware is selected in the Password Generator a Word List option is now shown providing multiple word lists for you to choose from in addition to the original Reinhold word list. The default is now Electronic Frontier Foundation’s improved random word list, which we’re finding to be really quite good. In short, the generated pass phrases are much easier to remember.
In addition to the Reinhold and EFF variants we’ve also added Spanish, French, German, Italian, Danish, Swedish, and Japanese lists. As we’re not native speakers of these languages we’d really appreciate any feedback on how well these options work for native speakers and those more familiar.
Changes in this Version
Adds new Word List option to Password Generator for Diceware passwords
Word List includes the EFF and Reinhold variants and several additional languages
Updates Show/Hide All Masked feature to respond to state of masked fields
Ends edit mode when starting WiFi sync to ensure pending edits are persisted
Fixes crash related to blank entry names
Updates Dropbox sync to latest SDK release for bug fixes
Download: Mac App Store
If your purchased Codebook (or STRIP) in the Mac App Store:
Hi - nice upgrade. The Japanese list looks good, after a few refreshes. It’s “normal” looking.
I have an interesting variation on a word list in Japanese. I add trendy words and phrases to mine, not just dictionary words.
With 3.2.2 on latest macOS, I observed something. I had been picking through Facebook’s mobile menus to get 2FA codes, but noticed that they also allow 3rd party apps so, I thought I’d set it up.
I added a TOTP field to my Facebook entry, and pasted in the secret from the Facebook app as usual.
I noticed that the TOTP field was “masked” instead of showing the code as it had done.
When I used SA to verify the code, it was normal, unmasked.
I switched back to Codebook proper, and it was still masked.
I switched away from the entry and back, and the TOTP field was “normal” again, with the code visible.
With 3.2.2 on latest macOS, I observed something. I had been picking through Facebook’s mobile menus to get 2FA codes, but noticed that they also allow 3rd party apps so, I thought I’d set it up.
I added a TOTP field to my Facebook entry, and pasted in the secret from the Facebook app as usual.
I noticed that the TOTP field was “masked” instead of showing the code as it had done.
When I used SA to verify the code, it was normal, unmasked.
I switched back to Codebook proper, and it was still masked.
I switched away from the entry and back, and the TOTP field was “normal” again, with the code visible.
We noticed this as well. So there’s a small bug in the current release of Codebook related to the recently adjusted masking behavior. The bug is as follows: If you add a new field that’s associated with an un-masked type (i.e. TOTP in your scenario), it will add as masked temporarily (as if you had right clicked and selected “Hide ”). As you noted a current workaround is to navigate away from the entry and then back to it, or toggle the “Mask all” toolbar button and re-toggle it. Sorry about this.
We do have a fix in place that will be included in the next round of betas and should be included in the next official update. I’ll post back here when we’ve got a beta prepared.