all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: tobias.geerinckx.rice@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: lynx: Support HTTPS (SSL) connections
Date: Thu, 3 Mar 2016 22:01:40 -0500	[thread overview]
Message-ID: <20160304030140.GA30676@jasmine> (raw)
In-Reply-To: <1457059066-8060-1-git-send-email-tobias.geerinckx.rice@gmail.com>

On Fri, Mar 04, 2016 at 03:37:46AM +0100, tobias.geerinckx.rice@gmail.com wrote:
> From: Tobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com>
> 
> * gnu/packages/lynx.scm (lynx)[inputs]: Add 'openssl'.
> [arguments]: Convert to list; add configure flag for SSL support.

Wow, thanks for this patch!

Can you say if you learned anything else... "interesting" about lynx and
https support?

For example, a couple months ago I was reading our bug reports and saw
an old one about https support in w3m (another console browser). I dug a
little deeper and realized that https support was completely broken by
default. You can see the result in commit 62339e2d493bf87.

So, do you know if lynx is still supporting broken ciphers and
protocols, or if there are other problems of that nature?

Also, what is role of gnutls once this patch is applied? Does lynx need
to refer to both gnutls and openssl?

> ---
>  gnu/packages/lynx.scm | 30 +++++++++++++++++-------------
>  1 file changed, 17 insertions(+), 13 deletions(-)
> 
> diff --git a/gnu/packages/lynx.scm b/gnu/packages/lynx.scm
> index 3182b3e..7e1ef1d 100644
> --- a/gnu/packages/lynx.scm
> +++ b/gnu/packages/lynx.scm
> @@ -48,24 +48,28 @@
>                ("libidn" ,libidn)
>                ("gnutls" ,gnutls)
>                ("libgcrypt" ,libgcrypt)
> +              ("openssl" ,openssl)
>                ("unzip" ,unzip)
>                ("zlib" ,zlib)
>                ("gzip" ,gzip)
>                ("bzip2" ,bzip2)))
>      (arguments
> -     `(#:configure-flags '("--with-pkg-config"
> -                           "--with-screen=ncurses"
> -                           "--with-zlib"
> -                           "--with-bzlib"
> -                           "--with-gnutls"
> -                           ;; "--with-socks5"    ; XXX TODO
> -                           "--enable-widec"
> -                           "--enable-ascii-ctypes"
> -                           "--enable-local-docs"
> -                           "--enable-htmlized-cfg"
> -                           "--enable-gzip-help"
> -                           "--enable-nls"
> -                           "--enable-ipv6")
> +     `(#:configure-flags
> +       (list "--with-pkg-config"
> +             "--with-screen=ncurses"
> +             "--with-zlib"
> +             "--with-bzlib"
> +             "--with-gnutls"
> +             (string-append "--with-ssl="
> +                            (assoc-ref %build-inputs "openssl"))
> +             ;; "--with-socks5"    ; XXX TODO
> +             "--enable-widec"
> +             "--enable-ascii-ctypes"
> +             "--enable-local-docs"
> +             "--enable-htmlized-cfg"
> +             "--enable-gzip-help"
> +             "--enable-nls"
> +             "--enable-ipv6")
>         #:tests? #f  ; no check target
>         #:phases (alist-replace
>                   'install
> -- 
> 2.6.3
> 
> 

  reply	other threads:[~2016-03-04  3:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  2:37 [PATCH] gnu: lynx: Support HTTPS (SSL) connections tobias.geerinckx.rice
2016-03-04  3:01 ` Leo Famulari [this message]
2016-03-19 17:29   ` Tobias Geerinckx-Rice
2016-03-19 18:41     ` Efraim Flashner
2016-03-19 20:59       ` Tobias Geerinckx-Rice
2016-03-19 21:01       ` Tobias Geerinckx-Rice
2016-03-19 21:23         ` Efraim Flashner
2016-03-19 21:29           ` Tobias Geerinckx-Rice
2016-03-20 21:16         ` Ludovic Courtès
2016-03-20  8:15     ` Leo Famulari
2016-04-07  1:32       ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160304030140.GA30676@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=tobias.geerinckx.rice@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.