<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 24, 2014 at 6:47 PM, Christos Vasilakis <span dir="ltr"><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
On Mar 24, 2014, at 6:24 PM, Tadeas Kriz <<a href="mailto:tkriz@redhat.com">tkriz@redhat.com</a>> wrote:<br>
<br>
> Hey,<br>
><br>
> I’m done with testing the new crypto. The only thing that I’ve already discussed with cvasilak is that if anyone updates to the new crypto and already had some data stored with the old one, it will crash when trying to read them. Other than that everything works.<br>
<br>
</div>For the record, unfortunately due to change of symmetic crypto to use NaCl and moving away from common crypto, old encrypted data will fail to be read with the new version. But we believe relying on NaCI for both symm/asymm encryption is the way to move forward and the main motivation for pausing this release of agios to incorporate latest crypto. As sooner we switch, the better.<br>
</blockquote><div><br></div><div>+9001 :-)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
For any user that will be affected by this, a possible dump of the old data using ‘read:all’, and reload on the new version can be an option. This downside will be documented on our release notes.<br></blockquote><div><br>
</div><div>yeah - I do not think it's a serious problem. This library is pretty young, and under active development. +1 on documentation/release notes for the issue.</div><div><br></div><div>And yeah, as you said: better sooner than later to switch :-)</div>
<div><br></div><div>Great job and thanks for the update!</div><div><br></div><div>-Matthias</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards,<br>
Christos<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> —<br>
> Tadeas Kriz<br>
><br>
> On 21 Mar 2014, at 12:43, Christos Vasilakis <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>> wrote:<br>
><br>
>> Hi everyone,<br>
>><br>
>> after discussion with Corinne, we have decided to pause the release of aerogear-ios this week, and release early next. The reason is that we would like the upcoming release to include dependency of the new aerogear-crypto changes that were incorporated this week[1], mainly the update of the symmetric encryption to use NaCI. We feel, that it makes sense to release both at the same time.<br>
>><br>
>> For aerogear-ios, a minor ‘private' API change is needed, but would like a bit of time for testing.<br>
>><br>
>> Let us know your thoughts/concerns.<br>
>><br>
>> Regards<br>
>> Christos<br>
>><br>
>> [1] <a href="https://github.com/aerogear/aerogear-crypto-ios/pull/18" target="_blank">https://github.com/aerogear/aerogear-crypto-ios/pull/18</a><br>
>><br>
>><br>
>> On Mar 18, 2014, at 9:37 AM, Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> wrote:<br>
>><br>
>>> Hello iOS Friends,<br>
>>><br>
>>> AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1).<br>
>>><br>
>>> To test it, open Podfile and point to the latest git branch<br>
>>> pod 'AeroGear', :git => '<a href="https://github.com/aerogear/aerogear-ios.git" target="_blank">https://github.com/aerogear/aerogear-ios.git</a>'<br>
>>><br>
>>> Help us make this release a success, give it a trial, and let us know how it goes for your project.<br>
>>><br>
>>> ++<br>
>>> Corinne<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>
>><br>
>><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>
><br>
><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>
<br>
<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>