After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789135 - balsa: port to OpenSSL 1.1
balsa: port to OpenSSL 1.1
Status: RESOLVED OBSOLETE
Product: balsa
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Balsa Maintainers
Balsa Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-10-18 09:32 UTC by Emilio Pozuelo Monfort
Modified: 2021-06-01 22:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Emilio Pozuelo Monfort 2017-10-18 09:32:22 UTC 
Hi,

OpenSSL 1.1 made structs private. That means you can no longer access struct members directly, but there are accessor functions that you can use instead. There were other API changes as well.

It'd be good to get balsa ported.

See https://wiki.openssl.org/index.php/OpenSSL_1.1.0_Changes
Comment 1 Peter Bloomfield 2017-10-18 15:13:15 UTC 
Thanks for the suggestion!

Balsa's SSL code was updated in git shortly after the last release, so I believe all that is needed is releasing a new version.
Comment 2 Peter Bloomfield 2017-10-20 12:42:56 UTC 
I just verified that Balsa installed from the Fedora 27 package balsa-2.5.3-5.fc27.x86_64 in fact links to /lib64/libssl.so.1.1 from the openssl-libs-1.1.0f-9.fc27.x86_64 package, so porting is complete, at least as far as the latest Fedora is concerned.
Comment 3 Emilio Pozuelo Monfort 2017-10-23 08:06:57 UTC 
Sure, but Fedora ships a patch for openssl 1.1:

http://pkgs.fedoraproject.org/cgit/rpms/balsa.git/tree/build-ssl-1.1.patch

So assuming that patch is upstream, we would need a release as you said. Can we have one?

Thanks!
Comment 4 Emilio Pozuelo Monfort 2017-12-01 17:34:16 UTC 
 (In reply to Peter Bloomfield from comment #1)
> Thanks for the suggestion!
> 
> Balsa's SSL code was updated in git shortly after the last release, so I
> believe all that is needed is releasing a new version.

I just realized that the last release was a year ago. Maybe it's time to get a new one, not just for this fix but for all the others that have been committed since then?

Otherwise, I may look at applying that patch too.
Comment 5 André Klapper 2021-06-01 22:42:00 UTC 
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/balsa/-/issues/

Thank you for your understanding and your help.