News for hackers. Stuff that matters.

A comment on Reverse Engineering Native Apps by Intercepting Network Traffic. Parent comment

Re:Reverse Engineering Native Apps by Intercepting Network T... by joosters on Sunday July 31, 2016 @08:37AM (#12196702)
That's what you'd like to think, but the numerous terms & conditions that you've agreed to for your apps means that you're wrong, some data isn't yours.
[ Parent | on HN ]
Re:Reverse Engineering Native Apps by Intercepting Network T... by tokenizerrr on Monday August 01, 2016 @04:28AM (#12200901)
No, it really doesnt. Terms of service are only legally binding within the law and the EU has already ruled that reverse Engineering software on your own device is just fine.

So I'll happily keep on ignoring those tldrs.

[ Parent | on HN ]
Re:Reverse Engineering Native Apps by Intercepting Network T... by __b__ on Sunday July 31, 2016 @10:01AM (#12196991)
OK, then how do we separate the data that is his versus data that belongs to somene else? Maybe we would have to look at what is being sent from the app?
[ Parent | on HN ]
Re:Reverse Engineering Native Apps by Intercepting Network T... by joosters on Sunday July 31, 2016 @10:32AM (#12197110)
Who knows? The two things are unrelated. My comment wasn't anti-reverse engineering, just stating a fact: just because something is in your phone doesn't mean it's yours.
[ Parent | on HN ]
Re:Reverse Engineering Native Apps by Intercepting Network T... by __b__ on Sunday July 31, 2016 @12:05PM (#12197492)
The parent stated "Data generated on my phone belongs to me."

I interpreted this as "Data generated by me on my phone belongs to me."

The user could agree to license her rights to the data, e.g. via terms and conditions. But it's still her data. That's why the agreement is necessary.

None of this has anything to do with "reverse engineering".

The scenario I am thinking of is a user looking at her data being sent from her hardware over an internet connection that she is paying for.

[ Parent | on HN ]