Lots of suggestions!

Codebook
1

Hello,

I have a few suggestions and feature requests for Codebook Cloud:

  1. Login Alerts
    Login alerts would improve my sense of security.

  2. Alternative Authentication Methods:
    Adding options like Yubikey or TOTP would provide an additional layer of security for accessing Codebook Cloud.

  3. URL Schemes, Deeplinks, and X-Callback
    Although there might be security considerations, it would be awesome to have direct links to entries, such as using “codebook://abc-123-def-456”.

  4. Previous Passwords
    While there are workarounds, including a native history of changes feature in the GUI would be greatly appreciated.

  5. HaveIBeenPwned
    Codebook providers this feature per-entry, but I would like to conduct a comprehensive audit of my entire database. Periodic checks in the background might help avoid hitting rate limits?

Thank you for considering these requests!

2

@exchange807, Thanks for reaching out to us on Discuss and for your feature suggestions. Let me answer your questions/suggestions in line:

  1. Login Alerts: This is a nice idea, but also might be an unwanted additional notification for some users so we might set it as a preference but we can certainly take a look into this and have an internal discussion to see how best to proceed.

  2. Alternative Authentication Login: We have discussed adding an additional method of authentication for logging into Codebook Cloud but have not decided on how to do it just yet but it is in our plans. We are just finishing up a “Passkeys” option that will be released shortly which would be an alternative to username and password

  3. URL Schemes, Deeplinks, and X-Callback: This is not something we are considering at this time. You can already launch websites from within Codebook but going further than that does cause some security concerns at the current time.

  4. Previous Passwords: We actually have done some work on this and we are calling it “Field History” where a user can see the previous field value history so incase you need to enter a previous password when changing one, you will have that information handy. We hope to release this in a future release, just not sure which one yet.

  5. HaveIBeenPawned: We do have a future feature update already scheduled for something like this. It will probably be a view where you can see the time your passwords have been the same and also if you might be using the same passwords in multiple entries. We have not gotten all the things mapped out that we want to track but we have a good idea based on other requests for this type of feature. We will give more information on the feature after we have a plan in place and begin work on the feature.

Thanks for the suggestions, we really appreciate them

Cheers,
Don

3

Hey Don. Thanks for the response! Glad to hear some of this is in the pipeline.