[prev in list] [next in list] [prev in thread] [next in thread] 

List:       privoxy-developers
Subject:    [privoxy-devel] [ ijbswa-Feature Requests-1094348 ] Authentication/Password
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2005-06-02 18:53:30
Message-ID: E1Dduos-0002gb-Jb () sc8-sf-web1 ! sourceforge ! net
[Download RAW message or body]

Feature Requests item #1094348, was opened at 2005-01-01 21:13
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=361118&aid=1094348&group_id=11118

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Configuration
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Authentication/Password

Initial Comment:
Please add the ability to not only permit access by IP (or 
range of IPs via subnet masking), but also by password. 
While most users are implementing Privoxy in a gateway 
context (LAN IPs, therefor very easily masked or DHCP 
rules on routing equipment to assign certain IPs by 
MAC), I (and presumably others) would like to use 
Privoxy in a totally WAN setting. Many people, even on 
higher end connections are forced to use dynamic IPs.

My humble suggestion would be to have 3 levels of 
access:

1) anonymous - no username or password required. This 
would be used in the LAN setting, because you can use 
the permit-access configuration variable to set access 
by IP or range of IPs

2) semi-anonymous - either no username, or assumed 
username of "anonymous" and a password. This way 
people running Privoxy could make their proxy server 
available to whomever simply by giving them the "generic 
user" password and not having to edit the configuration 
for the new IP, or even know it.

3) full login - requires user-specific username and 
password, and assigns rules per user, similar to FTP 
access.

This would permit easily administration by having classes 
of users and rules associated with each class. Please 
give this consideration, as I believe it would be both 
easily implemented (any client software that uses 
proxies already has fields for login information), and 
would go miles towards polishing an already excellent 
program.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2005-06-02 11:53

Message:
Logged In: NO 

Please add the ability to pass user:password to a forwarded proxy. We have an \
authenicated squid proxy at work, and I can't use Privoxy with it, because it won't \
pass through my credentials.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2005-05-23 06:48

Message:
Logged In: NO 

Hopefully this option will be a fact soon! Really like to
see it to, so I have more control about it usage.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2005-02-16 15:29

Message:
Logged In: NO 

I Agree. I Dont like the fact that anyone can view a blocked site anyway....

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=361118&aid=1094348&group_id=11118


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Ijbswa-developers mailing list
Ijbswa-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ijbswa-developers


[prev in list] [next in list] [prev in thread] [next in thread]