mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
21 lines
1.6 KiB
Plaintext
21 lines
1.6 KiB
Plaintext
---
|
|
title: "Enhancing Security and Usability: Project Upgrades"
|
|
---
|
|
|
|
At KMS, we're constantly striving to elevate the security and usability standards of our platform to better serve our users.
|
|
With this commitment in mind, we're excited to introduce our latest addition, non-E2EE projects, aimed at addressing two significant issues while enhancing how clients interact with KMS programmatically.
|
|
|
|
Previously, users encountered a challenge where projects risked becoming inaccessible if the project creator deleted their account.
|
|
Additionally, our API lacked the capability to interact with projects without dealing with complex cryptographic operations.
|
|
These obstacles made API driven automation and collaboration a painful experience for a majority of our users.
|
|
|
|
To overcome these limitations, our upgrade focuses on disabling end-to-end encryption (E2EE) for projects.
|
|
While this may raise eyebrows, it's important to understand that this decision is a strategic move to make KMS easier to use and interact with.
|
|
|
|
But what does this mean for our users? Essentially nothing, there are no changes required on your end.
|
|
Rest assured, all sensitive data remains encrypted at rest according to the latest industry standards.
|
|
Our commitment to security remains unwavering, and this upgrade is a testament to our dedication to delivering on our promises in both security and usability when it comes to secrets management.
|
|
|
|
To increase consistency with existing and future integrations, all projects created on KMS from now on will have end-to-end encryption (E2EE) disabled by default.
|
|
This will not only reduce confusion for end users, but will also make the KMS API seamless to use.
|