Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English CC-BY-SA-3.0 0 0 0 0 0 0 0
Chinese (Simplified Han script) CC-BY-SA-3.0 0% 18 628 4,352 18 0 0 0
Finnish CC-BY-SA-3.0 5% 17 583 4,019 17 1 0 0
French CC-BY-SA-3.0 0% 18 628 4,352 18 0 0 0
Japanese CC-BY-SA-3.0 0% 18 628 4,352 18 0 0 0
Portuguese (Brazil) CC-BY-SA-3.0 0% 18 628 4,352 18 0 1 0
Spanish CC-BY-SA-3.0 0% 18 628 4,352 18 0 0 0
Please sign in to see the alerts.

Overview

Project website pagure.io/fedora-docs-l10n/packaging-guidelines
Instructions for translators

Mailing list for translators: <trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/packaging-guidelines.git
Repository branch master
Last remote commit automatic update of pot/po files a233f9785
♪ I'm a bot, bot, bot ♪ authored 6 days ago
Last commit in Weblate Translated using Weblate (Spanish) 76319285b
User avatar vareli authored 4 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Pkcs11Support.po
3 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 126 4,396 30,464
Source 18 628 4,352
Translated 15% 19 15% 673 15% 4,685
Needs editing 0% 0 0% 0 0% 0
Read-only 14% 18 14% 628 14% 4,352
Failing checks 1% 1 1% 45 1% 333
Strings with suggestions 1% 1 1% 45 1% 333
Untranslated strings 84% 107 84% 3,723 84% 25,779
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 20 changes 0 changes 0 changes 3 changes 0 changes 6 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

4,396
Hosted words
126
Hosted strings
15%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+15%
—
Contributors
—
User avatar None

Resource updated
File “po/es/master/pages/Pkcs11Support.po” was added. 11 months ago
User avatar None

String updated in the repository
This form is already accepted by some programs such as the OpenConnect VPN client. The certificate used in the above examples can be simply used as a client authentication certificate by adding the command-line option `-c 'pkcs11:manufacturer=piv_II;id=%01'`.
 
11 months ago
User avatar None

String updated in the repository
In particular when PKCS#11 objects are specified in a textual form which is visible to the user ''(e.g. on the command line or in a config file)'', objects SHOULD be specified in the form of a PKCS#11 URI as as described in https://tools.ietf.org/html/rfc7512[RFC7512].
 
11 months ago
User avatar None

String updated in the repository
https://tools.ietf.org/html/rfc7512[RFC7512] defines a 'PKCS#11 URI' as a standard way to identify tokens and objects. Fedora follows this standard and applications which refer to objects stored in smart cards or HSMs, must use RFC7512 to refer to certificates and private keys.
 
11 months ago
User avatar None

String updated in the repository
How to specify an object stored in a smart card/HSM
 
11 months ago
User avatar None

String updated in the repository
https://tools.ietf.org/html/rfc7512[RFC7512] defines a 'PKCS#11 URI' as a standard way to identify tokens and objects. Fedora follows this standard and applications which refer to tokens such as smart cards or HSMs, must use RFC7512 to refer to them. Note that an application must not require the '''module-name''' and '''module-path''' URI elements. Compliant with this policy applications should resolve URIs which do not contain these elements based [[#Registered|on the registered provider modules]]. Applications must not require the "slot" attribute, nor print it, since it is an esoteric PKCS#11 module implementation information that has no meaning for the end-user, and in several modules its value is not guaranteed to be unique (and may change for example after system reboot).
 
11 months ago
User avatar None

String updated in the repository
How to specify a specific smart card/HSM
 
11 months ago
User avatar None

String updated in the repository
Packages which can potentially use PKCS#11 tokens SHOULD automatically use the tokens which are present in the system's p11-kit configuration, rather than needing to have a PKCS#11 provider explicitly specified. That can be done by applications using the p11-kit library to get the list of modules, or by applications defaulting to the p11-kit proxy module (`+%{_libdir}/p11-kit-proxy.so+`), if no PKCS#11 provider module was specified by the user. The proxy module, is a single module wrapping all available registered modules.
 
11 months ago
User avatar None

String updated in the repository
How applications take advantage of registered provider modules
 
11 months ago
User avatar None

String updated in the repository
The packages SHOULD NOT provide the package config `*.pc` files for the PKCS#11 modules, since the applications are not supposed to link directly against these libraries. The PKCS#11 module shared object SHOULD NOT be in the -devel subpackage either.
 
11 months ago
Browse all component changes