My SuSE Watcher icon generally shows orange, and I frequently get dialog box that it is unable to connect. This is on SuSE 9.3 both at home and at work. At work, I am behind a firewall, and although my proxy settings are correct, there could be something blocking it. I checked SuSE Firewall settings, but I did not see any settings that might affect SuSE watcher. On both my home system (direct connect via Linksys router) and at work, I am able to do YOU. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
On Saturday 11 June 2005 8:21 am, Jerry Feldman wrote:
My SuSE Watcher icon generally shows orange, and I frequently get dialog box that it is unable to connect. This is on SuSE 9.3 both at home and at work. At work, I am behind a firewall, and although my proxy settings are correct, there could be something blocking it. I checked SuSE Firewall settings, but I did not see any settings that might affect SuSE watcher. On both my home system (direct connect via Linksys router) and at work, I am able to do YOU.
I find its the choice of You update server that is the problem. SuSEwatcher may have problems connecting to the last used sight where YOU won't. If you change to a different YOU download server and at least get the current list of patches then exit and try SuSEwatcher again it usually connects. This just happened to me with the Texas A&M University sight and switching to University of Chicago fixed SuSEwatcher... for now. Stan
Thanks for the answers to my SuSE Watcher question. At home, I certainly will set a different server up. At work, my (and root's) environment variable, http_proxy, is set up as an autoproxy. I've had to set up YOU to use an ftp mirror rather than a http mirror. Since this used to work, it may be that the company made some changes. They've been tightening up on their SPAM and virus exposure. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
I think I solved my work problem. I had been using an automatic proxy which is the preferred proxy, but apparently that does not work with YOU and SuSEWatcher. I switched to a manual proxy. Previously I was unable to obtain the mirror list or use the http mirrors. By using a manual proxy on port 8080, I was able to both use an http proxy as well as get a list of mirrors. I suspect then I reload SuSE Watcher, it will let me know if changing the proxy servers works. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
Am Samstag, 11. Juni 2005 15:21 schrieb Jerry Feldman:
My SuSE Watcher icon generally shows orange, and I frequently get dialog box that it is unable to connect. This is on SuSE 9.3 both at home and at work. At work, I am behind a firewall, and although my proxy settings are correct, there could be something blocking it. I checked SuSE Firewall settings, but I did not see any settings that might affect SuSE watcher. On both my home system (direct connect via Linksys router) and at work, I am able to do YOU. Hi Jerry, Maybe disabling the automatically Update search in the SuSE Watcher window would solve the the Problem or is a workaround. Is the network in a disconnect status, when the Window pops up?
Sorry for my bad english, it's not my native Language. Kind Regards, Rolf-Dieter Damm ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
On Saturday 11 June 2005 10:18 am, Rolf-Dieter Damm wrote:
Am Samstag, 11. Juni 2005 15:21 schrieb Jerry Feldman:
My SuSE Watcher icon generally shows orange, and I frequently get dialog box that it is unable to connect. This is on SuSE 9.3 both at home and at work. At work, I am behind a firewall, and although my proxy settings are correct, there could be something blocking it. I checked SuSE Firewall settings, but I did not see any settings that might affect SuSE watcher. On both my home system (direct connect via Linksys router) and at work, I am able to do YOU.
Hi Jerry, Maybe disabling the automatically Update search in the SuSE Watcher window would solve the the Problem or is a workaround. Is the network in a disconnect status, when the Window pops up?
Sorry for my bad english, it's not my native Language. Thanks. Please don't apologize. I think most of us should have good enough manners to understand that English is not everyone's native language. The last time I was in Germany, I went to a restaurant with some friends who I could communicate with in English for technical stuff, but neither my friends nor anyone at the restaurant spoke English. I had to refresh my German from college and figure out the menu on my own :-). -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
On Saturday 11 June 2005 15:21, Jerry Feldman wrote:
My SuSE Watcher icon generally shows orange, and I frequently get dialog box that it is unable to connect. This is on SuSE 9.3 both at home and at work. At work, I am behind a firewall, and although my proxy settings are correct, there could be something blocking it. I checked SuSE Firewall settings, but I did not see any settings that might affect SuSE watcher. On both my home system (direct connect via Linksys router) and at work, I am able to do YOU.
You need to set the proxy settings locally for your regular user. The full online update runs as root so it uses /root/.curlrc for its proxy settings. The susewatcher process runs as the normal user, so you need a /home/<user>/.curlrc with the proxy settings. Just copy it from /root/
On Saturday 11 June 2005 10:13 am, Anders Johansson wrote:
You need to set the proxy settings locally for your regular user. The full online update runs as root so it uses /root/.curlrc for its proxy settings. The susewatcher process runs as the normal user, so you need a /home/<user>/.curlrc with the proxy settings. Just copy it from /root/
OK, then it's education time for me from Anders! On my system, neither root nor any user has a ~/.curlrc. curl and compat-curl2 are installed. Proxy settings are configured globally via YaST, Network Services. I hadn't logged into KDE as root since updating to 9.3 so I did, ran SuSEwatcher to check for updates then logged out. No .curlrc anywhere. Checked the 9.2 backups and there isn't any .curlrc there either. Am I or my system missing something here? Thanks, Stan
On Saturday 11 June 2005 21:03, Stan Glasoe wrote:
On Saturday 11 June 2005 10:13 am, Anders Johansson wrote:
You need to set the proxy settings locally for your regular user. The full online update runs as root so it uses /root/.curlrc for its proxy settings. The susewatcher process runs as the normal user, so you need a /home/<user>/.curlrc with the proxy settings. Just copy it from /root/
OK, then it's education time for me from Anders!
On my system, neither root nor any user has a ~/.curlrc. curl and compat-curl2 are installed. Proxy settings are configured globally via YaST, Network Services. I hadn't logged into KDE as root since updating to 9.3 so I did, ran SuSEwatcher to check for updates then logged out. No .curlrc anywhere. Checked the 9.2 backups and there isn't any .curlrc there either.
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.
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? 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. Is this a bug or am I not seeing the reason for different ways to get at the same (?) information? Thanks, Stan
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
participants (4)
-
Anders Johansson -
Jerry Feldman -
Rolf-Dieter Damm -
Stan Glasoe