<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 21, 2013 at 6:19 PM, Douglas Campos <span dir="ltr"><<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On Tue, May 21, 2013 at 06:05:00PM +0200, Matthias Wessendorf wrote:<br>
> I think I mean more the Unified Push server has the "private key", while<br>
> the device uses the public key,<br>
> to perform the "auth" against the server-side variant (e.g. PhoneABC<br>
> registers itself with the Android variant)<br>
</div>Unless you have two key pairs, this adds zero security to the mix.<br></blockquote><div><br></div><div style>Not sure I follow, but if _every_ mobile application (MobileVariantInstance) needs to perform auth against the server to register itself with the MobileVariant (e.g. the logical construct of an Android variant), how or why are two key pairs needed.</div>
<div style><br></div><div style><br></div><div style>The public/private key I had in mind is just for the MobileVariant, so that _every_ devices that know the public key, can perform auth against it.</div><div style><br></div>
<div style>As said before this key pair is ONLY for working on the data of the MobileVariantInstance(s). Not more (no sending, no PushApp/MobileVariant registration; as said before).</div><div style><br></div><div style>Not sure I understand the two key pairs here (e.g. why two)</div>
<div style><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
amirite, abstractj?<br>
<div class=""><div class="h5"><br>
--<br>
qmx<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>