[NTG-context] Re: Invalid certificate for distribution.contextgarden.net

2023-11-23 Thread Marco Patzer
On Thu, 23 Nov 2023 11:32:45 +0100
Taco Hoekwater  wrote:

> The command 
> 
>   context —version
> 
> gives the local installed version. 

That lists the *local* version, not the most current available
version.

> Not sure whether there is a clean way to see if there is a remote
> newer update without actually doing an update.

This is how I check for the remote version:

  curl --silent --connect-timeout 5 \

'https://distribution.contextgarden.net/current/context/latest/tex/context/base/mkiv/context.mkiv'
 | sed -ne '/\\edef\\contextversion/s/.*{\(.*\)}/\1/p'

Not pretty, but has been working for a decade or so (except the
minimals → standalone change a while ago).

> You can check the mailing list, all new releases by Hans are now
> reported on the ntg-context list

That's not practical, I'm afraid.

Marco
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___


[NTG-context] Re: Invalid certificate for distribution.contextgarden.net

2023-11-23 Thread Taco Hoekwater


> On 23 Nov 2023, at 11:14, Marco Patzer  wrote:
> 
> On Thu, 23 Nov 2023 08:58:56 +0100
> Taco Hoekwater  wrote:
> 
>>> probably a side effect if moving some more to the (ntg) server in
>>> the netherlands (also setting up the build there)  
>> 
>> Even if it used the right certificate, it would not work right now
>> because of the move: there is nothing behind the connection.
> 
> I used that server to check for the latest context version. What's
> the recommended way to check for the latest version? Basically the
> output of the \contextversion command?

The command 

  context —version

gives the local installed version. 

Not sure whether there is a clean way to see if there is a remote newer update 
without actually doing an update. You can check the mailing list, all new 
releases by Hans are now reported on the ntg-context list, but that may be less 
convenient than an actual test. mtx-install.sh does not have a —dry-run or 
—upgradable switch, afaik.

Personally, I just run “bash install.sh” when I suspect there is a relevant 
update (install.sh is in the top-level context installation directory).

Best wishes,
Taco

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___


[NTG-context] Re: Invalid certificate for distribution.contextgarden.net

2023-11-23 Thread Marco Patzer
On Thu, 23 Nov 2023 08:58:56 +0100
Taco Hoekwater  wrote:

> > probably a side effect if moving some more to the (ntg) server in
> > the netherlands (also setting up the build there)  
> 
> Even if it used the right certificate, it would not work right now
> because of the move: there is nothing behind the connection.

I used that server to check for the latest context version. What's
the recommended way to check for the latest version? Basically the
output of the \contextversion command?

Marco
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___


[NTG-context] Re: Invalid certificate for distribution.contextgarden.net

2023-11-23 Thread Henning Hraban Ramm

Am 23.11.23 um 08:58 schrieb Taco Hoekwater:

This makes connections fail. distribution.contextgarden.net has to
be added to the Alternative Name list.

probably a side effect if moving some more to the (ntg) server in the 
netherlands (also setting up the build there)


Even if it used the right certificate, it would not work right now because of 
the move: there is nothing behind the connection.


Is there any news about the Slovenian server?

Hraban
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___


[NTG-context] Re: Invalid certificate for distribution.contextgarden.net

2023-11-23 Thread Taco Hoekwater



> On 23 Nov 2023, at 08:49, Hans Hagen  wrote:
> 
> On 11/22/2023 9:47 PM, Marco Patzer wrote:
>> Hi!
>> The site
>>   https://distribution.contextgarden.net/
>> uses an invalid certificate:
>>   echo | openssl s_client -servername 'distribution.contextgarden.net' 
>> -connect 'distribution.contextgarden.net':443 2>/dev/null |  openssl x509 
>> -noout -ext subjectAltName
>>   X509v3 Subject Alternative Name:
>>   DNS:4tex.ntg.nl, DNS:mailman.ntg.nl, DNS:mysql-admin.ntg.nl, 
>> DNS:ntg.nl, DNS:www.ntg.nl
>> This makes connections fail. distribution.contextgarden.net has to
>> be added to the Alternative Name list.
> probably a side effect if moving some more to the (ntg) server in the 
> netherlands (also setting up the build there)

Even if it used the right certificate, it would not work right now because of 
the move: there is nothing behind the connection.

Best wishes,
Taco


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___


[NTG-context] Re: Invalid certificate for distribution.contextgarden.net

2023-11-22 Thread Hans Hagen

On 11/22/2023 9:47 PM, Marco Patzer wrote:

Hi!

The site

   https://distribution.contextgarden.net/

uses an invalid certificate:

   echo | openssl s_client -servername 'distribution.contextgarden.net' -connect 
'distribution.contextgarden.net':443 2>/dev/null |  openssl x509 -noout -ext 
subjectAltName

   X509v3 Subject Alternative Name:
   DNS:4tex.ntg.nl, DNS:mailman.ntg.nl, DNS:mysql-admin.ntg.nl, DNS:ntg.nl, 
DNS:www.ntg.nl

This makes connections fail. distribution.contextgarden.net has to
be added to the Alternative Name list.
probably a side effect if moving some more to the (ntg) server in the 
netherlands (also setting up the build there)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___