search for: proxy_password

Simply modify yum.conf, add proxy=http://proxy.example.si:80/ proxy_username=some_username proxy_password=some_password work for me. Bla? Bogataj -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070213/04c947e3/attachment.html>

Hi Guys, My apologies for earlier mail without subject line. kindly ignore. i've CentOS 6.6 (Final) 64 bit version installed and I can not access the online repositories to install/update (pls see eror below the error), I tried to google this error I get a lot of links but nothing I could really solving this issue. I've already disabled ipv6 and also defined proxy in /etc/yum.conf.

...+extern const char *url; + +extern const char *auth_script; +extern unsigned auth_script_renew; +extern const char *cainfo; +extern const char *capath; +extern char *cookie; +extern struct curl_slist *headers; +extern char *password; +extern long protocols; +extern const char *proxy; +extern char *proxy_password; +extern const char *proxy_user; +extern bool sslverify; +extern bool tcp_keepalive; +extern bool tcp_nodelay; +extern uint32_t timeout; +extern const char *unix_socket_path; +extern const char *user; +extern const char *user_agent; + +/* The per-connection handle. */ +struct curl_handle { + CURL...

...Set HTTP/HTTPS cookies.\n" \ "password=<PASSWORD> The password for the user account.\n" \ "protocols=PROTO,PROTO,.. Limit protocols allowed.\n" \ @@ -369,6 +381,10 @@ curl_open (int readonly) curl_easy_setopt (h->c, CURLOPT_PROXYPASSWORD, proxy_password); if (cookie) curl_easy_setopt (h->c, CURLOPT_COOKIE, cookie); + if (cainfo) + curl_easy_setopt (h->c, CURLOPT_CAINFO, cainfo); + if (capath) + curl_easy_setopt (h->c, CURLOPT_CAPATH, capath); /* Get the file size and also whether the remote HTTP server * supports...

...This means that the box isn't yet talking proxy and is still trying to go through direct. To my yum.conf file i added lines similar to these: # The proxy server - proxy server:port number proxy=http://mycache.mydomain.com:3128 # The account details for yum connections proxy_username=yum-user proxy_password=qwerty I tried port 80 on that proxy line with the same results. Telneting to that ip/port works fine, iptables isn't blocking it. On the firewall i added the yum-user to the password file and used squid's ncsa_auth program to confirm the username/password combination, output was a simp...

This is an RFC only, at the very least it lacks tests. This implements a rather complex new feature in nbdkit-curl-plugin allowing you to specify an external shell script that can be used to fetch an authorization token for services which requires a token or cookie for access, especially if that token must be renewed periodically. The motivation can be seen in the changes to the docs in patch 2.

...-- a/plugins/curl/curl.c +++ b/plugins/curl/curl.c @@ -101,6 +101,8 @@ curl_load (void) nbdkit_error ("libcurl initialization failed: %d", (int) r); exit (EXIT_FAILURE); } + + load_pool (); } static void @@ -112,7 +114,7 @@ curl_unload (void) free (password); free (proxy_password); scripts_unload (); - free_all_handles (); + unload_pool (); curl_global_cleanup (); } diff --git a/plugins/curl/pool.c b/plugins/curl/pool.c index b6f4f8e5f..536123388 100644 --- a/plugins/curl/pool.c +++ b/plugins/curl/pool.c @@ -52,6 +52,7 @@ #include <nbdkit-plugin.h> +#i...

