[Pharo-dev] libssh2 1.7.0 & 1.8.0

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Fri Jan 4 04:35:41 EST 2019


At the risk of being pedantic, if we were really serious, for mid term, it
would be good to not compile ssl, but just link.

https://www.cvedetails.com/vulnerability-list/vendor_id-217/product_id-383/opdos-1/Openssl-Openssl.html

Le ven. 4 janv. 2019 à 10:13, Alistair Grant <akgrant0710 at gmail.com> a
écrit :

> Hi Guille,
>
> On Fri, 4 Jan 2019 at 09:54, Guillermo Polito <guillermopolito at gmail.com>
> wrote:
> >
> > Hi Alistair,
> >
> > On Fri, Jan 4, 2019 at 9:25 AM Alistair Grant <akgrant0710 at gmail.com>
> wrote:
> >>
> >> Hi Esteban,
> >>
> >> The VM is currently being built with libssh2 1.7.0, but this doesn't
> >> build on ARM v6 (Raspberry Pi) due to changes in openssl.
> >>
> >> libssh2 1.8.0, which was released in October 2016, builds and appears
> >> to function correctly (the VM crashes when attempting to commit from
> >> within Iceberg, but I think this is an unrelated problem).
> >
> >
> > May I ask if you mean commit or push?
>
> I meant commit.  I guess that it is doing a comparison of the image to
> the git repository to determine what has changed (to present the
> dialog saying which methods have changed).  It's a call to free() that
> actually causes the problem.
>
>
> > Because commiting should not incure into any network activity and thus
> the ssl is never used.
>
> Which is why I thought it is unrelated :-)
>
>
> > I don't know about the satus of libssl and libgit, but it is certain
> that libgit uses libssl, so we have to be careful that the versions of
> libgit and libssl are compatible.
>
> I cloned the pharo repository as a basic check that they are working
> together (plus the testing on Ubuntu).
>
>
> >> I've built and done some ad-hoc testing of libssh2 1.8.0 on linux 64
> >> bit (Ubuntu 16.04) and haven't had any issues.
> >>
> >> What do you think of upgrading from libssh2 1.7.0 to 1.8.0?
> >>
> >> I don't know how close Pharo 7.0 is to release
> >
> >
> > Super close :)
>
> :-)
>
> Cheers,
> Alistair
>
>
> >> , but I expect this can
> >> wait until Pharo 8.0 if you prefer.
> >
> >
> > Or maybe for a 7.1?
> > We should be able to have easier and shorter release cycles in the
> future.
> >
> > Thanks Alistair ^^
> >
> >>
> >> For convenience: https://www.libssh2.org/
> >>
> >> Thanks,
> >> Alistair
> >>
> >
> >
> > --
> >
> >
> >
> > Guille Polito
> >
> > Research Engineer
> >
> > Centre de Recherche en Informatique, Signal et Automatique de Lille
> >
> > CRIStAL - UMR 9189
> >
> > French National Center for Scientific Research - http://www.cnrs.fr
> >
> >
> > Web: http://guillep.github.io
> >
> > Phone: +33 06 52 70 66 13
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20190104/b98d9ab1/attachment.html>


More information about the Pharo-dev mailing list