[squeak-dev] How to change the update URL for Trunk HTTPS?

Eliot Miranda eliot.miranda at gmail.com
Fri Sep 11 13:42:36 UTC 2020


Hi Levente, Hi Tobias, Hi Vanessa,

    would it be possible to layer in a hack to avoid having to edit the URLs?  At some point in Monticello update a http connection is made.  If at that point there is a url translation dictionary (a map) then a http url could be mapped selectively to an https one.  If there is no entry in the map no translation occurs.  Or does that break things upstream?

_,,,^..^,,,_ (phone)

> On Sep 11, 2020, at 3:24 AM, Thiede, Christoph <Christoph.Thiede at student.hpi.uni-potsdam.de> wrote:
> 
> 
> Hi all,
> 
> 
> 
> sounds as if the Squeak world would not yet be ready to migrate completely to HTTPS? Maybe a hybrid solution (i.e. relative URLs in the update map) could indeed be a better solution?
> 
> 
> 
> > There's no need for that. #defaultUpdateURL will not change DefaultUpdateURL's value.
> 
> 
> 
> Yes, it won't, but #defaultUpdateURL: will do so.
> 
> 
> 
> > Nobody outside HPI seriously tested the environment.
> 
> 
> How could such a test look like?
> 
> Best,
> Christoph
> Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Tobias Pape <Das.Linux at gmx.de>
> Gesendet: Freitag, 11. September 2020 08:18:17
> An: The general-purpose Squeak developers list
> Betreff: Re: [squeak-dev] How to change the update URL for Trunk HTTPS?
>  
> 
> > On 09.09.2020, at 22:56, Thiede, Christoph <Christoph.Thiede at student.hpi.uni-potsdam.de> wrote:
> > 
> > Hi all,
> > 
> > Levente, thanks for the improvements! I attempted to only patch as much as required for updating the image via the docking bar menu or the Monticello Browser.
> > Why aren't you using 'MCHttpRepository allInstancesDo:' in your version?
> > And I used the Compiler in my version in order not to change the DefaultUpdateURL class variable if it was not set before.
> > 
> > > That would mean, changing the update maps.
> > 
> > +1 for doing so. Could there be any possible problems? Environments that do not support SSL today? Possible performance problems?
> 
> Our SSL support is lacking.
> No actual Cert checking on Unix.
> Nobody outside HPI seriously tested the environment.
> 
> Thats about it.
>         -t
> 
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200911/ab41244b/attachment.html>


More information about the Squeak-dev mailing list