Vydané zdroje
Stáhnout zdroje ZIP
CH-J Server Manager
Procházejte adresáře a soubory konkrétního vydání aplikace.
Zdroje jsou zveřejněny pod CH-J Proprietary Software License 1.14. Jejich dostupnost nemění licenční podmínky ani neposkytuje další oprávnění.
1
{\rtf1\ansi\deff0{\fonttbl{\f0 Arial;}}\uc1\f0\fs202
CH-J Server Manager \u8212? Before installation / P\u345?ed instalac\u237? / Vor der Installation\par3
\par4
The following guidance is informational, non-binding and separate from the Software License. The agreement control applies only to the license in the final section.\par5
N\u225?sleduj\u237?c\u237? pokyny jsou informativn\u237?, nez\u225?vazn\u233? a odd\u283?len\u233? od licence. Souhlas se vztahuje pouze na licenci v z\u225?v\u283?re\u269?n\u233? \u269?\u225?sti.\par6
Die folgenden Hinweise sind informativ, unverbindlich und von der Lizenz getrennt. Die Zustimmung gilt nur f\u252?r die Lizenz im letzten Abschnitt.\par7
\par8
# CH-J Server Manager \u8212? Pokyny k provozn\u237? bezpe\u269?nosti a z\u225?lohov\u225?n\u237?\par9
\par10
**Informativn\u237? a nez\u225?vazn\u225? doporu\u269?en\u237? (nejsou sou\u269?\u225?st\u237? softwarov\u233? licence)** \par11
**11. \u345?\u237?jna 2026**\par12
\par13
Tento dokument uv\u225?d\u237? pouze praktick\u233? p\u345?\u237?klady. Nen\u237? sou\u269?\u225?st\u237? CH-J Proprietary Software License, neukl\u225?d\u225? samostatn\u233? smluvn\u237? povinnosti a neslibuje bezchybn\u253? provoz ani obnovu dat. Provozovatel\u233? by m\u283?li p\u345?izp\u367?sobit ochrann\u225? opat\u345?en\u237? dot\u269?en\u253?m syst\u233?m\u367?m, platn\u253?m pr\u225?vn\u237?m p\u345?edpis\u367?m, sv\u253?m opr\u225?vn\u283?n\u237?m a p\u345?edv\u237?dateln\u253?m rizik\u367?m. Souvisej\u237?c\u237? ustanoven\u237? jsou v odd\u237?lech 3.5 a 7.2 p\u345?\u237?slu\u353?n\u233? softwarov\u233? licence. \u268?ten\u237? ani dodr\u382?ov\u225?n\u237? t\u283?chto p\u345?\u237?klad\u367? nen\u237? samostatnou smluvn\u237? podm\u237?nkou.\par14
\par15
## 1. Chra\u328?te data na p\u345?ipojen\u253?ch syst\u233?mech\par16
\par17
- Ur\u269?ete d\u367?le\u382?it\u233? soubory na serveru, datab\u225?ze, stav aplikac\u237?, \u250?daje o p\u345?\u237?stupov\u253?ch opr\u225?vn\u283?n\u237?ch a syst\u233?mov\u233? konfigurace, kter\u233? m\u367?\u382?e operace ovlivnit.\par18
- Uchov\u225?vejte z\u225?lohy dostate\u269?n\u283? nez\u225?visle na \u382?iv\u233?m syst\u233?mu, aby chybn\u253? p\u345?\u237?kaz, ransomware, porucha hardwaru nebo n\u225?hodn\u233? smaz\u225?n\u237? s men\u353?\u237? pravd\u283?podobnost\u237? zni\u269?ily origin\u225?ly i z\u225?lohy z\u225?rove\u328?. Podle okolnost\u237? lze pou\u382?\u237?t odd\u283?len\u233? \u250?lo\u382?i\u353?t\u283? a p\u345?\u237?stupov\u225? opr\u225?vn\u283?n\u237? nebo nem\u283?nn\u233? \u269?i offline kopie.\par19
- P\u345?izp\u367?sobte \u269?etnost a dobu uchov\u225?v\u225?n\u237? z\u225?loh p\u345?ijateln\u233? ztr\u225?t\u283? dat a po\u382?adovan\u233? dob\u283? obnovy.\par20
- Pravideln\u283? ov\u283?\u345?ujte, \u382?e z\u225?lohy existuj\u237?, jsou \u269?iteln\u233? a lze je obnovit. Kopie, kterou nelze obnovit, poskytuje jen malou ochranu.\par21
- RAID, zrcadlen\u237? disk\u367?, snapshoty nebo vysok\u225? dostupnost mohou b\u253?t u\u382?ite\u269?n\u233?, ale nemus\u237? nahradit nez\u225?visl\u233? a obnoviteln\u233? z\u225?lohy.\par22
- P\u345?i spr\u225?v\u283? syst\u233?m\u367? z\u225?kazn\u237?ka nebo zam\u283?stnavatele postup koordinujte s opr\u225?vn\u283?n\u253?m spr\u225?vcem z\u225?loh. Nekop\u237?rujte chr\u225?n\u283?n\u225? z\u225?kaznick\u225? data na osobn\u237? \u250?lo\u382?i\u353?t\u283? a nep\u345?istupujte k nim bez opr\u225?vn\u283?n\u237?.\par23
\par24
## 2. P\u345?ed rizikov\u253?mi operacemi testujte\par25
\par26
Softwarov\u225? licence v odd\u237?lu 3.5 vysv\u283?tluje stav vyd\u225?n\u237? a souvisej\u237?c\u237? upozorn\u283?n\u237?. Tyto pokyny nep\u345?id\u225?vaj\u237? \u382?\u225?dn\u233? samostatn\u233? omezen\u237? ani pr\u225?vn\u237? podm\u237?nku.\par27
\par28
- Pokud je to mo\u382?n\u233?, na testovac\u237?m nebo neproduk\u269?n\u237?m serveru vyzkou\u353?ejte funkce aplikace, na kter\u233? se chcete spol\u233?hat, zejm\u233?na z\u225?pis soubor\u367?, hromadn\u233? operace, SSH p\u345?\u237?kazy, zm\u283?ny opr\u225?vn\u283?n\u237? a automatizovan\u233? \u250?lohy.\par29
- Testujte s necitliv\u253?mi nebo postradateln\u253?mi daty, ov\u283?\u345?te vybran\u233? c\u237?lov\u233? syst\u233?my a identity a podle dostupnosti zva\u382?te zku\u353?ebn\u237? b\u283?h bez proveden\u237? zm\u283?n.\par30
- P\u345?\u237?slu\u353?n\u233? funkce znovu otestujte po podstatn\u253?ch aktualizac\u237?ch aplikace, zm\u283?n\u225?ch opr\u225?vn\u283?n\u237? na serveru, konfigurace nebo automatizace.\par31
- Pokud vhodn\u233? testovac\u237? prost\u345?ed\u237? nem\u225?te, zva\u382?te operaci v men\u353?\u237?m rozsahu, dodate\u269?n\u233? potvrzen\u237?, kontrolu z\u225?loh a jasn\u253? pl\u225?n n\u225?vratu do p\u367?vodn\u237?ho stavu.\par32
- Vyhn\u283?te se zbyte\u269?n\u233?mu pou\u382?\u237?v\u225?n\u237? privilegovan\u253?ch relac\u237?; opr\u225?vn\u283?n\u237? p\u345?ihla\u353?ovac\u237?ch \u250?daj\u367? omezte na skute\u269?n\u283? pot\u345?ebn\u233? \u269?innosti.\par33
\par34
## 3. V\u253?po\u269?ty hash\u367? a kontroly integrity\par35
\par36
- Lok\u225?ln\u237? hashe a porovn\u225?n\u237? kontroln\u237?ch sou\u269?t\u367? mohou pomoci odhalit n\u225?hodn\u233? i \u250?mysln\u233? zm\u283?ny. V\u253?sledek je v\u353?ak vypov\u237?daj\u237?c\u237? pouze p\u345?i porovn\u225?n\u237? s o\u269?ek\u225?vanou hodnotou z\u237?skanou z d\u367?v\u283?ryhodn\u233?ho zdroje.\par37
- Pro bezpe\u269?nostn\u283? v\u253?znamn\u233? kontroly integrity up\u345?ednost\u328?ujte modern\u237? kryptografick\u233? hashovac\u237? algoritmy, nap\u345?\u237?klad SHA-256 nebo SHA-512. MD5, SHA-1 a nekryptografick\u233? kontroln\u237? sou\u269?ty nejsou vhodn\u253?m d\u367?kazem bezpe\u269?nosti proti \u250?mysln\u253?m zm\u283?n\u225?m.\par38
- Lok\u225?ln\u237? hashovac\u237? n\u225?stroj s\u225?m nez\u225?lohuje data ani nedokazuje, \u382?e vzd\u225?len\u253? server nebyl napaden.\par39
\par40
## 4. Prost\u345?ed\u237? s vy\u353?\u353?\u237?m rizikem\par41
\par42
CH-J Server Manager je ur\u269?en k b\u283?\u382?n\u233? spr\u225?v\u283? syst\u233?m\u367?, nikoli k pln\u283?n\u237? bezpe\u269?nostn\u283? kritick\u233? ochrann\u233?, \u345?\u237?dic\u237? nebo nouzov\u233? funkce. P\u345?ipojen\u237? k organizaci provozuj\u237?c\u237? kritick\u233? syst\u233?my samo o sob\u283? neznamen\u225?, \u382?e b\u283?\u382?n\u225? spr\u225?va IT je bezpe\u269?nostn\u283? kritick\u253?m pou\u382?it\u237?m. Zjist\u283?te, zda konkr\u233?tn\u237? spravovan\u253? syst\u233?m nebo proces m\u367?\u382?e p\u345?\u237?mo ovlivnit \u382?ivot \u269?i zdrav\u237?, a \u345?i\u271?te se p\u345?\u237?slu\u353?n\u253?mi postupy organizace ve spolupr\u225?ci s kvalifikovan\u253?mi pracovn\u237?ky pro bezpe\u269?nost.\par43
\par44
## 5. Po incidentu\par45
\par46
Uchovejte relevantn\u237? logy bez odhalen\u237? p\u345?ihla\u353?ovac\u237?ch \u250?daj\u367?, pokud je to bezpe\u269?n\u233? zastavte destruktivn\u237? \u250?lohy, informujte opr\u225?vn\u283?n\u233?ho provozovatele a postupujte podle pl\u225?nu vlastn\u237?ka syst\u233?mu pro \u345?e\u353?en\u237? incident\u367? a obnovu. Nep\u345?edpokl\u225?dejte, \u382?e automatick\u233? opakov\u225?n\u237? operace je bezpe\u269?n\u233?.\par47
\par48
---\par49
\par50
Tyto pokyny jsou vzd\u283?l\u225?vac\u237?, dobrovoln\u233? a nez\u225?vazn\u233?. Nem\u283?n\u237? softwarovou licenci, neukl\u225?daj\u237? dal\u353?\u237? pr\u225?vn\u237? povinnosti a neomezuj\u237? z\u225?konn\u225? pr\u225?va.\par51
\par52
\par53
---\par54
\par55
# CH-J Server Manager \u8211? Hinweise zum sicheren Betrieb und zur Datensicherung\par56
\par57
**Unverbindliche Informationen (kein Bestandteil der Softwarelizenz)** \par58
**11. Oktober 2026 \u183? Unverbindliche Hinweise zur jeweils anwendbaren einheitlichen Lizenz**\par59
\par60
Dieses Dokument enth\u228?lt ausschlie\u223?lich praktische Empfehlungen. Es wird nicht Bestandteil der CH-J Server Manager Proprietary Software License und begr\u252?ndet keine zus\u228?tzlichen vertraglichen Pflichten. Es ist weder eine Zusicherung fehlerfreien Betriebs noch eine Garantie f\u252?r eine erfolgreiche Wiederherstellung. Angemessene Vorsichtsma\u223?nahmen richten sich nach den betroffenen Systemen, den Berechtigungen und dem vorhersehbaren Risiko. Ma\u223?geblich bleiben die Lizenz und das anwendbare Recht.\par61
\par62
## 1. Daten auf verbundenen Systemen sch\u252?tzen\par63
\par64
- Wichtige Dateien, Datenbanken, Zugangsdaten und Konfigurationen identifizieren, die durch eine geplante Aktion betroffen sein k\u246?nnten.\par65
- Sicherungskopien m\u246?glichst unabh\u228?ngig vom Produktivsystem aufbewahren, sodass Fehlbedienungen, Schadsoftware oder Hardwareausf\u228?lle nicht gleichzeitig Originale und Sicherungen zerst\u246?ren. Je nach Risiko kommen getrennte Speichersysteme, eingeschr\u228?nkte Zugriffsrechte oder unver\u228?nderbare beziehungsweise offline verwahrte Kopien in Betracht.\par66
- H\u228?ufigkeit und Aufbewahrungsdauer der Sicherungen anhand der gew\u252?nschten Wiederherstellungsziele planen.\par67
- Vorhandensein, Lesbarkeit und Wiederherstellbarkeit der Sicherungen regelm\u228?\u223?ig pr\u252?fen.\par68
- RAID, Spiegelung, Snapshots und Hochverf\u252?gbarkeit k\u246?nnen hilfreich sein, ersetzen aber nicht in jedem Fall unabh\u228?ngige und wiederherstellbare Sicherungen.\par69
- Bei fremden oder arbeitgeberseitigen Systemen die zust\u228?ndige und berechtigte Person einbeziehen; keine Kundendaten ohne entsprechende Berechtigung kopieren.\par70
\par71
## 2. Vor risikoreichen Aktionen testen\par72
\par73
Ma\u223?geblich f\u252?r den Reifestatus und die Warnhinweise ist Abschnitt 3.5 der jeweils anwendbaren Softwarelizenz. Diese Hinweise erg\u228?nzen die Lizenz nicht um Nutzungsverbote oder weitere rechtliche Bedingungen.\par74
- In einer geeigneten Testumgebung nur die tats\u228?chlich vorgesehenen Funktionen erproben, besonders Datei\u228?nderungen, L\u246?schungen, SSH-Befehle, Rechte\u228?nderungen und automatisierte Aktionen.\par75
- Nach wesentlichen Programmaktualisierungen oder \u196?nderungen der Serverumgebung relevante Tests erneut erw\u228?gen.\par76
- Ist eine getrennte Testumgebung nicht praktikabel, begrenzte Testl\u228?ufe, Kontrolle von Sicherungen und einen Wiederherstellungsplan in Betracht ziehen, sofern die Lizenz die beabsichtigte Nutzung erlaubt.\par77
- Zugriffsrechte nach M\u246?glichkeit auf die erforderlichen Operationen beschr\u228?nken.\par78
\par79
## 3. Hashes und Integrit\u228?tspr\u252?fungen\par80
\par81
- Lokale Hashwerte und Pr\u252?fsummen k\u246?nnen \u196?nderungen erkennbar machen. F\u252?r eine belastbare Pr\u252?fung muss der erwartete Vergleichswert aus einer vertrauensw\u252?rdigen Quelle stammen.\par82
- F\u252?r sicherheitsrelevante Pr\u252?fungen moderne kryptografische Hashverfahren wie SHA-256 oder SHA-512 bevorzugen. MD5, SHA-1 und nichtkryptografische Pr\u252?fsummen sind kein geeigneter Nachweis gegen gezielte Manipulation.\par83
- Das lokale Hash-Werkzeug erstellt keine Datensicherung und beweist nicht, dass ein entfernter Server unver\u228?ndert oder sicher ist.\par84
\par85
## 4. Systeme mit erh\u246?htem Risiko\par86
\par87
CH-J Server Manager dient der allgemeinen Systemverwaltung, nicht als sicherheitskritische Schutz-, Steuerungs- oder Notfallkomponente. Allein die Verwaltung gew\u246?hnlicher IT-Systeme einer Klinik oder Industrieanlage ist deshalb nicht generell untersagt. Entscheidend sind die konkret betroffenen Systeme und m\u246?gliche unmittelbare Folgen f\u252?r Leben und Gesundheit. Organisationsinterne Schutzverfahren und qualifiziertes Fachpersonal k\u246?nnen einzubeziehen sein.\par88
\par89
## 5. Nach einem Vorfall\par90
\par91
Relevante Protokolle ohne Offenlegung von Zugangsdaten sichern, laufende sch\u228?dliche Aufgaben nach M\u246?glichkeit stoppen, die zust\u228?ndigen Personen informieren und die vorgeschriebenen Wiederherstellungsabl\u228?ufe befolgen. Automatische Wiederholungen sind nicht stets ungef\u228?hrlich.\par92
\par93
---\par94
\par95
Diese Hinweise sind freiwillig, informativ und unverbindlich. Sie \u228?ndern weder die Lizenz noch zwingende gesetzliche Rechte.\par96
\par97
\par98
---\par99
\par100
# CH-J Server Manager \u8212? Operational Safety and Backup Guidance\par101
\par102
**Informational and non-binding guidance (not part of the Software License)** \par103
**October 11, 2026**\par104
\par105
This document gives practical examples only. It is not incorporated into the CH-J Server Manager Proprietary Software License, does not impose separate contractual obligations and does not promise error-free operation or recovery. Operators should adapt safeguards to the affected systems, applicable laws, their permissions and the foreseeable risk. The relevant provisions are Sections 3.5 and 7.2 of the applicable CH-J Server Manager Proprietary Software License. Reading or following these examples is not a separate contractual requirement.\par106
\par107
## 1. Protect data on connected systems\par108
\par109
- Identify important server files, databases, application state, access-control data, and system configurations that could be affected by an operation.\par110
- Keep backup copies sufficiently independent from the live system so that an erroneous command, ransomware, hardware failure or accidental deletion is less likely to destroy the originals and the backups together. Options include separate storage and access controls, immutable or offline copies when appropriate.\par111
- Make sure the backup frequency and retention are appropriate for acceptable recovery-point and recovery-time objectives.\par112
- Periodically confirm that backups exist, are readable and can be restored. A copy that cannot be restored provides little protection.\par113
- RAID, mirrored disks, snapshots or high availability may be useful, but do not always replace independent, recoverable backups.\par114
- When managing a client's or employer's systems, coordinate with the authorised backup owner. Do not copy restricted customer data to personal storage or access data without permission.\par115
\par116
## 2. Test before risky operations\par117
\par118
The Software License (Section 3.5) explains the release-stage status and warnings. This guidance adds no separate restriction or legal condition.\par119
\par120
- On a staging or non-production server when feasible, exercise only the application functions you plan to rely on, especially file writes, bulk operations, SSH commands, permission changes and automated jobs.\par121
- Test with non-sensitive or disposable data, confirm the selected target systems and identities and consider a dry run where available.\par122
- Test relevant functions again after material application updates, changed server permissions, configuration changes or changes to automation.\par123
- If no suitable staging environment exists, consider a reduced-scope operation, additional confirmation, backup checks and a clear rollback plan.\par124
- Avoid unnecessary privileged sessions; limit credentials to the actions actually needed.\par125
\par126
## 3. Hashing and integrity checks\par127
\par128
- Local hashes and checksum comparisons can help detect accidental or deliberate changes, but the result is meaningful only when compared with an expected value obtained from a trustworthy source.\par129
- For security-sensitive integrity checks, prefer modern cryptographic hash algorithms such as SHA-256 or SHA-512. MD5, SHA-1 and non-cryptographic checksums are not appropriate proofs of security against deliberate modification.\par130
- The local hash tool does not itself back up data or prove that a remote server is uncompromised.\par131
\par132
## 4. Higher-risk environments\par133
\par134
CH-J Server Manager is for general system administration, not for performing a safety-critical protection, control or emergency function. A connection to an organisation that operates critical systems does not by itself make ordinary IT administration a safety-critical use. Determine whether the specific system or process you manage can directly impact life or health, and consult the organisation's required procedures and qualified safety personnel.\par135
\par136
## 5. After an incident\par137
\par138
Preserve relevant logs without exposing credentials, stop destructive tasks if safe, notify the authorised operator, and follow the system owner's incident-response and restore process. Do not assume that an automated retry is safe.\par139
\par140
---\par141
\par142
This guidance is educational, optional and non-binding. It does not change the Software License, impose additional legal duties or limit statutory rights.\par143
\par144
\par145
---\par146
\par147
APPLICATION LICENSE \u8212? AGREEMENT APPLIES ONLY TO THIS SECTION\par148
\par149
CH-J Proprietary Software License\par150
\par151
Version 1.14 \u8212? Unified Cross-Platform License\par152
License text date: October 11, 2026\par153
\par154
Licensor: Josef Chud\u253?, using the project name CH-J.\par155
\par156
All rights held by the Licensor in the Software are reserved except as expressly granted below or provided by law. Copyright, license and attribution notices belonging to third parties remain applicable.\par157
\par158
1. Scope\par159
\par160
This License grants permissions concerning the Software defined in Section 2 only to the extent that the Licensor holds the necessary rights. It applies only to releases and items expressly distributed by the Licensor under this License, Version 1.14. Each such release must identify this License by its name and version in its accompanying release materials and provide its full text. A reference to CH-J Server Manager, inclusion in a repository or a similarity to another release does not by itself make this License applicable to an otherwise unmarked item. For an unmarked item, applicable rights must be established from its own express licensing information and applicable law; no permission is implied merely from the absence of a license notice.\par161
\par162
This License is offered with an expressly identified release. A user accepts its contractual terms by expressly agreeing to them after having a reasonable opportunity to review the complete License, for example by selecting an acceptance control before installation or first use. Where legally effective, knowingly downloading, building, installing or using the Software after a reasonable opportunity to review these terms also constitutes acceptance. Permissions take effect upon legally effective acceptance or as otherwise provided by applicable law. Nothing in this paragraph removes rights available independently under applicable law or other applicable licenses.\par163
\par164
The same License governs copies distributed directly by the Licensor and copies made available with the Licensor's authorisation through application marketplaces, including the Microsoft Store, the Apple App Store and the Mac App Store. Where a marketplace imposes mandatory conditions for acquisition or use of its distributed copies, those conditions also apply to that channel, without altering the terms for copies obtained elsewhere or overriding mandatory statutory rights. The Licensor authorises each marketplace chosen by the Licensor to distribute the corresponding official editions under the Licensor's separate distribution arrangements; this is not a public permission to redistribute the Software. Specific Apple requirements are incorporated into the relevant provisions of this single License.\par165
\par166
Third-Party Materials retain their separate licenses. Inclusion in the same package, executable or repository does not replace those licenses or withdraw rights already granted under them. Section 6 addresses separate licenses and permissions and the rights granted by hosting platforms.\par167
\par168
2. Definitions\par169
\par170
Software means the CH-J Server Manager application, including its source code, executable forms, documentation and first-party components, to the extent expressly distributed by the Licensor under this License and within the Licensor's authority to license. Third-Party Materials are not brought under this License merely by being included in or distributed with the application.\par171
\par172
Third-Party Materials means code, libraries, assets, documentation and other material supplied under a separate license, including any third-party code that remains subject to its original license. Applicable license texts and notices identify such material; an omitted or incorrect notice does not extinguish the rights of its right holder.\par173
\par174
Apple Store Copy means a copy of the Software officially made available by the Licensor through Apple's App Store, including iOS or iPadOS editions, or through the Mac App Store. Microsoft Store Copy means a copy officially made available by the Licensor through the Microsoft Store. These descriptions identify a distribution channel; they do not create separate software licenses.\par175
\par176
Pre-release Build means an official release designated by the Licensor as Alpha, Beta or Release Candidate, or an official release under this License whose release stage is not expressly designated. Stable Release means an official release expressly designated as Stable in its accompanying release information. A distribution channel, package format or version number alone does not establish release status. These stage labels describe release maturity; they do not create separate license permissions or restrictions.\par177
\par178
Commercial Use means use in connection with a business, trade, self-employed professional activity, internal administration of a for-profit enterprise, or the provision of paid services to others. It includes use by employees and contractors for those purposes, whether on personal or business-owned equipment and whether at home or at work.\par179
\par180
Non-Commercial Use means use outside those purposes, including personal projects, hobbies, non-commercial learning and research, public administration, and the non-business activities of non-profit organisations. Use supporting a commercial activity is Commercial Use even if that activity does not yet make a profit.\par181
\par182
3. Permitted Use and Restrictions\par183
\par184
3.1. Application use. Subject to this License and its effective application under Section 1, the Licensor permits you, on a non-exclusive worldwide basis, to download, install and run official releases for your personal use or your organisation's operations, including the administration of third-party servers for customers. Important release-stage warnings are provided in Section 3.5.\par185
\par186
Both Commercial Use and Non-Commercial Use of any release distributed under this License are permitted without license fees indefinitely. There is no required payment for use of the Software. The same permission applies to Pre-release Builds and Stable Releases, subject to the other provisions of this License.\par187
\par188
You may make copies reasonably necessary for installation, execution, internal deployment and backup. An organisation may allow its authorised employees and contractors to use those copies for its operations under this License, subject to any applicable restrictions attached to the acquisition channel.\par189
\par190
For an Apple Store Copy, the permission granted under this License is non-exclusive and non-transferable, and its scope is limited to using the Software on Apple-branded products you own or control, as permitted by the Usage Rules in the applicable Apple Media Services Terms and Conditions or the applicable Mac App Store terms. Other accounts associated with a purchaser may access or use the Software through Family Sharing, volume purchasing or Legacy Contacts where the applicable Apple rules permit that access or use. This License does not authorise activity that conflicts with those applicable Usage Rules. Statutory transfer and other mandatory rights preserved by Section 9 remain unaffected.\par191
\par192
For a Microsoft Store Copy, the acquisition and use of that copy also remain subject to applicable Microsoft Store acquisition and usage rules. The permission for Commercial Use in this License expresses the Licensor's authorisation; the Microsoft Store's separate mandatory rules, if applicable, are not waived by this License. Neither store-specific rule changes the permissions granted for copies lawfully obtained through other authorised channels.\par193
\par194
3.2. Source inspection and building from source. If the Licensor expressly makes the Software's source code available, you may read it to understand or evaluate the Software. You may also obtain and compile unmodified first-party source code from an official release expressly distributed under this License, using the supplied build instructions, solely to make executable copies for the uses and internal deployment permitted by Section 3.1.\par195
\par196
You may adjust build settings, local paths, environment variables, dependency versions and generated build files as reasonably needed for compilation, but this permission does not authorise changing the Software's first-party source code or maintaining an independently modified development version. The compiled copies remain subject to this License as to the Licensor's material, and any bundled Third-Party Materials remain subject to their own licenses. Public or external redistribution of source code or self-built executable copies is not permitted under this paragraph.\par197
\par198
Merely making source code visible does not grant any broader right to reuse, modify, redistribute or incorporate copyright-protected portions into another project, except as independently permitted under Sections 6 and 9.\par199
\par200
3.3. Reserved activities. Except for the permissions above, the exceptions in Sections 6 and 9, or the Licensor's separate express written permission, you may not:\par201
\par202
- extract, reproduce or incorporate copyright-protected portions of the Software's code into another project, application or service;\par203
- modify, adapt or translate the Software, or create derivative versions;\par204
- create, maintain or publish an independent development fork, whether public or private;\par205
- redistribute, sell, sublicense, publish, mirror or make available copies of the Software or its source code outside the internal deployment permitted in Section 3.1;\par206
- remove or misrepresent copyright, license or origin notices contained in the Software.\par207
\par208
A development fork means a separate copy or development line of the Software maintained independently of the official project. Permitted backups, internal deployments and exercises of rights independently granted under Section 6.3 are not, by themselves, prohibited development forks under this License. An authorised marketplace's distribution of official releases, or access to a store copy through permitted Family Sharing, volume licensing or comparable marketplace mechanisms, is not prohibited redistribution by an end user.\par209
\par210
3.4. Independent work and normal configuration. These restrictions do not prevent normal configuration through the Software's intended interfaces, writing your own scripts or plugins using those interfaces, or creating and using your own server configurations and data. This does not authorise copying copyright-protected code into those scripts or plugins.\par211
\par212
The Licensor claims no ownership of your independently created work. This License does not claim exclusive rights over unprotected ideas, algorithms or functionality, or prohibit independent development that does not infringe the Licensor's rights.\par213
\par214
3.5. Intended purpose, authorised access, release status and safety-critical use. The Software is intended for general system administration, SSH and SFTP operations, file management, monitoring, server and network diagnostics, and related operations on systems that the user owns or is lawfully authorised to administer. It also includes local file-hash calculation, checksum verification, comparison and integrity checking, where those functions are included in the relevant edition. These functions do not, by themselves, guarantee authenticity, security or freedom from tampering. This License does not grant access rights to any remote system, account or data. You may use the Software only within your actual authorisation and in compliance with applicable law. Deliberately accessing, modifying or interfering with systems or data without authorisation is not permitted by this License.\par215
\par216
A Pre-release Build is an unfinished release intended primarily for evaluation and testing. It may have incomplete functions or safeguards, compatibility changes, and defects that could interrupt services or damage data. Production use is strongly discouraged; evaluation in a controlled environment with non-critical data is recommended. This warning describes release maturity and risk; it does not prohibit production use or narrow the permissions granted in Section 3.1. An official release under this License without an express stage designation is treated as a Pre-release Build for these notices.\par217
\par218
A Stable Release is designated for general use, including consideration for production deployment after the user's own reasonable assessment. The Licensor uses the Stable designation following a release-readiness review addressing known material security weaknesses, the integrity and authenticity of software updates and packages, and relevant platform distribution requirements. An identified risk may be addressed by remediation or by documented, tested mitigating controls appropriate to the intended release; no particular security implementation is mandated by this description. A Stable designation is not a warranty, security certification, promise that all vulnerabilities have been discovered, or guarantee of uninterrupted or error-free operation. Release-stage descriptions do not modify the liability rules in Sections 7 and 9 or restrict mandatory rights.\par219
\par220
The Software is not intended or licensed to serve as a safety-critical control, protection or emergency-response component where failure or incorrect operation could directly endanger life or health. The Licensor makes no representation that the Software meets safety-certification requirements for such a role. Merely administering ordinary, non-safety-critical IT systems belonging to a hospital, industrial site or another organisation is not prohibited solely because of the organisation's activities. This paragraph does not exclude any liability or mandatory rights preserved under Sections 7.3 and 9.\par221
\par222
4. Free Use and Support for Development\par223
\par224
Commercial Use and Non-Commercial Use are permitted without license fees indefinitely. No payment is required to obtain or exercise the permissions granted by this License.\par225
\par226
Development of CH-J Server Manager may be supported through the Official Website identified in Section 11. The website may describe available ways to support the project. Such support is entirely optional; it is not a condition of downloading, installing, using or updating the Software and does not, by itself, purchase additional license rights, warranties, maintenance, priority treatment or technical support.\par227
\par228
This License creates no payment obligation, suggested amount per installation, recurring contribution, installation-counting requirement or obligation to report usage. No license keys, activation, installation registration, installation reports or telemetry are required for license compliance.\par229
\par230
5. Ownership, Names and Branding\par231
\par232
Copyright and other intellectual-property rights remain with their respective owners. This License grants permissions; it does not transfer ownership.\par233
\par234
Use of the project name to identify the Software and acknowledge its origin is permitted. This License does not authorise misleading claims of authorship, endorsement or official status, or use of the Licensor's branding as the branding of a separate product.\par235
\par236
This License is concluded between the end user and the Licensor. For an Apple Store Copy, both parties acknowledge that Apple Inc. ("Apple") is not a party to this License and that the Licensor, not Apple, is solely responsible for the Software and its content. Apple and its subsidiaries are third-party beneficiaries of this License as it relates to Apple Store Copies. Upon the end user's acceptance, Apple has the right, and is deemed to have accepted the right, to enforce the applicable terms of this License against the end user as a third-party beneficiary. This does not transfer copyright or other ownership to Apple. Distribution through the Microsoft Store likewise does not transfer copyright or ownership to Microsoft; Microsoft is not made a third-party beneficiary by this License.\par237
\par238
6. Third-Party Materials, Separate Permissions and Hosting Platforms\par239
\par240
6.1. Third-party licenses and other authors' rights. Third-Party Materials retain their own terms. Required license texts and notices must be preserved. Copyright in third-party code remains with its respective right holders; publication of this License does not constitute their consent to replace their licenses.\par241
\par242
The Licensor may include, modify or redistribute such material only to the extent permitted by its existing license, a separate authorisation or applicable law. This License does not restrict permissions independently available under those licenses.\par243
\par244
Where an existing license permits additional or different terms for the Licensor's modifications or for a derivative work as a whole, those terms may apply within the scope of that permission. They do not cancel the existing license's conditions or the rights already granted in pre-existing material.\par245
\par246
6.2. Previously granted permissions, if any. This License does not revoke rights validly granted to a recipient by the Licensor or another right holder under different terms for specific material. Such rights remain governed by the terms under which they were actually granted. No prior public release or grant of rights under another license is presumed by this provision.\par247
\par248
6.3. Hosting-platform permissions. If the Licensor publishes the Software on a platform under terms granting users rights to view or make platform-hosted forks, this License does not withdraw those separately granted rights. For example, publication in a public GitHub repository is subject to GitHub's applicable public-repository terms.\par249
\par250
This exception extends only as far as the separately granted platform rights. It does not itself grant additional permission to extract code for another product or distribute modified application releases. No platform permission is created by this License merely because an unauthorised third party uploads the Software there.\par251
\par252
6.4. Third-party services and agreements. When using the Software, you must comply with the third-party terms that apply to services you actually access, including relevant terms of your network or mobile provider, hosting provider, remote systems, cloud providers and any applicable software marketplace. The permissions granted by this License do not themselves grant rights to those third-party services or materials.\par253
\par254
7. Warranties, Support and Limitation of Liability\par255
\par256
7.1. Released condition and support. The Software is supplied in its released condition. Unless expressly agreed, the Licensor gives no separate contractual guarantee that it will be uninterrupted, error-free, free of vulnerabilities or suitable for a particular purpose. No specific service level, support response time, update schedule or maintenance period is promised by this License.\par257
\par258
Statutory rights concerning defects, agreed characteristics and any mandatory update obligations remain unaffected. For an Apple Store Copy, the Licensor alone, and not Apple, is responsible for providing any maintenance and support that the Licensor expressly undertakes or that applicable law requires. The parties acknowledge that Apple has no obligation whatsoever to furnish maintenance or support services for an Apple Store Copy.\par259
\par260
7.2. Operational risk and reasonable precautions. Subject to Sections 7.3 and 7.4, the user assesses whether and how to deploy the Software on the systems they are authorised to administer. The Software can execute commands, alter configurations, change permissions and modify or delete data. Its use therefore calls for precautions proportionate to the affected systems and reasonably foreseeable risks.\par261
\par262
7.2.1. Backups and recovery of connected systems. Before using functions that may put important data or configurations at risk, the user is responsible for arranging or reasonably confirming suitable backup and recovery measures for the affected connected servers and other target systems, to the extent reasonably practicable and within the user's authority and control. If another authorised operator controls those systems, reasonable coordination or confirmation may suffice; this License does not require unauthorised access to, or copying of, third-party data. Simply connecting with the Software does not mean the Software has created or verified a backup.\par263
\par264
7.2.2. Testing before operational reliance. A Pre-release Build should be evaluated in a controlled environment using non-critical or disposable data wherever reasonably practicable. Before relying on the Software, including a Stable Release, on live or production systems, the user is responsible for reasonably assessing the suitability and behaviour of the functions intended for that use, proportionate to foreseeable risks. Relevant checks should be reconsidered after material changes to the Software or operating environment. This does not require testing unrelated functionality or discovering defects that reasonable checks could not reveal. The risk warning for Pre-release Builds in Section 3.5 remains advisory and is not a separate condition of the license grant.\par265
\par266
7.2.3. Legal significance of precautions. The precautions in Sections 7.2.1 and 7.2.2 describe steps taken in the user's own interest to avoid or mitigate loss (Obliegenheiten), not separate contractual duties owed to the Licensor. Omitting them does not by itself create a claim for damages payable to the Licensor or grounds for terminating this License under Section 8. Any failure to take reasonable precautions may be considered as contributory fault (Mitverschulden) only where and to the extent that the law applicable to the claim permits it and the omission contributed to the occurrence or extent of the damage, including under section 254 BGB where German law governs.\par267
\par268
The Licensor is not responsible for losses caused solely by a user's incorrect instructions, selection of a wrong target or acts of other persons for which the Licensor is not legally responsible. Nothing in Section 7.2 automatically excludes liability for defects in the Software, removes any duty separately undertaken by the Licensor, shifts the statutory burden of proof, or restricts the non-excludable rights and liabilities addressed in Sections 7.3 and 9.\par269
\par270
Practical examples concerning backups, recovery checks, test environments and risk reduction are described in the separate Operational Safety and Backup Guidance, which may accompany official releases and may be published on the Official Website (Section 11). The guidance is informational and non-binding. Neither publication nor reference to it incorporates it into this License, makes its examples enforceable contractual duties or alters statutory rights.\par271
\par272
7.3. Liability that is not limited. Nothing in this License excludes or limits liability that arises under applicable law for:\par273
\par274
- intentional misconduct or gross negligence;\par275
- culpably caused injury to life, body or health;\par276
- fraudulent concealment of a defect;\par277
- breach of an expressly assumed guarantee, to the extent of that guarantee;\par278
- mandatory product liability or any other liability that cannot lawfully be excluded or limited.\par279
\par280
This applies to relevant conduct of the Licensor and of persons for whose conduct the Licensor is legally responsible.\par281
\par282
7.4. Gratuitous provision and ordinary negligence. Permission to use the Software under this License is granted without a license fee. Supporting the development of the project through its website is not required under this License.\par283
\par284
Subject to Section 7.3, the Licensor's liability for ordinary negligence is excluded except for the breach of an essential contractual obligation. In the event of such a breach, liability for ordinary negligence is limited to damage that was foreseeable when the contractual relationship was formed and is typical of that relationship.\par285
\par286
An essential contractual obligation is an obligation necessary to achieve the fundamental purpose of the contractual relationship and on whose performance the user may ordinarily rely. Any more favourable statutory limitation of liability applicable to gratuitous provision remains unaffected.\par287
\par288
7.5. Data loss and business interruption. Claims concerning data loss, damaged configurations, server downtime, lost profits or other operational losses are subject to the same rules in Sections 7.3 and 7.4. These categories are not subject to a separate blanket exclusion.\par289
\par290
7.6. Scope of protection. These rules concern the liability of Josef Chud\u253? as Licensor. They do not themselves create personal liability for the Licensor's representatives, employees or agents. Any separate personal liability of such persons, and any limitations applicable to it, are determined by the law governing the relevant claim.\par291
\par292
Mandatory consumer rights and non-excludable remedies for defects remain unaffected.\par293
\par294
7.7. Marketplace warranties, product claims and intellectual-property claims. For an Apple Store Copy, the Licensor, not Apple, is solely responsible for any product warranties, whether express or implied by law, to the extent not effectively disclaimed under Sections 7 and 9 and applicable law. If an Apple Store Copy fails to conform to an applicable warranty, you may notify Apple, and Apple will refund any purchase price paid for that application. For an application obtained for no purchase price, this refund is ordinarily zero. To the maximum extent permitted by applicable law, Apple has no other warranty obligation relating to the Apple Store Copy, and any other claims, losses, liabilities, damages, costs or expenses attributable to failure to conform to a warranty are the Licensor's responsibility rather than Apple's, subject to Sections 7.3 and 7.4 and applicable law.\par295
\par296
The parties acknowledge that the Licensor, not Apple, is responsible for addressing claims by an end user or third party relating to an Apple Store Copy or its possession or use, including product-liability claims; allegations of non-compliance with legal or regulatory requirements; and claims under consumer-protection, privacy or similar law. If a third party alleges that an Apple Store Copy or its possession or use infringes that party's intellectual-property rights, the Licensor, not Apple, is solely responsible for investigating, defending, settling and discharging that claim. This provision allocates responsibility as between Apple and the Licensor. It does not expand contractual disclaimers beyond what applicable law permits or waive a user's mandatory remedies.\par297
\par298
For a Microsoft Store Copy, the Licensor remains responsible for its own Software, warranties and claims according to Sections 7 and 9 and applicable law. Nothing in this License purports to disclaim any independent obligations that Microsoft itself has under applicable law or its own applicable marketplace terms.\par299
\par300
8. Duration and Breach\par301
\par302
Permissions for a version distributed under this License continue indefinitely while its conditions are met. Publishing different terms for a later version does not change the terms for a version already received.\par303
\par304
If a material breach remains uncorrected for 30 days after you receive an individual notice from the Licensor in text form under Section 11, the Licensor may terminate the permissions affected by that breach, subject to applicable law. The notice must identify the breach, the permissions affected and what is reasonably required to remedy it.\par305
\par306
The notice period does not authorise otherwise prohibited copying, distribution or reuse. It does not prevent the Licensor from seeking remedies otherwise available for infringement, subject to the requirements of applicable law.\par307
\par308
9. Mandatory Rights and Interpretation\par309
\par310
Nothing in this License limits rights that cannot lawfully be restricted by agreement. This includes applicable consumer rights and statutory permissions for necessary backup copies, observing or testing program operation, decompilation for interoperability under the legally prescribed conditions, and any other mandatory exceptions for computer programs.\par311
\par312
The restrictions in Section 3 apply only where the Licensor has a legal right to impose them. Mandatory rights concerning transfer or resale of lawfully acquired copies remain unaffected.\par313
\par314
You must observe applicable export-control, sanctions and other trade laws when using the Software. For an Apple Store Copy, you additionally represent and warrant that (a) you are not located in any country or territory subject to a United States Government embargo or designated by the United States Government as supporting terrorism, and (b) you are not listed on any United States Government list of prohibited or restricted parties. Obligations that cannot be lawfully imposed, and mandatory statutory protections, remain unaffected.\par315
\par316
If a provision is unenforceable, applicable law determines its effect and the effect on the remainder of the License.\par317
\par318
10. Governing Law and Jurisdiction\par319
\par320
10.1. Governing law. This License and the contractual relationship arising from it are governed by the law of the Federal Republic of Germany.\par321
\par322
If you are a consumer, this choice of law does not deprive you of the protection of provisions that cannot be derogated from by agreement under the law that would apply without this choice. In particular, the mandatory protection of the law of your country of habitual residence remains applicable where the conditions of Article 6 of Regulation (EC) No 593/2008 (Rome I) are met. Overriding mandatory provisions of applicable law remain unaffected.\par323
\par324
10.2. Jurisdiction. The courts having jurisdiction are determined by the applicable statutory rules. This License does not establish an exclusive place of jurisdiction.\par325
\par326
Mandatory rules protecting consumers in court proceedings remain unaffected, including Articles 18 and 19 of Regulation (EU) No 1215/2012 (Brussels I bis) where applicable. The choice of German law does not, by itself, require a consumer to bring proceedings in Germany.\par327
\par328
11. License Contact, Official Website and Notices\par329
\par330
Licensor / developer legal name: Josef Chud\u253? (project name: CH-J)\par331
Contact Email: support@sm.ch-j.de\par332
Official Website: https://www.sm.ch-j.de/\par333
\par334
The Contact Email may be used for enquiries, complaints, claims concerning the Software, notices to the Licensor and requests for permission. The email address's name does not create a voluntary support or response-time commitment. No website account or Software registration is required.\par335
\par336
Additional legally required developer contact details may be made available through the applicable official marketplace listing and other notices required by law. This statement does not replace any requirement of a marketplace or applicable law to include specific contact details directly in a license agreement.\par337
\par338
Notices under Section 8 must be delivered individually in readable text that the recipient can retain, for example by email, to an address at which the recipient can lawfully be contacted. A general website announcement alone is not such a notice. The 30-day remedy period begins on receipt, not merely on sending or publication.\par339
\par340
This Section does not replace mandatory requirements for the form, receipt or service of legal notices or restrict other legally available methods of service.\par341
\par342
---\par343
\par344
End of License.\par345
}SHA-256: e1fc4a9b190368e23fc466fcd9efbfe18cbd93b2b409e0aeef1c2d9bd42a1748
SHA-256 archivu: 5ac91caf4fa32a6fdb114f2430deed486fbe7489d5eea343d1f034169fafb5e0