Re: [H-source-users] Introduction

[bill-auger]

On Tue, 20 Jul 2021 06:14:43 +0200 Denis wrote:
> without having the h-client
> send the username / password in clear?

h-client has SSL is enabled already

> * Connection #0 to host h-node.org left intact
> *   Trying 209.51.188.186:443...
> * Connected to h-node.org (209.51.188.186) port 443 (#0)
> * ALPN, offering h2
> * ALPN, offering http/1.1
> * successfully set certificate verify locations:
> *  CAfile: /etc/ssl/certs/ca-certificates.crt
> *  CApath: none
> * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
> * ALPN, server did not agree to a protocol
> * Server certificate:
> *  subject: CN=www.h-node.com
> *  start date: Jun  6 09:06:41 2021 GMT
> *  expire date: Sep  4 09:06:41 2021 GMT
> *  subjectAltName: host "h-node.org" matched cert's "h-node.org"
> *  issuer: C=US; O=Let's Encrypt; CN=R3
> > *  SSL certificate verify ok.
> * SSL certificate status: good (0)
> > GET /users/logout/en HTTP/1.1
> Host: h-node.org
> User-Agent: PycURL/7.43.0.3 libcurl/7.77.0 OpenSSL/1.1.1k
>             zlib/1.2.11 zstd/1.5.0 libidn2/2.3.1
>             libpsl/0.21.1 (+libidn2/2.3.0) libssh2/1.9.0 nghttp2/1.43.0

in fact, when i tried using HTTP, it appears that the server
redirects to HTTPS, but the URL is mangled, and the
follow-through doesn't even connect

> * Connected to h-node.org (209.51.188.186) port 80 (#0)
> ....
> < HTTP/1.1 301 Moved Permanently
> < Location: https://h-node.orgdownload/all/en
> ....
> * Issue another request to this URL:
> 'https://h-node.orgdownload/all/en'
> * Could not resolve host: h-node.orgdownload


On Tue, 20 Jul 2021 06:14:43 +0200 Denis wrote:
> For instance In Parabola, the same username / password works for
> several things (the wiki, the bugreport system and so on) probably
> thanks to LDAP.

those are separate credentials - there is a long-standing open
ticket for that feature request


On Tue, 20 Jul 2021 06:14:43 +0200 Denis wrote:
> Maybe that could work for most FSDG distributions and
> we could also add other
> common infrastructure like the FSF single sign-on login system

sure that would be great - in theory, h-node, the FSD wiki, and
FSDG distro bug trackers and wikis, could all be authed by the
FSF/libreplanet service (encouraging users of any one, to use
the others)

i dont know how deep the relation should go though, or if the
FSF would want to manage it - the libreplanet and FSD wikis
require separate crenentials now too