Mailinglist Archive: opensuse (2441 mails)

[Anders Johansson <andjoh@xxxxxxxxxx>]

On Saturday 11 June 2005 22:23, Stan Glasoe wrote:
> On Saturday 11 June 2005 2:21 pm, Anders Johansson wrote:
> >> On Saturday 11 June 2005 21:03, Stan Glasoe wrote:
> > > Am I or my system missing something here?
> >
> > Yes, an authenticating proxy.
> >
> > I should have mentioned that the curlrc is only needed if you need a
> > username and password to log into the proxy. The actual proxy server and
> > port settings are taken from one of the *_proxy environment variables.
>
> Ah. don't have the ol' authenticating proxy set up yet. Another project on
> the list.
>
> So how does that tie into the SuSEwatcher/YOU and how they can't/can work
> with the YOU servers? I'm thinking that the authenticating proxy is on my
> end since the YOU servers aren't requiring any authentication right?

Right.

> So why 
> would I need .curlrc to keep SuSEwatcher and YOU able to talk to the same
> destination? I assumed that SuSEwatcher and YOU used an identical method of
> contacting and querying the servers for info on updates but apparently not.

They do, they both use curl to pull the information from the server. The thing 
is that when you configure the proxy setting in YaST, the username and 
password is set for root only. If you want to be able to use it as a regular 
user, you need to set it for that user.

>
> Is this a bug or am I not seeing the reason for different ways to get at
> the same (?) information?

Not a bug, a security feature. Usernames and passwords shouldn't be put in 
place for all users. If a user is allowed to log into the proxy, she will be 
issued her own username and password

If a company sets up an authenticating proxy, it is usually for a reason. 
Setting the authentication details as public information would negate the 
whole point of the authentication