Sounds good?

On Monday, March 31, 2014, Bruno Oliveira <bruno@abstractj.org> wrote:

So I think we reached a dead end. If you want passphrase encryption, and they must be reversible because Apple requires it. How your workflow would look like?

1. Login
2. Register an application
3. Make use of our client to encrypt passphrase/certificate
4. Use cURL to upload the encrypted data

????

>From the developers perspective I would never use that.

If the certificate should be only provided when creating the variant inside Admin UI, you don’t need a client like discussed here (https://issues.jboss.org/browse/AGPUSH-561). Why would I need a client to encrypt files and require cURL to upload it?

--
abstractj

On March 31, 2014 at 3:16:47 PM, Matthias Wessendorf (matzew@apache.org) wrote:
> > Cä
>
> On Monday, March 31, 2014(http://airmail.calendar/2014-03-31%2012:00:00%20GMT-3),
> Matthias Wessendorf
> wrote:
> >
> >
> > On Monday, March 31, 2014(http://airmail.calendar/2014-03-31%2012:00:00%20GMT-3),
> Bruno Oliveira
> wrote:
> > > Feel free to post your questions here, sorry about that.
> > >
> > > My question is: Should the sender implement certificate upload
> as a feature?
> >
> > Nope
>
>
> The certificate should be only provided when creating the actual
> iOS variant (e.g inside the AdminUI - or its REST APIs)