Le samedi 11 mars 2017 à 01:09 +0100, Wolfgang Wiedmeyer a écrit : > Signed-off-by: Wolfgang Wiedmeyer <wolf...@wiedmeyer.de>
Can we drop this now that we're moving away from CaCert certificates? > --- > about.php | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/about.php b/about.php > index 0cebc13..94d0f86 100644 > --- a/about.php > +++ b/about.php > @@ -52,6 +52,10 @@ > <div class="panel-heading"><h3 class="panel- > title">Why doesn't Replicant guide users through installing complementary > proprietary components?</h3></div> > <div class="panel-body"><p>Replicant is a > free software project and thus does not encourage nor enforce the use of > proprietary software. Providing instructions to install such components is a > way of encouraging the use of proprietary software, which is not an ethical > thing to do.</p></div> > </div> > + <div class="panel panel-default" id="cacert- > certificate-error"> > + <div class="panel-heading"><h3 class="panel- > title">Why do I get a warning message when connecting to the Replicant website > with https?</h3></div> > + <div class="panel-body"><p>Replicant's > website uses a certificate issued by the community-driven certificate > authority <a href="//www.cacert.org/">CAcert</a>;. You get the warning because > CAcert's root certificate is not trusted by your browser. It should however be > possible to add the CAcert root certificate to the certificates your browser > or your operating system trusts. Replicant will use certificates issued by <a > href="https://letsencrypt.org/";>Let's Encrypt</a> as soon as possible which > will solve this issue. Replicant's website is currently hosted by <a > href="https://osuosl.org/";>OSU Open Source Lab</a> and their infrastructure > does not yet support Let's Encrypt.</p></div> > + </div> > </div> > <div class="col-md-3"> > <div class="list-group"> > @@ -65,6 +69,7 @@ > <a href="#replicant-based-omnirom" > class="list-group-item">Why is Replicant based on CyanogenMod instead of > OmniROM?</a> > <a href="#shipping-proprietary-components" > class="list-group-item">Why doesn't Replicant ship with proprietary components > when free replacements are missing?</a> > <a href="#installing-proprietary-components" > class="list-group-item">Why doesn't Replicant guide users through installing > complementary proprietary components?</a> > + <a href="#cacert-certificate-error" > class="list-group-item">Why do I get a warning message when connecting to the > Replicant website with https?</a> > </div> > </div> > </div> -- Paul Kocialkowski, developer of free digital technology and hardware support Website: https://www.paulk.fr/ Coding blog: https://code.paulk.fr/ Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Replicant mailing list Replicant@lists.osuosl.org http://lists.osuosl.org/mailman/listinfo/replicant
