Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove nullable, nonnull, const from initWithAddress #8

Open
ma11hew28 opened this issue Jul 27, 2017 · 4 comments
Open

Remove nullable, nonnull, const from initWithAddress #8

ma11hew28 opened this issue Jul 27, 2017 · 4 comments

Comments

@ma11hew28
Copy link

Why are those keywords included here:

https://github.com/ChatSecure/SignalProtocol-ObjC/blob/master/Classes/Models/SignalAddress_Internal.h#L17

They are not included for SignalPreKey or SignalSignedPreKey.

@ma11hew28
Copy link
Author

ma11hew28 commented Jul 27, 2017

Also, it might be nice to add newlines to SignalPreKey_Internal.h & SignalSignedPreKey_Internal.h to keep the line-spacing consistent with the other internal header files.

@chrisballinger
Copy link
Member

What keywords? signal_protocol_address is internal to the C implementation and shouldn't be exposed to the public Obj-C headers.

Btw I'm curious, are you planning on using this library in a shipping product, or just poking around? Make sure to be mindful of the GPL/App Store license, as there's still no straightforward way to get a closed source exception from Moxie, to my knowledge.

@ma11hew28
Copy link
Author

I was referring to the keywords nullable, nonnull, and const. I don't understand why -[SignalAddress initWithAddress:] and -[SignalSignedPreKey initWithSignedPreKey] are different. I also didn't know what nullable and nonnull meant, but now that I do, it seems like at least nonnull can be removed.

OK. Thank you for that information. We're planning on using this library in a shipping iPhone app. Do we have to open source our server code too if it doesn't use any Signal libraries?

@chrisballinger
Copy link
Member

What's the app? You'll need to release all of the source code, including all linked 3rd party dependencies, and make sure that your app's license is compatible with the GPL: https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses

You don't need to open source your server, but you should consider it if you're offering people a "secure" messenger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants