diff options
| author | Android Partner Docs <noreply@android.com> | 2017-04-24 12:03:41 -0700 |
|---|---|---|
| committer | Clay Murphy <claym@google.com> | 2017-04-24 16:05:12 -0700 |
| commit | 9062ef8241bdd128e4b44e1084a74d1b8ecf9f93 (patch) | |
| tree | ee7cd663247c82e5140d436e502c289bb255813b /en/security/overview/implement.html | |
| parent | 043d60370a041acfef0f1d5715944d72992dc267 (diff) | |
| download | source.android.com-9062ef8241bdd128e4b44e1084a74d1b8ecf9f93.tar.gz | |
Docs: Changes to source.android.com
- 154078436 Correct constraint on call_site_id's in DEX format by claym <claym@google.com>
- 153880797 Attribution updates to the April public security bulletin by Android Partner Docs <noreply@android.com>
- 153847481 Updates to ASAN instructions by Android Partner Docs <noreply@android.com>
- 153776051 update to include LLVM Sanitizer information by Android Partner Docs <noreply@android.com>
- 153770085 Add Camera ITS to home by claym <claym@google.com>
- 153751709 Change link to go to Android Issue Tracker instead of the... by Android Partner Docs <noreply@android.com>
- 153612674 Add redirect from source/download to initializing by claym <claym@google.com>
- 153605118 Repalce SCS links to YIR with /reports links by daroberts <daroberts@google.com>
- 153476630 Add Zer0 conf slides to Security reports by daroberts <daroberts@google.com>
- 153208805 Add blog post note to Issue Tracker documentation by daroberts <daroberts@google.com>
- 153202288 Docs: Add camera ITS-in-a-box, new camera section by hvm <hvm@google.com>
PiperOrigin-RevId: 154078436
Change-Id: I008b9cb25646e7a4b1b154fe9f91cf2c42e9c0bc
Diffstat (limited to 'en/security/overview/implement.html')
| -rw-r--r-- | en/security/overview/implement.html | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/en/security/overview/implement.html b/en/security/overview/implement.html index bbe1967c..7233a34d 100644 --- a/en/security/overview/implement.html +++ b/en/security/overview/implement.html @@ -56,6 +56,9 @@ automated source code review. Best practices:</p> application code using the Android SDK and correct any identified issues.</li> <li>Native code should be analyzed using an automated tool that can detect memory management issues such as buffer overflows and off-by-one errors.</li> +<li>The Android build system has support for many of the LLVM sanitizers, +such as AddressSanitizer and UndefinedBehaviorSanitizer which can be used +for this purpose.</li> </ul> <h3 id="auto-test">Using automated testing</h3> |