Passphrase encryption - round III
by Bruno Oliveira
Good morning slackland, yesterday I had a hangout with Matthias and we agreed that the whole key agreement thing would bring more complexity from the developer’s pespective. That’s the reason why the client with airline was dropped.
Here comes the new proposal: https://gist.github.com/abstractj/ef1e3d53619796f4e87e
# Passphrase encryption for UPS
**Note**: This is NOT a replacement for SSL
## Scenario
- Developers wants to upload passphrase and certificate for iOS variants. The passphrase must be stored encrypted and restored in clear while sending messages.
## Jira references
- https://issues.jboss.org/browse/AGPUSH-565 (*Dropped*). After a hangout with Matthias, we agreed that would complicate the developer's workflow.
- https://issues.jboss.org/browse/AGPUSH-358
## Proposal
Today we can't guarantee that our developers will have an [HSM](http://en.wikipedia.org/wiki/Hardware_security_module) to manage encryption keys. Neither we can store the private keys in a separated database, for the push server.
If somehow the database is compromised, private keys could be exposed and most of the sensitive data decrypted.
The suggestion is to make use of a *KDF function* per application to encrypt passphrases, not perfect, but helps (like we did in the past for password reset). Where encryption key means:
```
PK = PBKDF2(Secret Key, Salt)
```
*Secret Key*: In the ideal world, users would be required to provide a password for encryption. In this scenario we don't want them to be prompted to input the password, or add extra parameters to the UPS endpoints. So the suggestion is to provide secret key configured on the server and protected by the ACL's from the operating system
*Salt*: 16 bytes non-deterministic used to encrypt/decrypt the data on the server per application and stored into the database.
### Secret key configuration
The file can be generated and checked if something exists during the application start up.
- config.properties
```
secret_key = "d9eb5171c59a4c817f68b0de27b8c1e340c2341b52cdbc60d3083d4e8958532" \
"18dcc5f589cafde048faec956b61f864b9b5513ff9ce29bf9e5d58b0f234f8e3b"
```
or
- config.json
```
{"secret_key":"d9eb5171c59a4c817f68b0de27b8c1e340c2341b52cdbc60d3083d4e8958532" \
"18dcc5f589cafde048faec956b61f864b9b5513ff9ce29bf9e5d58b0f234f8e3b"}
```
### Sending push messages
Passphrases must be reversible for Apple, that's why we make use of symmetric encryption here.
# REST API
## Register push app
```POST | rest/applications```
### HTTP request
Remain unchanged
### HTTP response
Remain unchanged
## iOS Variant
### HTTP request
Remain unchanged
### HTTP response
Remain unchanged
## Sender
### HTTP request
Remain unchanged
### HTTP response
Remain unchanged
# Clients
No changes at the client side.
Thoughts?
--
abstractj
7 years, 5 months
Community release checklists
by Karel Piwko
Hi,
I've drafted a few checklists for QE to go through for community releases
(UPS, OS Cart, Cordova Push Plugin). I've put them there:
https://gist.github.com/kpiwko/9956724
Any feedback on their content is very welcomed.
As for the location, I think the best way would be to put them directly into
GH repositories, for instance into RELEASE.ad / RELEASE.md file, together with
release process instructions (not existing yet). General testing instructions,
applicable for any project, can go to aerogear-parent or aerogear-testing-tools
and be crosslinked.
Thoughts?
Thanks,
Karel
7 years, 5 months
cordova plugin release
by Erik Jan de Wit
Hi,
I would like to release another version of the cordova push plugin (next week thursday), the major feature will be the new simplified API that is already on the master branch and there have already been successful builds. Releasing it will update the version to 0.0.4 and make it available on the registry, it would also provide a test for the gradle release script.
Cheers,
Erik Jan
7 years, 5 months
Android Studio / Gradle support
by Marc Sluiter
(next try, sorry again)
Hi all,
some time ago there was already a discussion about using Android Studio / Gradle
[1], but as far as I can see nothing happened afterwards.
So I was curious if I can get the cookbook application running with Android's
new build system, and want to share what I found out so far:
My first approach was to migrate the cookbook first, and using the library as
dependency only. But that didn't work out, because the Androd dependencies in
the pom.xml of the lib could not be found. I really didn't want to install them
with the maven-android-sdk-deployer, because that's not needed anymore with the
new build system, it accesses directly the installed Android SDK.
So I migrated the lib first. The first issue was: how do I get the aar into my
local maven repository? Solution: the Gradle Android Maven plugin [2]. After
some configuration I could install the lib into my local maven repo with
"gradlew clean install". Nice.
Then I looked how I can run the Robolectric tests in the lib. That seems to be a
problem, because the Android Gradle plugin team seems to be focused on running
tests in AVDs or on real devices only [3]. Then I found another Gradle plugin to
the rescue... at least I thought: the Robolectric team itself maintains the
Gradle Android Unit Testing plugin [4], which should run JUnit and Robolectric
tests, but unfortunatly it was broken by the latest Android Gradle plugin
update... [5]. So I prepared running the tests, but had to comment out the
plugin for the moment.
So back to the cookbook: here I had to use a workaround now for accessing my
local maven repo, because the official and easy way is broken in Gradle itself
atm [6]. But with the workaround I could run the cookbook app on my device with
"gradle clean installDebug"... finally (And with the OpenShift Push Server it
was easy to test the push functionality, great!)
So my resume of this adventure:
before that I liked Android Studio very much, I used it for some little private
fun apps already, and had only few problems. It has features (e.g. product
flavors) which were more difficult to handle with maven. But I tested only by
deploying and using the apps on my own devices (shame on me, I know...), so
missing JUnit/Robolectric support was not an issue for me. And my library
project was part of the app's project (works nice with Gradle!), so no local
maven issues.
But now I think that there is still some work to do with Android Studio and the
Android Gradle plugin. Some gaps can be filled with 3rd party plugins, but the
chance that they get broken by new versions of the build system is not low,
development is very fast.
One point I forgot: I did not have a look into the Travis stuff, because I don't
know it yet.
If you are interested in my results, see here:
https://github.com/slintes/aerogear-android/tree/gradle
https://github.com/slintes/aerogear-android-cookbook/tree/gradle
Kind regards,
Marc
[1]
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-Google-s-G...
[2] https://github.com/dcendents/android-maven-plugin
[3] http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Testing
[4] https://github.com/robolectric/gradle-android-test-plugin
[5] https://github.com/robolectric/gradle-android-test-plugin/issues/8
[6] https://code.google.com/p/android/issues/detail?id=63908
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
7 years, 5 months
