Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. inn.eyrie.org now supports TLS (and uses it for Trac)
      (Russ Allbery)


----------------------------------------------------------------------

Message: 1
Date: Thu, 21 Nov 2013 19:21:22 -0800
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: inn.eyrie.org now supports TLS (and uses it for Trac)
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

It's increasingly best practice to make web site contents available via
TLS, and particularly important for anything that involves a password.
When I did the first quick-and-dirty setup of inn.eyrie.org's Trac
installation, I never bothered, but it started bugging me the other day.

This is now fixed: inn.eyrie.org content is available via either TLS or
without TLS, except for Trac which is now forced to TLS.

Note that inn.eyrie.org uses a CAcert.org certificate, so it may or may
not be trusted by your browser.  It's trusted by Debian, but you may see
an unrecognized certificate authority warning on other platforms.

Please let me know if you run into any problems or if I broke anything.

-- 
Russ Allbery ([email protected])              <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.


------------------------------

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers

End of inn-workers Digest, Vol 57, Issue 2
******************************************

Reply via email to