Sisyphus repositório
Última atualização: 20 junho 2021 | SRPMs: 17558 | Visitas: 21241887
en ru br
ALT Linux repositórios
S:10.10.5-alt3

Group :: Sistema/Servidores
RPM: pki-core

 Main   Changelog   Spec   Patches   Sources   Download   Gear   Bugs e FR  Repocop 


package id estatus teste mensagem
pki-acme-10.10.5-alt3.x86_64
fail
unsafe-tmp-usage-in-scripts The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/pki/acme/bin/pki-acme-run: $ grep -A5 -B5 /tmp/ /usr/share/pki/acme/bin/pki-acme-run [ -f /var/lib/tomcats/pki/conf/certs/ca_signing.key ] then echo "INFO: Importing CA Signing Certificate and Key" # generate random password openssl rand -hex 8 > /tmp/password... [the rest of the message is skipped]
pki-acme-10.10.5-alt3.x86_64
info
arch-dep-package-consists-of-usr-share The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
pki-base-java-10.10.5-alt3.x86_64
info
arch-dep-package-consists-of-usr-share The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
pki-ca-10.10.5-alt3.x86_64
info
arch-dep-package-consists-of-usr-share The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
pki-javadoc-10.10.5-alt3.x86_64
info
arch-dep-package-consists-of-usr-share The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
pki-kra-10.10.5-alt3.x86_64
info
arch-dep-package-consists-of-usr-share The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
dogtag-pki-server-theme-10.10.5-alt3.x86_64
info
arch-dep-package-consists-of-usr-share The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.
pki-acme-10.10.5-alt3.x86_64
ok
buildroot
pki-acme-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-acme-10.10.5-alt3.x86_64
ok
checkbashisms
pki-base-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-base-10.10.5-alt3.x86_64
ok
buildroot
pki-base-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-base-10.10.5-alt3.x86_64
ok
checkbashisms
pki-base-java-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-base-java-10.10.5-alt3.x86_64
ok
buildroot
pki-base-java-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-base-java-10.10.5-alt3.x86_64
ok
checkbashisms
pki-ca-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-ca-10.10.5-alt3.x86_64
ok
buildroot
pki-ca-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-ca-10.10.5-alt3.x86_64
ok
checkbashisms
pki-console-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-console-10.10.5-alt3.x86_64
ok
buildroot
pki-console-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-console-10.10.5-alt3.x86_64
ok
checkbashisms
pki-core-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-core-10.10.5-alt3.x86_64
ok
buildroot
pki-core-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-core-10.10.5-alt3.x86_64
ok
checkbashisms
pki-healthcheck-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-healthcheck-10.10.5-alt3.x86_64
ok
buildroot
pki-healthcheck-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-healthcheck-10.10.5-alt3.x86_64
ok
checkbashisms
pki-javadoc-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-javadoc-10.10.5-alt3.x86_64
ok
buildroot
pki-javadoc-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-javadoc-10.10.5-alt3.x86_64
ok
checkbashisms
pki-kra-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-kra-10.10.5-alt3.x86_64
ok
buildroot
pki-kra-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-kra-10.10.5-alt3.x86_64
ok
checkbashisms
pki-ocsp-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-ocsp-10.10.5-alt3.x86_64
ok
buildroot
pki-ocsp-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-ocsp-10.10.5-alt3.x86_64
ok
checkbashisms
pki-server-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-server-10.10.5-alt3.x86_64
ok
buildroot
pki-server-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-server-10.10.5-alt3.x86_64
ok
checkbashisms
pki-symkey-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-symkey-10.10.5-alt3.x86_64
ok
buildroot
pki-symkey-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-symkey-10.10.5-alt3.x86_64
ok
checkbashisms
pki-symkey-debuginfo-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-symkey-debuginfo-10.10.5-alt3.x86_64
ok
buildroot
pki-symkey-debuginfo-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-symkey-debuginfo-10.10.5-alt3.x86_64
ok
checkbashisms
pki-tks-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-tks-10.10.5-alt3.x86_64
ok
buildroot
pki-tks-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-tks-10.10.5-alt3.x86_64
ok
checkbashisms
pki-tools-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-tools-10.10.5-alt3.x86_64
ok
buildroot
pki-tools-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-tools-10.10.5-alt3.x86_64
ok
checkbashisms
pki-tools-debuginfo-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-tools-debuginfo-10.10.5-alt3.x86_64
ok
buildroot
pki-tools-debuginfo-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-tools-debuginfo-10.10.5-alt3.x86_64
ok
checkbashisms
pki-tps-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-tps-10.10.5-alt3.x86_64
ok
buildroot
pki-tps-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-tps-10.10.5-alt3.x86_64
ok
checkbashisms
pki-tps-debuginfo-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
pki-tps-debuginfo-10.10.5-alt3.x86_64
ok
buildroot
pki-tps-debuginfo-10.10.5-alt3.x86_64
ok
sisyphus_check
pki-tps-debuginfo-10.10.5-alt3.x86_64
ok
checkbashisms
python3-module-pki-base-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
python3-module-pki-base-10.10.5-alt3.x86_64
ok
buildroot
python3-module-pki-base-10.10.5-alt3.x86_64
ok
sisyphus_check
python3-module-pki-base-10.10.5-alt3.x86_64
ok
checkbashisms
dogtag-pki-server-theme-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
dogtag-pki-server-theme-10.10.5-alt3.x86_64
ok
buildroot
dogtag-pki-server-theme-10.10.5-alt3.x86_64
ok
sisyphus_check
dogtag-pki-server-theme-10.10.5-alt3.x86_64
ok
checkbashisms
dogtag-pki-console-theme-10.10.5-alt3.x86_64
ok
unsafe-tmp-usage-in-scripts
dogtag-pki-console-theme-10.10.5-alt3.x86_64
ok
buildroot
dogtag-pki-console-theme-10.10.5-alt3.x86_64
ok
sisyphus_check
dogtag-pki-console-theme-10.10.5-alt3.x86_64
ok
checkbashisms
 
projeto & código: Vladimir Lettiev aka crux © 2004-2005, Andrew Avramenko aka liks © 2007-2008
mantenedor atual: Michael Shigorin
mantenedor da tradução: Fernando Martini aka fmartini © 2009