...apath; +extern char *cookie; +extern const char *cookie_script; +extern unsigned cookie_script_renew; +extern struct curl_slist *headers; +extern const char *header_script; +extern unsigned header_script_renew; +extern char *password; +extern long protocols; +extern const char *proxy; +extern char *proxy_password; +extern const char *proxy_user; +extern bool sslverify; +extern bool tcp_keepalive; +extern bool tcp_nodelay; +extern uint32_t timeout; +extern const char *unix_socket_path; +extern const char *user; +extern const char *user_agent; + +/* The per-connection handle. */ +struct curl_handle { + CURL...

Evolution of this patch series: https://www.redhat.com/archives/libguestfs/2020-July/thread.html#00073 Instead of auth-script, this implements header-script and cookie-script. It can be used for similar purposes but the implementation is somewhat saner. Rich.

.... I've already disabled ipv6 and also defined proxy in > /etc/yum.conf. ... This is stating the obvious but it looks like your proxy definition in yum.conf does not work. I assume you have something like: proxy=http://<hostname>:<port> with a possible proxy_username=whoever and proxy_password=whatever if required in yum.conf Check these again, I find I often read what I thought I typed, not what I actually did. If this is correct tcpdump may give you some useful information on what is actually happening. Regards

...proxy server and yum work like ... charm. You can find manual in http://www.centos.org/docs/4/html/yum/sn-yum-proxy-server.html. I'm usualy edit /etc/yum.conf and put there #proxy adress:port - take care of / proxy=http://proxy.somedomain.si:80/ #proxy username and passwd proxy_username= proxy_password= Have a nice day. Bla? -----Original Message----- Message: 2 Date: Mon, 20 Jul 2009 12:17:49 -0400 From: Alberto Garc?a G?mez <alberto at ipimtzcm.rimed.cu> Subject: [CentOS] YUM Proxy To: "CentOS mailing list" <centos at centos.org> Message-ID: <001a01ca0955$9ff627e0$0...

Is there a way to use an HTTP proxy (with a user/pass) with yum? Or at least a way to pass a user/pass through yum? I have a situation with a CentOS server behind a web filter appliance. Thanks, Scott

Hello all, How can I configure yum to download updates when I need to authenticate to a Microsoft Forefront proxy?? I have tried to configure http_proxy variable as a "http_proxy="http://DOMAIN\\user:passwd at proxy:port/", but it doesn't works ... I have tried to set http_user and http_passwd also without luck. Thanks.

...gt; -static const char *cainfo = NULL; > -static const char *capath = NULL; > -static char *cookie = NULL; > -static struct curl_slist *headers = NULL; > -static char *password = NULL; > -static long protocols = CURLPROTO_ALL; > -static const char *proxy = NULL; > -static char *proxy_password = NULL; > -static const char *proxy_user = NULL; > -static bool sslverify = true; > -static bool tcp_keepalive = false; > -static bool tcp_nodelay = true; > -static uint32_t timeout = 0; > -static const char *unix_socket_path = NULL; > -static const char *user = NULL; > -sta...

Yum using proxy that requires authentication and a Password that contains the two characters \/ fails normally I can get yum to work with a proxy that requires authentication when required by doing something like http_proxy=http://<my username>:<my password>@<proxy server>:<proxy server port> export http_proxy or by filling in the appropriate information in yum.conf.

...w if it will ever bite someone in practice, but it's always nicer to be able to point a bug report back to a commit message stating that the change was intentional if it does come up. > +++ b/plugins/curl/curl.c > @@ -62,7 +62,7 @@ static const char *proxy_user = NULL; > static char *proxy_password = NULL; > static char *cookie = NULL; > static bool sslverify = true; > -static long timeout = 0; > +static uint32_t timeout = 0; > @@ -334,7 +336,7 @@ curl_open (int readonly) > curl_easy_setopt (h->c, CURLOPT_REDIR_PROTOCOLS, protocols); > } > if (timeout...

I'm mainly posting this to the list as a back-up. It does work, it does _not_ improve performance in any noticable way. However I'm having lots of trouble getting HTTP/2 to work (with or without this patch) and that's stopping me from testing anything properly. Rich.

...101,6 +101,8 @@ curl_load (void) > nbdkit_error ("libcurl initialization failed: %d", (int) r); > exit (EXIT_FAILURE); > } > + > + load_pool (); > } > > static void > @@ -112,7 +114,7 @@ curl_unload (void) > free (password); > free (proxy_password); > scripts_unload (); > - free_all_handles (); > + unload_pool (); > curl_global_cleanup (); > } > > diff --git a/plugins/curl/pool.c b/plugins/curl/pool.c > index b6f4f8e5f..536123388 100644 > --- a/plugins/curl/pool.c > +++ b/plugins/curl/pool.c > @@ -...

...kit_realpath (const char *path); extern int nbdkit_nanosleep (unsigned sec, unsigned nsec); diff --git a/plugins/curl/curl.c b/plugins/curl/curl.c index 0ed3984..cf01aae 100644 --- a/plugins/curl/curl.c +++ b/plugins/curl/curl.c @@ -62,7 +62,7 @@ static const char *proxy_user = NULL; static char *proxy_password = NULL; static char *cookie = NULL; static bool sslverify = true; -static long timeout = 0; +static uint32_t timeout = 0; static const char *unix_socket_path = NULL; static long protocols = CURLPROTO_ALL; @@ -204,7 +204,9 @@ curl_config (const char *key, const char *value) } else if (...

On Mon, Sep 23, 2019 at 12:05:11PM -0500, Eric Blake wrote: > > + int nbdkit_parse_long (const char *what, const char *str, long *r); > > + int nbdkit_parse_unsigned_long (const char *what, > > + const char *str, unsigned long *r); > > Do we really want to encourage the use of parse_long and > parse_unsigned_long? Those differ between