Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.prolog > #14197

Re: broken and insecure links (Was: comp.lang.prolog Frequently Asked Questions)

From Mild Shock <janburse@fastmail.fm>
Newsgroups comp.lang.prolog
Subject Re: broken and insecure links (Was: comp.lang.prolog Frequently Asked Questions)
Date 2024-09-20 11:19 +0200
Message-ID <vcjemc$dhdf$1@solani.org> (permalink)
References (1 earlier) <vcja71$df34$1@solani.org> <vcjcco$g1tk$1@solani.org> <vcjcgo$g1tk$2@solani.org> <vcjcrc$g28h$1@solani.org> <vcjdhl$dgun$1@solani.org>

Show all headers | View raw


But its up to the server admin paranoia to
provide HTTPS at all. Your paranoia goes away
if you notice that HTTPS is practially recommended

for example under the EU GDPR or CCPA.

https://gdpr.eu/

https://oag.ca.gov/privacy/ccpa

Mild Shock schrieb:
> GIT does also produce a HTTPS warning and
> not allow HTTP at all, it works with a HTTP
> client that has redirect(true):
> 
> $ git clone http://www.dogelog.ch/dogelog/.git
> Cloning into 'dogelog'...
> warning: redirecting to https://www.dogelog.ch/dogelog/.git/
> Fetching objects: 4613, done.
> 
> The warning tells me I have a **security glitch**
> using initially HTTP, and I should use a HTTPS
> link from the start.
> 
> Your SWI-Prolog GIT library might suppress this
> warning, which is **not ok** in my opinion. To avoid
> the warning I directly publish a HTTPS link:
> 
> 1 GIT Access
> For binary files and source code initially:
> git clone https://www.dogelog.ch/dogelog/.git
> 
> Mild Shock schrieb:
>> Here is a sketch how this could be checked:
>> ```
>>      http_open(_, _, [final_url(FinalURL)]),
>>      (\+ sub_atom(FinalURL, 0, _, _, 'https:') ->
>>             /* show some warning or even fatal error */
>> ```
>> [https://www.swi-prolog.org/pldoc/man?predicate=http_open/3](https://www.swi-prolog.org/pldoc/man?predicate=http_open/3) 
>>
>>
>> Or better using the `redirect(false`) http option
>> from the beginning. Some modern HTTP clients have
>> even a third `redirect/1` option besides true and
>>
>> false that prevents HTTP to HTTPS promotion.

Back to comp.lang.prolog | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

comp.lang.prolog Frequently Asked Questions Markus Triska <triska@logic.at> - 2024-09-16 04:59 +0000
  broken and insecure links (Was: comp.lang.prolog Frequently Asked Questions) Mild Shock <janburse@fastmail.fm> - 2024-09-20 10:02 +0200
    Re: broken and insecure links (Was: comp.lang.prolog Frequently Asked Questions) Mild Shock <janburse@fastmail.fm> - 2024-09-20 10:39 +0200
      Re: broken and insecure links (Was: comp.lang.prolog Frequently Asked Questions) Mild Shock <janburse@fastmail.fm> - 2024-09-20 10:42 +0200
        Re: broken and insecure links (Was: comp.lang.prolog Frequently Asked Questions) Mild Shock <janburse@fastmail.fm> - 2024-09-20 10:59 +0200
          Re: broken and insecure links (Was: comp.lang.prolog Frequently Asked Questions) Mild Shock <janburse@fastmail.fm> - 2024-09-20 11:19 +0200
  Re: comp.lang.prolog Frequently Asked Questions Mild Shock <janburse@fastmail.fm> - 2024-09-20 14:04 +0200
    Re: comp.lang.prolog Frequently Asked Questions Mild Shock <janburse@fastmail.fm> - 2024-09-20 20:38 +0200
      Re: comp.lang.prolog Frequently Asked Questions Mild Shock <janburse@fastmail.fm> - 2024-09-20 20:41 +0200

csiph-web