SUSE has an in-house translations created by contracted translators in past. The work flow did not allow to merge translations between openSUSE and SLE trees up to now. It caused translation divergence. SLE Merge Robot is an output of the merge effort, and “suggests” to use SLE translation. Please review carefully, and keep standard terminology used in your language.
Initial import of yast was created from the community translations, but strings actually missing in the community translation were taken from the contracted SUSE Linux Enterprise translations. These translations are mixed in Weblate. If you are interested in the SUSE Linux Enterprise translations import review, go to <ftp://ftp.suse.com/pub/people/sbrabec/yast-translations-sle-contributions/>
The translation was automatically locked due to following alerts: Could not merge the repository.
Other components
| Component | Translated | Untranslated | Untranslated words | Untranslated characters | Checks | Suggestions | Comments | |
|---|---|---|---|---|---|---|---|---|
Glossary
yast-security
GPL-2.0
|
0 | 0 | 0 | 0 | 0 | 0 | ||
|
|
||||||||
Overview
| Project website | github.com/yast/yast-security |
|---|---|
| Project maintainers |
 ancorgonzalezsosa
 LubosKocman
|
| Translation process |
|
| Translation license | GNU General Public License v2.0 only |
| Source code repository |
git@github.com:yast/yast-translations.git
|
| Repository branch | master |
| Last remote commit |
New POT for text domain 'hana-ha'.
7869d671a6
YaST Jenkins authored 2 weeks ago |
| Last commit in Weblate |
Translated using Weblate (Indonesian)
27c35fddb9
 arifbudiman authored a month ago |
| Weblate repository |
https://l10n.opensuse.org/git/yast-base/master/
|
| Filemask | po/security/*.po |
| Translation file |
Download
po/security/sv.po
|
| Last change | April 12, 2023, 9:55 a.m. |
| Last author | Luna Jernberg |
String statistics
| Strings percent | Hosted strings | Words percent | Hosted words | Characters percent | Hosted characters | |
|---|---|---|---|---|---|---|
| Total | 215 | 2,724 | 18,210 | |||
| Translated | 100% | 215 | 100% | 2,724 | 100% | 18,210 |
| Needs editing | 0% | 0 | 0% | 0 | 0% | 0 |
| Failing checks | 1% | 4 | 3% | 91 | 3% | 547 |
| Strings with suggestions | 1% | 1 | 1% | 3 | 1% | 28 |
| Not translated strings | 0% | 0 | 0% | 0 | 0% | 0 |
 LunaJernbergc15bd25a134943af
New translation |
|
|
LunaJernbergc15bd25a134943af
Translation changed |
|
|
LunaJernbergc15bd25a134943af
New translation |
|
|
LunaJernbergc15bd25a134943af
New translation |
|
|
LunaJernbergc15bd25a134943af
Translation changed |
|
|
LunaJernbergc15bd25a134943af
New translation |
|
|
LunaJernbergc15bd25a134943af
New translation |
|
|
LunaJernbergc15bd25a134943af
Translation changed |
|
|
LunaJernbergc15bd25a134943af
New translation |
|
|
LunaJernbergc15bd25a134943af
New translation |
|
| 215 | File in original format as translated in the repository | gettext PO file | |||||||
|---|---|---|---|---|---|---|---|---|---|
| 215 | All strings, converted files enriched with comments; suitable for offline translation | CSV | gettext MO | gettext PO | TBX | TMX | XLIFF 1.1 with gettext extensions | XLIFF 1.1 | XLSX |
<p>This section allows to configure the installed system to conform with the guidelines of a given security policy like the Security Technical Implementation Guide (STIG) of the Defense Information Systems Agency (DISA).</p>
<p>Enabling a policy allows to configure the new system to execute a full security scan using the OpenSCAP tools in the first boot. By default, that will generate a report at <tt>/var/log/ssg-apply/</tt> listing the rules that would need some kind of remediation. The system can also be configured to automatically apply remediations right after the initial scan. Note that may lead to a system that is secure to the point of being unusable for some use cases. It is also possible to completely skip the automatic scan.</p>
<p>Enabling a security policy will also cause the installer to check some rules that can hardly be remediated after installation. For each failing rule the installer will display several well-known identifiers and a link to the functionality of the installer that can be used to manually remediate the issue before installing.<p>
<p>Det här avsnittet gör det möjligt att konfigurera det installerade systemet så att det överensstämmer med riktlinjerna för en given säkerhetspolicy, som Säkerhets teknisk implementeringsguide (STIG) från Defens Informationssystems byrån (DISA).</p>
<p>Att aktivera en policy gör det möjligt att konfigurera det nya systemet för att utföra en fullständig säkerhetsgenomsökning med OpenSCAP-verktygen vid den första uppstarten. Som standard genererar det en rapport till <tt>/var/log/ssg-apply/</tt> som listar reglerna som skulle behöva någon form av åtgärd. Systemet kan också konfigureras för att automatiskt tillämpa korrigeringar direkt efter den första skanningen. Observera att det kan leda till ett system som är säkert till den grad att det är oanvändbart för vissa användningsfall. Det är också möjligt att helt hoppa över den automatiska skanningen.</p>
<p>Att aktivera en säkerhetspolicy kommer också att få installationsprogrammet att kontrollera vissa regler som knappast kan åtgärdas efter installationen. För varje felaktig regel kommer installationsprogrammet att visa flera välkända identifierare och en länk till installationsprogrammets funktionalitet som kan användas för att manuellt åtgärda problemet innan installation.<p>