[guardian-dev] Crypto export regulations for apps on Google Play

[Gillian "Gus" Andrews]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Not on the Android store, but James is currently working with lawyer
Camille Francois to try to get the route to getting crypto apps in the
French Apple App store, specifically, smoothed out so it's easier for
developers in our space. This was spurred by ChatSecure iOS having some
trouble with this process.

Would it help to hold a workshop to help developers handle the process
of publishing crypto apps to mobile stores, at CTS in Valencia in March?

Gus

On 10/23/14, 12:00 PM, guardian-dev-request at lists.mayfirst.org wrote:
> Message: 3 Date: Wed, 22 Oct 2014 19:31:19 -0400 From: Hans-Christoph Steiner
<hans at guardianproject.info> To: guardian-dev at lists.mayfirst.org Subject:
Re: [guardian-dev] Crypto export regulations for apps on Google Play
Message-ID: <54483E47.2030404 at guardianproject.info> Content-Type:
text/plain; charset=utf-8 There is a page on guardianproject.info
somewhere that we email to the US Gov. .hc str4d wrote:
>> > Hello,
>> >
>> > I have been developing the I2P Android and Bote apps for some time
>> > now, and am aiming to publish them in the Google Play store. But both
>> > apps involve cryptography (I2P at the network transport layer, Bote
>> > for encrypted email), and I know little about crypto export
>> > regulations (US or otherwise). The US export regulations have not been
>> > an issue for us before, because the apps are publicly developed and
>> > hosted outside the US.
>> >
>> > I know there are several Guardian Project apps (and others on this ML)
>> > already on Google Play that will have encountered these issues before
>> > (Orbot, ChatSecure, TextSecure).
>> >
>> > - What was your experience with getting published?
>> > - How did you comply with the crypto export regulations for open
>> > source software (which are still not clear to me, the website Google
>> > linked to is not easy to comprehend)?
>> > - Are there countries that you cannot publish to, or where you have
>> > had trouble doing so?
>> > - What advice can you give to developers of new apps using crypto?
>> >
>> > str4d
>> > _______________________________________________
>> > Guardian-dev mailing list
>> >
>> > Post: Guardian-dev at lists.mayfirst.org
>> > List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
>> >
>> > To Unsubscribe
>> >         Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>> >         Or visit:
https://lists.mayfirst.org/mailman/options/guardian-dev/hans%40guardianproject.info
>> >
>> > You are subscribed as: hans at guardianproject.info
>> >
> -- PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81
------------------------------

- -- 
Gillian "Gus" Andrews
Senior Program Associate, Secure User Practices
Open Internet Tools Project
openitp.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUSUcTAAoJEOrwrs2Zrn53alwH/3iaCaxzge4NLr9NM0UBi0YB
eeeW5s2z4L10sgSTBgCRJnY45YPO1osGcmVMnNL+HS+qZt8abAMl5KQhtK+pT2ch
bVUDHQ+e08kknvbLQ4Wkld96eB2GVLlcQuANT4hsIIP04AwAfPTl8meoHNxbLyhO
75YSQOwNXpBJXjuH4F6/o5iOfoLH2bMLwTEkQxMYEFIGGinrvtlU+acMhUKFoy2i
hIPI02hv1TxDvY76BTo6dcke5CxspwrqRT8JEJCNIV/efgJREC17EPyprT27Wd0F
1vrm3OXPppZA6FWqOS52AXb9JhPcHUbHIAqpX4j6dSLmyI9ftu7om7MHjK5kCdU=
=1cbF
-----END PGP SIGNATURE-----