How to tell rpm to use proxy authentication for accessing the Internet
 

Hello,

I'm new here, hope that I'm posting this question in right category. I'm working at Bank as the Banking Application Administrator. Basically we have M$ Windows Server machines connected in domain (yes, I know how you like it ;) ) but we also have couple of linux based hosts. So one of them is SUSE Linux Enterprise Server 10 (32-bit), on which is installed Claroline (learning platform) and now I have to upgrade its version.

The problem is, that this machine is not connected to the internet, because according to our internal policy, all our PCs should access internet through the MS TMG proxy server.

So, my question is, how it's possible to upgrade some packages on my linux machine using internet connection, hence through the TMG proxy (which needs domain user authentication). I've already tried to upgrade software (PHP and Apache) package by package, downloading .rpm-s, but it becomes too complicated.

Please help, thanks in advance.

If TMG (previously ISA) accepts NTLM auth see http://ntlmaps.sourceforge.net/ ?

Thanks unSpawn for your fast reply, I've found another workaround. Just in case someone will be interested in: I've just made our sysadmins to grant access to internet, through the proxy without user authentication on SUSE machines IP, then I just configured YaST to use proxy and that's it. But anyways, SLES 10 is dead is not supported anymore, so unfortunately it's impossible to upgrade existing system.

By the way, is it possible to put other distribution's rpm repository URL for SLES 10?

That would be the easy way out, yes ;-p


Given SLES 10 is unsupported (last upgrade was SP4 in 2011) I would consider that support and security-wise the wrong question. I strongly suggest either first installing SLES 11 (SP2 Feb. 2012) or moving to another (Enterprise?) distribution.

Yes, I think I have no choice. We have couple of other linux based servers and all of them are already migrated to Red Hat Enterprise Server, I just hoped that I could find the solution to upgrade an existing version, but well... :(

OK, thanks anyways for your extremely quick feedback and wish you nice day (well, if you live near to my time zone :) )

Thank deities you have the opportunity to migrate to RHEL instead of having to sink time into securing, auditing and maintaining obsolete SW...


NP. Same to you, regardless of your TZ, LQ being about global comms anyways.