From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] *Simple* guide to implementing digest-auth combined with IP based whitelist?
Date: Tue, 03 Apr 2012 15:06:58 -0400 [thread overview]
Message-ID: <4F7B4A52.30105@libertytrek.org> (raw)
I've never had a need to protect a site like this so am totally new to it...
I've been reading, and everything says that digest-auth is preferred to
basic-http-auth (yes, I know that this isn't a very sophisticated level
of protection, but it is all we need for this site), but is there also a
way to whitelist certain static IP address so people on those don't get
prompted for a username/password?
Thanks for any pointers to tfm...
next reply other threads:[~2012-04-03 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 19:06 Tanstaafl [this message]
2012-04-03 20:25 ` [gentoo-user] *Simple* guide to implementing digest-auth combined with IP based whitelist? Michael Orlitzky
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=4F7B4A52.30105@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=gentoo-user@lists.gentoo.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