mirror of
https://github.com/Termix-SSH/Termix.git
synced 2026-10-29 14:45:24 +00:00
Luke GustafsonandZacharyZcR
6b708106e1
* fix(sso): send the PKCE verifier for GitHub login (#1534) * fix(remote-desktop): clip cursor overflow without disabling zoom (#1535) * test(remote-desktop): preserve sessions beyond one hour (#1536) * fix(hosts): expose controls for overflowing editor tabs (#1537) * fix(hosts): expose controls for overflowing editor tabs * test(hosts): mock resize observation in admin panel tests * fix(status): skip TCP probes while host sessions are active (#1538) * fix(database): batch session activity persistence (#1539) * docs(api): describe cookie and API key authentication (#1540) * fix(snippets): repair missing note column on SQLite upgrades (#1541) * fix(docker): retain stored SSH credential association (#1543) * fix(file-manager): render transfer toasts without plugin hooks (#1546) * feat(hosts): keep compact row actions inline (#1547) * fix(auth): allow retrying unavailable second-factor interfaces (#1549) * fix(auth): reject unresolved legacy identity provisioning (#1550) * fix(desktop): ship the plugin SDK inside Mac App Store builds (#1551) * fix(tmux): pass full session info to the terminal's session picker (#1552) The tmux.sessions service reduced detected sessions to bare names, but the picker reads session.name, so every entry rendered blank and selecting one sent an empty name, which created a new session instead of attaching. * fix(ssh): read force keyboard-interactive as a boolean when resolving hosts (#1553) The column holds the text "true"/"false", and the resolver passed it through as-is. The string "false" is truthy, so the password provider treated every saved host as forced keyboard-interactive and left the password out. Jump hops are built straight from the resolved host, so a password hop whose server doesn't offer keyboard-interactive failed with "All configured authentication methods failed". * fix(database): batch database saves for bulk host writes (#1554) * fix(database): yield to the event loop between database saves Each SQLite save serializes and encrypts the whole database into new buffers, which V8 only releases once the event loop turns. Boot migrations and bulk host import write plugin settings per host and per key in an awaited loop, so hundreds of full copies piled up and the container ran out of memory. * fix(database): save once per bulk host write instead of once per row On SQLite every repository write force-saves the whole database. Boot plugin data migrations, host defaults materialization and the bulk host routes write one row per host per setting, so they serialized and encrypted the full database hundreds of times in a row. DatabaseSaveTrigger.batched wraps a function so force saves made while it runs collapse into a single save when it finishes. Nested scopes fold into the outer one, and work that outlives its scope saves normally. * feat(hosts): add instance-wide predefined tag suggestions (#1548) * feat(hosts): add shared predefined tag suggestions * style(hosts): format tag catalog routes * test(database): advance fake timers past the save yield (#1555) * fix(i18n): complete Simplified Chinese core and plugin translations (#1542) * fix(i18n): complete Chinese onboarding and navigation labels * fix(i18n): translate remaining Chinese core and plugin interfaces * fix(i18n): translate host editor tab overflow controls * fix(i18n): use consistent Chinese fleet terminology * fix(i18n): localize hardcoded controls and plugin views * fix(i18n): translate built-in homepage widget catalog * test(homepage): follow translated timezone placeholder * fix(i18n): translate plugin-provided homepage widgets * fix(i18n): localize feature settings section titles * fix: 2.8 oidc accounts unable to sign in after upgrading (#1381) * fix: plugins losing the saved ssh login when copying a host (#1391) * fix: fleets, proxmox and automations not getting the host sudo password * fix: host imports running a defaults pass and metrics restart per host (#1384) * fix: high cpu from status probes and full database saves on every sample (#1300) * fix: user data export freezing the server (#1393) * fix: op:// secret references rejected as ssh keys on credentials (#1394) * fix: slow file deletes from the trash lookups on every delete (#1390) * fix: add openapi docs and error handling to host tag routes * test: compare download stream buffers directly so it stops timing out * chore: drop em dash from host row comment * chore: update release notes for 2.9.1 * fix: restore space to add host tags and redesign predefined tags editor * fix: host key silently accepted when the host is missing from the database (#1397) * fix: clearer host login failed status label and fix its translations (#1396) * chore: add host key and status label fixes to release notes * fix: sso and ldap provider dialogs overflowing the screen and using mismatched toggles * chore: increment ver * fix(audit): store plugin entries with no acting user as a null user_id (#1556) Plugin audit entries written outside a request used the literal "system" as user_id. That column references users.id, so the insert was refused (Postgres logs it as an FK violation) and the entry was silently dropped. Write null instead and keep "system" / plugin:<id> in username. * chore: add sso/ldap dialog and audit log fixes to release notes * fix: tunnels and host settings missing from shared hosts on desktop * fix: remote desktop logins missing from shared hosts on desktop * fix: simplify host status to online/offline and keep it live without a refresh * chore: sync Crowdin translations for 2.9.1 --------- Co-authored-by: ZacharyZcR <zacharyzcr1984@gmail.com>
73 lines
2.5 KiB
JSON
73 lines
2.5 KiB
JSON
{
|
|
"editor": {
|
|
"profile": "Vault 簽署者設定檔",
|
|
"selectProfile": "選取 Vault 設定檔...",
|
|
"hint": "設定來自共用設定檔；連線時您將透過 OIDC 登入 Vault。不會儲存任何機密。",
|
|
"docs": "檢視文件",
|
|
"sharedProfile": "{{name}} （共享）"
|
|
},
|
|
"profiles": {
|
|
"new": "新增設定檔",
|
|
"manage": "管理 Vault 設定檔",
|
|
"name": "易記名稱",
|
|
"vaultAddr": "Vault 位址",
|
|
"namespace": "命名空間",
|
|
"oidcMount": "OIDC 驗證掛載",
|
|
"oidcRole": "OIDC 角色",
|
|
"sshMount": "SSH 機密掛載",
|
|
"sshRole": "SSH 簽署者角色",
|
|
"validPrincipals": "有效主體",
|
|
"keyType": "暫時金鑰類型",
|
|
"shareWithAll": "與所有使用者共用",
|
|
"create": "建立設定檔",
|
|
"created": "Vault 設定檔已建立",
|
|
"saved": "Vault 設定檔已儲存",
|
|
"deleted": "Vault 設定檔已刪除",
|
|
"saveFailed": "無法儲存 Vault 設定檔",
|
|
"deleteFailed": "無法刪除 Vault 設定檔",
|
|
"save": "儲存設定檔",
|
|
"validationError": "名稱、Vault 位址和 SSH 簽署者角色為必填",
|
|
"none": "尚無 Vault 設定檔。",
|
|
"sharedBadge": "已共用",
|
|
"edit": "編輯",
|
|
"delete": "刪除"
|
|
},
|
|
"hosts": {
|
|
"filterAuthVault": "保險庫"
|
|
},
|
|
"dialog": {
|
|
"title": "需要 Vault 登入",
|
|
"description": "已開啟視窗以登入 HashiCorp Vault。在該處完成登入；此連線將自動繼續。",
|
|
"failed": "Vault 驗證失敗。請再試一次。",
|
|
"reopen": "重新開啟登入視窗"
|
|
},
|
|
"permissions": {
|
|
"use": {
|
|
"title": "使用 Vault SSH 簽名",
|
|
"description": "建立 Vault 簽署者設定檔並連接到使用 Vault 的主機。"
|
|
},
|
|
"share": {
|
|
"title": "共享庫配置文件",
|
|
"description": "將 Vault 簽署者設定檔標記為共用，以便每個使用者都可以選擇它。"
|
|
}
|
|
},
|
|
"settings": {
|
|
"redirectUri": {
|
|
"label": "重定向 URI",
|
|
"description": "將此 URL 新增至 Termix 登入的每個 Vault OIDC 角色的 allowed_redirect_uris 中。"
|
|
},
|
|
"legacyCallback": {
|
|
"label": "使用舊的重定向 URI",
|
|
"description": "繼續發送 /vault/oidc/callback，這是 2.9 版本之前使用的重定向 URI。一旦您的 Vault 角色允許使用新的重定向 URI，就將其關閉。"
|
|
},
|
|
"host": {
|
|
"profileId": {
|
|
"label": "Vault 簽署者設定檔"
|
|
}
|
|
}
|
|
},
|
|
"plugin": {
|
|
"name": "HashiCorp Vault"
|
|
}
|
|
}
|