v1.19 Updates

[Aetherinox]

v1.19

The following is a list of initial dependency updates, fixes, and functionality changes for the next version of KeeWeb.

Tasks

• Update all dependencies to newer version
  • Reference: Dev - Dependencies #2160
  • Numerous dependencies removed in favor of newer forks / better performing
• Adjustments to ensure files / code conforms with newest standards dictated by the various dependencies
• Changed the way preset settings are displayed.
• Add passphrase functionality
• Add support for UUID4 generation
• Add SHA-512 preset
• Add reveal password on main window.
  • Disabled by default, most be enabled in KeeWeb settings
  • Ref: Ability to Show Master Password when typing #2050
• Add new setting to allow for full file paths to be displayed in "Recently Opened" list
  • Ref: Path of Databasefile - feature request #2118
• Add new security measure to wipe textfield password after 1 minute of inactivity
  • This is for users who enter text in the database password field but never press enter to open the db. After 1 minute of inactivity, the textbox will be wiped.
• Re-introduce KeeWeb fav-icon grabber service as Cloudflare worker
  • Added ability to specify different icon size when fetching
    • https://services.keeweb.info/favicon/domainToFetch.com/64
    • default icon size 32 x 32
  • Future update will include ability to specify your own favicon service
  • Ref: Favicon download is broken #2108
• Add support for multiple otpauth syntax
  • otpauth://totp?secret=
  • otpauth://totp/default?secret=
• Added ability to go two levels deeper with folders with proper formatting
• Added markdown update
  • Users can now attach .md files to vaults and view the contents of the markdown file.
  • Supports all normal markdown such as lists, checkboxes, tables, headers, images, etc.
  • Added syntax highlighting for codeblocks which supports languages such as javascript, php, lua, python,20+ others
  • Supports footnotes
  • Supports Github alert boxes
  • Added new CSS properties so that each theme can have different colors / layout.
• Patched critical vulnerabilities
• Bump minimum Node to v18.12.0 LTS
  • If you wish to build your own version of KeeWeb, you must utilize one of the following versions of node:
    • ^18.12.0
    • ^20.9.0
    • >=22.0.0
  • NPM v10.6.0
• No longer requires environment variable for legacy support / OpenSSL
  • Fixes: error:0308010C:digital envelope routines::unsupported
  • Ref: fix: add legacy support for npm run dev #2144
  • Ref: how to build keeweb locally together with kdbxweb? #2090
• Numerous bug fixes / changes:
  • fix: convert space character to non-breaking space on password reveal #2151
  • fix: support multiple otpauth url structures #2148
  • fix: addresses not being able to unset a keyfile once added to a vault #2146
  • Fix remove key file #2030
  • Bump electron to 13 #2052
  • Fixed issue with Csv parser parse (#1904) #1944
  • [Fix] handle gdrive shortcuts #2008
  • Favicon download is broken #2108

Notes

• This bundle of changes address 95% of all dependencies, except electron. As of Electron v14, the remote api has been removed and added as its own package. The next major project will be stripping out the old remote references and integrating the new API.
• Do not merge yet until other commits are added

[marclaporte]

Given the quantity and nature of the changes, I wonder if the next release should be 1.2.0 or even 2.0.0 instead of 1.1.9

[Aetherinox]

Given the quantity and nature of the changes, I wonder if the next release should be 1.2.0 or even 2.0.0 instead of 1.1.9

We're going to go with 1.19 for the next revision, as it's mostly bug fixes and getting things up to speed. The list may look like a lot, but it's really just small things that lead to big issues and dependencies.

We're going to be doing a major update to Electron, which is going to change the remote API, which Electron split it up into its own package now.

As well as some major changes to the base itself, as we gear up for react. And those types of changes will be major and can be flagged under a v2 release.

This release is a lot of small things, nothing that is going to dramatically change how the software functions. Plus this upcoming release is me also getting familiar with the base itself. I don't want to start doing those types of major changes and pushing them to the public until I know for a fact that things are going to go smoothly.

Coupled with the fact that we're in the middle of securing API tokens for Microsoft, Google, etc. And @HarlemSquirrel has been invested in working on getting the browser plugins going. So depending on when that gets done, it would be great to have them in by v2.