ryhanson
Joined 14 years ago
Joined 14 years ago
Microsoft sure has come a long way over the past few years. I'm glad to see that developers are embracing it too!
Here is an open-source tool I've used in the past to do quick static security checks on APKs: https://github.com/ajinabraham/Mobile-Security-Framework-Mob...
It also supports dynamic analysis, but I haven't used that portion of it yet.
I, too, am interested in the other enterprise tools that are built on top of this though.
You should definitely avoid mixing server side and client side templates, but if that's too much work, scrubbing would work. You would need to strip the expression stand and end symbols. Default symbols are '{{' and '}}', but some apps use different symbols to avoid collisions with other template engines that use the double curly brace.
The problem ends up being that they mix server side templates with client side templates. If user input is rendered in a server side template and ends up in an element that is part of the Angular scope, the expression will evaluate. So attaching an angular controller to your body tag and then including server side templates within the body, is bad...
Being able to go from a computer with f.lux to my iPhone with f.lux will play much nicer with my eyes at night. I can literally feel the strain in my eyes when going from f.lux to no f.lux.
I'm a believer in: Just build something that works and iterate off that. Prototype rather than over-engineer. Over-engineering early is future proofing for a future that may never happen.