mirror of
https://github.com/Termix-SSH/Termix.git
synced 2026-10-30 07:05: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": "스텝 CA"
|
|
},
|
|
"editor": {
|
|
"label": "스텝 CA",
|
|
"description": "ID 공급자를 통해 로그인하고 Step CA에서 이 호스트에 대한 단기 SSH 인증서를 발급받으세요. CA URL, 루트 지문 및 OIDC 프로비저너는 관리자가 관리 설정의 Step CA 섹션에서 설정합니다.",
|
|
"docs": "문서 보기"
|
|
},
|
|
"dialog": {
|
|
"title": "단계 CA 인증 필요",
|
|
"description": "계속하려면 브라우저에서 인증을 완료하십시오. 인증서는 CA(인증 기관)에서 허용하는 기간 동안 유효합니다.",
|
|
"openBrowser": "브라우저로 인증하기",
|
|
"waiting": "브라우저에서 인증 대기 중...",
|
|
"authenticating": "인증 처리 중..."
|
|
},
|
|
"errors": {
|
|
"authFailed": "인증에 실패했습니다. 자격 증명을 확인하고 다시 시도하세요.",
|
|
"timeout": "인증 시간이 초과되었습니다. 다시 시도하세요."
|
|
},
|
|
"settings": {
|
|
"caUrl": {
|
|
"label": "CA URL",
|
|
"description": "SmallStep CA의 HTTPS URL을 입력하십시오. Step CA를 비활성화하려면 CA URL, 지문 및 프로비저너 필드를 비워 두십시오.",
|
|
"placeholder": "https://ca.internal:9000"
|
|
},
|
|
"fingerprint": {
|
|
"label": "루트 지문(SHA-256)",
|
|
"description": "루트 인증서 지문은 CA 부트스트랩 단계에서 확인할 수 있습니다."
|
|
},
|
|
"provisioner": {
|
|
"label": "OIDC 프로비저너 이름",
|
|
"description": "CA의 OIDC 프로비저너 이름을 입력합니다. 그런 다음 호스트의 인증 유형으로 \"단계별 CA\"를 선택합니다."
|
|
},
|
|
"privateEndpoints": {
|
|
"label": "허용된 개인 Step CA 호스트",
|
|
"description": "Step CA 인증서 흐름이 접촉할 수 있는 개인 호스트는 CA 자체와 (내부 호스트인 경우) ID 공급자입니다. 쉼표 또는 줄 바꿈으로 구분하십시오."
|
|
},
|
|
"redirectUri": {
|
|
"label": "리디렉션 URI",
|
|
"description": "이 URL을 OIDC 프로비저너 뒤에 있는 ID 공급자에게 허용된 리디렉션 URI로 등록하십시오."
|
|
},
|
|
"legacyCallback": {
|
|
"label": "이전 리디렉션 URI를 사용하세요",
|
|
"description": "2.9 이전 버전에서 사용했던 리디렉션 URI인 /host/step-ca-callback을 계속 전송하세요. ID 공급자가 새 URI를 허용하면 이 기능을 비활성화하십시오."
|
|
}
|
|
},
|
|
"plugin": {
|
|
"name": "Step CA"
|
|
}
|
|
}
|