Stuart Henderson writes:
[...]
> jca, your diff is OK with me.
Committed.
I'm slowly cooking up patches for upstream. Unless anyone is already on
it? :)
--
jca | PGP: 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
On 2014/11/19 23:34, Mikolaj Kucharski wrote:
> I've tested below patch and results seems to be good:
>
>
> for i in www.secure.io www.secure.io:8443 www.amazon.com www.google.com
> www.facebook.com
> do
> for j in auto sslv2 sslv3 tlsv1 tlsv1_1 tlsv1_2 pfs
> do
> echo "===> wget -S -O /
I've tested below patch and results seems to be good:
for i in www.secure.io www.secure.io:8443 www.amazon.com www.google.com
www.facebook.com
do
for j in auto sslv2 sslv3 tlsv1 tlsv1_1 tlsv1_2 pfs
do
echo "===> wget -S -O /dev/null --progress dot:mega --secure-protocol $j
https://$i/ <
Mikolaj Kucharski writes:
> I can confirm that below diff, makes wget work on TLSv1.2-only site again.
Thanks for confirming.
So, here's a patch that makes wget use TLSv1+ instead of TLSv1.0 by
default - and with --secure-protocol=pfs - while making sure that we
don't accept SSLv[23].
Index: M
I can confirm that below diff, makes wget work on TLSv1.2-only site again.
On Wed, Nov 19, 2014 at 09:04:55PM +0100, Jérémie Courr??ges-Anglas wrote:
> Index: patches/patch-src_openssl_c
> ===
> RCS file: /cvs/ports/net/wget/patches/
Stuart Henderson writes:
> On 2014/11/19 08:16, Kent Fritz wrote:
>> Wget is only sending TLS 1.0 in client hello, and the server is
>> refusing. This seems to be a problem with the port, as wget 1.14 on
>> my Linux box sends a TLS 1.2 hello, as does wget on OpenBSD 5.4 (also
>> 1.14).
>
> This
On 2014/11/19 16:38, Stuart Henderson wrote:
> On 2014/11/19 08:16, Kent Fritz wrote:
> > Wget is only sending TLS 1.0 in client hello, and the server is
> > refusing. This seems to be a problem with the port, as wget 1.14 on
> > my Linux box sends a TLS 1.2 hello, as does wget on OpenBSD 5.4 (al
On 2014/11/19 08:16, Kent Fritz wrote:
> Wget is only sending TLS 1.0 in client hello, and the server is
> refusing. This seems to be a problem with the port, as wget 1.14 on
> my Linux box sends a TLS 1.2 hello, as does wget on OpenBSD 5.4 (also
> 1.14).
This is fallout from our OPENSSL_VERSION
Wget is only sending TLS 1.0 in client hello, and the server is
refusing. This seems to be a problem with the port, as wget 1.14 on
my Linux box sends a TLS 1.2 hello, as does wget on OpenBSD 5.4 (also
1.14).
On Tue, Nov 18, 2014 at 10:31 PM, Mikolaj Kucharski
wrote:
> Hi,
>
> I didn't notice w
Hi,
I didn't notice when it started, as ftp and curl just work, but wget
fails for following https site:
# wget --debug -O /dev/null https://www.secure.io/
Setting --output-document (outputdocument) to /dev/null
DEBUG output created by Wget 1.16 on openbsd5.6.
URI encoding = '646'
converted 'ht
10 matches
Mail list logo
