krzyzanowskim/OpenSSL

Privacy Manifest and Signature

jzilske opened this issue · 11 comments

jzilske commented

As per the Upcoming third-party SDK requirements using OpenSSL in an App on the App Store will require a privacy manifest (cf. Privacy manifest files) starting next spring. Since the package comes with precompiled libraries a code signature may also be required. Is that something that you would consider providing?

krzyzanowskim commented

yes. technically.
theoretically I’m not the author of OpenSSL

jzilske commented

Yes, that's what I thought as well. 🙂
Do you think this should rather be taken to the OpenSSL foundation then?

FilDevTronic commented

@krzyzanowskim would you be able to provide an update on this issue? Will you be adding the required privacy manifest by the April deadline in this project? 🙏🏻

jzilske commented

FWIW, a discussion about this has been started on the official OpenSSL repo: openssl/openssl#23262

  • 👍1
corentios commented

Following this

jzilske commented

FWIW, a discussion about this has been started on the official OpenSSL repo: openssl/openssl#23262

...and it seems there's nothing coming: openssl/openssl#23262 (comment)

BaroneX commented

It looks like we need to fork this repository, add our own privacy manifest, and sign it ourselves.

krzyzanowskim commented

looks like you can also propose changes to the build script in a PR

thapovand commented

@krzyzanowskim Please Look into #195 for the Privacy Manifest

jzilske commented

Thank you very much @krzyzanowskim!