From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v3] redirect to TLS WebUI if authorisation required
Date: Wed, 18 Oct 2017 21:15:01 +0100 [thread overview]
Message-ID: <ED627FDC-7BD1-4C6C-9D51-FFAF0D26FA0B@ipfire.org> (raw)
In-Reply-To: <20171018203024.4a759d18.peter.mueller@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]
No I don’t think so.
Just merged it. Thanks.
> On 18 Oct 2017, at 7:30 pm, Peter Müller <peter.mueller(a)link38.eu> wrote:
>
> Hello Michael,
>
>> Hi,
>>
>>> On Tue, 2017-10-17 at 19:49 +0200, Peter Müller wrote:
>>> Do not allow credentials being submitted in plaintext to Apache.
>>> Instead, redirect the user with a 301 to the TLS version of IPFire's
>>> web interface.
>>>
>>> Not sure if this has been merged (and is working) yet... :-)
>>
>> Why do you doubt that this is working?
> This patch does not appear in the public git repository. So I assume something
> was wrong with it.
>
> Best regards,
> Peter Müller
>>
>> -Michael
>>
>>>
>>> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
>>> ---
>>> config/httpd/vhosts.d/ipfire-interface.conf | 24 ++++++++----------------
>>> 1 file changed, 8 insertions(+), 16 deletions(-)
>>>
>>> diff --git a/config/httpd/vhosts.d/ipfire-interface.conf
>>> b/config/httpd/vhosts.d/ipfire-interface.conf
>>> index 27fd25a95..be15cd041 100644
>>> --- a/config/httpd/vhosts.d/ipfire-interface.conf
>>> +++ b/config/httpd/vhosts.d/ipfire-interface.conf
>>> @@ -12,25 +12,17 @@
>>> Require all granted
>>> </Directory>
>>> <DirectoryMatch "/srv/web/ipfire/html/(graphs|sgraph)">
>>> - AuthName "IPFire - Restricted"
>>> - AuthType Basic
>>> - AuthUserFile /var/ipfire/auth/users
>>> - Require user admin
>>> + Options SymLinksIfOwnerMatch
>>> + RewriteEngine on
>>> + RewriteCond %{HTTPS} off
>>> + RewriteRule (.*) https://%{SERVER_NAME}:444/$1 [R=301,L]
>>> </DirectoryMatch>
>>> ScriptAlias /cgi-bin/ /srv/web/ipfire/cgi-bin/
>>> <Directory /srv/web/ipfire/cgi-bin>
>>> - AllowOverride None
>>> - Options None
>>> - AuthName "IPFire - Restricted"
>>> - AuthType Basic
>>> - AuthUserFile /var/ipfire/auth/users
>>> - Require user admin
>>> - <Files chpasswd.cgi>
>>> - Require all granted
>>> - </Files>
>>> - <Files webaccess.cgi>
>>> - Require all granted
>>> - </Files>
>>> + Options SymLinksIfOwnerMatch
>>> + RewriteEngine on
>>> + RewriteCond %{HTTPS} off
>>> + RewriteRule (.*) https://%{SERVER_NAME}:444/$1 [R=301,L]
>>> </Directory>
>>> Alias /updatecache/ /var/updatecache/
>>> <Directory /var/updatecache>
>
prev parent reply other threads:[~2017-10-18 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 17:49 Peter Müller
2017-10-18 14:58 ` Michael Tremer
2017-10-18 18:30 ` Peter Müller
2017-10-18 20:15 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ED627FDC-7BD1-4C6C-9D51-FFAF0D26FA0B@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox