1:09 p.m.
In CVS, we've now switched to using libcurl for HTTP support
(as opposed to using code that was ripped from wget once upon
a time).
This will make our network support more flexible and
extensible but it means we now have another dependency. To
build current CVS gretl you'll need the appropriate "dev"
package for libcurl -- or go for the original source at
http://curl.haxx.se/libcurl/
Allin Cottrell
3:45 p.m.
I have updated README.packages to include the "curl" dependency.
Hélio
On Fri, Jun 8, 2012 at 2:09 PM, Allin Cottrell <cottrell(a)wfu.edu> wrote:
In CVS, we've now switched to using libcurl for HTTP support
(as opposed to using code that was ripped from wget once upon
a time).
This will make our network support more flexible and
extensible but it means we now have another dependency. To
build current CVS gretl you'll need the appropriate "dev"
package for libcurl -- or go for the original source at
http://curl.haxx.se/libcurl/
Allin Cottrell
_______________________________________________
Gretl-devel mailing list
Gretl-devel(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-devel
10:50 a.m.
Em sexta-feira, 8 de junho de 2012, Allin Cottrell escreveu:
In CVS, we've now switched to using libcurl for HTTP support
(as opposed to using code that was ripped from wget once upon
a time).
This will make our network support more flexible and
extensible but it means we now have another dependency. To
build current CVS gretl you'll need the appropriate "dev"
package for libcurl -- or go for the original source at
http://curl.haxx.se/libcurl/
Allin Cottrell
_______________________________________________
Gretl-devel mailing list
Gretl-devel(a)lists.wfu.edu <javascript:;>
http://lists.wfu.edu/mailman/listinfo/gretl-devel
--
Henrique Andrade*
*
10:55 a.m.
Dear Allin,
Using libcurl we would be able to have secure proxy authentication?
Best,
Henrique
P.S.: I'm sorry for sending the blank message.
Enviado via iPad
Em 08/06/2012, às 10:09, Allin Cottrell <cottrell(a)wfu.edu> escreveu:
In CVS, we've now switched to using libcurl for HTTP support
(as opposed to using code that was ripped from wget once upon
a time).
This will make our network support more flexible and
extensible but it means we now have another dependency. To
build current CVS gretl you'll need the appropriate "dev"
package for libcurl -- or go for the original source at
http://curl.haxx.se/libcurl/
Allin Cottrell
_______________________________________________
Gretl-devel mailing list
Gretl-devel(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-devel
2:02 p.m.
On Thu, 14 Jun 2012, Henrique Andrade wrote:
Using libcurl we would be able to have secure proxy authentication?
Yes, that should be possible, though it may take a little
experimentation to get it right. Here are two things to try.
1) Under the "Network" tab in gretl's Preferences dialog, set
the HTTP proxy and check "Use HTTP proxy". The general form of
the proxy string is now
http://[username:password@]host[:port]
where [...] denotes an optional element, and "host" can be
given as hostname or IP number. For example
http://myname:mypass@www.myproxy.net:80
2) Alternatively, blank out the HTTP proxy entry under
Preferences and uncheck the "Use HTTP proxy" box, and instead
put the appropriate value into the environment variable
"http_proxy". This may already be defined on your system. As
in
http_proxy=http://myname:mypass@www.myproxy.net:80
This environment variable should be respected by libcurl (but
it will be overriden by any proxy specification passed by
gretl).
Allin
2:10 p.m.
That is a very unsecure authentication!
Most of those Proxies all hacked, because of clear text auth.
Should'nt it be https:// ?
(Henrique: I understand that you may be accessing from an Intranet,
but at least you should be aware of the risks.)
On Thu, Jun 14, 2012 at 3:02 PM, Allin Cottrell <cottrell(a)wfu.edu> wrote:
On Thu, 14 Jun 2012, Henrique Andrade wrote:
> Using libcurl we would be able to have secure proxy authentication?
Yes, that should be possible, though it may take a little
experimentation to get it right. Here are two things to try.
1) Under the "Network" tab in gretl's Preferences dialog, set
the HTTP proxy and check "Use HTTP proxy". The general form of
the proxy string is now
http://[username:password@]host[:port]
where [...] denotes an optional element, and "host" can be
given as hostname or IP number. For example
http://myname:mypass@www.myproxy.net:80
2) Alternatively, blank out the HTTP proxy entry under
Preferences and uncheck the "Use HTTP proxy" box, and instead
put the appropriate value into the environment variable
"http_proxy". This may already be defined on your system. As
in
http_proxy=http://myname:mypass@www.myproxy.net:80
This environment variable should be respected by libcurl (but
it will be overriden by any proxy specification passed by
gretl).
Allin
_______________________________________________
Gretl-devel mailing list
Gretl-devel(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-devel
2:26 p.m.
On Thu, 14 Jun 2012, Hélio Guilherme wrote:
That is a very unsecure authentication!
Most of those Proxies all hacked, because of clear text auth.
Libcurl should take care of negotiation with the server, and
will presumably not send the password in clear text if that
can be avoided (e.g. use NTLM).
Should'nt it be https:// ?
It can be https://, in fact it can be just about any protocol.
Allin
2:36 p.m.
Dear Allin and Guilherme,
Now I'm a little bit afraid. I'm using this here at my work and we
have a lot of confidential stuff. It is a bank :-)
So if you believe there are risks I think I should not use this feature.
Additionally, still talking about security questions... In R we have
an option to ask for the password every time the user initialize the
software. Is this a possible and desirable feature?
Best,
Henrique
Enviado via iPhone
Em 14/06/2012, às 11:26, Allin Cottrell <cottrell(a)wfu.edu> escreveu:
On Thu, 14 Jun 2012, Hï¿œlio Guilherme wrote:
> That is a very unsecure authentication!
>
> Most of those Proxies all hacked, because of clear text auth.
Libcurl should take care of negotiation with the server, and will presumably not send the
password in clear text if that can be avoided (e.g. use NTLM).
> Should'nt it be https:// ?
It can be https://, in fact it can be just about any protocol.
Allin
_______________________________________________
Gretl-devel mailing list
Gretl-devel(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-devel
2:45 p.m.
The use of passwords should be avoided.
I think that we will not need for passwords in Gretl, unless we are
acessing a secure database server (but then the protocol should deal
with that).
If the users needs to protect a datafile, then an external tool should
be used (for example a ZIP archiver with password).
Hélio
On Thu, Jun 14, 2012 at 3:36 PM, Henrique Andrade
<henrique.coelho(a)gmail.com> wrote:
Dear Allin and Guilherme,
Now I'm a little bit afraid. I'm using this here at my work and we
have a lot of confidential stuff. It is a bank :-)
So if you believe there are risks I think I should not use this feature.
Additionally, still talking about security questions... In R we have
an option to ask for the password every time the user initialize the
software. Is this a possible and desirable feature?
Best,
Henrique
Enviado via iPhone
Em 14/06/2012, às 11:26, Allin Cottrell <cottrell(a)wfu.edu> escreveu:
> On Thu, 14 Jun 2012, Hï¿œlio Guilherme wrote:
>
>> That is a very unsecure authentication!
>>
>> Most of those Proxies all hacked, because of clear text auth.
>
> Libcurl should take care of negotiation with the server, and will presumably not send
the password in clear text if that can be avoided (e.g. use NTLM).
>
>> Should'nt it be https:// ?
>
> It can be https://, in fact it can be just about any protocol.
>
> Allin
> _______________________________________________
> Gretl-devel mailing list
> Gretl-devel(a)lists.wfu.edu
> http://lists.wfu.edu/mailman/listinfo/gretl-devel
_______________________________________________
Gretl-devel mailing list
Gretl-devel(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-devel
2:12 p.m.
Dear Allin,
I tested the suggested configuration and it work just like a charm.
Thanks so much!
Best regards,
Henrique
Enviado via iPhone
Em 14/06/2012, às 11:02, Allin Cottrell <cottrell(a)wfu.edu> escreveu:
On Thu, 14 Jun 2012, Henrique Andrade wrote:
> Using libcurl we would be able to have secure proxy authentication?
Yes, that should be possible, though it may take a little
experimentation to get it right. Here are two things to try.
1) Under the "Network" tab in gretl's Preferences dialog, set
the HTTP proxy and check "Use HTTP proxy". The general form of
the proxy string is now
http://[username:password@]host[:port]
where [...] denotes an optional element, and "host" can be
given as hostname or IP number. For example
http://myname:mypass@www.myproxy.net:80
2) Alternatively, blank out the HTTP proxy entry under
Preferences and uncheck the "Use HTTP proxy" box, and instead
put the appropriate value into the environment variable
"http_proxy". This may already be defined on your system. As
in
http_proxy=http://myname:mypass@www.myproxy.net:80
This environment variable should be respected by libcurl (but
it will be overriden by any proxy specification passed by
gretl).
Allin
_______________________________________________
Gretl-devel mailing list
Gretl-devel(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-devel
4:57 p.m.
On Thu, 14 Jun 2012, Henrique Andrade wrote:
I tested the suggested configuration and it work just like a charm.
Thanks so much!
Good to hear.
Re. security concerns, in today's snapshot I've rebuilt the
libcurl 7.26 DLL with SSPI enabled. I believe that if your
credentials are stored in Windows you should now be able to
authenticate with blank username and password fields in the
proxy string.
My understanding is that you should keep the empty skeleton of
"user:password@proxyhost", as in
http[s]://:@proxyhost[:port]
However I have no way of testing this.
Allin
4328
days inactive
4334
days old
10 comments
3 participants
participants (3)
-
Allin Cottrell -
Henrique Andrade -
Hélio Guilherme