mirror of
https://github.com/Termix-SSH/Termix.git
synced 2026-10-29 22:55: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>
52 lines
2.5 KiB
JSON
52 lines
2.5 KiB
JSON
{
|
|
"hosts": {
|
|
"filterAuthStepca": "Paso CA"
|
|
},
|
|
"editor": {
|
|
"label": "Paso CA",
|
|
"description": "Inicie sesión a través de su proveedor de identidad y permita que Step CA emita un certificado SSH de corta duración para este host. La URL de la CA, la huella digital raíz y el proveedor OIDC los configura un administrador en la sección Step CA de la configuración de administración.",
|
|
"docs": "Ver documentación"
|
|
},
|
|
"dialog": {
|
|
"title": "Se requiere autenticación de CA.",
|
|
"description": "Para continuar, complete la autenticación en su navegador. El certificado seguirá siendo válido mientras su autoridad de certificación lo permita.",
|
|
"openBrowser": "Abrir navegador para autenticarse",
|
|
"waiting": "Esperando autenticación en el navegador...",
|
|
"authenticating": "Procesando autenticación..."
|
|
},
|
|
"errors": {
|
|
"authFailed": "La autenticación falló. Revisa tus credenciales e inténtalo de nuevo.",
|
|
"timeout": "La autenticación expiró. Inténtalo de nuevo."
|
|
},
|
|
"settings": {
|
|
"caUrl": {
|
|
"label": "URL de CA",
|
|
"description": "La URL HTTPS de su CA de Smallstep. Deje la URL de la CA, la huella digital y el aprovisionador vacíos para desactivar Step CA.",
|
|
"placeholder": "https://ca.internal:9000"
|
|
},
|
|
"fingerprint": {
|
|
"label": "Huella digital de la raíz (SHA-256)",
|
|
"description": "La huella digital del certificado raíz, como se muestra en el paso ca bootstrap."
|
|
},
|
|
"provisioner": {
|
|
"label": "nombre del proveedor OIDC",
|
|
"description": "Nombre del proveedor OIDC de la CA. A continuación, seleccione \"Step CA\" como tipo de autenticación del host."
|
|
},
|
|
"privateEndpoints": {
|
|
"label": "Hosts de CA de paso privado permitidos",
|
|
"description": "Los hosts privados con los que puede contactar el flujo de certificados de Step CA son: la propia CA y, si es interna, su proveedor de identidad. Sepárelos con comas o saltos de línea."
|
|
},
|
|
"redirectUri": {
|
|
"label": "URI de redirección",
|
|
"description": "Registre esta URL como una URI de redireccionamiento permitida con el proveedor de identidad que se encuentra detrás del aprovisionador OIDC."
|
|
},
|
|
"legacyCallback": {
|
|
"label": "Utilice la URI de redireccionamiento antigua",
|
|
"description": "Sigue enviando /host/step-ca-callback, la URI de redireccionamiento que se usaba antes de la versión 2.9. Desactívala una vez que tu proveedor de identidad permita la nueva."
|
|
}
|
|
},
|
|
"plugin": {
|
|
"name": "Step CA"
|
|
}
|
|
}
|