diff options
| author | galaxico <galatoulas@cti.gr> | 2021-10-10 03:44:13 +0300 |
|---|---|---|
| committer | galaxico <galatoulas@cti.gr> | 2021-10-10 03:44:13 +0300 |
| commit | 0db8b7c97fc38b865693f1314b82457c0fd1f767 (patch) | |
| tree | 5abad664d953238ebf71d577253ae0c173625a54 /greek/security | |
| parent | 1c8cb8603bb43df72c04f9feac4a0178bd67796f (diff) | |
updated Greek intro/index.wml
Diffstat (limited to 'greek/security')
| -rw-r--r-- | greek/security/faq.wml | 15 |
1 files changed, 10 insertions, 5 deletions
diff --git a/greek/security/faq.wml b/greek/security/faq.wml index e504858df6a..907f6fe6664 100644 --- a/greek/security/faq.wml +++ b/greek/security/faq.wml @@ -1,12 +1,12 @@ #use wml::debian::template title="Debian security FAQ" #include "$(ENGLISHDIR)/security/faq.inc" -#use wml::debian::translation-check translation="84ede1208c98808ea39a461f115525dd3a87a989" maintainer="galaxico" +#use wml::debian::translation-check translation="6e1fa2e1aabb151dc8ce2445ee60cc40675fb927" maintainer="galaxico" <maketoc> <toc-add-entry name=buthow>I received a DSA via debian-security-announce, how can I upgrade the vulnerable packages?</toc-add-entry> -<p>A: As the DSA mail says, you should upgrade the packages affected by the +<p>A: As the DSA mail says, you should upgrade the packages affected by the announced vulnerability. You can do this by just upgrading (after updating the list of available packages with <tt>apt-get update</tt>) every package in your system with <tt>apt-get upgrade</tt> or by @@ -80,7 +80,7 @@ so things will not change or break unexpectedly as a result of a security fix. You can check if you are running a secure version of a package by looking at the package changelog, or comparing its - exact version number with the version indicated in the Debian + exact version number with the version indicated in the Debian Security Advisory.</p> <toc-add-entry name=archismissing>I received an advisory, but the build for one @@ -102,7 +102,7 @@ inactive, support for stable will always have priority. If you want to have a secure (and stable) server you are strongly encouraged to stay with stable.</p> - + <toc-add-entry name=testing>How is security handled for <tt>testing</tt>?</toc-add-entry> <p>A: Security for testing benefits from the security efforts of the entire project for unstable. However, there is a minimum two-day migration delay, @@ -159,7 +159,7 @@ <toc-add-entry name=contact>How can I reach the security team?</toc-add-entry> -<p>A: Security information can be sent to security@debian.org or +<p>A: Security information can be sent to security@debian.org or team@security.debian.org, both of which are read by the members of the security team. </p> @@ -365,6 +365,11 @@ href="https://github.com/RedHatProductSecurity/CVE-HOWTO">\ CVE OpenSource Request HOWTO</a>.</p> +<toc-add-entry name=disclosure-policy>Does Debian have a vulnerability disclosure policy?</toc-add-entry> +<p>A: Debian has published a <a href="disclosure-policy">vulnerability + disclosure policy</a> as part of its participation in the CVE + program. + <h1>Deprecated Debian security FAQ</h1> <toc-add-entry name=localremote>What does <q>local (remote)</q> mean?</toc-add-entry> |