all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: 34861@debbugs.gnu.org
Subject: bug#34861: TLS Error with Flatpak
Date: Fri, 22 Mar 2019 22:00:23 +0100	[thread overview]
Message-ID: <87mulm4obc.fsf@gnu.org> (raw)
In-Reply-To: <dfcdcf49dcd70cf3bb43f71c494ae148@disroot.org> (Raghav Gururajan's message of "Tue, 19 Mar 2019 00:43:03 +0000")

Hi Raghav,

"Raghav Gururajan" <rvgn@disroot.org> skribis:

> Please find the log at: https://bin.disroot.org/?597e32cb7e42e40e#r9lqwZ6w7sIAWlY2mt6dsgKCKRO5q0ZVt9U69vnZVZs=
> 
> 5462  connect(12, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("93.93.130.103")}, 16) = -1 EINPROGRESS (Operation now in progress)

[...]

> 5462  getsockopt(12, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
> 5462  setsockopt(12, SOL_TCP, TCP_NODELAY, [1], 4) = 0

[...]

> 5462  close(12)                         = 0

[...]

> 5461  write(2, "\33[31m\33[1merror: \33[22m\33[0mTLS support is not available\n", 54) = 54

Thanks for sending the strace output.  That output shows that Flatpak
never tries to access /etc/ssl/certs, ~/.guix-profile/etc/ssl/certs or
anything like that.

The error message comes from GLib, in gdummytlsbackend.c.  AFAICS our
GLib also includes the TLS (not dummy) backend:

--8<---------------cut here---------------start------------->8---
$ objdump -T /gnu/store/0q9pq9flr76rh4bv2524niknknnl2kvq-glib-2.56.3/lib/libgio-2.0.so | grep g_tls_backend
0000000000093e90 g    DF .text	0000000000000082  Base        g_tls_backend_get_default_database
0000000000093dd0 g    DF .text	000000000000006f  Base        g_tls_backend_supports_tls
0000000000093f40 g    DF .text	000000000000001b  Base        g_tls_backend_get_client_connection_type
0000000000093e40 g    DF .text	0000000000000049  Base        g_tls_backend_supports_dtls
0000000000093db0 g    DF .text	0000000000000015  Base        g_tls_backend_get_default
0000000000093f80 g    DF .text	0000000000000072  Base        g_tls_backend_get_dtls_client_connection_type
0000000000093f60 g    DF .text	000000000000001b  Base        g_tls_backend_get_server_connection_type
0000000000094000 g    DF .text	0000000000000072  Base        g_tls_backend_get_dtls_server_connection_type
0000000000094080 g    DF .text	000000000000007f  Base        g_tls_backend_get_file_database_type
0000000000093d20 g    DF .text	0000000000000084  Base        g_tls_backend_get_type
0000000000093f20 g    DF .text	000000000000001b  Base        g_tls_backend_get_certificate_type
--8<---------------cut here---------------end--------------->8---

Libsoup does this:

--8<---------------cut here---------------start------------->8---
static gboolean
soup_socket_setup_ssl (SoupSocket    *sock,
		       const char    *ssl_host,
		       GCancellable  *cancellable,
		       GError       **error)
{
	SoupSocketPrivate *priv = soup_socket_get_instance_private (sock);
	GTlsBackend *backend = g_tls_backend_get_default ();
--8<---------------cut here---------------end--------------->8---

‘g_tls_backend_get_default’ itself looks like this:

--8<---------------cut here---------------start------------->8---
GTlsBackend *
g_tls_backend_get_default (void)
{
  return _g_io_module_get_default (G_TLS_BACKEND_EXTENSION_POINT_NAME,
				   "GIO_USE_TLS", NULL);
}
--8<---------------cut here---------------end--------------->8---

Could you try setting the ‘GIO_USE_TLS’ environment variable?  Like:

  export GIO_USE_TLS=tls

or maybe:

  export GIO_USE_TLS=GTlsBackend

and then run Flatpak in that environment?

TIA,
Ludo’.

  reply	other threads:[~2019-03-22 21:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 20:36 bug#34861: TLS Error with Flatpak Raghav Gururajan
2019-03-18  9:49 ` Ludovic Courtès
2019-03-18 17:31 ` Raghav Gururajan
2019-03-18 21:24   ` Ricardo Wurmus
2019-03-18 23:10   ` Raghav Gururajan
2019-03-19  0:21     ` Ricardo Wurmus
2019-03-19  0:43     ` Raghav Gururajan
2019-03-22 21:00       ` Ludovic Courtès [this message]
2019-03-23  4:02       ` Raghav Gururajan
2019-03-23  8:05         ` Ricardo Wurmus
2019-03-24  6:48         ` Raghav Gururajan
2019-03-24 22:13           ` Ludovic Courtès
2019-03-24 22:13           ` Ludovic Courtès

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=87mulm4obc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=34861@debbugs.gnu.org \
    --cc=rvgn@disroot.org \
    /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.