diff options
| author | Clay Murphy <claym@google.com> | 2018-08-21 20:21:55 +0000 |
|---|---|---|
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | 2018-08-21 20:21:55 +0000 |
| commit | 1df0e249e72adda586d75f8ae7657e2ca56ab8c5 (patch) | |
| tree | 5945fd2f5ea8465b5c29deab3682a65d5c88835c | |
| parent | 080e50de3cb31822de0ba5b649e11924086b7817 (diff) | |
| parent | 04c1f72d4c8ff2763c6961b6eae77a10abc00b66 (diff) | |
| download | source.android.com-1df0e249e72adda586d75f8ae7657e2ca56ab8c5.tar.gz | |
Merge "Docs: Changes to source.android.com"
161 files changed, 9709 insertions, 2879 deletions
diff --git a/en/compatibility/9.0/android-9.0-cdd.html b/en/compatibility/9.0/android-9.0-cdd.html index 8f93b15b..e3561c86 100644 --- a/en/compatibility/9.0/android-9.0-cdd.html +++ b/en/compatibility/9.0/android-9.0-cdd.html @@ -9935,7 +9935,7 @@ </p> <ul> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/?pretty=full&no-merges">Document changelog</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/?pretty=full&no-merges">Document changelog</a> </li> </ul> <p> @@ -9943,43 +9943,43 @@ </p> <ol> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/1_introduction?pretty=full&no-merges">Introduction</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/1_introduction?pretty=full&no-merges">Introduction</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/2_device_types?pretty=full&no-merges">Device Types</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/2_device_types?pretty=full&no-merges">Device Types</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/3_software?pretty=full&no-merges">Software</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/3_software?pretty=full&no-merges">Software</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/4_application-packaging?pretty=full&no-merges">Application Packaging</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/4_application-packaging?pretty=full&no-merges">Application Packaging</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/5_multimedia?pretty=full&no-merges">Multimedia</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/5_multimedia?pretty=full&no-merges">Multimedia</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/6_dev-tools-and-options?pretty=full&no-merges">Developer Tools and Options</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/6_dev-tools-and-options?pretty=full&no-merges">Developer Tools and Options</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/7_hardware-compatibility?pretty=full&no-merges">Hardware Compatibility</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/7_hardware-compatibility?pretty=full&no-merges">Hardware Compatibility</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/8_performance-and-power?pretty=full&no-merges">Performance and Power</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/8_performance-and-power?pretty=full&no-merges">Performance and Power</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/9_security-model?pretty=full&no-merges">Security Model</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/9_security-model?pretty=full&no-merges">Security Model</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/10_software-compatibility-testing?pretty=full&no-merges">Software Compatibility Testing</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/10_software-compatibility-testing?pretty=full&no-merges">Software Compatibility Testing</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/11_updatable-software?pretty=full&no-merges">Updatable Software</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/11_updatable-software?pretty=full&no-merges">Updatable Software</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/12_document-changelog?pretty=full&no-merges">Document Changelog</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/12_document-changelog?pretty=full&no-merges">Document Changelog</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/13_contact-us?pretty=full&no-merges">Contact Us</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/13_contact-us?pretty=full&no-merges">Contact Us</a> </li> </ol> <h3 id="12_1_changelog_viewing_tips"> diff --git a/en/compatibility/android-cdd.html b/en/compatibility/android-cdd.html index 8f93b15b..e3561c86 100644 --- a/en/compatibility/android-cdd.html +++ b/en/compatibility/android-cdd.html @@ -9935,7 +9935,7 @@ </p> <ul> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/?pretty=full&no-merges">Document changelog</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/?pretty=full&no-merges">Document changelog</a> </li> </ul> <p> @@ -9943,43 +9943,43 @@ </p> <ol> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/1_introduction?pretty=full&no-merges">Introduction</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/1_introduction?pretty=full&no-merges">Introduction</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/2_device_types?pretty=full&no-merges">Device Types</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/2_device_types?pretty=full&no-merges">Device Types</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/3_software?pretty=full&no-merges">Software</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/3_software?pretty=full&no-merges">Software</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/4_application-packaging?pretty=full&no-merges">Application Packaging</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/4_application-packaging?pretty=full&no-merges">Application Packaging</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/5_multimedia?pretty=full&no-merges">Multimedia</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/5_multimedia?pretty=full&no-merges">Multimedia</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/6_dev-tools-and-options?pretty=full&no-merges">Developer Tools and Options</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/6_dev-tools-and-options?pretty=full&no-merges">Developer Tools and Options</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/7_hardware-compatibility?pretty=full&no-merges">Hardware Compatibility</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/7_hardware-compatibility?pretty=full&no-merges">Hardware Compatibility</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/8_performance-and-power?pretty=full&no-merges">Performance and Power</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/8_performance-and-power?pretty=full&no-merges">Performance and Power</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/9_security-model?pretty=full&no-merges">Security Model</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/9_security-model?pretty=full&no-merges">Security Model</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/10_software-compatibility-testing?pretty=full&no-merges">Software Compatibility Testing</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/10_software-compatibility-testing?pretty=full&no-merges">Software Compatibility Testing</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/11_updatable-software?pretty=full&no-merges">Updatable Software</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/11_updatable-software?pretty=full&no-merges">Updatable Software</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/12_document-changelog?pretty=full&no-merges">Document Changelog</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/12_document-changelog?pretty=full&no-merges">Document Changelog</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pi-dev/13_contact-us?pretty=full&no-merges">Contact Us</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/pie-dev/13_contact-us?pretty=full&no-merges">Contact Us</a> </li> </ol> <h3 id="12_1_changelog_viewing_tips"> diff --git a/en/compatibility/cts/downloads.html b/en/compatibility/cts/downloads.html index df5e21cc..b5dc66cb 100644 --- a/en/compatibility/cts/downloads.html +++ b/en/compatibility/cts/downloads.html @@ -56,96 +56,96 @@ href="https://dl.google.com/dl/android/cts/android-cts_instant-9.0_r1-linux_x86- <h2 id="android-81">Android 8.1</h2> <p>Android 8.1 is the release of the development milestone code-named Oreo-MR1. The source code for the following tests can be synced with the -'android-cts-8.1_r7' tag in the open-source tree.</p> +'android-cts-8.1_r8' tag in the open-source tree.</p> <ul> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-8.1_r7-linux_x86-arm.zip">Android -8.1 R7 Compatibility Test Suite (CTS) - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-8.1_r8-linux_x86-arm.zip">Android +8.1 R8 Compatibility Test Suite (CTS) - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-8.1_r7-linux_x86-x86.zip">Android -8.1 R7 Compatibility Test Suite (CTS) - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-8.1_r8-linux_x86-x86.zip">Android +8.1 R8 Compatibility Test Suite (CTS) - x86</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.1_r7-linux_x86-arm.zip">Android -8.1 R7 CTS Verifier - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.1_r8-linux_x86-arm.zip">Android +8.1 R8 CTS Verifier - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.1_r7-linux_x86-x86.zip">Android -8.1 R7 CTS Verifier - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.1_r8-linux_x86-x86.zip">Android +8.1 R8 CTS Verifier - x86</a></li> </ul> <h2 id="android-80">Android 8.0</h2> <p>Android 8.0 is the release of the development milestone code-named Oreo. The source code for the following tests can be synced with the -'android-cts-8.0_r11' tag in the open-source tree.</p> +'android-cts-8.0_r12' tag in the open-source tree.</p> <ul> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-8.0_r11-linux_x86-arm.zip">Android -8.0 R11 Compatibility Test Suite (CTS) - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-8.0_r12-linux_x86-arm.zip">Android +8.0 R12 Compatibility Test Suite (CTS) - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-8.0_r11-linux_x86-x86.zip">Android -8.0 R11 Compatibility Test Suite (CTS) - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-8.0_r12-linux_x86-x86.zip">Android +8.0 R12 Compatibility Test Suite (CTS) - x86</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.0_r11-linux_x86-arm.zip">Android -8.0 R11 CTS Verifier - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.0_r12-linux_x86-arm.zip">Android +8.0 R12 CTS Verifier - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.0_r11-linux_x86-x86.zip">Android -8.0 R11 CTS Verifier - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.0_r12-linux_x86-x86.zip">Android +8.0 R12 CTS Verifier - x86</a></li> </ul> <h2 id="android-71">Android 7.1</h2> <p>Android 7.1 is the release of the development milestone code-named Nougat-MR1. The source code for the following tests can be synced with the -'android-cts-7.1_r19' tag in the open-source tree.</p> +'android-cts-7.1_r20' tag in the open-source tree.</p> <ul> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-7.1_r19-linux_x86-arm.zip">Android -7.1 R19 Compatibility Test Suite (CTS) - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-7.1_r20-linux_x86-arm.zip">Android +7.1 R20 Compatibility Test Suite (CTS) - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-7.1_r19-linux_x86-x86.zip">Android -7.1 R19 Compatibility Test Suite (CTS) - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-7.1_r20-linux_x86-x86.zip">Android +7.1 R20 Compatibility Test Suite (CTS) - x86</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-7.1_r19-linux_x86-arm.zip">Android -7.1 R19 CTS Verifier - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-7.1_r20-linux_x86-arm.zip">Android +7.1 R20 CTS Verifier - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-7.1_r19-linux_x86-x86.zip">Android -7.1 R19 CTS Verifier - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-7.1_r20-linux_x86-x86.zip">Android +7.1 R20 CTS Verifier - x86</a></li> </ul> <h2 id="android-70">Android 7.0</h2> <p>Android 7.0 is the release of the development milestone code-named Nougat. The source code for the following tests can be synced with the -'android-cts-7.0_r23' tag in the open-source tree.</p> +'android-cts-7.0_r24' tag in the open-source tree.</p> <ul> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-7.0_r23-linux_x86-arm.zip">Android -7.0 R23 Compatibility Test Suite (CTS) - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-7.0_r24-linux_x86-arm.zip">Android +7.0 R24 Compatibility Test Suite (CTS) - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-7.0_r23-linux_x86-x86.zip">Android -7.0 R23 Compatibility Test Suite (CTS) - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-7.0_r24-linux_x86-x86.zip">Android +7.0 R24 Compatibility Test Suite (CTS) - x86</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-7.0_r23-linux_x86-arm.zip">Android -7.0 R23 CTS Verifier - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-7.0_r24-linux_x86-arm.zip">Android +7.0 R24 CTS Verifier - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-7.0_r23-linux_x86-x86.zip">Android -7.0 R23 CTS Verifier - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-7.0_r24-linux_x86-x86.zip">Android +7.0 R24 CTS Verifier - x86</a></li> </ul> <h2 id="android-60">Android 6.0</h2> <p>Android 6.0 is the release of the development milestone code-named Marshmallow. The source code for the following tests can be synced with the -'android-cts-6.0_r30' tag in the open-source tree.</p> +'android-cts-6.0_r31' tag in the open-source tree.</p> <ul> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-6.0_r30-linux_x86-arm.zip">Android -6.0 R30 Compatibility Test Suite (CTS) - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-6.0_r31-linux_x86-arm.zip">Android +6.0 R31 Compatibility Test Suite (CTS) - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-6.0_r30-linux_x86-x86.zip">Android -6.0 R30 Compatibility Test Suite (CTS) - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-6.0_r31-linux_x86-x86.zip">Android +6.0 R31 Compatibility Test Suite (CTS) - x86</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-6.0_r30-linux_x86-arm.zip">Android -6.0 R30 CTS Verifier - ARM</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-6.0_r31-linux_x86-arm.zip">Android +6.0 R31 CTS Verifier - ARM</a></li> <li><a -href="https://dl.google.com/dl/android/cts/android-cts-verifier-6.0_r30-linux_x86-x86.zip">Android -6.0 R30 CTS Verifier - x86</a></li> +href="https://dl.google.com/dl/android/cts/android-cts-verifier-6.0_r31-linux_x86-x86.zip">Android +6.0 R31 CTS Verifier - x86</a></li> </ul> <h2 id="android-51">Android 5.1</h2> diff --git a/en/compatibility/cts/secure-element.md b/en/compatibility/cts/secure-element.md index e827c0a0..0c3933b6 100644 --- a/en/compatibility/cts/secure-element.md +++ b/en/compatibility/cts/secure-element.md @@ -35,82 +35,44 @@ Elements (essentially checks if devices have SE HAL implementation and if yes, how many). This is used as the basis to test the API and the underlying Secure Element implementation. -## Terminology - -<table> -<thead> -<tr> -<th>Term</th> -<th>Definition</th> -</tr> -</thead> -<tbody> -<tr> -<td>AID</td> -<td>Application Identifier</td> -</tr> -<tr> -<td>APDU</td> -<td>Application Protocol Data Unit</td> -</tr> -<tr> -<td>BER</td> -<td>Basic Encoding Rules</td> -</tr> -<tr> -<td>TLV</td> -<td>Tag Length Value</td> -</tr> -<tr> -<td>UICC </td> -<td>UMTS Integrated Circuit Card</td> -</tr> -<tr> -<td>ARA</td> -<td>Access Rule Application Master</td> -</tr> -<tr> -<td>ARF</td> -<td>Access Rule File</td> -</tr> -<tr> -<td>Applet</td> -<td>Java Card application on Secure Element</td> -</tr> -</tbody> -</table> - ## Open Mobile API test cases -Open Mobile API test cases are used to enforce API guidelines and to confirm the +Open Mobile API (OMAPI) test cases are used to enforce API guidelines and to +confirm the underlying implementation of Secure Elements meets the Open Mobile API -specification. These test cases require installation of a special applet that +specification. These test cases require installation of a special applet, a Java +Card application on Secure Element, that is used by the CTS application for communication. For installation, use the sample applet found in -[CtsAndroidOmapiTestApplet.java](https://android.googlesource.com/platform/cts/+/master/tests/tests/secure_element/sample_applet/src/com/android/cts/omapi/test/CtsAndroidOmapiTestApplet.java){: .external} and [test.cap](https://android.googlesource.com/platform/cts/+/master/tests/tests/secure_element/sample_applet/test.cap){: .external}. +[`CtsAndroidOmapiTestApplet.java`](https://android.googlesource.com/platform/cts/+/master/tests/tests/secure_element/sample_applet/src/com/android/cts/omapi/test/CtsAndroidOmapiTestApplet.java){: .external} +and +[`test.cap`](https://android.googlesource.com/platform/cts/+/master/tests/tests/secure_element/sample_applet/test.cap){: .external}. To pass OMAPI test cases, the underlying Secure Element Service and the SE should be capable of the following: <ol> -<li>All Secure Element Reader names should start with SIM or eSE or SD.</li> +<li>All Secure Element Reader names should start with SIM, eSE, or SD.</li> <li>Non-SIM based readers should be capable of opening basic channels.</li> -<li><p><code>CtsOmapiTestCases.apk</code> should be capable of selecting an -applet with the following AIDs:</p> +<li><code>CtsOmapiTestCases.apk</code> should not be capable of selecting the +A000000476416E64726F6964435453FF AID:</li> +<li><code>CtsOmapiTestCases.apk</code> should be capable of selecting an +applet with the following application identifiers (AIDs): <ol> - <li><p>0xA000000476416E64726F696443545331</p> + <li>0xA000000476416E64726F696443545331 <ol> - <li><p>The applet should throw a Security Exception when it receives the - following APDUs in android.se.omapi.Channel.Transmit (hereby referred to - as <em>Transmit</em>):</p> + <li>The applet should throw a Security Exception when it receives the + following application protocol data unit (APDUs) in + <code>android.se.omapi.Channel.Transmit</code> + (<em>Transmit</em>): <ol> <li>0x00700000</li> <li>0x00708000</li> <li>0x00A40404104A535231373754657374657220312E30</li> </ol> </li> - <li><p>The applet should return no data when it receives the following - APDUs in<em> Transmit</em>:</p> + <li>The applet should return no data when it receives the following + APDUs in <em>Transmit</em>: <ol> <li>0x00060000</li> <li>0x80060000</li> @@ -122,8 +84,8 @@ applet with the following AIDs:</p> <li>0x940A000001AA</li> </ol> </li> - <li><p>The applet should return 256 byte data for the following - <em>Transmit</em> APDUs:</p> + <li>The applet should return 256-byte data for the following + <em>Transmit</em> APDUs: <ol> <li>0x0008000000</li> <li>0x8008000000</li> @@ -134,8 +96,8 @@ applet with the following AIDs:</p> <li>0xA00C000001AA00</li> <li>0x940C000001AA00</li> </ol> - <li><p>The applet should return the following Status word responses for - the respective <em>Transmit</em> APDU:</p> + <li>The applet should return the following status word responses for + the respective <em>Transmit</em> APDU: <table> <thead> <tr> @@ -467,14 +429,14 @@ applet with the following AIDs:</p> </tr> </tbody> </table> - <p class="note"><strong>Note:</strong> The response should contain data + <small>*The response should contain data that is the same as input APDU, - except the first byte is 0x01 instead of 0x00.</p> + except the first byte is 0x01 instead of 0x00.</small> </li> - <li><p>The applet should return Segmented responses of size 2048 bytes for + <li>The applet should return segmented responses of size 2048 bytes for commands a,b,c,d, f and g whereas 32767 bytes for APDU(e), with last - data byte being 0xFF and success status word<0x9000> for the following - APDUs:</0x9000></p> + data byte being 0xFF and success status word <0x9000> for the following + APDUs: <ol> <li>0x00C2080000</li> <li>0x00C4080002123400</li> @@ -486,22 +448,16 @@ applet with the following AIDs:</p> </ol> </li> <li>The applet should return success status word <0x9000> for the given - APDU: 0x00F40000</li> + APDU: 0x00F40000</li> </ol> - <li><p>A000000476416E64726F696443545332</p> + <li>A000000476416E64726F696443545332 <ol> - <li><p>This AID when selected should return a select response greater than - 2 bytes that are correctly BER TLV formatted.</p></li> + <li>When selected, this AID should return a select response greater than + 2 bytes that are correctly formatted using Basic Encoding Rules (BER) and + tag-length-value (TLV).</li> </ol> </li> </ol> - -<li><p><code>CtsOmapiTestCases.apk</code> should not be capable of selecting the -following AID:</p> - <ol> - <li>A000000476416E64726F6964435453FF</li> - </ol> -</li> </ol> ## Access Control test cases @@ -509,14 +465,14 @@ following AID:</p> Access Control uses configured in the Secure Element ensure that only the application with access to an applet can communicate with it. Additionally, Android supports configuring rules for specific APDUs that can be exchanged by -the APK. The following tests will require the device manufacturer to configure -special Access Control Rules (either ARA or ARF) to pass. +the APK. -We recommend using the same applet that is used for OMAPI tests (see applet -functional behavior described in Open Mobile API test cases section) as the same +To pass these tests, configure special Access Control Rules, either Access Rule +Application Master (ARA) or Access Rule File (ARF). You should use the applet +that is used for [OMAPI tests](#open_mobile_api_test_cases) as the same commands need to be supported to pass the Access Control tests. -You must create an instance of the applet under each of the following AIDs: +Create an instance of the applet under these AIDs: - 0xA000000476416E64726F696443545340 - 0xA000000476416E64726F696443545341 @@ -533,15 +489,15 @@ You must create an instance of the applet under each of the following AIDs: - 0xA000000476416E64726F69644354534E - 0xA000000476416E64726F69644354534F -### 1. `CtsSecureElementAccessControlTestCases1` +### `CtsSecureElementAccessControlTestCases1` -- Hash of the APK: 0x4bbe31beb2f753cfe71ec6bf112548687bb6c34e -- Authorized AIDs +- **Hash of the APK:** 0x4bbe31beb2f753cfe71ec6bf112548687bb6c34e +- **Authorized AIDs** - 0xA000000476416E64726F696443545340 - 1. Authorized APDU for above AID: 0x00060000A0060000 - 1. Unauthorized APDUs for above AID: + 1. Authorized APDU: 0x00060000A0060000 + 1. Unauthorized APDUs: 1. 0x0008000000 1. 0x80060000 @@ -550,14 +506,14 @@ You must create an instance of the applet under each of the following AIDs: - 0xA000000476416E64726F696443545341 - 1. Authorized APDUs for above AID: + 1. Authorized APDUs: 1. 0x94060000 1. 0x9408000000 1. 0x940C000001AA00 1. 0x940A000001AA - 1. Unauthorized APDUs for above AID: + 1. Unauthorized APDUs: 1. 0x00060000 1. 0x80060000 @@ -596,24 +552,24 @@ You must create an instance of the applet under each of the following AIDs: - 0xA000000476416E64726F69644354534F -- Unauthorized AID: +- **Unauthorized AIDs** - 0xA000000476416E64726F696443545343 - 0xA000000476416E64726F696443545346 -### 2. `CtsSecureElementAccessControlTestCases2` +### `CtsSecureElementAccessControlTestCases2` -- Hash of the APK: 0x93b0ff2260babd4c2a92c68aaa0039dc514d8a33 -- Authorized AIDs: +- **Hash of the APK:** 0x93b0ff2260babd4c2a92c68aaa0039dc514d8a33 +- **Authorized AIDs:** - 0xA000000476416E64726F696443545340 - 1. Authorized APDU for the above AID: + 1. Authorized APDUs: 1. 0x00060000 1. 0xA0060000 - 1. Unauthorized APDU for the above AID: + 1. Unauthorized APDUs: 1. 0x0008000000 1. 0x80060000 @@ -622,14 +578,14 @@ You must create an instance of the applet under each of the following AIDs: - 0xA000000476416E64726F696443545341 - 1. Authorized APDU for the above AID: + 1. Authorized APDUs: 1. 0x94060000 1. 0x9408000000 1. 0x940C000001AA00 1. 0x940A000001AA - 1. Unauthorized APDU for the above AID: + 1. Unauthorized APDUs: 1. 0x0006000 1. 0x80060000 @@ -650,7 +606,7 @@ You must create an instance of the applet under each of the following AIDs: - 0xA000000476416E64726F696443545346 -- Unauthorized AIDs: +- **Unauthorized AIDs** - 0xA000000476416E64726F696443545342 - 0xA000000476416E64726F696443545344 @@ -663,14 +619,14 @@ You must create an instance of the applet under each of the following AIDs: - 0xA000000476416E64726F69644354534E - 0xA000000476416E64726F69644354534F -### 3. `CtsSecureElementAccessControlTestCases3` +### `CtsSecureElementAccessControlTestCases3` -- Hash of the APK: 0x5528ca826da49d0d7329f8117481ccb27b8833aa -- Authorized AIDs: +- **Hash of the APK:** 0x5528ca826da49d0d7329f8117481ccb27b8833aa +- **Authorized AIDs:** - 0xA000000476416E64726F696443545340 - 1. Authorized APDU for the above AID: + 1. Authorized APDUs: 1. 0x00060000 1. 0x80060000 @@ -691,14 +647,14 @@ You must create an instance of the applet under each of the following AIDs: - 0xA000000476416E64726F696443545341 - 1. Authorized APDU for the above AID: + 1. Authorized APDUs: 1. 0x94060000 1. 0x9408000000 1. 0x940C000001AA00 1. 0x940A00000aAA - 1. Unauthorized APDU for the above AID: + 1. Unauthorized APDUs: 1. 0x00060000 1. 0x80060000 @@ -717,7 +673,7 @@ You must create an instance of the applet under each of the following AIDs: - 0xA000000476416E64726F696443545346 -- Unauthorized AIDs: +- **Unauthorized AIDs** - 0xA000000476416E64726F696443545342 - 0xA000000476416E64726F696443545343 @@ -733,26 +689,26 @@ You must create an instance of the applet under each of the following AIDs: ## Appendix -### Sample applet and installation steps for UICC +### Sample applet and installation steps for UMTS Integrated Circuit Card (UICC) #### 1. Package specification -File name: `google-cardlet.cap` +**File name:** `google-cardlet.cap` -Package AID: 6F 6D 61 70 69 63 61 72 64 6C 65 74 -Version: 1.0 -SHA1: 5F72E0A073BA9E61A7358F2FE3F031 -SHA256: ECC1217AA0BC687DD89D5BB233F743 +**Package AID:** 6F 6D 61 70 69 63 61 72 64 6C 65 74 +**Version:** 1.0 +**SHA1:** 5F72E0A073BA9E61A7358F2FE3F031 +**SHA256:** ECC1217AA0BC687DD89D5BB233F743 -Module AIDs: -6F 6D 61 70 69 4A 53 52 31 37 37 = SelectResponse module +**Module AIDs:** +6F 6D 61 70 69 4A 53 52 31 37 37 = SelectResponse module 6F 6D 61 70 69 43 61 63 68 69 6E 67 = XXLResponse module -Imports: +**Imports:** javacard.framework v1.3 - A0000000620101 java.lang v1.0 - A0000000620001 -Size on card: 4463 +**Size on card:** 4463 #### 2. Installation steps @@ -766,18 +722,19 @@ Run installation command for each applet. Command to install applet <code>80E60C00300C6F6D617069636172646C65740B<var>module_AID</var>10<var>AID</var>010002C90000</code><br> -Module_AID => 6F 6D 61 70 69 4A 53 52 31 37 37 -AID: A000000476416E64726F696443545331 +**Module_AID**: 6F 6D 61 70 69 4A 53 52 31 37 37 +**AID:** A000000476416E64726F696443545331 + <code>80E60C00310C6F6D617069636172646C65740B<var>module_AID</var>10<var>AID</var>010002C9000</code><br> -Module_AID => 6F 6D 61 70 69 43 61 63 68 69 6E 67 -AID: A000000476416E64726F696443545332 +**Module_AID**: 6F 6D 61 70 69 43 61 63 68 69 6E 67 +**AID:** A000000476416E64726F696443545332 ##### AccessControl tests (template using PKCS#15 structure) <code>80E60C003C0C6F6D617069636172646C65740B<var>module_AID</var>10<var>AID</var>01000EEF0AA008810101A5038201C0C90000</code><br> -Module_AID => 6F 6D 61 70 69 4A 53 52 31 37 37 +**Module_AID**: 6F 6D 61 70 69 4A 53 52 31 37 37 -AIDs: +**AIDs:** + 0xA000000476416E64726F696443545340 + 0xA000000476416E64726F696443545341 diff --git a/en/compatibility/cts/sensor-fusion-box-assembly.md b/en/compatibility/cts/sensor-fusion-box-assembly.md index adba778f..29780cf0 100644 --- a/en/compatibility/cts/sensor-fusion-box-assembly.md +++ b/en/compatibility/cts/sensor-fusion-box-assembly.md @@ -34,7 +34,7 @@ vendors. 990 Richard Ave, Ste 103, Santa Clara, CA 95050 fred@acuspecinc.com * *MYWAY DESIGN* - Website: http://www.myway.tw/ + Website: [http://www.myway.tw/](http://www.myway.tw/){: .external} Fu-ming (Troy) Tsai, tsaifuming0205@gmail.com ## Building a Sensor Fusion Box @@ -64,7 +64,7 @@ stickers to the plastic box components: 1. Apply vinyl on the smooth side of the ABS (acrylonitrile butadiene styrene) as shown in **Figure 2**. For helpful tips on applying vinyl, refer to - [wikiHow](https://www.wikihow.com/Install-a-Vinyl-Graphic). + [wikiHow](https://www.wikihow.com/Install-a-Vinyl-Graphic){: .external}. 1. Cut out the necessary holes on the vinyl. <img src="images/sensor_fusion_assembly_abs_pieces.png" width="350" alt="BS pieces"> diff --git a/en/compatibility/vts/automated-test-infra.html b/en/compatibility/vts/automated-test-infra.html index 8d6d30d9..cc4da178 100644 --- a/en/compatibility/vts/automated-test-infra.html +++ b/en/compatibility/vts/automated-test-infra.html @@ -40,7 +40,7 @@ <p> <img src="images/vts-automated.png" alt="Automated test architecture" - title="Automated test architecture""> + title="Automated test architecture"> </p> <figcaption> <strong>Figure 1.</strong> VTS automated testing infrastructure architecture diff --git a/en/compatibility/vts/hal-testability.html b/en/compatibility/vts/hal-testability.html index cf534574..ecbe6175 100644 --- a/en/compatibility/vts/hal-testability.html +++ b/en/compatibility/vts/hal-testability.html @@ -143,7 +143,7 @@ android.hardware.nfc@1.0::I*/* (/vendor/lib64/hw/) <p> <img src="images/testability-check-compliance.png" alt="Testability check for compliance" - title="Testability check for compliance""> + title="Testability check for compliance"> </p> <figcaption> <strong>Figure 1.</strong> Testability check for VTS compliance tests diff --git a/en/devices/_toc-connectivity.yaml b/en/devices/_toc-connectivity.yaml index 239f5bc5..833b600a 100644 --- a/en/devices/_toc-connectivity.yaml +++ b/en/devices/_toc-connectivity.yaml @@ -9,6 +9,8 @@ toc: path: /devices/bluetooth/services - title: Bluetooth Low Energy path: /devices/bluetooth/ble + - title: BLE for Hearing Aids + path: /devices/bluetooth/asha - title: BLE Advertising path: /devices/bluetooth/ble_advertising - title: Verifying and Debugging Bluetooth @@ -61,6 +63,8 @@ toc: path: /devices/tech/connect/wifi-overview - title: Wi-Fi HAL path: /devices/tech/connect/wifi-hal + - title: Wi-Fi Infrastructure Features + path: /devices/tech/connect/wifi-infrastructure - title: STA/AP Concurrency path: /devices/tech/connect/wifi-sta-ap-concurrency - title: MAC Randomization diff --git a/en/devices/architecture/hidl-java/index.html b/en/devices/architecture/hidl-java/index.html index 45eefc7d..d56fd1cc 100644 --- a/en/devices/architecture/hidl-java/index.html +++ b/en/devices/architecture/hidl-java/index.html @@ -48,20 +48,19 @@ version 1.0 that is registered as service name <code>foo-bar</code>:</p> <ul> <li>Add the following to Android.mk: -<pre class="prettyprint">LOCAL_JAVA_LIBRARIES += android.hardware.foo-V1.0-java</pre> +<pre class="prettyprint">LOCAL_STATIC_JAVA_LIBRARIES += android.hardware.foo-V1.0-java</pre> <strong>OR</strong><br> </li> <li>Add the following to Android.bp: <pre class="prettyprint"> -shared_libs: [ +static_libs: [ /* … */ "android.hardware.foo-V1.0-java", ], </pre> -The static version of the library is also available as -<code>android.hardware.foo-V1.0-java-static</code>.</li> +</li> </ul> </li> <li>Add the following to your Java file: @@ -117,7 +116,7 @@ stubs conform to the interface).</p> <p><code>-Lmakefile</code> generates the rules that run this command at build time and allow you to include -<code>android.hardware.foo-V1.0-java(-static)?</code> and link against the +<code>android.hardware.foo-V1.0-java</code> and link against the appropriate files. A script that automatically does this for a project full of interfaces can be found at <code>hardware/interfaces/update-makefiles.sh</code>. The paths in this example are relative; hardware/interfaces can be a temporary diff --git a/en/devices/architecture/hidl/versioning.html b/en/devices/architecture/hidl/versioning.html index c67910d9..fe4ec95d 100644 --- a/en/devices/architecture/hidl/versioning.html +++ b/en/devices/architecture/hidl/versioning.html @@ -219,7 +219,7 @@ as a method parameter), use the fully-qualified type name:</p> (e.g., <code>android.hardware.nfc</code>).</li> <li><code><var>VERSION</var></code> is the dot-separated major.minor-version format of the package (e.g., <code>1.0</code>).</li> -<li><code><var>UDT</var></code> is the the dot-separated name of a HIDL UDT. +<li><code><var>UDT</var></code> is the dot-separated name of a HIDL UDT. Since HIDL supports nested UDTs and HIDL interfaces can contain UDTs (a type of nested declaration), dots are used to access the names.</li> </ul> @@ -656,10 +656,12 @@ enum Brightness : @1.0::Brightness { AUTOMATIC }; enum Color : @1.0::Brightness { HW_GREEN, RAINBOW }; </pre> -<p>Unless a method warrants a new name, it should be named similarly to what it -is extending. For example, the method <code>foo_1_1</code> in -<code>@1.1::IFoo</code> may replace the functionality of the <code>foo</code> -method in <code>@1.0::IFoo</code>.</p> +<p>If a method can have a new semantic name (for instance +<code>fooWithLocation</code>) then that is preferred. Otherwise, it should be +named similarly to what it is extending. For example, the method +<code>foo_1_1</code> in <code>@1.1::IFoo</code> may replace the functionality +of the <code>foo</code> method in <code>@1.0::IFoo</code> if there is no better +alternative name.</p> <h2 id=package-ext>Package-level versioning</h2> <p>HIDL versioning occurs at the package level; after a package is published, it diff --git a/en/devices/architecture/kernel/config.html b/en/devices/architecture/kernel/config.html index 49ae7e1d..94cba30d 100644 --- a/en/devices/architecture/kernel/config.html +++ b/en/devices/architecture/kernel/config.html @@ -5,6 +5,7 @@ <meta name="book_path" value="/_book.yaml" /> </head> <body> + {% include "_versions.html" %} <!-- Copyright 2017 The Android Open Source Project @@ -22,74 +23,125 @@ --> -<p>Use the following configuration settings as a base for an Android kernel -configuration. Settings are organized into <code>android-base</code>, -<code>android-base-<arch></code>, and <code>android-recommended</code> -.cfg files:</p> +<p> + Use the following configuration settings as a base for an Android kernel + configuration. Settings are organized into <code>android-base</code>, + <code>android-base-<var>ARCH</var></code>, and + <code>android-recommended</code> .cfg files: +</p> <ul> -<li><code>android-base</code>. These options enable core Android features and -should be configured as specified by all devices.</li> -<li><code>android-base-<arch></code>. These options enable core Android -features and should be configured as specified by all devices of architecture -<arch>. Not all architectures have a corresponding file of -architecture-specific required options. If your architecture does not have a -file, it does not have any additional architecture-specific kernel configuration -requirements for Android.</li> -<li><code>android-recommended</code>. These options enable advanced Android -features and are optional for devices.</li> + <li><code>android-base</code>. These options enable core Android features and + should be configured as specified by all devices.</li> + <li><code>android-base-<var>ARCH</var></code>. These options enable core + Android features and should be configured as specified by all devices of + architecture <var>ARCH</var>. Not all architectures have a corresponding file + of architecture-specific required options. If your architecture does not have + a file, it does not have additional architecture-specific kernel configuration + requirements for Android.</li> + <li><code>android-recommended</code>. These options enable advanced Android + features and are optional for devices.</li> </ul> -<p>These configuration files are located in the -<code><a href="https://android.googlesource.com/kernel/configs/" class="external">kernel/configs</a></code> -repo. Use the set of configuration files that corresponds to the version of the -kernel you are using.</p> +<p> + These configuration files are located in the + <code><a href="https://android.googlesource.com/kernel/configs/" class="external">kernel/configs</a></code> + repo. Use the set of configuration files that corresponds to the version of + the kernel you are using. +</p> -<p>For details on controls already undertaken to strengthen the kernel on your -devices, see <a href="/security/overview/kernel-security.html">System -and Kernel Security</a>. For details on required settings, see the -<a href="/compatibility/cdd.html">Android Compatibility Definition -Document (CDD)</a>.</p> +<p> + For details on controls already undertaken to strengthen the kernel on your + devices, see <a href="/security/overview/kernel-security.html">System and + Kernel Security</a>. For details on required settings, see the + <a href="/compatibility/cdd.html">Android Compatibility Definition Document + (CDD)</a>. +</p> <h2 id="generating">Generating kernel config</h2> -<p>For devices that have a minimalist defconfig, you can use the -<code>merge_config.sh</code> script in the kernel tree to enable options:</p> + +<p> + For devices that have a minimalist <code>defconfig</code>, use the + <code>merge_config.sh</code> script in the kernel tree to enable options: +</p> <pre class="devsite-click-to-copy"> -ARCH=<arch> scripts/kconfig/merge_config.sh <...>/device_defconfig <...>/android-base.cfg <...>/android-base-<arch>.cfg <...>/android-recommended.cfg +ARCH=<var>ARCH</var> scripts/kconfig/merge_config.sh <...>/device_defconfig <...>/android-base.cfg <...>/android-base-<var>ARCH</var>.cfg <...>/android-recommended.cfg </pre> -<p>This generates a <code>.config</code> file you can use to save a new -defconfig or compile a new kernel with Android features enabled.</p> +<p> + This generates a <code>.config</code> file you can use to save a new + <code>defconfig</code> or compile a new kernel with Android features enabled. +</p> + +<h2 id="additional-kernel-reqs">Additional kernel config requirements</h2> + +<p> + In some cases, the platform maintainer can choose from multiple kernel + features to satisfy an Android dependency. Such dependencies cannot be + expressed in the kernel config fragment files (described above) because the + format for those files does not support logical expressions. In Android + {{ androidPVersionNumber }}, + <a href="/compatibility/cts/">Compatibility Test Suite (CTS)</a> and + <a href="/compatibility/vts/">Vendor Test Suite (VTS)</a> verify the following + requirements are satisfied: +</p> + +<ul> + <li><code>CONFIG_OF=y</code> or <code>CONFIG_ACPI=y</code></li> + <li>4.4 and 4.9 kernels have <code>CONFIG_ANDROID_LOW_MEMORY_KILLER=y</code> + OR have both <code>CONFIG_MEMCG=y</code> and <code>CONFIG_MEMCG_SWAP=y</code> + </li> + <li><code>CONFIG_DEBUG_RODATA=y</code> or + <code>CONFIG_STRICT_KERNEL_RWX=y</code></li> + <li><code>CONFIG_DEBUG_SET_MODULE_RONX=y</code> or + <code>CONFIG_STRICT_MODULE_RWX=y</code></li> + <li>For ARM64 only: <code>CONFIG_ARM64_SW_TTBR0_PAN=y</code> or + <code>CONFIG_ARM64_PAN=y</code></li> +</ul> + +<p> + In addition, the <code>CONFIG_INET_UDP_DIAG</code> option must be set to + <code>y</code> for 4.9 kernels in Android {{ androidPVersionNumber }}. +</p> <h2 id="usb">Enabling USB host mode options</h2> -<p>For USB host mode audio, enable the following options:</p> +<p> + For USB host mode audio, enable the following options: +</p> + <pre class="devsite-click-to-copy"> CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=y # CONFIG_USB_AUDIO is for a peripheral mode (gadget) driver </pre> -<p>For USB host mode MIDI, enable the following option:</p> -<pre class="devsite-click-to-copy"> -CONFIG_SND_USB_MIDI=y -</pre> +<p> + For USB host mode MIDI, enable the following option: +</p> + +<pre class="devsite-click-to-copy">CONFIG_SND_USB_MIDI=y</pre> <h2 id="Seccomp-BPF-TSYNC">Seccomp-BPF with TSYNC</h2> -<p>Seccomp-BPF is a kernel security technology that enables the creation of -sandboxes to restrict the system calls a process is allowed to make. The TSYNC -feature enables the use of Seccomp-BPF from multithreaded programs. This ability -is limited to architectures that have seccomp support upstream: ARM, ARM64, x86, -and x86_64.</p> - -<h3 id="backport-ARM-32">Backporting for Kernel 3.10 for ARM-32, X86, X86_64</h3> - -<p>Ensure that <code>CONFIG_SECCOMP_FILTER=y</code> is enabled in the Kconfig -(verified as of the Android 5.0 CTS), then cherry-pick the following changes -from the AOSP kernel/common:android-3.10 repository: -<a href="https://android.googlesource.com/kernel/common/+log/9499cd23f9d05ba159 -fac6d55dc35a7f49f9ce76..a9ba4285aa5722a3b4d84888e78ba8adc0046b28" class="external">9499cd23f9d05ba159fac6d55dc35a7f49f9ce76..a9ba4285aa5722a3b4d84888e78ba8adc0046b28</a> + +<p> + Seccomp-BPF is a kernel security technology that enables the creation of + sandboxes to restrict the system calls a process is allowed to make. The + TSYNC feature enables the use of Seccomp-BPF from multithreaded programs. This + ability is limited to architectures that have seccomp support upstream (ARM, + ARM64, x86, and x86_64). +</p> + +<h3 id="backport-ARM-32">Backporting for kernel 3.10 for ARM-32, X86, +X86_64</h3> + +<p> + Ensure <code>CONFIG_SECCOMP_FILTER=y</code> is enabled in the + <code>Kconfig</code> (verified as of the Android 5.0 CTS), then cherry-pick + the following changes from the + <a href="https://android.googlesource.com/kernel/common/+log/9499cd23f9d05ba159fac6d55dc35a7f49f9ce76..a9ba4285aa5722a3b4d84888e78ba8adc0046b28" class="external">AOSP + kernel/common:android-3.10 repository</a>: </p> <ul> @@ -127,9 +179,13 @@ ARM: add seccomp syscall</a> by Kees Cook</li> </ul> <h3 id="backport-ARM-64">Backporting for Kernel 3.10 for ARM-64</h3> -<p>Ensure <code>CONFIG_SECCOMP_FILTER=y</code> is enabled in the Kconfig -(verified as of the Android 5.0 CTS), then cherry-pick the following changes -from the AOSP kernel/common:android-3.10 repository:</p> + +<p> + Ensure <code>CONFIG_SECCOMP_FILTER=y</code> is enabled in the + <code>Kconfig</code> (verified as of the Android 5.0 CTS), then cherry-pick + the following changes from the AOSP kernel/common:android-3.10 repository: +</p> + <ul> <li><a href="https://android.googlesource.com/kernel/common/+/cfc7e99e9e3900056028a7d90072e9ea0d886f8d" class="external">cfc7e99e9 arm64: Add __NR_* definitions for compat syscalls</a> by JP Abgrall</li> diff --git a/en/devices/architecture/vintf/dm.html b/en/devices/architecture/vintf/dm.html index 091094dc..28884749 100644 --- a/en/devices/architecture/vintf/dm.html +++ b/en/devices/architecture/vintf/dm.html @@ -126,7 +126,7 @@ with. To bump the Target FCM Version of a device, vendors need to:</p> <li>Modify HAL Versions in the device manifest file.</li> <li>Modify the Target FCM Version in the device manifest file.</li> <li>Remove deprecated HAL versions.</li> -<li>For devices launched with {{ androidPVersionNumber }} or older, cherry-pick +<li>For devices launched with Android {{ androidPVersionNumber }} or lower, cherry-pick these CLs before generating OTA update packages: <ul> <li><a href="https://android-review.googlesource.com/722283">CL 722283</a></li> diff --git a/en/devices/architecture/vintf/match-rules.html b/en/devices/architecture/vintf/match-rules.html index dd79254b..b34b2190 100644 --- a/en/devices/architecture/vintf/match-rules.html +++ b/en/devices/architecture/vintf/match-rules.html @@ -4,6 +4,7 @@ <meta name="project_path" value="/_project.yaml" /> <meta name="book_path" value="/_book.yaml" /> </head> + {% include "_versions.html" %} <body> <!-- Copyright 2017 The Android Open Source Project @@ -390,6 +391,38 @@ ro.boot.avb_version == 2.3 && ro.boot.vbmeta.avb_version == 2.1 <font style="font-family: Roboto, Arial, Helvetica, sans-serif; background-color: green; color: white"> match </font> </pre> +<h3 id="avb-version-ota">Matching AVB version during OTA</h3> +<p>For devices launched with Android {{ androidPVersionNumber }} or lower, during OTA, the AVB +version requirements in framework compatibility matrix are matched against the current AVB version +on the device. If the AVB version has an major version upgrade during an OTA (for example, from +0.0 to 1.0), the check in OTA does not reflect the compatibility after the OTA.</p> +<p>To mitigate the issue, an OEM can place a fake AVB version in the OTA package +(<code>compatibility.zip</code>) to pass the check. To do so:</p> +<ol> +<li>Cherry-pick the following CLs to the Android {{ androidPVersionNumber }} source tree: +<ul> + <li><a href="https://android-review.googlesource.com/732261" class="external">CL 732261</a></li> + <li><a href="https://android-review.googlesource.com/732262" class="external">CL 732262</a></li> +</ul> +</li> +<li>Define <code>BOARD_OTA_FRAMEWORK_VBMETA_VERSION_OVERRIDE</code> for the device. Its value +should equal the AVB version before the OTA, i.e. the AVB version of the device when it was +launched.</li> +<li>Rebuild the OTA package.</li> +</ol> +<p>These changes automatically place +<code>BOARD_OTA_FRAMEWORK_VBMETA_VERSION_OVERRIDE</code> as +<code>compatibility-matrix.avb.vbmeta-version</code> in the following files: +<ul> + <li><code>/system/compatibility_matrix.xml</code> + (which is not used in Android {{ androidPVersionNumber }}) on the device</li> + <li><code>system_matrix.xml</code> in <code>compatibility.zip</code> in the OTA package</li> +</ul> +These changes do not affect other framework compatibility matrices, including +<code>/system/etc/vintf/compatibility_matrix.xml</code>. After the OTA, the new value in +<code>/system/etc/vintf/compatibility_matrix.xml</code> is used for compatibility checks instead. +</p> + <h2 id="vndk">VNDK version matches</h2> <p>The device compatibility matrix declares the required VNDK version in <code>compatibility-matrix.vendor-ndk.version</code>. If the device diff --git a/en/devices/audio/latency/latency.html b/en/devices/audio/latency/latency.html index 03dabb64..27b6d555 100644 --- a/en/devices/audio/latency/latency.html +++ b/en/devices/audio/latency/latency.html @@ -39,31 +39,31 @@ </tr> <tr> <td>Common causes of audio latency</td> - <td><a href="latency_contrib.html">Contributors to Audio Latency</a></td> + <td><a href="/devices/audio/latency/contrib.html">Contributors to Audio Latency</a></td> </tr> <tr> <td>Android's audio latency-reduction efforts</td> - <td><a href="latency_design.html">Design For Reduced Latency</a></td> + <td><a href="/devices/audio/latency/design.html">Design For Reduced Latency</a></td> </tr> <tr> <td>Techniques to measure audio latency</td> <td> - <a href="latency_measure.html">Measuring Audio Latency</a><br /> - <a href="testing_circuit.html">Light Testing Circuit</a><br /> - <a href="loopback.html">Audio Loopback Dongle</a> + <a href="/devices/audio/latency/measure.html">Measuring Audio Latency</a><br /> + <a href="/devices/audio/latency/testing_circuit.html">Light Testing Circuit</a><br /> + <a href="/devices/audio/latency/loopback.html">Audio Loopback Dongle</a> </td> </tr> <tr> <td>Round-trip audio latency results</td> - <td><a href="latency_measurements.html">Audio Latency Measurements</a></td> + <td><a href="/devices/audio/latency/measurements.html">Audio Latency Measurements</a></td> </tr> <tr> <td>Applications</td> - <td><a href="latency_app.html">Audio Latency for App Developers</a></td> + <td><a href="/devices/audio/latency/app.html">Audio Latency for App Developers</a></td> </tr> <tr> <td>AAudio and MMAP</td> - <td><a href="aaudio.html">AAudio for OEMs and SoC Vendors</a></td> + <td><a href="/devices/audio/aaudio.html">AAudio for OEMs and SoC Vendors</a></td> </table> </body> diff --git a/en/devices/audio/latency/measure.html b/en/devices/audio/latency/measure.html index aa703140..44cba6c3 100644 --- a/en/devices/audio/latency/measure.html +++ b/en/devices/audio/latency/measure.html @@ -34,7 +34,8 @@ <p> There are several techniques available to measure output latency, with varying degrees of accuracy and ease of running, described below. Also -see the <a href="testing_circuit.html">Testing circuit</a> for an example test environment. +see the <a href="/devices/audio/latency/testing_circuit.html">Testing circuit</a> + for an example test environment. </p> <h3 id="ledTest">LED and oscilloscope test</h3> @@ -68,7 +69,7 @@ If your production device does not have an LED, you can install the the same time it outputs audio. <p class="note"><strong>Note:</strong> To get useful results, it is crucial to use the correct APIs in the test app so that you're exercising the fast audio output path. - See <a href="latency_design.html">Design For Reduced Latency</a> for + See <a href="/devices/audio/latency/design.html">Design For Reduced Latency</a> for background.</p> </li> <li>Place a light sensor next to the LED.</li> @@ -134,7 +135,8 @@ located in the <code>audio_utils</code> library. <h3 id="loopback">Audio Loopback Dongle</h3> <p> - The <a href="loopback.html">Dr. Rick O'Rang audio loopback dongle</a> is handy for + The <a href="/devices/audio/latency/loopback.html">Dr. Rick O'Rang audio + loopback dongle</a> is handy for measuring round-trip latency over the headset connector. The image below demonstrates the result of injecting an impulse into the loop once, and then allowing the feedback loop to oscillate. diff --git a/en/devices/audio/latency/measurements.html b/en/devices/audio/latency/measurements.html index b5372248..20ded63d 100644 --- a/en/devices/audio/latency/measurements.html +++ b/en/devices/audio/latency/measurements.html @@ -26,7 +26,7 @@ is an important system performance metric. While many kinds of <a href="latency.html">audio latency</a> metrics exist, one useful and well-understood metric is -<a href="latency_measure.html#measuringRoundTrip">round-trip latency</a>, +<a href="/devices/audio/latency/measure.html#measuringRoundTrip">round-trip latency</a>, defined as the time it takes for an audio signal to enter the input of a mobile device, be processed by an app running on the application processor, and exit the output.</p> @@ -65,8 +65,8 @@ CPU.</li> <h2 id="how">How we measure</h2> <p>We made the measurements listed on this page using the -<a href="loopback.html">Dr. Rick O'Rang audio loopback dongle</a> and an -<a href="latency_measure.html#larsenTest">audio feedback (Larsen effect) +<a href="/devices/audio/latency/loopback.html">Dr. Rick O'Rang audio loopback dongle</a> and an +<a href="/devices/audio/latency/measure.html#larsenTest">audio feedback (Larsen effect) test</a>. Measurements assume the application signal processing adds zero algorithmic delay and near-zero computational delay.</p> @@ -90,9 +90,9 @@ increases algorithmic delay for the on-device path.</li> <p>There are cases where on-device microphone and speaker latencies <em>do</em> matter, but they are usually for one direction, not round-trip. Techniques for measuring unidirectional latency are described at -<a href="latency_measure.html#measuringOutput">Measuring Output Latency</a> +<a href="/devices/audio/latency/measure.html#measuringOutput">Measuring Output Latency</a> and -<a href="latency_measure.html#measuringInput">Measuring Input Latency</a>.</p> +<a href="/devices/audio/latency/measure.html#measuringInput">Measuring Input Latency</a>.</p> <h2 id="examples">Example measurements</h2> diff --git a/en/devices/bluetooth/asha.html b/en/devices/bluetooth/asha.html new file mode 100644 index 00000000..d64d8a70 --- /dev/null +++ b/en/devices/bluetooth/asha.html @@ -0,0 +1,787 @@ +<html devsite> + <head> + <title>Hearing Aid Audio Support Using Bluetooth LE</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); you may + not use this file except in compliance with the License. You may obtain a + copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, WITHOUT + WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the + License for the specific language governing permissions and limitations + under the License. + --> + + <p> + Hearing aid devices (HA) can have improved accessibility on + Android-powered mobile devices by using connection-oriented L2CAP + channels (COC) over Bluetooth Low Energy (BLE). COC uses an elastic + buffer of several audio packets to maintain a steady flow of audio, even + in the presence of packet loss. This buffer provides audio quality for + hearing aid devices at the expense of latency. + </p> + + <p> + The design of COC references the + <a href="https://www.bluetooth.com/specifications/bluetooth-core-specification">Bluetooth Core Specification Version 5</a> + (BT). To stay aligned with the core specifications, all multi-byte + values on this page should be read as little-endian. + </p> + + <h2 id="terminology">Terminology</h2> + + <ul> + <li> + <strong>Central</strong> - the Android device that scans for + advertisements over Bluetooth. + </li> + <li> + <strong>Peripheral</strong> - the hearing instrument that sends + advertisement packets over Bluetooth. + </li> + </ul> + + <h2 id="network-topology-and-system-architecture"> + Network topology and system architecture + </h2> + + <p> + When using COC for hearing aids, the network topology assumes a single + central and two peripherals, one left and one right, as seen in + <strong>Figure 1</strong>. The Bluetooth audio system views the left + and right peripherals as a single audio sink. If a peripheral is + missing, due to a monaural fit or a loss of connection, then the + central mixes the left and right audio channel and transmits the audio + to the remaining peripheral. If the central loses connection to both + peripherals, then the central considers the link to the audio sink + lost. In those cases, the central routes audio to another output. + </p> + + <p><img src="/devices/bluetooth/images/bt_asha_topology.png"><br /> + <strong>Figure 1.</strong> Topology for pairing hearing aids with + Android mobile devices using COC over BLE + </p> + + <p> + When the central is not streaming audio data to the peripheral and can + maintain a BLE connection, the central should not disconnect from the + peripheral. Maintaining the connection allows the data communication + to the GATT server residing on the peripheral. + </p> + + <aside class="note"> + <strong>Note</strong>: There is no audio backlink between the central + and the peripherals. During a phone call the central microphones are + used for voice input. + </aside> + + <p> + When pairing and connecting hearing devices, the central should: + </p> + + <ul> + <li> + Keep track of the more recent left and right peripherals paired. + Those two peripherals should be considered the audio sink. + </li> + <li> + Assume the peripherals are in use if a valid pairing exists. The + central should attempt to connect or reconnect with the paired + device when the connection is lost. + </li> + <li> + Assume the peripherals are no longer in use if a pairing is deleted. + </li> + </ul> + + <p> + In the cases above, <em>pairing</em> refers to the action of + registering a set of hearing aids with a given UUID and + left/right designators in the OS, not the Bluetooth pairing process. + </p> + + <h2 id="system-requirements">System requirements</h2> + + <p> + To properly implement COC for a good user experience, the Bluetooth + systems in the central and peripheral devices should: + </p> + + <ul> + <li> + implement a compliant BT 4.2 or higher controller + </li> + <li> + support at least 2 simultaneous LE links with parameters as + described in <a href="#audio-packet-format-and-timing">Audio packet + format and timing</a>. + </li> + <li> + have an LE credit based flow control [BT Vol 3, Part A, Sec 10.1]. + Devices should support an MTU and MPS size of at least 240 bytes on + COC and be able to buffer up to 8 packets. + </li> + <li> + have an LE data length extension [BT Vol 6, Part B, Sec 5.1.9] with + a payload of at least 24887 bytes. It is recommended that the data + length is at least 250 bytes. + </li> + <li> + have the central device support the HCI LE Connection Update Command + and comply with the non-zero minimum_CE_Length parameter. + </li> + <li> + maintain the data throughput for two LE COC connections to two + different peripherals with the connection intervals and payload + sizes in <a href="#audio-packet-format-and-timing">Audio packet + format and timing</a>. + </li> + <li> + have the peripheral set the <code>MaxRxOctets</code> and + <code>MaxRxTime</code> parameters in the <code>LL_LENGTH_REQ</code> + or <code>LL_LENGTH_RSP</code> frames to be the smallest required values + that are necessary for these specifications. This lets the central + optimize its time scheduler when calculating the amount of time + needed to receive a frame. + </li> + </ul> + + <p> + The peripheral and central may implement 2 Mbit PHY as specified in + BT 5. The central should support audio links up to 64 kbit/s on both 1 + Mbit and 2 Mbit PHY but can choose to limit support for links + requiring more than 64 kbit/s to the 2 Mbit PHY in order to improve + coexistence with other 2.4 GHz devices. The BLE long range PHY should + not be used. + </p> + + <p> + COC uses the standard Bluetooth mechanisms for link layer encryption + and frequency hopping. + </p> + + <h2 id="asha-gatt-services">ASHA GATT services</h2> + + <p> + A peripheral should implement the Audio Streaming for Hearing Aid + (ASHA) GATT server service described below. The peripheral should + advertise this service when in general discoverable mode to let the + central recognize an audio sink. Any LE audio streaming operations + shall require encryption. The BLE audio streaming consists of the + following characteristics: + </p> + + <table> + <tr> + <th>Characteristic</th> + <th>Properties</th> + <th>Description</th> + </tr> + <tr> + <td>ReadOnlyProperties</td> + <td>Read</td> + <td>See <a href="#readonlyproperties">ReadOnlyProperties</a>.</td> + </tr> + <tr> + <td>AudioControlPoint</td> + <td>Write without Response</td> + <td> + Control point for audio stream. See + <a href="#audiocontrolpoint">AudioControlPoint</a>. + </td> + </tr> + <tr> + <td>AudioStatusPoint</td> + <td>Read/Notify</td> + <td> + Status report field for the audio control point. Opcodes are: + <ul> + <li><strong>0</strong> - Status OK</li> + <li><strong>-1</strong> - Unknown command</li> + <li><strong>-2</strong> - Illegal parameters</li> + </ul> + </td> + </tr> + <tr> + <td>Volume</td> + <td>Write without Response</td> + <td> + Byte between -128 and 0 indicating volume in dB. -128 should be + interpreted as mute. 0 dB with a rail-to-rail sine tone streamed + should represent a 100 dBSPL input equivalent on the hearing + instrument. The central should stream in nominal full scale and + use this variable to set the desired presentation level in the + peripheral. + </td> + </tr> + <tr> + <td>LE_PSM</td> + <td>Read</td> + <td> + PSM to use for connecting the audio channel. To be picked from the + dynamic range [BT Vol 3, Part A, Sec 4.22] + </td> + </tr> + </table> + + <p>The UUIDs assigned to the service and characteristics:</p> + + <p><strong>Service UUID</strong>: <code>{0xFDF0}</code></p> + + <table> + <tr> + <th>Characteristic</th> + <th>UUID</th> + </tr> + <tr> + <td>ReadOnlyProperties</td> + <td><code>{6333651e-c481-4a3e-9169-7c902aad37bb}</code></td> + </tr> + <tr> + <td>AudioControlPoint</td> + <td><code>{f0d4de7e-4a88-476c-9d9f-1937b0996cc0}</code></td> + </tr> + <tr> + <td>AudioStatus</td> + <td><code>{38663f1a-e711-4cac-b641-326b56404837}</code></td> + </tr> + <tr> + <td>Volume</td> + <td><code>{00e4ca9e-ab14-41e4-8823-f9e70c7e91df}</code></td> + </tr> + <tr> + <td>LE_PSM</td> + <td><code>{2d410339-82b6-42aa-b34e-e2e01df8cc1a}</code></td> + </tr> + </table> + + <p> + In addition to the ASHA GATT service, the peripheral should also + implement the Device Information Service to let the central detect the + manufacturer names and device names of the peripheral. + </p> + + <h3 id="readonlyproperties">ReadOnlyProperties</h3> + + <p>ReadOnlyProperties have the following values:</p> + + <table> + <tr> + <th>Byte</th> + <th>Description</th> + </tr> + <tr> + <td>0</td> + <td>Version - must be 0x01</td> + </tr> + <tr> + <td>1</td> + <td>See <a href="#devicecapabilities">DeviceCapabilities</a>.</td> + </tr> + <tr> + <td>2-9</td> + <td>See <a href="#hisyncid">HiSyncId</a>.</td> + </tr> + <tr> + <td>10</td> + <td>See <a href="#featuremap">FeatureMap</a><strong>.</strong></td> + </tr> + <tr> + <td>11-12</td> + <td> + RenderDelay. This is the time, in milliseconds, the peripheral + needs in order to render audio after the start command has been + issued, such as for loading codecs.The RenderDelay can be used + by the central to delay audio playback of short messages. + </td> + </tr> + <tr> + <td>13-14</td> + <td> + PreparationDelay. This is the time, in milliseconds, the + peripheral needs in order to render audio after the start + command has been issued,such as for loading codecs. The + PreparationDelay can be used by the central to delay audio + playback of short messages. + </td> + </tr> + <tr> + <td>15-16</td> + <td> + Supported <a href="#codec-ids">Codec IDs</a>. This is a bitmask + of supported codec IDs. A 1 in a bit location corresponds to a + supported codec. All other bits should be set to 0. + </td> + </tr> + </table> + + + <h4 id="devicecapabilities">DeviceCapabilities</h4> + + <table> + <tr> + <th>Bit</th> + <th>Description</th> + </tr> + <tr> + <td>0</td> + <td>Device side (Left: 0, Right: 1).</td> + </tr> + <tr> + <td>1</td> + <td> + Monaural (0) / Binaural (1). Indicates whether the device is + stand-alone and receives mono data, or if the device is part + of a set. + </td> + </tr> + <tr> + <td>2-7</td> + <td>Reserved (set to 0).</td> + </tr> + </table> + + <h4 id="hisyncid">HiSyncID</h4> + + <table> + <tr> + <th>Byte</th> + <th>Description</th> + </tr> + <tr> + <td>0-1</td> + <td>ID of the manufacturer.</td> + </tr> + <tr> + <td>2-7</td> + <td> + Unique ID identifying the hearing aid set. This ID must be set + to the same on both the left and the right peripheral. + </td> + </tr> + </table> + + <h4 id="featuremap">FeatureMap</h4> + + <table> + <tr> + <th>Bit</th> + <th>Description</th> + </tr> + <tr> + <td>0</td> + <td>LE COC audio streaming supported (Yes/No).</td> + </tr> + <tr> + <td>1-7</td> + <td>Reserved (set to 0).</td> + </tr> + </table> + + <h4 id="codec-ids">Codec IDs</h4> + + <p> + If the bit is set, then that particular codec is support. + </p> + + <table> + <tr> + <th>Bit number</th> + <th>Codec and sample rate</th> + <th>Required bitrate</th> + <th>Frame time</th> + <th>Mandatory on central (C) or peripheral (P)</th> + </tr> + <tr> + <td>0</td> + <td>Reserved</td> + <td>Reserved</td> + <td>Reserved</td> + <td>Reserved</td> + </tr> + <tr> + <td>1</td> + <td>G.722 @ 16 kHz</td> + <td>64 kbit/s</td> + <td>Variable</td> + <td>C and P</td> + </tr> + <tr> + <td>2</td> + <td>G.722 @ 24 kHz</td> + <td>96 kbit/s</td> + <td>Variable</td> + <td>C</td> + </tr> + <tr> + <td>3</td> + <td>OPUS @ 48 kHz ?</td> + <td>48 kbit/s</td> + <td>10 ms</td> + <td>Not supported</td> + </tr> + <tr> + <td colspan="5"> + 3-15 are reserved.<br /> + 0 is also reserved. + </td> + </tr> + </table> + + <h3 id="audiocontrolpoint">AudioControlPoint</h3> + + <p> + This control point cannot be used when the LE COC is closed. See + <a href="#starting-and-stopping-an-audio-stream">Starting and + stopping an audio stream</a> for the procedure description. + </p> + + <table> + <tr> + <th>Opcode</th> + <th>Arguments</th> + <th>Description</th> + </tr> + <tr> + <td>1 <code>«Start»</code></td> + <td> + <ul> + <li><code>uint8_t codec</code></li> + <li><code>uint8_t audiotype</code></li> + <li><code>int8_t volume</code></li> + </ul> + </td> + <td> + Instructs the peripheral to reset the codec and start the + playback of frame 0. The codec field indicates the bit number + of the Codec ID to use for this playback.<br /><br /> + The audio type bit field indicates the audio type(s) present + in the stream: + <ul> + <li><strong>0</strong> - Unknown</li> + <li><strong>1</strong> - Ringtone</li> + <li><strong>2</strong> - Phonecall</li> + <li><strong>3</strong> - Media</li> + </ul> + The peripheral should not request connection updates before a + <code>«Stop»</code> opcode has been received. + </td> + </tr> + <tr> + <td>2 <code>«Stop»</code></td> + <td>None</td> + <td> + Instructs the peripheral to stop rendering audio. A new audio + setup sequence should be initiated following this stop in order + to render audio again. The peripheral may request a connection + update following this command. + </td> + </tr> + </table> + + <h2 id="advertisements-for-asha-gatt-service"> + Advertisements for ASHA GATT Service + </h2> + + <p> + The <a href="#asha-gatt-services">service UUID</a> must be in the + advertisement packet. In either the advertisement or the scan + response frame, the peripherals must have a Service Data: + </p> + + <table> + <tr> + <th>Byte offset</th> + <th>Name</th> + <th>Description</th> + </tr> + <tr> + <td>0</td> + <td>AD Length</td> + <td>>= 0x09</td> + </tr> + <tr> + <td>1</td> + <td>AD Type</td> + <td>0x16 (Service Data - 16-bits UUID)</td> + </tr> + <tr> + <td>2-3</td> + <td>Service UUID</td> + <td> + 0xFDF0 (little-endian)<br /><br /> + <strong>Note:</strong> This is a temporary ID. + </td> + </tr> + <tr> + <td>4</td> + <td>Protocol Version</td> + <td>0x01</td> + </tr> + <tr> + <td>5</td> + <td>Capability</td> + <td> + <ul> + <li><strong>0</strong> - left (0) or right (1) side</li> + <li><strong>1</strong> - single (0) or dual (1) devices.</li> + <li> + <strong>2-7</strong> - reserved. These bits must be zero. + </li> + </ul> + </td> + </tr> + <tr> + <td>6-9</td> + <td>Truncated <a href="#hisyncid">HiSyncID</a></td> + <td> + Four least significant bytes of the + <a href="#hisyncid">HiSyncId</a>. + </td> + </tr> + </table> + + <p> + The peripherals must have a <strong>Complete Local Name</strong> + data type that indicates the name of the hearing aid. This name will + be used on the mobile device's user interface so the user can select + the right device. The name should not indicate the left or right + channel since this information is provided in + <a href="#devicecapabilities">DeviceCapabilities</a>. + </p> + + <p> + If the peripherals put the name and service data types in the same + frame type (ADV or SCAN RESP), then the two data types should appear + in the same frame. This lets the mobile device scanner get both data + in the same scan result. + </p> + + <p> + During the initial pairing, it is important that the peripherals + advertise at a rate fast enough to let the mobile device quickly + discover the peripherals and bond to them. + </p> + + <h2 id="synchronizing-left-and-right-peripheral-devices">Synchronizing left and right peripheral devices</h2> + + <p> + To work with Bluetooth on Android mobile devices, peripheral devices + are responsible for ensuring that they are synchronized. The playback + on the left and right peripheral devices needs to be synchronized in + time. Both peripheral devices must play back audio samples from the + source at the same time. + </p> + + <p> + Peripheral devices can synchronize their time by using a sequence + number prepended to each packet of the audio payload. The central will + guarantee that audio packets that are meant to be played at the same + time on each peripheral have the same sequence number. The sequence + number is incremented by one after each audio packet. Each sequence + number is 8-bit long, so the sequence numbers will repeat after 256 + audio packets. Since each audio packet size and sample rate is fixed + for each connection, the two peripherals can deduce the relative + playing time. For more information about the audio packet, see + <a href="#audio-packet-format-and-timing">Audio packet format and + timing</a>. + </p> + + <h2 id="audio-packet-format-and-timing">Audio packet format and timing</h2> + + <p> + Packing audio frames (blocks of samples) into packets lets the hearing + instrument derive timing from the link layer timing anchors. To + simplify the implementation: + </p> + + <ul> + <li> + An audio frame should always match the connection interval in time. + For example, if the connection interval is 15ms and sample rate is + 1 kHz, then the audio frame should contain 240 samples. + </li> + <li> + Sample rates in the system are restricted to multiples of 8kHz to + always have an integer number of samples in a frame regardless of + the frame time or the connection interval. + </li> + <li> + A sequence byte should prepend audio frames. The sequence byte + should be counting with wrap-around and allow the peripheral to + detect buffer mismatch or underflow. + </li> + <li> + An audio frame should always fit into a single LE packet. The audio + frame should be sent as a separate L2CAP packet. The size of the LE + LL PDU should be:<br /> + <em>audio payload size + 1 (sequence counter) + 6 + (4 for L2CAP header, 2 for SDU)</em> + </li> + <li> + A connection event should always be large enough to contain 2 audio + packets and 2 empty packets for an ACK to reserve bandwidth for + retransmissions. + </li> + </ul> + + <p> + The peripherals should maintain a common clock at the same or better + resolution than the sample rate. This clock can be queried by the + central using the Timestamp command, which returns the value in + microseconds. The timestamp can be used to indicate the desired + playback time of the first audio frame to the peripherals when starting + the stream. The peripherals should perform the sample resynchronization + to keep in sync with the incoming stream based on the given timestamp. + </p> + + <p> + To give the central some flexibility, the G.722 packet length is not + specified. The G.722 packet length can change based on the connection + interval that the central sets. + </p> + + <p> + For all the codecs that a peripheral supports, the peripheral should + support the connection parameters below. This is a non-exhaustive list + of configurations that the central can implement. + </p> + + <table> + <tr> + <th>Codec</th> + <th>Bitrate</th> + <th>Connection interval</th> + <th>CE Length (1/2 Mbit)</th> + <th>Audio payload size</th> + </tr> + <tr> + <td>G.722 @ 16 kHz</td> + <td>64 kbit/s</td> + <td>10 ms</td> + <td>2500 / 2500 us</td> + <td>80 bytes</td> + </tr> + <tr> + <td>G.722 @ 16 kHz</td> + <td>64 kbit/s</td> + <td>15 ms</td> + <td>3750 / 2500 us</td> + <td>120 bytes</td> + </tr> + <tr> + <td>G.722 @ 16 kHz</td> + <td>64 kbit/s</td> + <td>20 ms</td> + <td>5000/3750 us</td> + <td>160 bytes</td> + </tr> + <tr> + <td>G.722 @ 24 kHz</td> + <td>96 kbit/s</td> + <td>10 ms</td> + <td>3750 / 2500 us</td> + <td>120 bytes</td> + </tr> + <tr> + <td>G.722 @ 24 kHz</td> + <td>96 kbit/s</td> + <td>15 ms</td> + <td>5000 / 2500 us</td> + <td>180 bytes</td> + </tr> + <tr> + <td>G.722 @ 24 kHz</td> + <td>96 kbit/s</td> + <td>20 ms</td> + <td>5000 / 3750 us</td> + <td>240 bytes</td> + </tr> + <tr> + <td>OPUS @ 48 kHz</td> + <td>48 kbit/s</td> + <td>10 ms</td> + <td>2500 / 2500</td> + <td>60 bytes</td> + </tr> + <tr> + <td>OPUS @ 48 kHz Joint Stereo (JS)</td> + <td>96 kbit/s</td> + <td>10 ms</td> + <td>3750 / 2500</td> + <td>120 bytes</td> + </tr> + </table> + + <h2 id="starting-and-stopping-an-audio-stream"> + Starting and stopping an audio stream + </h2> + + <aside class="note"> + <strong>Note:</strong> This section is based on simulations with an + audio frame buffer depth of 6. This depth is enough to prevent + underflow on the peripheral in most packet loss scenarios. With this + depth, the network delay in the system is six times the connection + interval. To keep delays down, a short connection interval is + preferred. + </aside> + + <p> + Before starting an audio stream, the central queries the peripherals + and establishes the best quality common denominator codec. The stream + setup then proceeds through sequence: + </p> + + <ol> + <li>PSM, and optionally, PreparationDelay is read.</li> + <li> + COC L2CAP channel is opened – the peripheral should grant 8 credits + initially. + </li> + <li> + A connection update is issued to switch the link to the parameters + required for the chosen codec. The replica latency is set to 0 in this + update. + </li> + <li> + Both the central and the peripheral host wait for the update + complete event. + </li> + <li> + Restart the audio encoder, and reset the packet sequence count to 0. + A <code>«Start»</code> command with the relevant parameters is + issued on the AudioControlPoint.</li> + <li> + The peripheral takes the first audio packet from its internal queue + (sequence number 0) and plays it back with the first sample placed + at the playback deadline. A new deadline is computed based on the + sequence number. This happens once per connection event while + checking the sequence number. + </li> + </ol> + + <p> + The central issues the <strong>«Stop»</strong> command to close the + audio stream. Once the audio stream is closed, the peripheral may ask + for more relaxed connection parameters. Go through the sequence above + again to restart the audio streaming. When the central is not + streaming audio, it should still maintain a LE connection for GATT + services. + </p> + + <p> + The peripheral should not issue a connection update to the central. + To save power, the central may issue a connection update to the + peripheral when it is not streaming audio. + </p> + </body> +</html> diff --git a/en/devices/bluetooth/images/bt_asha_topology.png b/en/devices/bluetooth/images/bt_asha_topology.png Binary files differnew file mode 100644 index 00000000..8be7a606 --- /dev/null +++ b/en/devices/bluetooth/images/bt_asha_topology.png diff --git a/en/devices/camera/external-usb-cameras.md b/en/devices/camera/external-usb-cameras.md index b9e93257..d39d849d 100644 --- a/en/devices/camera/external-usb-cameras.md +++ b/en/devices/camera/external-usb-cameras.md @@ -21,13 +21,13 @@ Book: /_book.yaml The Android platform supports the use of plug-and-play USB cameras (i.e. webcams) using the standard -[Android Camera2 API](https://developer.android.com/reference/android/hardware/camera2/package-summary.html) +[Android Camera2 API](https://developer.android.com/reference/android/hardware/camera2/package-summary.html){: .external} and the camera -[HIDL](/reference/hidl/android/hardware/camera/provider/2.4/ICameraProvider) +[HIDL](/reference/hidl/android/hardware/camera/provider/2.4/ICameraProvider){: .external} interface. Webcams generally support -[USB video class (UVC)](https://en.wikipedia.org/wiki/USB_video_device_class) +[USB video class (UVC)](https://en.wikipedia.org/wiki/USB_video_device_class){: .external} drivers and on Linux the standard -[Video4Linux (V4L)](https://en.wikipedia.org/wiki/Video4Linux) +[Video4Linux (V4L)](https://en.wikipedia.org/wiki/Video4Linux){: .external} driver is used to control UVC cameras. With support for webcams, devices can be used in lightweight use cases such as @@ -47,19 +47,19 @@ devices as with any regular camera application. For more information on how to implement USB cameras, see an external camera provider reference implementation at -[`ExternalCameraProvider`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/provider/2.4/default/CameraProvider.cpp). +[`ExternalCameraProvider`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/provider/2.4/default/CameraProvider.cpp){: .external}. The external camera device and session implementations are included in -[`ExternalCameraDevice`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/default/ExternalCameraDevice.cpp) +[`ExternalCameraDevice`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/default/ExternalCameraDevice.cpp){: .external} and -[`ExternalCameraDeviceSession`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/default/ExternalCameraDeviceSession.cpp). +[`ExternalCameraDeviceSession`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/default/ExternalCameraDeviceSession.cpp){: .external}. The Java client API includes a new -[`EXTERNAL`](https://developer.android.com/reference/android/hardware/camera2/CameraMetadata?authuser=3#INFO_SUPPORTED_HARDWARE_LEVEL_EXTERNAL) +[`EXTERNAL`](https://developer.android.com/reference/android/hardware/camera2/CameraMetadata?authuser=3#INFO_SUPPORTED_HARDWARE_LEVEL_EXTERNAL){: .external} hardware level. ## Implementation The implementation must support the -[`android.hardware.usb.host`](https://developer.android.com/guide/topics/connectivity/usb/host) +[`android.hardware.usb.host`](https://developer.android.com/guide/topics/connectivity/usb/host){: .external} system feature. Kernel support for UVC devices must also be enabled. You can enable this by @@ -71,7 +71,8 @@ adding the following to the respective kernel `deconfig` files. ``` Note: Make sure you also have this -[patch](https://patchwork.kernel.org/patch/6874491/) for uvcvideo. +[patch](https://patchwork.kernel.org/patch/6874491/){: .external} +for uvcvideo. To enable the external camera provider in the respective device build, which adds the necessary SELinux permissions, external camera configuration, and @@ -193,5 +194,5 @@ webcam must remain plugged in the specific device during the entire test run, otherwise some test cases will fail. Note: `media_profiles` entries are not available for external USB webcams, so -[camcorder profiles](https://developer.android.com/reference/android/media/CamcorderProfile) +[camcorder profiles](https://developer.android.com/reference/android/media/CamcorderProfile){: .external} are absent. diff --git a/en/devices/camera/motion-tracking.md b/en/devices/camera/motion-tracking.md index f2275187..3c18d1d9 100644 --- a/en/devices/camera/motion-tracking.md +++ b/en/devices/camera/motion-tracking.md @@ -22,11 +22,11 @@ Book: /_book.yaml # Motion Tracking In Android {{ androidPVersionNumber }}, camera devices can advertise -[motion tracking capability](https://developer.android.com/reference/android/hardware/camera2/CameraMetadata#REQUEST_AVAILABLE_CAPABILITIES_MOTION_TRACKING). +[motion tracking capability](https://developer.android.com/reference/android/hardware/camera2/CameraMetadata#REQUEST_AVAILABLE_CAPABILITIES_MOTION_TRACKING){: .external}. Cameras that support this feature do not produce motion tracking data itself, but instead are used by ARCore or an image-stabilization algorithm along with other sensors for scene analysis. To support this feature, devices must support -[`CONTROL_CAPTURE_INTENT_MOTION_TRACKING`](https://developer.android.com/reference/android/hardware/camera2/CameraMetadata#CONTROL_CAPTURE_INTENT_MOTION_TRACKING). +[`CONTROL_CAPTURE_INTENT_MOTION_TRACKING`](https://developer.android.com/reference/android/hardware/camera2/CameraMetadata#CONTROL_CAPTURE_INTENT_MOTION_TRACKING){: .external}. If this intent is part of the capture request, the camera must limit the exposure time to a maximum of 20 milliseconds to reduce motion blur. @@ -34,27 +34,27 @@ exposure time to a maximum of 20 milliseconds to reduce motion blur. A reference motion tracking implementation on the HAL side is available as part of the -[Camera HAL](https://android.googlesource.com/platform/hardware/qcom/camera/+/master/msm8998/QCamera2/HAL3/QCamera3HWI.cpp). +[Camera HAL](https://android.googlesource.com/platform/hardware/qcom/camera/+/master/msm8998/QCamera2/HAL3/QCamera3HWI.cpp){: .external}. ## Implementation To enable motion tracking on a camera device, make sure: + The - [`ANDROID_REQUEST_AVAILABLE_CAPABILITIES_MOTION_TRACKING`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#231) + [`ANDROID_REQUEST_AVAILABLE_CAPABILITIES_MOTION_TRACKING`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#231){: .external} capability is enabled. + The - [`ANDROID_CONTROL_CAPTURE_INTENT_MOTION_TRACKING`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#207) + [`ANDROID_CONTROL_CAPTURE_INTENT_MOTION_TRACKING`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#207){: .external} intent is supported and when included in a capture request limits the camera exposure time to a maximum of 20 milliseconds. + Lens calibration data from the following list is accurately reported in the static information and dynamic metadata fields: - + [`ANDROID_LENS_POSE_ROTATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#747) - + [`ANDROID_LENS_POSE_TRANSLATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#753) - + [`ANDROID_LENS_INTRINSIC_CALIBRATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#773) - + [`ANDROID_LENS_RADIAL_DISTORTION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#780) - + [`ANDROID_LENS_POSE_REFERENCE`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#79) + + [`ANDROID_LENS_POSE_ROTATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#747){: .external} + + [`ANDROID_LENS_POSE_TRANSLATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#753){: .external} + + [`ANDROID_LENS_INTRINSIC_CALIBRATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#773){: .external} + + [`ANDROID_LENS_RADIAL_DISTORTION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#780){: .external} + + [`ANDROID_LENS_POSE_REFERENCE`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#79){: .external} ## Validation diff --git a/en/devices/camera/multi-camera.md b/en/devices/camera/multi-camera.md index e2c79e1b..4e72691f 100644 --- a/en/devices/camera/multi-camera.md +++ b/en/devices/camera/multi-camera.md @@ -40,21 +40,21 @@ physical cameras. ## Examples and sources Multi-camera devices must be advertised via the -[logical multi-camera capability](https://developer.android.com/reference/android/hardware/camera2/CameraMetadata#REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA). +[logical multi-camera capability](https://developer.android.com/reference/android/hardware/camera2/CameraMetadata#REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA){: .external}. Camera clients can query the camera ID of the physical devices a particular logical camera is made of by calling -[`getPhysicalCameraIds()`](https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#getPhysicalCameraIds\(\)). +[`getPhysicalCameraIds()`](https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#getPhysicalCameraIds\(\)){: .external}. The IDs returned as part of the result are then used to control physical devices individually via -[`setPhysicalCameraId()`](https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration.html#setPhysicalCameraId\(java.lang.String\)). +[`setPhysicalCameraId()`](https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration.html#setPhysicalCameraId\(java.lang.String\)){: .external}. The results from such individual requests can be queried from the complete result by invoking -[`getPhysicalCameraResults()`](https://developer.android.com/reference/android/hardware/camera2/TotalCaptureResult.html#getPhysicalCameraResults\(\)). +[`getPhysicalCameraResults()`](https://developer.android.com/reference/android/hardware/camera2/TotalCaptureResult.html#getPhysicalCameraResults\(\)){: .external}. Individual physical camera requests may support only a limited subset of parameters. To receive a list of the supported parameters, developers can call -[`getAvailablePhysicalCameraRequestKeys()`](https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#getAvailablePhysicalCameraRequestKeys\(\)). +[`getAvailablePhysicalCameraRequestKeys()`](https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#getAvailablePhysicalCameraRequestKeys\(\)){: .external}. Physical camera streams are supported only for non-reprocessing requests and only for monochrome and bayer sensors. @@ -66,37 +66,37 @@ only for monochrome and bayer sensors. To add logical multi-camera devices on the HAL side: + Add a - [`ANDROID_REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#232) + [`ANDROID_REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#232){: .external} capability for any logical camera device backed by two or more physical cameras that are also exposed to an application. + Populate the static - [`ANDROID_LOGICAL_MULTI_CAMERA_PHYSICAL_IDS`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#161) + [`ANDROID_LOGICAL_MULTI_CAMERA_PHYSICAL_IDS`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#161){: .external} metadata field with a list of physical camera IDs. + Populate the depth-related static metadata required to correlate between physical camera streams' pixels: - [`ANDROID_LENS_POSE_ROTATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#747), - [`ANDROID_LENS_POSE_TRANSLATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#753), - [`ANDROID_LENS_INTRINSIC_CALIBRATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#773), - [`ANDROID_LENS_RADIAL_DISTORTION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#780), - [`ANDROID_LENS_POSE_REFERENCE`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#79)` + [`ANDROID_LENS_POSE_ROTATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#747){: .external}, + [`ANDROID_LENS_POSE_TRANSLATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#753){: .external}, + [`ANDROID_LENS_INTRINSIC_CALIBRATION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#773){: .external}, + [`ANDROID_LENS_RADIAL_DISTORTION`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#780){: .external}, + [`ANDROID_LENS_POSE_REFERENCE`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#79){: .external}. + Set the static - [`ANDROID_LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#167) + [`ANDROID_LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#167){: .external} metadata field to: - + [`ANDROID_LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE_APPROXIMATE`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#256): + + [`ANDROID_LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE_APPROXIMATE`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#256){: .external}: For sensors in master-master mode, no hardware shutter/exposure sync. - + [`ANDROID_LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE_CALIBRATED`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#257): + + [`ANDROID_LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE_CALIBRATED`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#257){: .external}: For sensors in master-slave mode, hardware shutter/exposure sync. + Populate - [`ANDROID_REQUEST_AVAILABLE_PHYSICAL_CAMERA_REQUEST_KEYS`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#106) + [`ANDROID_REQUEST_AVAILABLE_PHYSICAL_CAMERA_REQUEST_KEYS`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#106){: .external} with a list of supported parameters for individual physical cameras. The list can be empty if the logical device doesn't support individual requests. + If individual requests are supported, process and apply the individual - [`physicalCameraSettings`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/types.hal#226) + [`physicalCameraSettings`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/types.hal#226){: .external} that can arrive as part of capture requests and append the individual - [`physicalCameraMetadata`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/types.hal#289) + [`physicalCameraMetadata`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/types.hal#289){: .external} accordingly. The camera device must support replacing one logical YUV/RAW stream with @@ -107,7 +107,7 @@ physical cameras. For a logical camera, the mandatory stream combinations for the camera device of a certain hardware level is the same as what's required in -[`CameraDevice.createCaptureSession`](https://developer.android.com/reference/android/hardware/camera2/CameraDevice.html#createCaptureSession\(java.util.List<android.view.Surface>, android.hardware.camera2.CameraCaptureSession.StateCallback, android.os.Handler\)). +[`CameraDevice.createCaptureSession`](https://developer.android.com/reference/android/hardware/camera2/CameraDevice.html#createCaptureSession\(java.util.List<android.view.Surface>, android.hardware.camera2.CameraCaptureSession.StateCallback, android.os.Handler\)){: .external}. All the streams in the stream configuration map should be fused/logical frames. If certain stream combinations cannot be fused, they should not be included in @@ -128,7 +128,7 @@ the predefined `android.request.maxNumOutputStreams`. ### Guaranteed stream combination Both the logical camera and its underlying physical cameras must guarantee the -[mandatory stream combinations](https://developer.android.com/reference/android/hardware/camera2/CameraDevice#createcapturesession_4) +[mandatory stream combinations](https://developer.android.com/reference/android/hardware/camera2/CameraDevice#createcapturesession_4){: .external} required for their device levels. A logical camera device should operate in the same way as a physical camera @@ -181,15 +181,15 @@ You can customize your device implementation in the following ways. Logical multi-camera devices must pass Camera CTS like any other regular camera. The test cases that target this type of device can be found in the -[`LogicalCameraDeviceTest`](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/) +[`LogicalCameraDeviceTest`](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/){: .external} module. These three ITS tests target multi-camera systems to facilitate the proper fusing of images: -+ [`scene1/test_multi_camera_match.py`](https://android.googlesource.com/platform/cts/+/master/apps/CameraITS/tests/scene1/) -+ [`scene4/test_multi_camera_alignment.py`](https://android.googlesource.com/platform/cts/+/master/apps/CameraITS/tests/scene4/) -+ [`sensor_fusion/test_multi_camera_frame_sync.py`](https://android.googlesource.com/platform/cts/+/master/apps/CameraITS/tests/sensor_fusion/) ++ [`scene1/test_multi_camera_match.py`](https://android.googlesource.com/platform/cts/+/master/apps/CameraITS/tests/scene1/){: .external} ++ [`scene4/test_multi_camera_alignment.py`](https://android.googlesource.com/platform/cts/+/master/apps/CameraITS/tests/scene4/){: .external} ++ [`sensor_fusion/test_multi_camera_frame_sync.py`](https://android.googlesource.com/platform/cts/+/master/apps/CameraITS/tests/sensor_fusion/){: .external} The scene1 and scene4 tests run with the [ITS-in-a-box](/compatibility/cts/camera-its-box) test @@ -204,7 +204,9 @@ motion and asserts that the gyroscope and image sensor timestamps match and that the multi-camera frames are in sync. All boxes are available through AcuSpec, Inc. -([www.acuspecinc.com](http://www.acuspecinc.com), fred@acuspecinc.com) and MYWAY -Manufacturing ([www.myway.tw](http://www.myway.tw), sales@myway.tw). +([www.acuspecinc.com](http://www.acuspecinc.com){: .external}, +fred@acuspecinc.com) and MYWAY +Manufacturing ([www.myway.tw](http://www.myway.tw){: .external}, sales@myway.tw). Additionally, the rev1 ITS box can be purchased through West-Mark -([www.west-mark.com](http://www.west-mark.com), dgoodman@west-mark.com). +([www.west-mark.com](http://www.west-mark.com){: .external}, +dgoodman@west-mark.com). diff --git a/en/devices/camera/session-parameters.md b/en/devices/camera/session-parameters.md index 881f9dba..57bd3053 100644 --- a/en/devices/camera/session-parameters.md +++ b/en/devices/camera/session-parameters.md @@ -30,24 +30,24 @@ efficiently. ## Examples and source A reference session parameter implementation is already part of the -[CameraHal](https://android.googlesource.com/platform/hardware/qcom/camera/+/master/msm8998/QCamera2/HAL3/QCamera3HWI.cpp). +[CameraHal](https://android.googlesource.com/platform/hardware/qcom/camera/+/master/msm8998/QCamera2/HAL3/QCamera3HWI.cpp){: .external}. This HAL uses the legacy Hal API. -The [binderized](https://source.android.com/devices/architecture/hal-types) +The [binderized](/devices/architecture/hal-types) CameraHal that implements the camera HIDL API must use the respective HIDL -[sessionParams](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/types.hal#111) +[sessionParams](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/device/3.4/types.hal#111){: .external} entry to access any new incoming session parameters during stream configuration. Camera clients can query the keys of all supported session parameters by calling -[`getAvailableSessionKeys()`](https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics#getAvailableSessionKeys()) +[`getAvailableSessionKeys()`](https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics#getAvailableSessionKeys(){: .external}) and eventually set their initial values via -[`setSessionParameters()`](https://developer.android.com/reference/android/hardware/camera2/params/SessionConfiguration#setSessionParameters\(android.hardware.camera2.CaptureRequest\)). +[`setSessionParameters()`](https://developer.android.com/reference/android/hardware/camera2/params/SessionConfiguration#setSessionParameters\(android.hardware.camera2.CaptureRequest\){: .external}). ## Implementation Your CameraHal implementation must populate the -[`ANDROID_REQUEST_AVAILABLE_SESSION_KEYS`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#99) +[`ANDROID_REQUEST_AVAILABLE_SESSION_KEYS`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.3/types.hal#99){: .external} within the respective static camera metadata and provide a subset of -[`ANDROID_REQUEST_AVAILABLE_REQUEST_KEYS`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#1016), +[`ANDROID_REQUEST_AVAILABLE_REQUEST_KEYS`](https://android.googlesource.com/platform/hardware/interfaces/+/master/camera/metadata/3.2/types.hal#1016){: .external}, which contains a list of keys that are difficult to apply per-frame and can result in unexpected delays when modified during the capture session lifetime. @@ -72,10 +72,10 @@ available session parameter list empty. CTS includes the following new cases for testing session parameters: -+ [`CameraDeviceTest#testSessionConfiguration`](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/CameraDeviceTest.java#795) -+ [`CameraDeviceTest#testCreateSessionWithParameters`](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/CameraDeviceTest.java#1038) -+ [`CameraDeviceTest#testSessionParametersStateLeak`](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/CameraDeviceTest.java#870) -+ [`NativeCameraDeviceTest#testCameraDevicePreviewWithSessionParameters`](https://android.googlesource.com/platform/cts/+/master/tests/camera/libctscamera2jni/native-camera-jni.cpp#2140) ++ [`CameraDeviceTest#testSessionConfiguration`](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/CameraDeviceTest.java#795){: .external} ++ [`CameraDeviceTest#testCreateSessionWithParameters`](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/CameraDeviceTest.java#1038){: .external} ++ [`CameraDeviceTest#testSessionParametersStateLeak`](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/CameraDeviceTest.java#870){: .external} ++ [`NativeCameraDeviceTest#testCameraDevicePreviewWithSessionParameters`](https://android.googlesource.com/platform/cts/+/master/tests/camera/libctscamera2jni/native-camera-jni.cpp#2140){: .external} In general, once a certain parameter is part of the session key list, its current value is included as part of the session parameters passed during stream diff --git a/en/devices/camera/singleprod-multiconsum.md b/en/devices/camera/singleprod-multiconsum.md index 91915255..7b120b08 100644 --- a/en/devices/camera/singleprod-multiconsum.md +++ b/en/devices/camera/singleprod-multiconsum.md @@ -24,7 +24,7 @@ Book: /_book.yaml This feature introduces a set of methods that allows camera clients to add and remove output surfaces dynamically while the capture session is active and camera streaming is ongoing. A new output can map to a specific, user-selected -[shared camera](https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration#enableSurfaceSharing\(\)) +[shared camera](https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration#enableSurfaceSharing\(\)){: .external} stream. After a surface is added, it can be removed at any time. The general idea is to share the buffers associated with a particular camera @@ -45,12 +45,12 @@ the camera service. ## Examples and source The core implementation of this feature can be found in the -[`Camera3StreamSplitter`](https://android.googlesource.com/platform/frameworks/av/+/master/services/camera/libcameraservice/device3/Camera3StreamSplitter.cpp) +[`Camera3StreamSplitter`](https://android.googlesource.com/platform/frameworks/av/+/master/services/camera/libcameraservice/device3/Camera3StreamSplitter.cpp){: .external} module. Documentation on this feature can be found in the developer reference: -+ [`updateOutputConfiguration()`](https://developer.android.com/reference/android/hardware/camera2/CameraCaptureSession.html#updateOutputConfiguration\(android.hardware.camera2.params.OutputConfiguration\)) -+ [`addSurface()`](https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration#addSurface\(android.view.Surface\)) -+ [`removeSurface()`](https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration#removeSurface\(android.view.Surface\)) ++ [`updateOutputConfiguration()`](https://developer.android.com/reference/android/hardware/camera2/CameraCaptureSession.html#updateOutputConfiguration\(android.hardware.camera2.params.OutputConfiguration\)){: .external} ++ [`addSurface()`](https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration#addSurface\(android.view.Surface\)){: .external} ++ [`removeSurface()`](https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration#removeSurface\(android.view.Surface\)){: .external} ## Implementation @@ -60,7 +60,7 @@ implemented on the framework side. ## Validation Your implementation must pass CTS cases that cover this feature from the -[MultiViewTest](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/MultiViewTest.java) +[MultiViewTest](https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts/MultiViewTest.java){: .external} module and the -[native JNI library](https://android.googlesource.com/platform/cts/+/master/tests/camera/libctscamera2jni/native-camera-jni.cpp) +[native JNI library](https://android.googlesource.com/platform/cts/+/master/tests/camera/libctscamera2jni/native-camera-jni.cpp){: .external} for the native API. diff --git a/en/devices/camera/versioning.html b/en/devices/camera/versioning.html index b6e3404f..48b3d8c4 100644 --- a/en/devices/camera/versioning.html +++ b/en/devices/camera/versioning.html @@ -100,8 +100,8 @@ API1 should work as they do on devices running earlier Android release versions. including efficient zero-copy burst/streaming flows and per-frame controls of exposure, gain, white balance gains, color conversion, denoising, sharpening, and more. For details, watch the -<a href="https://www.youtube.com/watch?v=92fgcUNCHic&feature=youtu.be&t=29m50s">Google -I/O video overview</a>.</p> +<a href="https://www.youtube.com/watch?v=92fgcUNCHic&feature=youtu.be&t=29m50s" class="external"> + Google I/O video overview</a>.</p> <p>Android 5.0 and later includes Camera API2; however, devices running Android 5.0 and later may not support all Camera API2 features. The @@ -110,15 +110,21 @@ through the Camera API2 interfaces reports one of the following support levels:</p> <ul> -<li><code>LEGACY</code>. These devices expose capabilities to apps through the +<li><code>LEGACY</code>: These devices expose capabilities to apps through the Camera API2 interfaces that are approximately the same capabilities as those exposed to apps through the Camera API1 interfaces. The legacy frameworks code conceptually translates Camera API2 calls into Camera API1 calls; legacy devices do not support Camera API2 features such as per-frame controls.</li> -<li><code>FULL</code>. These devices support all of major capabilities of Camera -API2 and must use Camera HAL 3.2 or later and Android 5.0 or later.</li> -<li><code>LIMITED</code>. These devices support some Camera API2 capabilities +<li><code>LIMITED</code>: These devices support some Camera API2 capabilities (but not all) and must use Camera HAL 3.2 or later.</li> +<li><code>FULL</code>: These devices support all of major capabilities of Camera +API2 and must use Camera HAL 3.2 or later and Android 5.0 or later.</li> +<li><code>LEVEL_3</code>: These devices support YUV reprocessing and RAW image +capture, along with additional output stream configurations.</li> +<li><code>EXTERNAL</code>: These devices are similar to <code>LIMITED</code> +devices with some exceptions; for example, some sensor or lens information may +not be reported or have less stable frame rates. This level is used for external +cameras such as USB webcams.</li> </ul> <p>Individual capabilities are exposed via the @@ -304,7 +310,8 @@ that this combination of consumers is not supported. <p> See the <code><a - href="https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration.html#enableSurfaceSharing()">enableSurfaceSharing</a></code> + href="https://developer.android.com/reference/android/hardware/camera2/params/OutputConfiguration.html#enableSurfaceSharing()" class="external"> + enableSurfaceSharing</a></code> developer documentation for additional details.</p> <h4 id="system-api-for-custom-camera-modes">System API for custom camera @@ -317,8 +324,8 @@ limited to at most two specific outputs at once, etc. Various OEMs have expressed interest in defining other custom modes for hardware-specific capabilities. Under the hood, the mode is just an integer passed to <code>configure_streams</code>. See: -<a href="https://source.android.com/reference/hidl/android/hardware/camera/device/3.2/ICameraDeviceSession#configurestreams"> -<code>hardware/camera/device/3.2/ICameraDeviceSession#configurestreams</code></a> +<a href="/reference/hidl/android/hardware/camera/device/3.2/ICameraDeviceSession#configurestreams"> +<code>hardware/camera/device/3.2/ICameraDeviceSession#configurestreams</code></a>. </p> <p> @@ -335,10 +342,11 @@ their custom camera app use the system API. <p> The method name is <code><a - href="https://developer.android.com/reference/android/hardware/camera2/CameraCaptureSession.StateCallback.html#onCaptureQueueEmpty(android.hardware.camera2.CameraCaptureSession)">android.hardware.camera2.CameraDevice#createCustomCaptureSession</a></code>. + href="https://developer.android.com/reference/android/hardware/camera2/CameraCaptureSession.StateCallback.html#onCaptureQueueEmpty(android.hardware.camera2.CameraCaptureSession)" class="external"> + android.hardware.camera2.CameraDevice#createCustomCaptureSession</a></code>. See: -<a href="https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/hardware/camera2/CameraDevice.java#805"> - <code>frameworks/base/core/java/android/hardware/camera2/CameraDevice.java#805</code></a></p> +<a href="https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/hardware/camera2/CameraDevice.java#805" class="external"> + <code>frameworks/base/core/java/android/hardware/camera2/CameraDevice.java#805</code></a>.</p> <aside class="note"><strong>Note:</strong> In the Android 8.1 release, applications must be preinstalled on the system image to access this API. @@ -375,7 +383,8 @@ definition, using the version 0 definition of dataspace encoding.</li> <li>General metadata additions which are available to use for HALv3.2 or newer: <ul> <li> - <a href="https://developer.android.com/reference/android/hardware/camera2/CameraMetadata.html#INFO_SUPPORTED_HARDWARE_LEVEL_3"><code>ANDROID_INFO_SUPPORTED_HARDWARE_LEVEL_3</code> + <a href="https://developer.android.com/reference/android/hardware/camera2/CameraMetadata.html#INFO_SUPPORTED_HARDWARE_LEVEL_3" class="external"> + <code>ANDROID_INFO_SUPPORTED_HARDWARE_LEVEL_3</code> </a> <li><code>ANDROID_CONTROL_POST_RAW_SENSITIVITY_BOOST</code></li> <li><code>ANDROID_CONTROL_POST_RAW_SENSITIVITY_BOOST_RANGE</code></li> diff --git a/en/devices/index.html b/en/devices/index.html deleted file mode 100644 index d20a3e0a..00000000 --- a/en/devices/index.html +++ /dev/null @@ -1,30 +0,0 @@ -<html devsite> - <head> - <title>Develop Android Devices</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2018 The Android Open Source Project - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. - --> - - -<p>Welcome to the development documentation for the Android platform. Here you -will find instructions for implementing particular Android interfaces. Use the -horizontal menu above to delve into specific subtabs and sections.</p> - - </body> -</html> diff --git a/en/devices/tech/config/index.html b/en/devices/tech/config/index.html deleted file mode 100644 index a4f252b7..00000000 --- a/en/devices/tech/config/index.html +++ /dev/null @@ -1,29 +0,0 @@ -<html devsite> - <head> - <title>Configuration</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2017 The Android Open Source Project - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. - --> - - - -<p> The following sections contain information, documentation, tips and tricks for configuring Android components.</p> - - </body> -</html> diff --git a/en/devices/tech/connect/carrier-wifi.md b/en/devices/tech/connect/carrier-wifi.md index c775cbf8..be25f4b9 100644 --- a/en/devices/tech/connect/carrier-wifi.md +++ b/en/devices/tech/connect/carrier-wifi.md @@ -35,7 +35,7 @@ Wi-Fi. ### Manufacturers In the carrier config manager, configure the following parameters, located in -[`CarrierConfigManager.java`](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/CarrierConfigManager.java), +[`CarrierConfigManager.java`](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/CarrierConfigManager.java){: .external}, for each carrier: + `KEY_CARRIER_WIFI_STRING_ARRAY`: Base64-encoded Wi-Fi SSID. diff --git a/en/devices/tech/connect/data-plans.md b/en/devices/tech/connect/data-plans.md index f61af73a..ad21b4ed 100644 --- a/en/devices/tech/connect/data-plans.md +++ b/en/devices/tech/connect/data-plans.md @@ -31,7 +31,7 @@ example, setting warnings and limits to manage their data usage. To configure data plans, carriers can add functionality to their existing Android apps using the -[`SubscriptionPlan` APIs](https://developer.android.com/reference/android/telephony/SubscriptionPlan.Builder). +[`SubscriptionPlan` APIs](https://developer.android.com/reference/android/telephony/SubscriptionPlan.Builder){: .external}. The APIs are designed to support a wide range of data plan types, including both recurring and non-recurring plans, and plans that change over time. @@ -54,9 +54,9 @@ sm.setSubscriptionPlans(subId, Lists.newArrayList( The device only lets an app configure data plans under one of these conditions: + The SIM card has explicitly defined an app that can manage it, as defined by - [`SubscriptionManager.canManageSubscription()`](https://developer.android.com/reference/android/telephony/SubscriptionManager.html#canManageSubscription\(android.telephony.SubscriptionInfo\)). + [`SubscriptionManager.canManageSubscription()`](https://developer.android.com/reference/android/telephony/SubscriptionManager.html#canManageSubscription\(android.telephony.SubscriptionInfo\)){: .external}. + The carrier has pushed the - [`KEY_CONFIG_PLANS_PACKAGE_OVERRIDE_STRING`](https://developer.android.com/reference/android/telephony/CarrierConfigManager#KEY_CONFIG_PLANS_PACKAGE_OVERRIDE_STRING) + [`KEY_CONFIG_PLANS_PACKAGE_OVERRIDE_STRING`](https://developer.android.com/reference/android/telephony/CarrierConfigManager#KEY_CONFIG_PLANS_PACKAGE_OVERRIDE_STRING){: .external} value via `CarrierConfigManager` to indicate which app can manage the carrier's data plans. + The device has an app built into the system image that has the @@ -73,9 +73,9 @@ update data plan details on a daily basis, but carriers are free to use a wide range of mechanisms, such as receiving data plan details via carrier-internal SMS messages. Idle maintenance services are best implemented with a `JobScheduler` job that uses -[`setRequiresDeviceIdle()`](https://developer.android.com/reference/android/app/job/JobInfo.Builder#setRequiresDeviceIdle\(boolean\)) +[`setRequiresDeviceIdle()`](https://developer.android.com/reference/android/app/job/JobInfo.Builder#setRequiresDeviceIdle\(boolean\)){: .external} and -[`setRequiresCharging()`](https://developer.android.com/reference/android/app/job/JobInfo.Builder.html#setRequiresCharging\(boolean\)). +[`setRequiresCharging()`](https://developer.android.com/reference/android/app/job/JobInfo.Builder.html#setRequiresCharging\(boolean\)){: .external}. ## Usage by OS @@ -84,17 +84,17 @@ following ways: + The plan details are surfaced via the Settings app to display accurate data usage to users and to provide - [direct deep links into the carrier app](https://developer.android.com/reference/android/telephony/SubscriptionManager.html#ACTION_MANAGE_SUBSCRIPTION_PLANS) + [direct deep links into the carrier app](https://developer.android.com/reference/android/telephony/SubscriptionManager.html#ACTION_MANAGE_SUBSCRIPTION_PLANS){: .external} for upgrade/upsell opportunities. + The data usage warning and limit notification thresholds are automatically configured based on the plan details; the warning is set to 90% of the limit. + If the carrier temporarily indicates the network is - ["congested"](https://developer.android.com/reference/android/telephony/SubscriptionManager.html#setSubscriptionOverrideCongested\(int,%20boolean,%20long\)), + ["congested"](https://developer.android.com/reference/android/telephony/SubscriptionManager.html#setSubscriptionOverrideCongested\(int,%20boolean,%20long\)){: .external}, the OS delays JobScheduler jobs that can be time-shifted, reducing the load on the carrier network. + If the carrier temporarily indicates the network is - ["unmetered"](https://developer.android.com/reference/android/telephony/SubscriptionManager#setSubscriptionOverrideUnmetered\(int,%20boolean,%20long\)), + ["unmetered"](https://developer.android.com/reference/android/telephony/SubscriptionManager#setSubscriptionOverrideUnmetered\(int,%20boolean,%20long\)){: .external}, the OS can report the cellular connection as "unmetered" until the carrier clears the override, or until the timeout value (if provided) is reached. + By comparing the user's current data usage with the overall data limit, the diff --git a/en/devices/tech/connect/esim-euicc-api.md b/en/devices/tech/connect/esim-euicc-api.md index 607fef86..87dd7c86 100644 --- a/en/devices/tech/connect/esim-euicc-api.md +++ b/en/devices/tech/connect/esim-euicc-api.md @@ -77,9 +77,9 @@ code to the OEM LUI). ### APIs The following APIs can be found in the -[`EuiccManager` reference documentation](https://developer.android.com/reference/android/telephony/euicc/EuiccManager) +[`EuiccManager` reference documentation](https://developer.android.com/reference/android/telephony/euicc/EuiccManager){: .external} and -[`EuiccManager.java`](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccManager.java). +[`EuiccManager.java`](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccManager.java){: .external}. #### Get instance (public) @@ -246,4 +246,4 @@ mgr.startResolutionActivity(getActivity(), 0 /* requestCode */, resultIntent, ca ### Constants To see a list of the the `public` constants in `EuiccManager`, see -[Constants](https://developer.android.com/reference/android/telephony/euicc/EuiccManager#constants). +[Constants](https://developer.android.com/reference/android/telephony/euicc/EuiccManager#constants){: .external}. diff --git a/en/devices/tech/connect/esim-modem-requirements.md b/en/devices/tech/connect/esim-modem-requirements.md index cd9f7d76..a67fb83d 100644 --- a/en/devices/tech/connect/esim-modem-requirements.md +++ b/en/devices/tech/connect/esim-modem-requirements.md @@ -44,24 +44,24 @@ capabilities: "Local Profile Management" and "Profile Download" per ETSI TS 102 ### Implement setSimPower API in Radio HAL v1.1 The modem shall support the -[setSimPower](https://source.android.com/reference/hidl/android/hardware/radio/1.1/IRadio#setsimcardpower_1_1) +[setSimPower](/reference/hidl/android/hardware/radio/1.1/IRadio#setsimcardpower_1_1) API. ### Implement getSimSlotsStatus API in IRadioConfig HAL v1.0 The modem shall support the -[getSimSlotsStatus](https://android.googlesource.com/platform/hardware/interfaces/+/master/radio/config/1.0/IRadioConfig.hal#51) +[getSimSlotsStatus](https://android.googlesource.com/platform/hardware/interfaces/+/master/radio/config/1.0/IRadioConfig.hal#51){: .external} API, which indicates whether a slot contains an eSIM. ### Implement getIccCardStatus API in IRadio HAL v1.2 The modem shall provide the ATR and slot ID of the card status as specified in the -[getIccCardStatus](https://source.android.com/reference/hidl/android/hardware/radio/1.0/IRadio#getIccCardStatus) +[getIccCardStatus](/reference/hidl/android/hardware/radio/1.0/IRadio#getIccCardStatus) API. This API was first introduced in v1.0 and, in v1.2, -[CardStatus](https://android.googlesource.com/platform/hardware/interfaces/+/master/radio/1.2/types.hal#341) +[CardStatus](https://android.googlesource.com/platform/hardware/interfaces/+/master/radio/1.2/types.hal#341){: .external} was changed to include -[ATR](https://android.googlesource.com/platform/hardware/interfaces/+/master/radio/1.2/types.hal#351). +[ATR](https://android.googlesource.com/platform/hardware/interfaces/+/master/radio/1.2/types.hal#351){: .external}. ### (Optional) Support eSIM OS OTA diff --git a/en/devices/tech/connect/esim-overview.md b/en/devices/tech/connect/esim-overview.md index fb9f7450..8c24b168 100644 --- a/en/devices/tech/connect/esim-overview.md +++ b/en/devices/tech/connect/esim-overview.md @@ -45,26 +45,26 @@ available LPA, and routes all the eUICC operations through an LPA instance. Mobile network operators interested in creating a _carrier app_ should look at the APIs in -[EuiccManager](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccManager.java), +[EuiccManager](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccManager.java){: .external}, which provides high-level profile management operations such as `downloadSubscription()`, `switchToSubscription()`, and `deleteSubscription()`. If you are a device OEM interested in creating your own LPA system app, you must extend -[EuiccService](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java) +[EuiccService](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java){: .external} for the Android framework to connect to your LPA services. In addition, you should use the APIs in -[EuiccCardManager](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccCardManager.java), +[EuiccCardManager](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccCardManager.java){: .external}, which provides ES10x functions based on GSMA Remote SIM Provisioning (RSP) v2.0. These functions are used to issue commands to the eUICC chip, such as `prepareDownload()`, `loadBoundProfilePackage()`, `retrieveNotificationList()`, and `resetMemory()`. The APIs in -[EuiccManager](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccManager.java) +[EuiccManager](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccManager.java){: .external} require a properly implemented LPA app to function and the caller of -[EuiccCardManager](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccCardManager.java) +[EuiccCardManager](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/euicc/EuiccCardManager.java){: .external} APIs must be an LPA. This is enforced by the Android framework. ## Making a carrier app @@ -205,10 +205,10 @@ user consent is required. For these cases, the caller's callback is called with `EuiccManager#EMBEDDED_SUBSCRIPTION_RESULT_RESOLVABLE_ERROR`. The callback `Intent` will contain internal extras such that when the caller passes it to -[`EuiccManager#startResolutionActivity`](https://developer.android.com/reference/android/telephony/euicc/EuiccManager.html#startResolutionActivity(android.app.Activity,%20int,%20android.content.Intent,%20android.app.PendingIntent)), +[`EuiccManager#startResolutionActivity`](https://developer.android.com/reference/android/telephony/euicc/EuiccManager.html#startResolutionActivity(android.app.Activity,%20int,%20android.content.Intent,%20android.app.PendingIntent)){: .external}, resolution can be requested through the LUI. Using the confirmation code for example again, -[`EuiccManager#startResolutionActivity`](https://developer.android.com/reference/android/telephony/euicc/EuiccManager.html#startResolutionActivity(android.app.Activity,%20int,%20android.content.Intent,%20android.app.PendingIntent)) +[`EuiccManager#startResolutionActivity`](https://developer.android.com/reference/android/telephony/euicc/EuiccManager.html#startResolutionActivity(android.app.Activity,%20int,%20android.content.Intent,%20android.app.PendingIntent)){: .external} triggers an LUI screen that allows the user to enter a confirmation code; after the code is entered, the download operation is resumed. This approach provides the carrier app with full control over when the UI is shown, but gives @@ -216,7 +216,7 @@ the LPA/LUI an extensible method for adding new handling of user-recoverable issues in the future without needing client apps to change. Android {{ androidPVersionNumber }} defines these resolvable errors in -[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java), +[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java){: .external}, which the LUI should handle: ``` @@ -256,7 +256,7 @@ Android platform loads certificates stored in the profile's Access Rule File to `EuiccManager` APIs. The high-level process is described below: 1. Operator signs the carrier app APK; the - [apksigner](https://developer.android.com/studio/command-line/apksigner) + [apksigner](https://developer.android.com/studio/command-line/apksigner){: .external} tool attaches the public-key certificate to the APK. 1. Operator/SM-DP+ prepares a profile and its metadata, which include an ARF that contains: @@ -298,8 +298,8 @@ RefArDo ::= [PRIVATE 2] SEQUENCE { -- Tag E2 ``` For more details on app signing, see -[Sign your app](https://developer.android.com/studio/publish/app-signing). For -details on carrier privileges, see +[Sign your app](https://developer.android.com/studio/publish/app-signing){: .external}. +For details on carrier privileges, see [UICC Carrier Privileges](/devices/tech/config/uicc). ## Making an LPA app @@ -313,7 +313,7 @@ integrating it with the Android system. The LPA and the eSIM OS on the eUICC chip must support at least GSMA RSP (Remote SIM Provisioning) v2.0 or v2.2. You should also plan to use SM-DP+ and SM-DS servers that have a matching RSP version. For detailed RSP architecture, see -[GSMA SGP.21 RSP Architecture Specification](https://www.gsma.com/newsroom/all-documents/sgp-21-rsp-architecture-v2-2/). +[GSMA SGP.21 RSP Architecture Specification](https://www.gsma.com/newsroom/all-documents/sgp-21-rsp-architecture-v2-2/){: .external}. In addition, to integrate with the eUICC APIs in Android {{ androidPVersionNumber }}, the device modem should send terminal capabilities @@ -336,7 +336,7 @@ An LPA consists of two separate components (may both be implemented in the same APK): the LPA backend, and the LPA UI or LUI. To implement the LPA backend, you must extend -[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java) +[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java){: .external} and declare this service in your manifest file. The service must require the `android.permission.BIND_EUICC_SERVICE` system permission to ensure that only the system can bind to it. The service must also include an intent filter with @@ -372,7 +372,7 @@ intent filter with the appropriate action, the `android.service.euicc.category.EUICC_UI` category, and a non-zero priority. Similar logic is used to pick the implementations for these activities as with picking the implementation of -[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java). +[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java){: .external}. For example: ``` @@ -392,9 +392,9 @@ For example: This implies that the UI implementing these screens can come from a different APK from the one that implements -[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java). +[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java){: .external}. Whether to have a single APK or multiple APKs (e.g. one that implements -[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java) +[`EuiccService`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/service/euicc/EuiccService.java){: .external} and one that provides LUI activities) is a design choice. ### EuiccCardManager @@ -445,7 +445,7 @@ Internally, `EuiccCardManager` binds to `EuiccCardController` (which runs in the phone process) through an AIDL interface, and each `EuiccCardManager` method receives its callback from the phone process through a different, dedicated AIDL interface. When using `EuiccCardManager` APIs, the caller (LPA) must provide an -[`Executor`](https://developer.android.com/reference/java/util/concurrent/Executor) +[`Executor`](https://developer.android.com/reference/java/util/concurrent/Executor){: .external} through which the callback is invoked. This `Executor` may run on a single thread or on a thread pool of your choice. @@ -494,7 +494,7 @@ are valid in Android builds. You should make sure the builds pass the following CTS test cases (for public APIs): -[https://android.googlesource.com/platform/cts/+/master/tests/tests/telephony/src/android/telephony/](https://android.googlesource.com/platform/cts/+/master/tests/tests/telephony/src/android/telephony/euicc/cts) +[https://android.googlesource.com/platform/cts/+/master/tests/tests/telephony/src/android/telephony/](https://android.googlesource.com/platform/cts/+/master/tests/tests/telephony/src/android/telephony/euicc/cts){: .external} Carriers implementing a carrier app should go through their normal in-house quality assurance @@ -508,4 +508,4 @@ testing. You should work with your modem vendor, eUICC chip or eSIM OS vendor, SM-DP+ vendors, and carriers to resolve issues and ensure interoperability of your LPA within the RSP architecture. A good amount of manual testing is inevitable. For best test coverage, you should follow the -[GSMA SGP.23 RSP Test Plan](https://www.gsma.com/newsroom/all-documents/sgp-23-v1-2-rsp-test-specification/). +[GSMA SGP.23 RSP Test Plan](https://www.gsma.com/newsroom/all-documents/sgp-23-v1-2-rsp-test-specification/){: .external}. diff --git a/en/devices/tech/connect/images/auto-wifi.png b/en/devices/tech/connect/images/auto-wifi.png Binary files differnew file mode 100644 index 00000000..c44ec898 --- /dev/null +++ b/en/devices/tech/connect/images/auto-wifi.png diff --git a/en/devices/tech/connect/images/connect-open-networks.png b/en/devices/tech/connect/images/connect-open-networks.png Binary files differnew file mode 100644 index 00000000..8f10f9fd --- /dev/null +++ b/en/devices/tech/connect/images/connect-open-networks.png diff --git a/en/devices/tech/connect/images/open-network-notification.png b/en/devices/tech/connect/images/open-network-notification.png Binary files differnew file mode 100644 index 00000000..b0fe3af0 --- /dev/null +++ b/en/devices/tech/connect/images/open-network-notification.png diff --git a/en/devices/tech/connect/images/wifi-network-quality.png b/en/devices/tech/connect/images/wifi-network-quality.png Binary files differnew file mode 100644 index 00000000..0e525cd7 --- /dev/null +++ b/en/devices/tech/connect/images/wifi-network-quality.png diff --git a/en/devices/tech/connect/ims.md b/en/devices/tech/connect/ims.md index 0a93f39f..c4197ad3 100644 --- a/en/devices/tech/connect/ims.md +++ b/en/devices/tech/connect/ims.md @@ -22,7 +22,7 @@ Book: /_book.yaml # Implementing IMS Android {{ androidPVersionNumber }} introduces a new SystemApi interface called -[ImsService](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/ims/) +[ImsService](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/ims/){: .external} to help you implement IP Multimedia Subsystem (IMS). The ImsService API is a well-defined interface between the Android platform and a vendor or carrier-provided IMS implementation. @@ -44,10 +44,10 @@ be Play Store updatable. Android provides an application on AOSP that implements portions of the ImsService API for testing and development purposes. You can find the application at -[/testapps/ImsTestService](https://android.googlesource.com/platform/packages/services/Telephony/+/master/testapps/ImsTestService/). +[/testapps/ImsTestService](https://android.googlesource.com/platform/packages/services/Telephony/+/master/testapps/ImsTestService/){: .external}. You can find the documentation for the ImsService API in -[ImsService](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/ims/ImsService.java) +[ImsService](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/ims/ImsService.java){: .external} and in the other classes in the API. ## Implementation @@ -152,7 +152,7 @@ IMS PDN for emergency calling. Any implementation of `ImsService` that wishes to support the MMTEL features should extend the `android.telephony.ims.MmTelFeature` base class and return a custom `MmTelFeature` implementation in -[`ImsService#createMmTelFeature`](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/ims/ImsService.java#335). +[`ImsService#createMmTelFeature`](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/ims/ImsService.java#335){: .external}. #### FEATURE_EMERGENCY_MMTEL @@ -197,7 +197,7 @@ appropriate. There are two types of ImsServices that the framework binds to: 1. Carrier "override" ImsService: These ImsServices are preloaded onto the device but are attached to one or more cellular carriers and will only be bound when a matching SIM card is inserted. This is configured using the - [`key_config_ims_package_override`](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/CarrierConfigManager.java#309) + [`key_config_ims_package_override`](https://android.googlesource.com/platform/frameworks/base/+/master/telephony/java/android/telephony/CarrierConfigManager.java#309){: .external} CarrierConfig key. 1. Device "default" ImsService: This is the default ImsService that is loaded onto the device by an OEM and should be designed to provide IMS services in @@ -205,7 +205,7 @@ appropriate. There are two types of ImsServices that the framework binds to: situations where the device has no SIM card inserted or the SIM card inserted does not have a carrier ImsService installed with it. This is defined in the device overlay - [`config_ims_package`](https://android.googlesource.com/platform/frameworks/base/+/master/core/res/res/values/config.xml#2705) + [`config_ims_package`](https://android.googlesource.com/platform/frameworks/base/+/master/core/res/res/values/config.xml#2705){: .external} key. Both of these ImsService implementations are required to be System applications, diff --git a/en/devices/tech/connect/rtt.md b/en/devices/tech/connect/rtt.md index cf13c983..abe02cd0 100644 --- a/en/devices/tech/connect/rtt.md +++ b/en/devices/tech/connect/rtt.md @@ -36,18 +36,18 @@ typed, character by character. ## Examples and source Framework components are available in AOSP at -[Call.RttCall](https://developer.android.com/reference/android/telecom/Call.RttCall) +[Call.RttCall](https://developer.android.com/reference/android/telecom/Call.RttCall){: .external} and -[Connection.RttTextStream](https://developer.android.com/reference/android/telecom/Connection.RttTextStream). +[Connection.RttTextStream](https://developer.android.com/reference/android/telecom/Connection.RttTextStream){: .external}. IMS/modem components are proprietary and should be supplied by the IMS/modem vendor. Dialer RTT reference implementation is also available. AOSP Dialer code for RTT: + InCall: - [/java/com/android/incallui/rtt](https://android.googlesource.com/platform/packages/apps/Dialer/+/master/java/com/android/incallui/rtt) + [/java/com/android/incallui/rtt](https://android.googlesource.com/platform/packages/apps/Dialer/+/master/java/com/android/incallui/rtt){: .external} + Call log: - [/java/com/android/dialer/rtt](https://android.googlesource.com/platform/packages/apps/Dialer/+/master/java/com/android/dialer/rtt) + [/java/com/android/dialer/rtt](https://android.googlesource.com/platform/packages/apps/Dialer/+/master/java/com/android/dialer/rtt){: .external} ## Implementation diff --git a/en/devices/tech/connect/third-party-call-apps.md b/en/devices/tech/connect/third-party-call-apps.md index 3e1b236f..95744e39 100644 --- a/en/devices/tech/connect/third-party-call-apps.md +++ b/en/devices/tech/connect/third-party-call-apps.md @@ -37,11 +37,11 @@ user engages in the 3P call. In Android {{ androidPVersionNumber }}, 3P calling apps are encouraged to implement the self-managed `ConnectionService` API. For more information on how to build a calling app using this API, see -[Build a calling app](https://developer.android.com/guide/topics/connectivity/telecom/selfManaged). +[Build a calling app](https://developer.android.com/guide/topics/connectivity/telecom/selfManaged){: .external}. The self-managed `ConnectionService` API also gives developers the opportunity to opt-in to having calls in their app logged in the system call log (see -[`EXTRA_LOG_SELF_MANAGED_CALLS`](https://developer.android.com/reference/android/telecom/PhoneAccount#EXTRA_LOG_SELF_MANAGED_CALLS)). +[`EXTRA_LOG_SELF_MANAGED_CALLS`](https://developer.android.com/reference/android/telecom/PhoneAccount#EXTRA_LOG_SELF_MANAGED_CALLS){: .external}). Per the requirements in the [Android Compatibility Definition Document (CDD)](/compatibility/android-cdd#7_4_data_connectivity) (section 7.4.1.2), you should ensure your dialer/phone app displays these @@ -51,9 +51,9 @@ see [Call log entries from 3P calling apps](#call_log_entries_from_3p_calling_apps)). Apps are responsible for setting -[`CAPABILITY_SUPPORT_HOLD`](https://developer.android.com/reference/android/telecom/Connection.html#CAPABILITY_SUPPORT_HOLD) +[`CAPABILITY_SUPPORT_HOLD`](https://developer.android.com/reference/android/telecom/Connection.html#CAPABILITY_SUPPORT_HOLD){: .external} and -[`CAPABILITY_HOLD`](https://developer.android.com/reference/android/telecom/Connection.html#CAPABILITY_HOLD) +[`CAPABILITY_HOLD`](https://developer.android.com/reference/android/telecom/Connection.html#CAPABILITY_HOLD){: .external} on their apps' connections. However, it is possible that an app cannot hold a call in some circumstances. The framework includes provisions for resolving these types of cases. @@ -85,11 +85,11 @@ See the user interface below for an example: Your dialer app can check if an incoming call causes another call to be disconnected by checking the -[call extras](https://developer.android.com/reference/android/telecom/Call.Details.html#getExtras\(\)). +[call extras](https://developer.android.com/reference/android/telecom/Call.Details.html#getExtras\(\)){: .external}. Make sure that -[`EXTRA_ANSWERING_DROPS_FG_CALL`](https://developer.android.com/reference/android/telecom/Connection.html#EXTRA_ANSWERING_DROPS_FG_CALL) +[`EXTRA_ANSWERING_DROPS_FG_CALL`](https://developer.android.com/reference/android/telecom/Connection.html#EXTRA_ANSWERING_DROPS_FG_CALL){: .external} is set to `TRUE`, and -[`EXTRA_ANSWERING_DROPS_FG_CALL_APP_NAME`](https://developer.android.com/reference/android/telecom/Connection.html#EXTRA_ANSWERING_DROPS_FG_CALL_APP_NAME) +[`EXTRA_ANSWERING_DROPS_FG_CALL_APP_NAME`](https://developer.android.com/reference/android/telecom/Connection.html#EXTRA_ANSWERING_DROPS_FG_CALL_APP_NAME){: .external} is set to the name of the app whose call is disconnected upon answering the incoming mobile call. @@ -97,7 +97,7 @@ incoming mobile call. Developers of 3P calling apps can opt-in to having calls in their app logged in the system call log (see -[`EXTRA_LOG_SELF_MANAGED_CALLS`](https://developer.android.com/reference/android/telecom/PhoneAccount#EXTRA_LOG_SELF_MANAGED_CALLS)). +[`EXTRA_LOG_SELF_MANAGED_CALLS`](https://developer.android.com/reference/android/telecom/PhoneAccount#EXTRA_LOG_SELF_MANAGED_CALLS){: .external}). This means that it is possible to have entries in the call log that are not for mobile network calls. @@ -114,22 +114,22 @@ illustrated below: </figure> To determine the name of an app associated with a call log entry, use the -[`PHONE_ACCOUNT_COMPONENT_NAME`](https://developer.android.com/reference/android/provider/CallLog.Calls.html#PHONE_ACCOUNT_COMPONENT_NAME) +[`PHONE_ACCOUNT_COMPONENT_NAME`](https://developer.android.com/reference/android/provider/CallLog.Calls.html#PHONE_ACCOUNT_COMPONENT_NAME){: .external} and -[`PHONE_ACCOUNT_ID`](https://developer.android.com/reference/android/provider/CallLog.Calls.html#PHONE_ACCOUNT_ID) +[`PHONE_ACCOUNT_ID`](https://developer.android.com/reference/android/provider/CallLog.Calls.html#PHONE_ACCOUNT_ID){: .external} columns in the call log provider to create an instance of -[`PhoneAccountHandle`](https://developer.android.com/reference/android/telecom/PhoneAccountHandle.html#PhoneAccountHandle\(android.content.ComponentName,%20java.lang.String\)), +[`PhoneAccountHandle`](https://developer.android.com/reference/android/telecom/PhoneAccountHandle.html#PhoneAccountHandle\(android.content.ComponentName,%20java.lang.String\)){: .external}, which identifies the source of a call log entry. Query -[`TelecomManager`](https://developer.android.com/reference/android/telecom/TelecomManager.html#getPhoneAccount\(android.telecom.PhoneAccountHandle\)) +[`TelecomManager`](https://developer.android.com/reference/android/telecom/TelecomManager.html#getPhoneAccount\(android.telecom.PhoneAccountHandle\)){: .external} to get the details for the PhoneAccount. \ To determine if a call log entry is from a 3P calling app, check -[`PhoneAccount` capabilities ](https://developer.android.com/reference/android/telecom/PhoneAccount.html#getCapabilities\(\)) +[`PhoneAccount` capabilities ](https://developer.android.com/reference/android/telecom/PhoneAccount.html#getCapabilities\(\)){: .external} to see if -[`CAPABILITY_SELF_MANAGED`](https://developer.android.com/reference/android/telecom/PhoneAccount.html#CAPABILITY_SELF_MANAGED) +[`CAPABILITY_SELF_MANAGED`](https://developer.android.com/reference/android/telecom/PhoneAccount.html#CAPABILITY_SELF_MANAGED){: .external} is set. The -[`getLabel`](https://developer.android.com/reference/android/telecom/PhoneAccount.html#getLabel\(\)) +[`getLabel`](https://developer.android.com/reference/android/telecom/PhoneAccount.html#getLabel\(\)){: .external} method of the returned `PhoneAccount` returns the name of the app associated with a call log entry from the 3P calling app. @@ -138,7 +138,7 @@ with a call log entry from the 3P calling app. To test that your device supports 3P calling apps, use the Telecomm test application, which implements the self-managed ConnectionService API. The application is located in -[`/packages/services/Telecomm/testapps/`](https://android.googlesource.com/platform/packages/services/Telecomm/+/master/testapps/). +[`/packages/services/Telecomm/testapps/`](https://android.googlesource.com/platform/packages/services/Telecomm/+/master/testapps/){: .external}. 1. Build the test app from the root of your Android source repository using: diff --git a/en/devices/tech/connect/wifi-aware.md b/en/devices/tech/connect/wifi-aware.md index 10477e49..2dfbfa04 100644 --- a/en/devices/tech/connect/wifi-aware.md +++ b/en/devices/tech/connect/wifi-aware.md @@ -22,32 +22,33 @@ Book: /_book.yaml # Wi-Fi Aware The -[Wi-Fi Aware](https://developer.android.com/guide/topics/connectivity/wifi-aware.html) +[Wi-Fi Aware](https://developer.android.com/guide/topics/connectivity/wifi-aware.html){: .external} feature added in Android 8.0 enables supporting devices to discover, connect, and range (added in Android {{ androidPVersionNumber }}) to one another directly using the Wi-Fi Aware protocol without internet or cellular network access. This -feature, built upon the [Wi-Fi Alliance](https://www.wi-fi.org/) (WFA) [Wi-Fi -Aware specification](https://www.wi-fi.org/discover-wi-fi/wi-fi-aware) (version -2.0), allows easy sharing of high-throughput data among trusted devices and apps -that are otherwise off-network. +feature, built upon the [Wi-Fi Alliance](https://www.wi-fi.org/){: .external} +(WFA) +[Wi-Fi Aware specification](https://www.wi-fi.org/discover-wi-fi/wi-fi-aware){: .external} +(version 2.0), allows easy sharing of high-throughput data among trusted devices +and apps that are otherwise off-network. ## Examples and source To use this feature, device manufacturers should implement the Wi-Fi -[Hardware Interface Design Language (HIDL)](/devices/architecture/hidl) -provided in the Android Open Source Project (AOSP). HIDL replaces the previous +[Hardware Interface Design Language (HIDL)](/devices/architecture/hidl) provided +in the Android Open Source Project (AOSP). HIDL replaces the previous [Hardware Abstraction Layer (HAL)](/devices/architecture/hal) structure used to streamline implementations by specifying types and method calls collected into interfaces and packages. Follow the Wi-Fi HIDL to employ the Wi-Fi Aware feature: hardware/interfaces/wifi/1.2. The Wi-Fi Aware HAL surface is very large; the -[hardware/interfaces/wifi/1.2/README-NAN.md]https://android.googlesource.com/platform/hardware/interfaces/+/master/wifi/1.2/README-NAN.md) +[hardware/interfaces/wifi/1.2/README-NAN.md](https://android.googlesource.com/platform/hardware/interfaces/+/master/wifi/1.2/README-NAN.md){: .external} file describes the subset that is currently in use by the framework. You can reference the legacy Wi-Fi HAL to see how it correlates with the new HIDL interface: -[hardware/libhardware_legacy/+/master/include/hardware_legacy/wifi_nan.h](https://android.googlesource.com/platform/hardware/libhardware_legacy/+/master/include/hardware_legacy/wifi_nan.h). +[hardware/libhardware_legacy/+/master/include/hardware_legacy/wifi_nan.h](https://android.googlesource.com/platform/hardware/libhardware_legacy/+/master/include/hardware_legacy/wifi_nan.h){: .external}. ## Implementation @@ -92,8 +93,8 @@ interfaces (NDPs) to be randomized and not be identical to the true MAC address of the device. The MAC addresses must be: + Randomized whenever Wi-Fi Aware is enabled or re-enabled. -+ When Wi-Fi Aware is enabled, the MAC address must be randomized at a - regular interval configured by the ++ When Wi-Fi Aware is enabled, the MAC address must be randomized at a regular + interval configured by the `NanConfigRequest.macAddressRandomizationIntervalSec` HIDL parameter. This is configured by the framework by default to be 30 minutes. @@ -102,9 +103,10 @@ of the device. The MAC addresses must be: ## Validation -Android provides a set of unit tests, integration tests (ACTS), [Compatibility Test Suite (CTS)](/compatibility/cts) tests, and [CTS Verifier](/compatibility/cts/verifier) -tests to validate the Wi-Fi Aware feature. Wi-Fi Aware can also be tested using -the +Android provides a set of unit tests, integration tests (ACTS), +[Compatibility Test Suite (CTS)](/compatibility/cts) tests, and +[CTS Verifier](/compatibility/cts/verifier) tests to validate the Wi-Fi Aware +feature. Wi-Fi Aware can also be tested using the [Vendor Test Suite (VTS)](/devices/tech/test_infra/tradefed/fundamentals/vts). ### Unit tests diff --git a/en/devices/tech/connect/wifi-debug.md b/en/devices/tech/connect/wifi-debug.md index 87e7ed76..eff986d0 100644 --- a/en/devices/tech/connect/wifi-debug.md +++ b/en/devices/tech/connect/wifi-debug.md @@ -84,7 +84,7 @@ the framework to save IPC costs. ### Implementation For a reference implementation, see the -[default implementation](https://android.googlesource.com/platform/hardware/interfaces/+/master/wifi/1.2/default/wifi_chip.cpp#1388) +[default implementation](https://android.googlesource.com/platform/hardware/interfaces/+/master/wifi/1.2/default/wifi_chip.cpp#1388){: .external} in the vendor HAL. You can disable firmware logging by setting the resource, @@ -101,8 +101,8 @@ a bug report. ### Manual test -Run this manual test to verify that old files in the [tombstone directory](/devices/tech/debug/#debuggerd) are -being deleted. +Run this manual test to verify that old files in the +[tombstone directory](/devices/tech/debug/#debuggerd) are being deleted. 1. Turn on Wi-Fi. 1. Connect to a network. diff --git a/en/devices/tech/connect/wifi-hal.md b/en/devices/tech/connect/wifi-hal.md index cd893444..e2005767 100644 --- a/en/devices/tech/connect/wifi-hal.md +++ b/en/devices/tech/connect/wifi-hal.md @@ -67,9 +67,9 @@ concurrently. The supported combinations are defined in the HAL and are exposed to the framework. The specification format is defined in `android/hardware/interfaces/wifi/1.0/IWifiChip.hal`. For example, a device may support one STA and one interface of either NAN -([Wi-Fi Aware](https://developer.android.com/guide/topics/connectivity/wifi-aware)) +([Wi-Fi Aware](https://developer.android.com/guide/topics/connectivity/wifi-aware){: .external}) or P2P -([Wi-Fi Direct](https://developer.android.com/guide/topics/connectivity/wifip2p)) +([Wi-Fi Direct](https://developer.android.com/guide/topics/connectivity/wifip2p){: .external}) type (but not both). This would be expressed as: `[{STA} <= 1, {NAN,P2P} <= 1]` diff --git a/en/devices/tech/connect/wifi-infrastructure.md b/en/devices/tech/connect/wifi-infrastructure.md new file mode 100644 index 00000000..8c917099 --- /dev/null +++ b/en/devices/tech/connect/wifi-infrastructure.md @@ -0,0 +1,173 @@ +Project: /_project.yaml +Book: /_book.yaml + +{% include "_versions.html" %} + +<!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> + +# Wi-Fi Infrastructure Features + +The Android Wi-Fi framework helps users connect to a good Wi-Fi network when +networks are available and needed. Android does that in multiple ways: + ++ **Open network notification**: Informing users about available _good_ open + Wi-Fi networks ++ **Turn on Wi-Fi automatically**: Re-enabling Wi-Fi when the user is near a + previously saved network ++ **Connect to open networks**: Automatically connecting the user to _good_ + open Wi-Fi networks ++ **Badging**: Displaying information about the quality of the available + networks + +The features described are implemented by AOSP code and you do not have to +explicitly enable or configure them. + +## Open network notification + +The *Open network notification* feature raises a notification to the user +whenever: + ++ Wi-Fi is enabled ++ The device is not connected to a Wi-Fi network ++ A Wi-Fi network that is both **open** and has a *sufficiently* + **high RSSI** (the same RSSI threshold as used by the internal Wi-Fi + selection algorithm) is available + +The feature can be enabled or disabled by the user using the Settings app at: + +**Settings** > **Network & internet** > **Wi-Fi** > **Wi-Fi preferences** > +**Open network notification** + +<figure> + <img src="/devices/tech/connect/images/open-network-notification.png" + alt="Open network notification feature" class="screenshot" width="350"> + <figcaption><strong>Figure 1.</strong> Open network notification + feature</figcaption> +</figure> + +## Turn on Wi-Fi automatically + +Users may disable Wi-Fi for a variety of reasons (e.g. a connection to a bad +network) and can then forget to re-enable it when arriving back home, resulting +in a bad experience (e.g. not being able to control home automation devices). +The _Turn on Wi-Fi automatically_ feature, introduced in +Android {{ androidPVersionNumber }}, +solves this issue by automatically +re-enabling Wi-Fi whenever the device is near a Wi-Fi network that is both a +**saved** network (i.e. one which the user explicitly connected to in the past) +and has a _sufficiently_ **high RSSI.** + +The feature can be enabled or disabled by the user using the Settings app at: + +**Settings** > **Network & internet** > **Wi-Fi** > **Wi-Fi preferences** > +**Turn on Wi-Fi automatically** + +<figure> + <img src="/devices/tech/connect/images/auto-wifi.png" + alt="Turn on Wi-Fi automatically" class="screenshot" width="350"> + <figcaption><strong>Figure 2.</strong> Turn on Wi-Fi automatically + feature</figcaption> +</figure> + +Wi-Fi Scanning (for Location) must be enabled for this feature to function. If +Wi-Fi Scanning is not enabled the user is prompted for permission to enable it. +Wi-Fi Scanning is required because scan results are used to determine whether +the device is in the vicinity of a Wi-Fi network that meets the criteria to +re-enable Wi-Fi connectivity. + +The feature avoids re-enabling Wi-Fi immediately after a user disables it, even +if the device observes a saved Wi-Fi network of sufficient quality. For +example, if the user is in the office and is connected to the office Wi-Fi (a +_saved_ network) and then disables Wi-Fi, the feature will not re-enable Wi-Fi +until the user arrives at a different environment with a different saved +network that meets the re-enabling criteria. + +## Auto connect to open networks + +The _Connect to open networks_ feature, available on Android 8.0 and higher, +automatically connects the device to +available high quality networks. The criteria are: + ++ Wi-Fi is enabled ++ The device is not connected to a Wi-Fi network ++ A Wi-Fi network that is both **open** and is _good_, as reported by the + external _Network rating provider_ (see next section), is available. + +The feature can be enabled or disabled by the user using the Settings app at: + +**Settings** > **Network & internet** > **Wi-Fi** > **Wi-Fi preferences** > +**Connect to open networks** + +<figure> + <img src="/devices/tech/connect/images/connect-open-networks.png" + alt="Connect to open networks" class="screenshot" width="350"> + <figcaption><strong>Figure 3.</strong> Connect to open networks feature and + Network rating provider menu</figcaption> +</figure> + +The _Connect to open networks_ feature is disabled if an external +_Network rating provider_ is not selected. The +user can select any of the available network rating providers using the Network +rating provider menu. + +### External network rating provider + +To help determine what constitutes a _good_ Wi-Fi network, Android supports +external _Network rating providers_ (also known as _Network scorers_) that +provide information about the quality of open Wi-Fi networks. For instance, a +network scorer may use historical performance data (e.g. this AP worked really +well in the past, good idea to try it now) to determine that a particular Wi-Fi +network is good. + +The list of available network rating providers is available to the user from +the **Settings** > **Network & internet** > **Wi-Fi** > **Wi-Fi preferences** > +**Advanced** > **Network rating provider** menu. The user may select one or +none of them. If none are available or selected, the _Connect to open networks_ +feature is disabled. + +You do not have to provide an external network rating provider. To create a +provider: + ++ Implement the API documented in `NetworkScoreManager`. ++ The external network rating provider must be a privileged app. ++ Configure your system to use your custom implementation by updating the + `config_defaultNetworkRecommendationProviderPackage` key in your product's + overlay configuration file of + `frameworks/base/core/res/res/values/config.xml`. + +If you do not want to include the default network rating provider +functionality, you can choose not to set a default provider property and hide +the **Network rating provider** screen in AOSP. + +### Wi-Fi network badging + +The information provided by the network rating provider is also used by the +_Wi-Fi Picker_ to add information on the quality of available Wi-Fi networks, +which can help the user with selecting Wi-Fi networks manually. Networks for +which information is available (provided by the external network rating +provider) will display speed information below the network name. + +<figure> + <img src="/devices/tech/connect/images/wifi-network-quality.png" + alt="Wi-Fi network quality" class="screenshot" width="350"> + <figcaption><strong>Figure 4.</strong> Wi-Fi networks with information + about network quality </figcaption> +</figure> + +Because this feature requires an external network rating provider, it is not +available, and no speed/quality information is displayed, if no such provider +is available or selected. diff --git a/en/devices/tech/connect/wifi-mac-randomization.md b/en/devices/tech/connect/wifi-mac-randomization.md index d1f4220b..01ee18b3 100644 --- a/en/devices/tech/connect/wifi-mac-randomization.md +++ b/en/devices/tech/connect/wifi-mac-randomization.md @@ -48,7 +48,7 @@ To implement MAC randomization on your device: implementation behavior may not work with certain chip vendors. 1. Set - [`config_wifi_support_connected_mac_randomization`](https://android.googlesource.com/platform/packages/apps/Settings/+/master/res/values/config.xml#46) + [`config_wifi_support_connected_mac_randomization`](https://android.googlesource.com/platform/packages/apps/Settings/+/master/res/values/config.xml#46){: .external} to **true** in the Settings `config.xml` (this can be done in a device custom overlay). @@ -67,7 +67,7 @@ The System UI must: Wi-Fi interface MAC address if the MAC randomization feature is enabled. Use the -[reference implementation](https://android.googlesource.com/platform/packages/apps/Settings/+/master/src/com/android/settings/development/WifiConnectedMacRandomizationPreferenceController.java) +[reference implementation](https://android.googlesource.com/platform/packages/apps/Settings/+/master/src/com/android/settings/development/WifiConnectedMacRandomizationPreferenceController.java){: .external} of Settings UI to implement new prompts. ## Validation diff --git a/en/devices/tech/connect/wifi-overview.md b/en/devices/tech/connect/wifi-overview.md index 702fdab1..6711a3a3 100644 --- a/en/devices/tech/connect/wifi-overview.md +++ b/en/devices/tech/connect/wifi-overview.md @@ -42,7 +42,7 @@ the Android Wi-Fi stack. ## Application framework At the application framework level is application code, which uses the various -[android.net.wifi](https://developer.android.com/reference/android/net/wifi/package-summary) +[android.net.wifi](https://developer.android.com/reference/android/net/wifi/package-summary){: .external} APIs to interact with the Wi-Fi framework and hardware. Internally, this code calls the Wi-Fi process through the Binder IPC mechanism. diff --git a/en/devices/tech/connect/wifi-rtt.md b/en/devices/tech/connect/wifi-rtt.md index be44df7f..b01ee9db 100644 --- a/en/devices/tech/connect/wifi-rtt.md +++ b/en/devices/tech/connect/wifi-rtt.md @@ -21,12 +21,13 @@ Book: /_book.yaml # Wi-Fi RTT (IEEE 802.11mc) -The [Wi-Fi Round Trip Time (RTT)](https://developer.android.com/guide/topics/connectivity/wifi-rtt) feature in Android -{{ androidPVersionNumber }} enables supporting devices to measure a -distance to other supporting devices: whether they are Access Points (APs) or -Wi-Fi Aware peers (if [Wi-Fi Aware](/devices/tech/connect/wifi-aware) is -supported on the device). This feature, built upon the IEEE 802.11mc protocol, -enables apps to use enhanced location accuracy and awareness. +The +[Wi-Fi Round Trip Time (RTT)](https://developer.android.com/guide/topics/connectivity/wifi-rtt){: .external} +feature in Android {{ androidPVersionNumber }} enables supporting devices to +measure a distance to other supporting devices: whether they are Access Points +(APs) or Wi-Fi Aware peers (if [Wi-Fi Aware](/devices/tech/connect/wifi-aware) +is supported on the device). This feature, built upon the IEEE 802.11mc +protocol, enables apps to use enhanced location accuracy and awareness. ## Examples and source @@ -41,7 +42,7 @@ Follow the Wi-Fi HIDL to employ the Wi-Fi RTT feature: You can refer to the legacy Wi-Fi HAL to see how it correlates with the new HIDL interface: -[hardware/libhardware_legacy/+/master/include/hardware_legacy/rtt.h](https://android.googlesource.com/platform/hardware/libhardware_legacy/+/master/include/hardware_legacy/rtt.h). +[hardware/libhardware_legacy/+/master/include/hardware_legacy/rtt.h](https://android.googlesource.com/platform/hardware/libhardware_legacy/+/master/include/hardware_legacy/rtt.h){: .external}. ## Implementation @@ -69,15 +70,20 @@ Otherwise, everything required for this feature is included in AOSP. ## MAC randomization -To enhance privacy, the MAC address used during Wi-Fi RTT transactions must be randomized, i.e., it must not match the native MAC address of the Wi-Fi interface. However, as an exception, when a device is associated with an AP, it may use the MAC address with which it is associated for any RTT transactions with that AP or with other APs. +To enhance privacy, the MAC address used during Wi-Fi RTT transactions must be +randomized, i.e., it must not match the native MAC address of the Wi-Fi +interface. However, as an exception, when a device is associated with an AP, it +may use the MAC address with which it is associated for any RTT transactions +with that AP or with other APs. ## Validation Android Compatibility Test Suite (CTS) tests exist for this feature. CTS detects -when the feature is enabled and automatically includes the associated tests. This feature can also be tested using the +when the feature is enabled and automatically includes the associated tests. +This feature can also be tested using the [Vendor Test Suite (VTS)](/devices/tech/test_infra/tradefed/fundamentals/vts) and -[acts/sl4a](https://android.googlesource.com/platform/tools/test/connectivity/+/master/acts/tests/google/wifi/), +[acts/sl4a](https://android.googlesource.com/platform/tools/test/connectivity/+/master/acts/tests/google/wifi/){: .external}, a test suite that conducts extensive integration testing. ### Unit tests @@ -145,9 +151,9 @@ be tested under the following conditions: and aligned with the 0.5m markers, also at 20cm above the floor. Note: This repetitive task can be performed by a small robot, but a human operator is also fine. -1. 50 ranging results should be recorded at each marker, along with the distance - from the access point. Statistics, such as range mean and variance should be - calculated for each marker position. +1. 50 ranging results should be recorded at each marker, along with the + distance from the access point. Statistics, such as range mean and variance, + should be calculated for each marker position. From the results in step 5, a chart can be drawn for ground truth (x-axis) against estimated range (y-axis) and a best fit regression line estimated. Ideal diff --git a/en/devices/tech/dalvik/dex-format.html b/en/devices/tech/dalvik/dex-format.html index 38547c97..b30c301e 100644 --- a/en/devices/tech/dalvik/dex-format.html +++ b/en/devices/tech/dalvik/dex-format.html @@ -2014,6 +2014,21 @@ passed in order and without any type conversions. <td>0x05</td> <td>Method handle is an instance method invoker</td> </tr> +<tr> + <td>METHOD_HANDLE_TYPE_INVOKE_CONSTRUCTOR</td> + <td>0x06</td> + <td>Method handle is a constructor method invoker</td> +</tr> +<tr> + <td>METHOD_HANDLE_TYPE_INVOKE_DIRECT</td> + <td>0x07</td> + <td>Method handle is a direct method invoker</td> +</tr> +<tr> + <td>METHOD_HANDLE_TYPE_INVOKE_INTERFACE</td> + <td>0x08</td> + <td>Method handle is an interface method invoker</td> +</tr> </tbody> </table> diff --git a/en/devices/tech/datausage/ebpf-traffic-monitor.md b/en/devices/tech/datausage/ebpf-traffic-monitor.md index 6d3f6139..6be4cf9b 100644 --- a/en/devices/tech/datausage/ebpf-traffic-monitor.md +++ b/en/devices/tech/datausage/ebpf-traffic-monitor.md @@ -101,6 +101,7 @@ HALs, drivers, or kernel code are required to implement the new eBPF tool. 1. `CONFIG_BPF=y` 1. `CONFIG_BPF_SYSCALL=y` 1. `CONFIG_NETFILTER_XT_MATCH_BPF=y` + 1. `CONFIG_INET_UDP_DIAG=y` The [VTS kernel config test](https://android.googlesource.com/platform/test/vts-testcase/kernel/+/master/config/VtsKernelConfigTest.py){: .external} diff --git a/en/devices/tech/display/display-cutouts.md b/en/devices/tech/display/display-cutouts.md index a99987ae..6e41f173 100644 --- a/en/devices/tech/display/display-cutouts.md +++ b/en/devices/tech/display/display-cutouts.md @@ -40,7 +40,7 @@ Android {{ androidPVersionNumber }} supports the following types of cutouts: ## Examples and source The following window manager code at -[frameworks/base/services/core/java/com/android/server/policy/PhoneWindowManager.java](https://android.googlesource.com/platform/frameworks/base/+/master/services/core/java/com/android/server/policy/PhoneWindowManager.java) +[PhoneWindowManager.java](https://android.googlesource.com/platform/frameworks/base/+/master/services/core/java/com/android/server/policy/PhoneWindowManager.java){: .external} shows how display frames are inset to the safe area when `LAYOUT_IN_DISPLAY_CUTOUT_MODE_ALWAYS` is not set. @@ -94,7 +94,7 @@ if (cutoutMode != LAYOUT_IN_DISPLAY_CUTOUT_MODE_ALWAYS) { ``` SystemUI renders in the cutout area, and needs to determine where it can draw. -[frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBarView.java](https://android.googlesource.com/platform/frameworks/base/+/master/packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBarView.java) +[PhoneStatusBarView.java](https://android.googlesource.com/platform/frameworks/base/+/master/packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBarView.java){: .external} provides an example of a view that determines where the display cutout is, how big it is, and whether or not the inset from the nav bar avoids the cutout area. @@ -225,8 +225,8 @@ black.</p></td> See these `dimens` files for the default definitions: -+ [`core/res/res/values-land/dimens.xml`](https://android.googlesource.com/platform/frameworks/base/+/master/core/res/res/values-land/dimens.xml) -+ [`core/res/res/values/dimens.xml`](https://android.googlesource.com/platform/frameworks/base/+/master/core/res/res/values/dimens.xml) ++ [`core/res/res/values-land/dimens.xml`](https://android.googlesource.com/platform/frameworks/base/+/master/core/res/res/values-land/dimens.xml){: .external} ++ [`core/res/res/values/dimens.xml`](https://android.googlesource.com/platform/frameworks/base/+/master/core/res/res/values/dimens.xml){: .external} Example overlay for an emulated cutout: @@ -276,4 +276,4 @@ Example overlay for an emulated cutout: ## Validation To validate your implementation of display cutouts, run the CTS tests at -[tests/framework/base/windowmanager/src/android/server/wm](https://android.googlesource.com/platform/cts/+/master/tests/framework/base/windowmanager/src/android/server/wm). +[tests/framework/base/windowmanager/src/android/server/wm](https://android.googlesource.com/platform/cts/+/master/tests/framework/base/windowmanager/src/android/server/wm){: .external}. diff --git a/en/devices/tech/display/synched-app-transitions.md b/en/devices/tech/display/synched-app-transitions.md index 6247b29a..d4c5c705 100644 --- a/en/devices/tech/display/synched-app-transitions.md +++ b/en/devices/tech/display/synched-app-transitions.md @@ -42,16 +42,13 @@ can transform notifications into the app surface. See the following references for this feature. -+ [`ActivityOptions.makeRemoteAnimation`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/app/ActivityOptions.java#844) - -+ [`RemoteAnimationAdapter`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/view/RemoteAnimationAdapter.java) - -+ [`RemoteAnimationRunner`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/view/IRemoteAnimationRunner.aidl) - -+ [`Activity.registerRemoteAnimations`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/app/Activity.java#7869) ++ [`ActivityOptions.makeRemoteAnimation`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/app/ActivityOptions.java#844){: .external} ++ [`RemoteAnimationAdapter`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/view/RemoteAnimationAdapter.java){: .external} ++ [`RemoteAnimationRunner`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/view/IRemoteAnimationRunner.aidl){: .external} ++ [`Activity.registerRemoteAnimations`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/app/Activity.java#7869){: .external} For a reference implementation for the notification launch animation, see -[`ActivityLaunchAnimator.java`](https://android.googlesource.com/platform/frameworks/base/+/master/packages/SystemUI/src/com/android/systemui/statusbar/notification/ActivityLaunchAnimator.java). +[`ActivityLaunchAnimator.java`](https://android.googlesource.com/platform/frameworks/base/+/master/packages/SystemUI/src/com/android/systemui/statusbar/notification/ActivityLaunchAnimator.java){: .external}. ## Implementation @@ -65,4 +62,4 @@ Note: This feature increases the load on the GPU and CPU during animations. To validate the performance of the animations, measure the performance of the controlling app, i.e. SystemUI or Launcher, during the animations as described in -[Test UI performance](https://developer.android.com/training/testing/performance). +[Test UI performance](https://developer.android.com/training/testing/performance){: .external}. diff --git a/en/devices/tech/health/deprecation.md b/en/devices/tech/health/deprecation.md index 4e92e7e3..fcaf711f 100644 --- a/en/devices/tech/health/deprecation.md +++ b/en/devices/tech/health/deprecation.md @@ -22,7 +22,7 @@ The framework will continue to work with health@1.0 until it is fully deprecated according to the standard [HAL deprecation schedule](/devices/architecture/vintf/fcm#hal-version-deprecation). When health@1.0 is deprecated (entry removed from -[framework compatibility matrix](https://source.android.com/devices/architecture/vintf/comp-matrices)), +[framework compatibility matrix](/devices/architecture/vintf/comp-matrices)), `healthd` and `libbatterymonitor` must also be removed from system to avoid unknown behaviors for healthd. As health@1.0 is an optional HAL and all `healthd` dependencies to health@1.0 are guarded by NULL checks, nothing should diff --git a/en/devices/tech/health/implementation.md b/en/devices/tech/health/implementation.md index 156c9e08..7132fe01 100644 --- a/en/devices/tech/health/implementation.md +++ b/en/devices/tech/health/implementation.md @@ -107,7 +107,7 @@ Then: * Update necessary SELinux permissions. For details, refer to -[hardware/interfaces/health/2.0/README.md](https://android.googlesource.com/platform/hardware/interfaces/+/master/health/2.0/README.md). +[hardware/interfaces/health/2.0/README.md](https://android.googlesource.com/platform/hardware/interfaces/+/master/health/2.0/README.md){: .external}. ## Health clients diff --git a/en/devices/tech/health/index.md b/en/devices/tech/health/index.md index 13790904..73c3fd1f 100644 --- a/en/devices/tech/health/index.md +++ b/en/devices/tech/health/index.md @@ -117,10 +117,10 @@ and recovery mode The health@2.0 HAL provides the same functionality to the framework as the old healthd daemon. It also provides APIs that are similar to what healthd previously provided as a binder service (i.e. -[IBatteryPropertiesRegistrar](https://android.googlesource.com/platform/frameworks/base/+/2392cbd888212f61a242058f749bcc39d495bf4b/core/java/android/os/IBatteryPropertiesRegistrar.aidl)). +[IBatteryPropertiesRegistrar](https://android.googlesource.com/platform/frameworks/base/+/2392cbd888212f61a242058f749bcc39d495bf4b/core/java/android/os/IBatteryPropertiesRegistrar.aidl){: .external}). The main interface, -[IHealth](https://android.googlesource.com/platform/hardware/interfaces/+/de542acbbf46812cfb53d231ecb50048baf8780e/health/2.0/IHealth.hal) +[IHealth](https://android.googlesource.com/platform/hardware/interfaces/+/de542acbbf46812cfb53d231ecb50048baf8780e/health/2.0/IHealth.hal){: .external} , provides the following functions: * `registerCallback`, to replace diff --git a/en/devices/tech/index.html b/en/devices/tech/index.html deleted file mode 100644 index fa523b43..00000000 --- a/en/devices/tech/index.html +++ /dev/null @@ -1,32 +0,0 @@ -<html devsite> - <head> - <title>Configure Android Devices</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2018 The Android Open Source Project - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. - --> - - -<p>Welcome to the Android platform configuration documentation. Here you can -find instructions for optimizing services and customizing features.</p> - -<p>Use the horizontal menu above to delve into specific subtabs and -sections.</p> - - </body> -</html> diff --git a/en/devices/tech/settings/index.html b/en/devices/tech/settings/index.html deleted file mode 100644 index 4f1ad735..00000000 --- a/en/devices/tech/settings/index.html +++ /dev/null @@ -1,31 +0,0 @@ -<html devsite> - <head> - <title>Design Android Settings</title> - <meta name="project_path" value="/_project.yaml" /> - <meta name="book_path" value="/_book.yaml" /> - </head> - <body> - <!-- - Copyright 2017 The Android Open Source Project - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. - --> - - - -<p>The pages in this section explain how to design consistent settings -interface. Use the horitonzal menu at the top to delve into specific subtabs and -sections.</p> - - </body> -</html> diff --git a/en/devices/tech/settings/settings-guidelines.md b/en/devices/tech/settings/settings-guidelines.md index 2d29aa8b..448a253d 100644 --- a/en/devices/tech/settings/settings-guidelines.md +++ b/en/devices/tech/settings/settings-guidelines.md @@ -419,7 +419,8 @@ explanation. If the form has one input field, use a normal dialog. This provides an easy way for users to enter a single input. -However, if the form has several fields, consider using a [full-screen dialog](https://material.io/design/components/dialogs.html#full-screen-dialog). +However, if the form has several fields, consider using a +[full-screen dialog](https://material.io/design/components/dialogs.html#full-screen-dialog){: .external}. This provides more screen space to arrange the fields in a clear pattern. <img src="images/settings-guidelines39.png" width="250" class="screenshot"> diff --git a/en/security/bulletin/_translation.yaml b/en/security/bulletin/_translation.yaml index 37f58a17..6a8d393a 100644 --- a/en/security/bulletin/_translation.yaml +++ b/en/security/bulletin/_translation.yaml @@ -1,4 +1,10 @@ ignore_paths: +- /security/bulletin/2018-06-01 +- /security/bulletin/2018-05-01 +- /security/bulletin/2018-04-01 +- /security/bulletin/2018-03-01 +- /security/bulletin/2018-02-01 +- /security/bulletin/2018-01-01 - /security/bulletin/2017 - /security/bulletin/2017-12-01 - /security/bulletin/2017-11-01 diff --git a/en/security/images/biometricprompt-architecture.png b/en/security/images/biometricprompt-architecture.png Binary files differindex edf3b79d..a909a9ca 100644 --- a/en/security/images/biometricprompt-architecture.png +++ b/en/security/images/biometricprompt-architecture.png diff --git a/en/security/keystore/tags.html b/en/security/keystore/tags.html index 0273fe06..5727be91 100644 --- a/en/security/keystore/tags.html +++ b/en/security/keystore/tags.html @@ -407,7 +407,7 @@ the <code>additionalParams</code> argument of If the specifiedmode is not in the modes associated with the key, the operation fails with <code>ErrorCode::INCOMPATIBLE_BLOCK_MODE</code>.</p> -<h2 id=boot_patchlevel">Tag::BOOT_PATCHLEVEL</h2> +<h2 id="boot_patchlevel">Tag::BOOT_PATCHLEVEL</h2> <p><strong>Version</strong>: 4</p> <p>Tag::BOOT_PATCHLEVEL specifies the boot image (kernel) security patch level with which the key may be used. This tag is never sent to the keymaster TA, but diff --git a/en/security/overview/acknowledgements.html b/en/security/overview/acknowledgements.html index 7071cb74..a596c769 100644 --- a/en/security/overview/acknowledgements.html +++ b/en/security/overview/acknowledgements.html @@ -88,6 +88,11 @@ of Symantec</td> <td>CVE-2017-13322</td> </tr> <tr> + <td>Scott Bauer + (<a href="https://twitter.com/ScottyBauer1" class="external">@ScottyBauer1</a>)</td> + <td>CVE-2018-9441</td> + </tr> + <tr> <td>Tencent Blade Team</td> <td>CVE-2017-18306, CVE-2017-18307</td> </tr> @@ -351,8 +356,7 @@ class="external">Mobile Security Research Team</a>, <tr> <td><a href="http://weibo.com/ele7enxxh">Zinuo Han</a> of Chengdu Security Response Center, Qihoo 360 Technology Co. Ltd</td> - <td>CVE-2017-13321, CVE-2017-13315, CVE-2017-13318, CVE-2017-13323, CVE-2017-13312, - CVE-2017-13319, CVE-2017-13317</td> + <td>CVE-2017-13321, CVE-2017-13318, CVE-2017-13323, CVE-2017-13319, CVE-2017-13317</td> </tr> </table> @@ -943,8 +947,8 @@ CVE-2017-8263, CVE-2017-9682, CVE-2017-13162</td> <td>Chenfu Bao (包沉浮) of Baidu X-Lab (百度安全实验室)</td> <td>CVE-2016-8417, CVE-2016-10236, CVE-2017-0728, CVE-2017-0738, CVE-2017-0766, CVE-2017-0794, CVE-2017-9681, CVE-2017-9684, CVE-2017-9693, -CVE-2017-9694, CVE-2017-9715, CVE-2017-9717, CVE-2017-9720, CVE-2017-11001, -CVE-2017-10999, CVE-2017-11057, +CVE-2017-9694, CVE-2017-9696, CVE-2017-9702, CVE-2017-9715, CVE-2017-9717, +CVE-2017-9720, CVE-2017-11001, CVE-2017-10999, CVE-2017-11057, CVE-2017-11060, CVE-2017-11061, CVE-2017-11064, CVE-2017-11089, CVE-2017-11090</td> </tr> <tr> @@ -952,8 +956,7 @@ CVE-2017-11060, CVE-2017-11061, CVE-2017-11064, CVE-2017-11089, CVE-2017-11090</ <td>CVE-2016-10280, CVE-2016-10281, CVE-2017-0463, CVE-2017-0506, CVE-2017-0565, CVE-2017-0711, CVE-2017-0741, CVE-2017-0742, CVE-2017-0751, CVE-2017-0796, CVE-2017-0798, CVE-2017-0800, CVE-2017-0827, CVE-2017-0843, -CVE-2017-0864, CVE-2017-9696, CVE-2017-9702, CVE-2017-9708, -CVE-2017-11000, CVE-2017-11059, CVE-2017-13170</td> +CVE-2017-0864, CVE-2017-9708, CVE-2017-11000, CVE-2017-11059, CVE-2017-13170</td> </tr> <tr> <td>Chenxiong Qian of Georgia Tech</td> @@ -1241,8 +1244,8 @@ CVE-2017-8261, CVE-2017-8268, CVE-2017-9718, CVE-2017-1000380</td> <td>Lenx Wei (韦韬) of Baidu X-Lab (百度安全实验室)</td> <td>CVE-2016-8417, CVE-2016-10236, CVE-2017-0728, CVE-2017-0738, CVE-2017-0766, CVE-2017-0794 CVE-2017-9681, CVE-2017-9684, CVE-2017-9693, -CVE-2017-9694, CVE-2017-9696, CVE-2017-9702, CVE-2017-9720, CVE-2017-10999, -CVE-2017-11001, CVE-2017-11057, +CVE-2017-9694, CVE-2017-9696, CVE-2017-9702, CVE-2017-9715, CVE-2017-9717, +CVE-2017-9720, CVE-2017-10999, CVE-2017-11001, CVE-2017-11057, CVE-2017-11060, CVE-2017-11061, CVE-2017-11064, CVE-2017-11089, CVE-2017-11090</td> </tr> <tr> diff --git a/en/security/overview/updates-resources.html b/en/security/overview/updates-resources.html index 03a0a4ef..ddc053a4 100644 --- a/en/security/overview/updates-resources.html +++ b/en/security/overview/updates-resources.html @@ -81,23 +81,32 @@ This table is ordered from least to most privileged.</p> </tr> <tr> <td>Privileged process</td> - <td>An application or process with capabilities that are restricted by + <td>An application or process with capabilities that would be forbidden by the SELinux <code>untrusted_app</code> domain.<br /> OR<br /> An application or process with important privileges that a third-party - application cannot obtain.</td> + application cannot obtain.<br /> + OR<br /> + A built-in hardware component on the device that is not part of the Trusted Computing Base + (TCB).</td> </tr> <tr> <td>Trusted Computing Base (TCB)</td> <td>Functionality that is part of the kernel, runs in the same CPU context as the kernel (such as device drivers), has direct access to kernel memory (such as - hardware components on the device), or is one of a handful of user services + hardware components on the device), has the capability to load scripts into a kernel component + (e.g. eBPF), the Baseband Processor, or is one of a handful of user services that is considered kernel equivalent: <code>init</code>, <code>ueventd</code>, and <code>vold</code>.</td> </tr> <tr> + <td>Bootloader</td> + <td>A component that configures the device on boot and then passes control to the + Android OS.</td> + </tr> + <tr> <td>Trusted Execution Environment (TEE)</td> - <td> A component that is designed to be protected from even a hostile kernel.</td> + <td>A component that is designed to be protected from even a hostile kernel.</td> </tr> </table> @@ -118,12 +127,14 @@ severity:</p> <td> <ul> <li>Arbitrary code execution in the TEE</li> - <li>Remote arbitrary code execution in a privileged process or the TCB</li> + <li>Remote arbitrary code execution in a privileged process, Bootloader, or the TCB</li> <li>Remote permanent denial of service (device inoperability: completely permanent or requiring re-flashing the entire operating system)</li> <li>Remote bypass of user interaction requirements on package installation or equivalent behavior</li> - <li>Secure Boot bypass</li> + <li>Remote bypass of user interaction requirements for any developer or security + settings modifications</li> + <li>Remote Secure Boot bypass</li> </ul> </td> </tr> @@ -131,26 +142,30 @@ severity:</p> <td><strong>High</strong></td> <td> <ul> + <li>Local Secure Boot bypass</li> <li>Remote arbitrary code execution in an unprivileged process</li> - <li>Arbitrary local code execution in a privileged process or the TCB</li> + <li>Local arbitrary code execution in a privileged process, Bootloader, or the TCB</li> <li>Unauthorized access to data secured by the TEE</li> - <li>Remote access to protected data (data normally accessible only to locally - installed apps that request permission, or that is limited to a privileged - process)</li> + <li>Local bypass of user interaction requirements on package installation or equivalent + behavior</li> + <li>Remote access to protected data (data that is limited to a privileged process)</li> <li>Local permanent denial of service (device inoperability: completely permanent or requiring re-flashing the entire operating system)</li> - <li>Remote temporary device denial of service (remote hang or reboot)</li> - <li>Remote bypass of user interaction requirements (access to functionality that + <li>Remote permanent denial of service (device requires a factory reset)</li> + <li>Remote bypass of user interaction requirements (access to functionality or data that would normally require either user initiation or user permission)</li> + <li>A general bypass for a defense in depth or exploit mitigation technology in the + Bootloader or TEE</li> + <li>A general bypass for operating system protections that isolate application data + or user profiles from each other</li> <li>Local bypass of user interaction requirements for any developer or security settings modifications</li> - <li>A general bypass for operating system protections that isolate application - data from other applications</li> - <li>A general bypass for operating system protections that isolate users or - profiles from one another</li> <li>Cryptographic Vulnerability in Standard TLS that allows for man-in-the-middle attacks</li> <li>Lockscreen bypass</li> + <li>Bypass of Device Protection/ Factory Reset Protection / Carrier Restrictions</li> + <li>Targeted prevention of access to emergency services</li> + <li>Bypass of user interaction requirements that are secured by the TEE</li> </ul> </td> </tr> @@ -159,23 +174,19 @@ severity:</p> <td> <ul> <li>Remote arbitrary code execution in a constrained process</li> + <li>Remote temporary device denial of service (remote hang or reboot)</li> <li>Local arbitrary code execution in an unprivileged process</li> <li>A general bypass for a defense in depth or exploit mitigation technology in - a privileged process, the TCB, or the TEE</li> + a privileged process or the TCB</li> <li>Bypass of restrictions on a constrained process</li> <li>Remote access to unprotected data (data normally accessible to any locally installed app)</li> - <li>Local access to protected data (data normally accessible only to locally - installed apps that request permission, or that is limited to a privileged - process)</li> + <li>Local access to protected data (data that is limited to a privileged process)</li> <li>Local bypass of user interaction requirements (access to functionality that would normally require either user initiation or user permission)</li> <li>Local permanent denial of service (device requires a factory reset)</li> <li>Cryptographic Vulnerability in standard crypto primitives that allows leaking of plaintext (not primitives used in TLS)</li> - <li>Bypass of Device Protection/ Factory Reset Protection</li> - <li>Bypass of Carrier Restrictions</li> - <li>Targeted prevention of access to emergency services</li> </ul> </td> </tr> @@ -243,10 +254,15 @@ ratings may change based on circumstances.</p> <td>Moderate Severity if the underlying vulnerability is Moderate or higher</td> </tr> <tr> - <td>Requires tamper-evident physical access</td> + <td>Requires physical access to device internals</td> <td>-2 Severity</td> </tr> <tr> + <td>A local attack that requires Developer Mode or any persistent developer mode settings + to be enabled on the device (and is not a bug in Developer Mode).</td> + <td>No higher than Low</td> + </tr> + <tr> <td>If no SELinux domain can conduct the operation under the Google-provided SEPolicy</td> <td>No Security Impact</td> diff --git a/en/security/verifiedboot/dm-verity.html b/en/security/verifiedboot/dm-verity.html index cc8e445f..952edd97 100644 --- a/en/security/verifiedboot/dm-verity.html +++ b/en/security/verifiedboot/dm-verity.html @@ -79,6 +79,17 @@ then verified up the tree. And since reading the block is such an expensive operation, the latency introduced by this block-level verification is comparatively nominal.</p> +<aside class="note"> +As an optimization for Android Go and similar low-RAM devices, dm-verity can be +configured to validate pages only the first time they are read from the data +device, rather than every time. After the first validation, a bit is set to +indicate successful validation. Because this optimization provides +a slightly reduced level of integrity guarantees, it should not be used for +higher-RAM devices. To learn more, see <a +href="https://android.googlesource.com/kernel/common/+/a73c9bca682673630cd95a7fa55190f53bab73cf" +class="external">these kernel patches</a>. +</aside> + <p>If verification fails, the device generates an I/O error indicating the block cannot be read. It will appear as if the filesystem has been corrupted, as is expected.</p> diff --git a/en/setup/community.html b/en/setup/community.html index 7b67d804..0f576a3f 100644 --- a/en/setup/community.html +++ b/en/setup/community.html @@ -308,7 +308,7 @@ banned from the list. are not welcome in our community under any circumstances. We don't have a formal policy on dealing with troublemakers, and we hope we never need one. That said, we do pledge to do our best to be fair, and we will always try to -warn someone before banning him or her.</p> +warn someone before banning them.</p> <h3 id="contacting">Contacting the moderators</h3> <p>If you see anyone being rude, call them out on it. This is your group too, diff --git a/en/setup/start/p-release-notes.md b/en/setup/start/p-release-notes.md index dcfedad0..cc5b6fce 100644 --- a/en/setup/start/p-release-notes.md +++ b/en/setup/start/p-release-notes.md @@ -607,6 +607,13 @@ associated to a network. In this release, a developer option can be enabled to cause a device to use a randomized MAC address when connecting to a Wi-Fi network. +#### Turn on Wi-Fi automatically + +[Turn on Wi-Fi automatically](/devices/tech/connect/wifi-infrastructure#turn_on_wi-fi_automatically) +allows users to automatically re-enable Wi-Fi whenever the device is near a +Wi-Fi network that has been saved and has a sufficiently high relative received +signal strength indicator (RSSI). + #### Wi-Fi Round Trip Time (RTT) [Wi-Fi Round Trip Time (RTT)](/devices/tech/connect/wifi-rtt) allows devices to diff --git a/en/setup/start/site-updates.html b/en/setup/start/site-updates.html index 78dab3a0..4aff2951 100644 --- a/en/setup/start/site-updates.html +++ b/en/setup/start/site-updates.html @@ -109,6 +109,8 @@ the Wi-Fi section includes the following new articles:</p> <ul> <li><a href="/devices/tech/connect/wifi-overview">Overview</a></li> <li><a href="/devices/tech/connect/wifi-hal">Wi-Fi HAL</a></li> + <li><a href="/devices/tech/connect/wifi-infrastructure"> + Wi-Fi Infrastructure Features</a></li> <li><a href="/devices/tech/connect/wifi-passpoint">Passpoint R1</a></li> <li><a href="/devices/tech/connect/wifi-debug">Testing and Debugging</a></li> </ul> diff --git a/ja/security/bulletin/2018-01-01.html b/ja/security/bulletin/2018-01-01.html index 31a530f1..d355c84c 100644 --- a/ja/security/bulletin/2018-01-01.html +++ b/ja/security/bulletin/2018-01-01.html @@ -22,15 +22,15 @@ <p><em>2018 年 1 月 2 日公開 | 2018 年 1 月 29 日更新</em></p> <p> -Android のセキュリティに関する公開情報には、Android 搭載端末に影響を与えるセキュリティの脆弱性の詳細を掲載しています。セキュリティ パッチレベル 2018-01-05 以降では、下記のすべての問題に対処しています。端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705">Android のバージョンを確認して更新する</a>をご覧ください。 +Android のセキュリティに関する公開情報には、Android 搭載端末に影響を及ぼすセキュリティの脆弱性の詳細を掲載しています。セキュリティ パッチレベル 2018-01-05 以降では、下記のすべての問題に対処しています。端末のセキュリティ パッチレベルを確認するには、「<a href="https://support.google.com/pixelphone/answer/4457705">Android のバージョンを確認して更新する</a>」の記事をご覧ください。 </p> <p> -Android パートナーには、情報公開の 1 か月前までにすべての問題が通知されます。Android オープンソース プロジェクト（AOSP）のリポジトリに、下記の問題に対するソースコードのパッチをリリースしています。また、この公開情報では、これらのパッチへのリンクに加え、AOSP 以外のパッチへのリンクも掲載しています。</p> +Android パートナーには、情報公開の少なくとも 1 か月前にすべての問題が通知されます。Android オープンソース プロジェクト（AOSP）のリポジトリに、下記の問題に対するソースコードのパッチをリリースしています。また、この公開情報では、これらのパッチへのリンクに加え、AOSP 以外のパッチへのリンクも掲載しています。</p> <p> 下記の問題のうち最も重大度の高いものは、メディア フレームワークに重大なセキュリティの脆弱性があるため、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあることです。<a href="/security/overview/updates-resources.html#severity">重大度の評価</a>は、攻撃対象の端末でその脆弱性が悪用された場合の影響に基づくもので、プラットフォームやサービスでのリスク軽減策が開発目的または不正な回避により無効となっていることを前提としています。 </p> <p> -この新たに報告された問題によって実際のユーザー端末が不正使用された報告はありません。下記の <a href="#mitigations">Android と Google サービスでのリスク軽減策</a>では、<a href="/security/enhancements/index.html">Android セキュリティ プラットフォームの保護</a>や Google Play プロテクトについて詳しく説明しています。こうした保護は、Android プラットフォームのセキュリティを強化するのに役立ちます。 +この新たに報告された問題によって実際のユーザー端末が不正使用された報告はありません。<a href="/security/enhancements/index.html">Android セキュリティ プラットフォームの保護</a>や Google Play プロテクトについて詳しくは、<a href="#mitigations">Android と Google サービスでのリスク軽減策</a>をご覧ください。こうした保護により、Android プラットフォームのセキュリティが改善されます。 </p> <p> <strong>注:</strong> 最新の無線（OTA）アップデートと Google 端末のファームウェア イメージについての情報は、2018 年 1 月の Pixel / Nexus のセキュリティに関する公開情報でご覧いただけます。 @@ -58,7 +58,7 @@ Android パートナーには、情報公開の 1 か月前までにすべての パッチレベル 2018-01-01 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。</p> <h3 id="android-runtime">Android ランタイム</h3> -<p>Android ランタイムの最も重大な脆弱性により、リモートの攻撃者によって、追加権限を取得するためのユーザー操作要件が回避されるおそれがあります。</p> +<p>Android ランタイムの最も重大な脆弱性により、リモートの攻撃者によって、追加権限を取得するためのユーザー操作の要件が回避されるおそれがあります。</p> <table> <colgroup><col width="17%" /> @@ -71,7 +71,7 @@ Android パートナーには、情報公開の 1 か月前までにすべての <th>参照</th> <th>タイプ</th> <th>重大度</th> - <th>更新対象の AOSP バージョン</th> + <th>更新された AOSP のバージョン</th> </tr> <tr> <td>CVE-2017-13176</td> @@ -97,7 +97,7 @@ Android パートナーには、情報公開の 1 か月前までにすべての <th>参照</th> <th>タイプ</th> <th>重大度</th> - <th>更新対象の AOSP バージョン</th> + <th>更新された AOSP のバージョン</th> </tr> <tr> <td>CVE-2017-13177</td> @@ -212,7 +212,7 @@ Android パートナーには、情報公開の 1 か月前までにすべての <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> - <td>CVE-2017-13199</td> + <td>CVE-2017-13199 </td> <td><a href="https://android.googlesource.com/platform/frameworks/base/+/42b2e419b48a26d2ba599d87e3a2a02c4aa625f4"> A-33846679</a></td> <td>DoS</td> @@ -222,7 +222,7 @@ Android パートナーには、情報公開の 1 か月前までにすべての </tbody></table> <h3 id="system">システム</h3> -<p>システムの最も重大な脆弱性により、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあります。</p> +<p>Qualcomm コンポーネントの最も重大な脆弱性により、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあります。</p> <table> <colgroup><col width="17%" /> @@ -235,7 +235,7 @@ Android パートナーには、情報公開の 1 か月前までにすべての <th>参照</th> <th>タイプ</th> <th>重大度</th> - <th>更新対象の AOSP バージョン</th> + <th>更新された AOSP のバージョン</th> </tr> <tr> <td>CVE-2017-13208</td> @@ -391,7 +391,7 @@ Android パートナーには、情報公開の 1 か月前までにすべての <th>参照</th> <th>タイプ</th> <th>重大度</th> - <th>更新対象の AOSP バージョン</th> + <th>更新された AOSP のバージョン</th> </tr> <tr> <td>CVE-2017-13183</td> @@ -540,7 +540,7 @@ QC-CR#2060780</a></td> </strong> </p> <p> -端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Android のバージョンを確認して更新する</a>をご覧ください。 +端末のセキュリティ パッチレベルを確認する方法については、「<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Android のバージョンを確認して更新する</a>」をご覧ください。 </p> <ul> <li>セキュリティ パッチレベル 2018-01-01 以降では、セキュリティ パッチレベル 2018-01-01 に関連するすべての問題に対処しています。</li> diff --git a/ja/security/bulletin/2018-02-01.html b/ja/security/bulletin/2018-02-01.html index df3b61ea..2cfdaf9b 100644 --- a/ja/security/bulletin/2018-02-01.html +++ b/ja/security/bulletin/2018-02-01.html @@ -30,10 +30,10 @@ Android パートナーには、情報公開の 1 か月前までにすべての 下記の問題のうち最も重大度の高いものは、メディア フレームワークに重大なセキュリティの脆弱性があるため、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあることです。<a href="/security/overview/updates-resources.html#severity">重大度の評価</a>は、攻撃対象の端末でその脆弱性が悪用された場合の影響に基づくもので、プラットフォームやサービスでのリスク軽減策が開発目的または不正な回避により無効となっていることを前提としています。 </p> <p> -この新たに報告された問題によって実際のユーザー端末が不正使用された報告はありません。<a href="/security/enhancements/index.html">Android セキュリティ プラットフォームの保護</a>や Google Play プロテクトについて詳しくは、<a href="#mitigations">Android と Google Play プロテクトでのリスク軽減策</a>をご覧ください。こうした保護により、Android プラットフォームのセキュリティが改善されます。 +この新たに報告された問題によって実際のユーザー端末が不正使用された報告はありません。<a href="/security/enhancements/index.html">Android セキュリティ プラットフォームの保護</a>や Google Play プロテクトについて詳しくは、<a href="#mitigations">Android と Google サービスでのリスク軽減策</a>をご覧ください。こうした保護により、Android プラットフォームのセキュリティが改善されます。 </p> <p class="note"> -<strong>注:</strong> 最新の無線（OTA）アップデートと Google 端末のファームウェア イメージについての情報は、<a href="/security/bulletin/pixel/2018-02-01">2018 年 2 月の Pixel / Nexus のセキュリティに関する公開情報</a>でご確認いただけます。 +<strong>注:</strong> 最新の無線（OTA）アップデートと Google 端末のファームウェア イメージについての情報は、<a href="/security/bulletin/pixel/2018-02-01">2018 年 2 月の Pixel / Nexus のセキュリティに関する公開情報</a>でご覧いただけます。 </p> <h2 id="mitigations">Android と Google サービスでのリスク軽減策</h2> <p> @@ -41,7 +41,7 @@ Android パートナーには、情報公開の 1 か月前までにすべての </p> <ul> <li>Android プラットフォームの最新版での機能強化により、Android 上の多くの問題の悪用が困難になります。Google では、すべてのユーザーに対し、できる限り最新バージョンの Android に更新することをおすすめしています。</li> -<li>Android セキュリティ チームは、<a href="https://www.android.com/play-protect">Google Play プロテクト</a>によって脆弱性の悪用を積極的に監視しており、<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">有害なおそれのあるアプリ</a>についてユーザーに警告しています。Google Play プロテクトは、<a href="http://www.android.com/gms">Google モバイル サービス</a>を搭載した端末ではデフォルトで有効になっており、Google Play 以外からアプリをインストールするユーザーにとっては特に重要です。</li> +<li>Android セキュリティ チームは、<a href="https://www.android.com/play-protect">Google Play プロテクト</a>によって脆弱性の悪用を積極的に監視しており、<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">害を及ぼすおそれのあるアプリ</a>についてユーザーに警告しています。Google Play プロテクトは、<a href="http://www.android.com/gms">Google モバイル サービス</a>を搭載した端末ではデフォルトで有効になっており、Google Play 以外からアプリをインストールするユーザーにとっては特に重要です。</li> </ul> <h2 id="2018-02-01-details">セキュリティ パッチレベル 2018-02-01 の脆弱性の詳細</h2> <p> @@ -502,7 +502,7 @@ QC-CR#2114187</a></td> <strong>6. セキュリティの脆弱性が、この公開情報と端末やパートナーのセキュリティに関する公開情報（Pixel / Nexus のセキュリティに関する公開情報など）に分けられているのはなぜですか？</strong> </p> <p> -Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、このセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、端末やパートナーのセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処は必須ではありません。Android 搭載端末やチップセットのメーカーは、自社の端末に関して他にも修正がある場合、自社のセキュリティ関連のウェブサイト（たとえば、<a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>、<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>、<a href="/security/bulletin/pixel/">Pixel / Nexus</a> のセキュリティに関する各公開情報）にその情報を掲載することが推奨されています。 +Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、このセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、端末やパートナーのセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処は必須ではありません。<a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>、<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a> などの Android 搭載端末やチップセットのメーカーには、自社の端末に関して他にも修正がある場合は、自社のセキュリティ関連のウェブサイトや <a href="/security/bulletin/pixel/">Pixel / Nexus</a> のセキュリティに関する公開情報にその情報を掲載することが推奨されています。 </p> <h2 id="versions">バージョン</h2> <table> diff --git a/ja/security/bulletin/2018-03-01.html b/ja/security/bulletin/2018-03-01.html index 63a6ad84..24b0c966 100644 --- a/ja/security/bulletin/2018-03-01.html +++ b/ja/security/bulletin/2018-03-01.html @@ -25,12 +25,12 @@ Android のセキュリティに関する公開情報には、Android 搭載端末に影響を与えるセキュリティの脆弱性の詳細を掲載しています。セキュリティ パッチレベル 2018-03-05 以降では、下記のすべての問題に対処しています。端末のセキュリティ パッチレベルの確認については、<a href="https://support.google.com/pixelphone/answer/4457705">Android のバージョンを確認して更新する</a>方法の説明をご覧ください。 </p> <p> -Android パートナーには、情報公開の 1 か月前までにすべての問題が通知されます。Android オープンソース プロジェクト（AOSP）のレポジトリに、各問題に対するソースコードのパッチをリリースしています。また、この公開情報では、これらのパッチへのリンクに加え、AOSP 以外のパッチへのリンクも掲載しています。</p> +Android パートナーには、情報公開の少なくとも 1 か月前にすべての問題が通知されます。Android オープンソース プロジェクト（AOSP）のレポジトリに、各問題に対するソースコードのパッチをリリースしています。また、この公開情報では、これらのパッチへのリンクに加え、AOSP 以外のパッチへのリンクも掲載しています。</p> <p> -下記の問題のうち最も重大度の高いものは、メディア フレームワークに重大なセキュリティの脆弱性があるため、離れた場所にいる攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあることです。<a href="/security/overview/updates-resources.html#severity">重大度の評価</a>は、攻撃対象の端末でその脆弱性が悪用された場合の影響に基づくもので、プラットフォームやサービスでのリスク軽減策が開発目的または不正な回避により無効となっていることを前提としています。 +下記の問題のうち最も重大度の高いものは、メディア フレームワークに重大なセキュリティの脆弱性があるため、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあることです。<a href="/security/overview/updates-resources.html#severity">重大度の評価</a>は、攻撃対象の端末でその脆弱性が悪用された場合の影響に基づくもので、プラットフォームやサービスでのリスク軽減策が開発目的または不正な回避により無効となっていることを前提としています。 </p> <p> -この新たに報告された問題によって実際のユーザー端末が不正使用された報告はありません。下記の <a href="#mitigations">Android と Google サービスでのリスク軽減策</a>では、<a href="/security/enhancements/index.html">Android セキュリティ プラットフォームの保護</a>や Google Play プロテクトについて詳しく説明しています。こうした保護は、Android プラットフォームのセキュリティを強化するのに役立ちます。 +この新たに報告された問題によって実際のユーザー端末が不正使用された報告はありません。<a href="/security/enhancements/index.html">Android セキュリティ プラットフォームの保護</a>や Google Play プロテクトについて詳しくは、<a href="#mitigations">Android と Google サービスでのリスク軽減策</a>をご覧ください。こうした保護により、Android プラットフォームのセキュリティが改善されます。 </p> <p class="note"> <strong>注:</strong> 最新の無線（OTA）アップデートと Google 端末のファームウェア イメージについての情報は、<a href="/security/bulletin/pixel/2018-03-01.html">2018 年 3 月の Pixel / Nexus のセキュリティに関する公開情報</a>でご覧いただけます。 @@ -42,11 +42,11 @@ Android パートナーには、情報公開の 1 か月前までにすべての </p> <ul> <li>機能強化された最新版の Android プラットフォームでは、Android 上の多くの問題について悪用が困難になります。Google では、すべてのユーザーに対し、できる限り最新バージョンの Android に更新することをおすすめしています。</li> -<li>Android セキュリティ チームは、<a href="https://www.android.com/play-protect">Google Play プロテクト</a>によって脆弱性の悪用を積極的に監視し、<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">害を及ぼすおそれのあるアプリ</a>についてユーザー向けの警告を出しています。Google Play プロテクトは、<a href="http://www.android.com/gms">Google モバイル サービス</a>を搭載した端末でデフォルトで有効になっており、Google Play 以外からアプリをインストールするユーザーにとって特に重要です。</li> +<li>Android セキュリティ チームは、<a href="https://www.android.com/play-protect">Google Play プロテクト</a>によって脆弱性の悪用を積極的に監視しており、<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">害を及ぼすおそれのあるアプリ</a>についてユーザーに警告しています。Google Play プロテクトは、<a href="http://www.android.com/gms">Google モバイル サービス</a>を搭載した端末でデフォルトで有効になっており、Google Play 以外からアプリをインストールするユーザーにとって特に重要です。</li> </ul> <h2 id="2018-03-01-details">セキュリティ パッチレベル 2018-03-01 の脆弱性の詳細</h2> <p> -パッチレベル 2018-03-01 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。脆弱性は、影響を受けるコンポーネントごとに分類しています。問題についての説明に加え、1 つの表に CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP バージョン（該当する場合）をまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に記載した番号に、追加の参照へのリンクを設定しています。</p> +パッチレベル 2018-03-01 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に記載した番号に、追加の参照へのリンクを設定しています。</p> <h3 id="media-framework">メディア フレームワーク</h3> <p>メディア フレームワークの最も重大な脆弱性により、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあります。</p> @@ -228,7 +228,7 @@ Android パートナーには、情報公開の 1 か月前までにすべての <h2 id="2018-03-05-details">セキュリティ パッチレベル 2018-03-05 の脆弱性の詳細</h2> <p> -パッチレベル 2018-03-05 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。影響を受けるコンポーネントごとに脆弱性を分類して、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、コンポーネント（該当する場合）、更新対象の AOSP バージョン（該当する場合）といった詳しい項目を記載しています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。 +パッチレベル 2018-03-05 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。影響を受けるコンポーネントごとに脆弱性を分類し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、コンポーネント（該当する場合）、更新対象の AOSP バージョン（該当する場合）などの詳細を記載しています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。 </p> <h3 id="kernel-components">カーネル コンポーネント</h3> @@ -492,7 +492,7 @@ QC-CR#1055934<a href="#asterisk">*</a></td> <h2 id="common-questions-and-answers">一般的な質問と回答</h2> <p> -上記の公開情報に対する一般的な質問とその回答について、以下をご確認ください。</p> +上記の公開情報に対する一般的な質問について、以下で回答します。</p> <p><strong>1. 上記の問題に対処するように端末が更新されているかどうかを確かめるには、どうすればよいですか？ </strong></p> <p>端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Android のバージョンを確認して更新する</a>をご覧ください。</p> @@ -597,7 +597,7 @@ QC-CR#1055934<a href="#asterisk">*</a></td> <strong>6. セキュリティの脆弱性が、この公開情報と端末やパートナーのセキュリティに関する公開情報（Pixel / Nexus のセキュリティに関する公開情報など）に分けられているのはなぜですか？</strong> </p> <p> -Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、このセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、端末やパートナーのセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処は必要ありません。Android 搭載端末やチップセットのメーカーは、自社の端末に関して他にも修正がある場合、自社のセキュリティ関連のウェブサイト（たとえば、<a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>、<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>、<a href="/security/bulletin/pixel/">Pixel / Nexus</a> のセキュリティについてそれぞれ公開されている情報）にその情報を掲載することが推奨されています。 +Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、このセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、端末やパートナーのセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処は必要ありません。<a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>、<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a> などの Android 搭載端末やチップセットのメーカーには、自社の端末に関して他にも修正がある場合は、自社のセキュリティ関連のウェブサイトや <a href="/security/bulletin/pixel/">Pixel / Nexus</a> のセキュリティに関する公開情報にその情報を掲載することが推奨されています。 </p> <h2 id="versions">バージョン</h2> <table> diff --git a/ja/security/bulletin/2018-04-01.html b/ja/security/bulletin/2018-04-01.html index ad0e06a3..81870f1c 100644 --- a/ja/security/bulletin/2018-04-01.html +++ b/ja/security/bulletin/2018-04-01.html @@ -45,14 +45,14 @@ Android パートナーには、情報公開の 1 か月前までにすべての </p> <ul> <li>機能強化された最新版の Android プラットフォームでは、Android 上の多くの問題について悪用が困難になります。Google では、すべてのユーザーに対し、できる限り最新バージョンの Android に更新することをおすすめしています。</li> -<li>Android セキュリティ チームは、<a href="https://www.android.com/play-protect">Google Play プロテクト</a>によって脆弱性の悪用を積極的に監視しており、<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">害を及ぼすおそれのあるアプリ</a>についてユーザーに警告しています。Google Play プロテクトは、<a href="http://www.android.com/gms">Google モバイル サービス</a>を搭載した端末ではデフォルトで有効になっており、Google Play 以外からアプリをインストールするユーザーにとっては特に重要です。</li> +<li>Android セキュリティ チームは、<a href="https://www.android.com/play-protect">Google Play プロテクト</a>によって脆弱性の悪用を積極的に監視しており、<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">害を及ぼすおそれのあるアプリ</a>についてユーザーに警告しています。Google Play プロテクトは、<a href="http://www.android.com/gms">Google モバイル サービス</a>を搭載した端末でデフォルトで有効になっており、Google Play 以外からアプリをインストールするユーザーにとって特に重要です。</li> </ul> <h2 id="2018-04-01-details">セキュリティ パッチレベル 2018-04-01 の脆弱性の詳細</h2> <p> -パッチレベル 2018-04-01 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。</p> +パッチレベル 2018-04-01 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に記載した番号に、追加の参照へのリンクを設定しています。</p> <h3 id="android-runtime">Android ランタイム</h3> -<p>Android ランタイムの最も重大な脆弱性により、リモートの攻撃者によって、追加権限を取得するためのユーザー操作要件が回避されるおそれがあります。</p> +<p>Android ランタイムの最も重大な脆弱性により、リモートの攻撃者によって、追加権限を取得するためのユーザー操作の要件が回避されるおそれがあります。</p> <table> <colgroup><col width="17%" /> diff --git a/ja/security/bulletin/2018-05-01.html b/ja/security/bulletin/2018-05-01.html index 5be1bbff..221de818 100644 --- a/ja/security/bulletin/2018-05-01.html +++ b/ja/security/bulletin/2018-05-01.html @@ -365,7 +365,7 @@ QC-CR#2138555</a></td> <p><strong>1. 上記の問題に対処するように端末が更新されているかどうかを確かめるには、どうすればよいですか？ </strong></p> -<p>端末のセキュリティ パッチレベルの確認について、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Android のバージョンを確認して更新する</a>方法の説明をご覧ください。</p> +<p>端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Android のバージョンを確認して更新する</a>をご覧ください。</p> <ul> <li>セキュリティ パッチレベル 2018-05-01 以降では、セキュリティ パッチレベル 2018-05-01 に関連するすべての問題に対処しています。</li> <li>セキュリティ パッチレベル 2018-05-05 以降では、セキュリティ パッチレベル 2018-05-05、およびそれ以前のすべてのパッチレベルに関連するすべての問題に対処しています。</li> diff --git a/ja/security/bulletin/2018-06-01.html b/ja/security/bulletin/2018-06-01.html index 007d7930..fe3ea05d 100644 --- a/ja/security/bulletin/2018-06-01.html +++ b/ja/security/bulletin/2018-06-01.html @@ -19,7 +19,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>2018 年 6 月 4 日公開 | 2018 年 6 月 6 日更新</em></p> +<p><em>2018 年 6 月 4 日公開 | 2018 年 7 月 24 日更新</em></p> <p>Android のセキュリティに関する公開情報には、Android 搭載端末に影響を与えるセキュリティの脆弱性の詳細を掲載しています。セキュリティ パッチレベル 2018-06-05 以降では、下記のすべての問題に対処しています。端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705">Android のバージョンを確認して更新する</a>をご覧ください。 </p> @@ -251,6 +251,35 @@ Android パートナーには、情報公開の 1 か月前までにすべての <p> パッチレベル 2018-06-05 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。影響を受けるコンポーネントごとに脆弱性を分類し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、コンポーネント（該当する場合）、更新対象の AOSP バージョン（該当する場合）などの詳細を記載しています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。</p> + +<h3 id="broadcom-components">Broadcom コンポーネント</h3> + +<p>Broadcom コンポーネントの最も重大な脆弱性により、リモートの攻撃者が、通常はローカルにインストールされた権限のあるアプリのみがアクセスできるデータにアクセスするおそれがあります。 +</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>コンポーネント</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-73665456<a href="#asterisk">*</a><br /> +B-CS4906525</td> + <td>ID</td> + <td>高</td> + <td>Bluetooth</td> + </tr> +</tbody></table> + <h3 id="kernel-components">カーネル コンポーネント</h3> <p>カーネル コンポーネントの最も重大な脆弱性により、悪意のあるローカルアプリによって特権プロセス内で任意のコードが実行されるおそれがあります。 @@ -564,7 +593,15 @@ QC-CR#2151241</a></td> <td>高</td> <td>WLAN</td> </tr> - <tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-73665204<a href="#asterisk">*</a><br /> + QC-CR#2187697</td> + <td>ID</td> + <td>高</td> + <td>Bluetooth</td> + </tr> + <tr> <td>CVE-2017-18159</td> <td>A-68992405<br /> <a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=633fa4ffb38bbfb0fad79204e19b9f59d42d7680">QC-CR#2105697</a> @@ -695,6 +732,33 @@ QC-CR#2161310</a></td> </tr> </tbody></table> +<h3 id="system-components">システム</h3> + +<p>システムの最も重大な脆弱性により、リモートの攻撃者が、通常はローカルにインストールされた権限のあるアプリのみがアクセスできるデータにアクセスするおそれがあります。 +</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>更新対象の AOSP バージョン</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/fa3d7e1f784d3bdbf8f9d8b572a60696289211b1">A-72377774</a></td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + <h2 id="common-questions-and-answers">一般的な質問と回答</h2> <p>上記の公開情報に対する一般的な質問とその回答について、以下をご確認ください。</p> <p><strong>1. 上記の問題に対処するように端末が更新されているかどうかを確かめるには、どうすればよいですか？</strong></p> @@ -819,6 +883,11 @@ Android 搭載端末の最新のセキュリティ パッチレベルを宣言 <td>2018 年 6 月 6 日</td> <td>公開情報を改訂し AOSP リンクを追加</td> </tr> + <tr> + <td>1.2</td> + <td>2018 年 7 月 24 日</td> + <td>公開情報を改訂し、基準に即した情報開示により CVE-2018-5383 への参照を追加</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/2018-07-01.html b/ja/security/bulletin/2018-07-01.html index 24b9dc82..1c6f0d00 100644 --- a/ja/security/bulletin/2018-07-01.html +++ b/ja/security/bulletin/2018-07-01.html @@ -19,22 +19,21 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>2018 年 7 月 2 日公開</em></p> +<p><em>2018 年 7 月 2 日公開 | 2018 年 7 月 3 日更新</em></p> <p> -Android のセキュリティに関する公開情報には、Android 搭載端末に影響を及ぼすセキュリティの脆弱性の詳細を掲載しています。セキュリティ パッチレベル 2018-07-05 以降では、下記のすべての問題に対処しています。端末のセキュリティ パッチレベルを確認するには、<a href="https://support.google.com/pixelphone/answer/4457705">Android のバージョンを確認して更新する</a>方法の説明をご覧ください。 +Android のセキュリティに関する公開情報には、Android 搭載端末に影響を及ぼすセキュリティの脆弱性の詳細を掲載しています。セキュリティ パッチレベル 2018-07-05 以降では、下記のすべての問題に対処しています。端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705">Android のバージョンを確認して更新する</a>をご覧ください。 </p> <p> -Android パートナーには、情報公開の少なくとも 1 か月前にすべての問題が通知されます。下記の問題に対するソースコードのパッチは、これから 48 時間の間に Android オープンソース プロジェクト（AOSP）レポジトリにリリースされます。AOSP リンクが利用可能になり次第、この公開情報を改訂します。 -</p> +Android パートナーには、情報公開の 1 か月前までにすべての問題が通知されます。Android オープンソース プロジェクト（AOSP）のレポジトリに、下記の問題に対するソースコードのパッチをリリースしています。また、この公開情報では、これらのパッチへのリンクに加え、AOSP 以外のパッチへのリンクも掲載しています。</p> <p> -下記の問題のうち最も重大度の高いものは、メディア フレームワークに重大なセキュリティの脆弱性があるため、離れた場所にいる攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあることです。<a href="/security/overview/updates-resources.html#severity">重大度の評価</a>は、攻撃対象の端末でその脆弱性が悪用された場合の影響に基づくもので、プラットフォームやサービスでのリスク軽減策が開発目的または不正な回避により無効となっていることを前提としています。 +下記の問題のうち最も重大度の高いものは、メディア フレームワークに重大なセキュリティの脆弱性があるため、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあることです。<a href="/security/overview/updates-resources.html#severity">重大度の評価</a>は、攻撃対象の端末でその脆弱性が悪用された場合の影響に基づくもので、プラットフォームやサービスでのリスク軽減策が開発目的または不正な回避により無効となっていることを前提としています。 </p> <p> -この新たに報告された問題によって実際のユーザー端末が不正使用された報告はありません。<a href="/security/enhancements/index.html">Android セキュリティ プラットフォームの保護</a>や Google Play プロテクトについて詳しくは、<a href="#mitigations">Android と Google Play プロテクトでのリスク軽減策</a>をご覧ください。こうした保護により、Android プラットフォームのセキュリティが改善されます。 +この新たに報告された問題によって実際のユーザー端末が不正使用された報告はありません。<a href="/security/enhancements/index.html">Android セキュリティ プラットフォームの保護</a>や Google Play プロテクトについて詳しくは、<a href="#mitigations">Android と Google サービスでのリスク軽減策</a>をご覧ください。こうした保護により、Android プラットフォームのセキュリティが改善されます。 </p> <p class="note"> -<strong>注:</strong> 最新の無線（OTA）アップデートと Google 端末のファームウェア イメージについての情報は、<a href="/security/bulletin/pixel/2018-07-01.html">2018 年 7 月の Pixel / Nexus のセキュリティに関する公開情報</a>についての記事でご覧いただけます。 +<strong>注:</strong> 最新の無線（OTA）アップデートと Google 端末のファームウェア イメージについての情報は、<a href="/security/bulletin/pixel/2018-07-01.html">2018 年 7 月の Pixel / Nexus のセキュリティに関する公開情報</a>でご覧いただけます。 </p> <h2 id="mitigations">Android と Google サービスでのリスク軽減策</h2> @@ -43,11 +42,11 @@ Android パートナーには、情報公開の少なくとも 1 か月前にす </p> <ul> <li>機能強化された最新版の Android プラットフォームでは、Android 上の多くの問題について悪用が困難になります。Google では、すべてのユーザーに対し、できる限り最新バージョンの Android に更新することをおすすめしています。</li> -<li>Android セキュリティ チームは、<a href="https://www.android.com/play-protect">Google Play プロテクト</a>によって脆弱性の悪用を積極的に監視しており、<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">有害なおそれのあるアプリ</a>についてユーザー向けの警告を出しています。Google Play プロテクトは、<a href="http://www.android.com/gms">Google モバイル サービス</a>を搭載した端末でデフォルトで有効になっており、Google Play 以外からアプリをインストールするユーザーにとって特に重要です。</li> +<li>Android セキュリティ チームは、<a href="https://www.android.com/play-protect">Google Play プロテクト</a>によって脆弱性の悪用を積極的に監視しており、<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">害を及ぼすおそれのあるアプリ</a>についてユーザーに警告しています。Google Play プロテクトは、<a href="http://www.android.com/gms">Google モバイル サービス</a>を搭載した端末でデフォルトで有効になっており、Google Play 以外からアプリをインストールするユーザーにとって特に重要です。</li> </ul> <h2 id="2018-07-01-details">セキュリティ パッチレベル 2018-07-01 の脆弱性の詳細</h2> <p> -パッチレベル 2018-07-01 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。</p> +パッチレベル 2018-07-01 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に記載した番号に、追加の参照へのリンクを設定しています。</p> <h3 id="framework">フレームワーク</h3> <p>フレームワークの最も重大な脆弱性により、リモートの攻撃者が特別に細工した pac ファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあります。</p> @@ -67,14 +66,14 @@ Android パートナーには、情報公開の少なくとも 1 か月前にす </tr> <tr> <td>CVE-2018-9433</td> - <td>A-38196219</td> + <td>A-38196219<a href="#asterisk">*</a></td> <td>RCE</td> <td>重大</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2</td> </tr> <tr> <td>CVE-2018-9410</td> - <td>A-77822336</td> + <td><a href="https://android.googlesource.com/platform/frameworks/minikin/+/62e88b9f3ac35e1e69d79c7a43c6f9ddcd5980a3">A-77822336</a></td> <td>ID</td> <td>高</td> <td>8.0、8.1</td> @@ -99,35 +98,35 @@ Android パートナーには、情報公開の少なくとも 1 か月前にす </tr> <tr> <td>CVE-2018-9411</td> - <td>A-79376389</td> + <td><a href="https://android.googlesource.com/platform/system/libhidl/+/e1302cfda34be9dd0a4aeae6bfa9561b44536758">A-79376389</a></td> <td>RCE</td> <td>重大</td> <td>8.0、8.1</td> </tr> <tr> <td>CVE-2018-9424</td> - <td>A-76221123</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/d3860e51b83296ae1d2921d8109210283573862a">A-76221123</a></td> <td>EoP</td> <td>高</td> <td>8.0、8.1</td> </tr> <tr> <td>CVE-2018-9428</td> - <td>A-74122779</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/46bd7c682db5bbc048b177c52448a7999e5740ce">A-74122779</a></td> <td>EoP</td> <td>高</td> <td>8.1</td> </tr> <tr> <td>CVE-2018-9412</td> - <td>A-78029004</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/fa12c0fcdc6607b746177ccad4f7099098b4849a">A-78029004</a></td> <td>DoS</td> <td>高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9421</td> - <td>A-77237570</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/ff2171f2460e3a6d3443ab957732b8b7d4831d40">A-77237570</a></td> <td>ID</td> <td>高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> @@ -152,28 +151,28 @@ Android パートナーには、情報公開の少なくとも 1 か月前にす </tr> <tr> <td>CVE-2018-9365</td> - <td>A-74121126</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/ae94a4c333417a1829030c4d87a58ab7f1401308">A-74121126</a></td> <td>RCE</td> <td>重大</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9432</td> - <td>A-73173182</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/a6fe2cd18c77c68219fe7159c051bc4e0003fc40">A-73173182</a></td> <td>EoP</td> <td>高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9420</td> - <td>A-77238656</td> + <td><a href="https://android.googlesource.com/platform/system/media/+/12df4b05fd918d836636e21f783df7ad9d5e17a3">A-77238656</a></td> <td>ID</td> <td>高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9419</td> - <td>A-74121659</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/f1c2c86080bcd7b3142ff821441696fc99c2bc9a">A-74121659</a></td> <td>ID</td> <td>高</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> @@ -182,8 +181,7 @@ Android パートナーには、情報公開の少なくとも 1 か月前にす <h2 id="2018-07-05-details">セキュリティ パッチレベル 2018-07-05 の脆弱性の詳細</h2> <p> -パッチレベル 2018-07-05 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。影響を受けるコンポーネントごとに脆弱性を分類し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、コンポーネント（該当する場合）、更新対象の AOSP バージョン（該当する場合）などの詳細を記載しています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。 -</p> +パッチレベル 2018-07-05 に該当するセキュリティ脆弱性の各項目について、下記に詳細を説明します。影響を受けるコンポーネントごとに脆弱性を分類し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、コンポーネント（該当する場合）、更新対象の AOSP バージョン（該当する場合）などの詳細を記載しています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に記載した番号に、追加の参照へのリンクを設定しています。</p> <h3 id="kernel-components">カーネル コンポーネント</h3> <p>カーネル コンポーネントの最も重大な脆弱性により、悪意のあるローカルアプリによって特権プロセス内で任意のコードが実行されるおそれがあります。</p> @@ -260,14 +258,6 @@ Android パートナーには、情報公開の少なくとも 1 か月前にす <td>WLAN</td> </tr> <tr> - <td>CVE-2018-5855</td> - <td>A-77527719<br /> - <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qca-wifi-host-cmn/commit/?id=61f4a467177afc23bdc1944ec61e52bed156c104">QC-CR#2181685</a></td> - <td>ID</td> - <td>高</td> - <td>WLAN</td> - </tr> - <tr> <td>CVE-2017-13077、CVE-2017-13078</td> <td>A-78285557<br /> <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=5c671a69c57ce4fd84f0eaf082b336a49d0cf5dd">QC-CR#2133114</a></td> @@ -417,13 +407,6 @@ Android パートナーには、情報公開の少なくとも 1 か月前にす <td>クローズドソース コンポーネント</td> </tr> <tr> - <td>CVE-2018-11258</td> - <td>A-72951054<a href="#asterisk">*</a></td> - <td>N/A</td> - <td>高</td> - <td>クローズドソース コンポーネント</td> - </tr> - <tr> <td>CVE-2018-11257</td> <td>A-74235874<a href="#asterisk">*</a></td> <td>N/A</td> @@ -477,7 +460,7 @@ Android パートナーには、情報公開の少なくとも 1 か月前にす <h2 id="common-questions-and-answers">一般的な質問と回答</h2> <p>上記の公開情報に対する一般的な質問とその回答について、以下をご確認ください。</p> <p><strong>1. 上記の問題に対処するように端末が更新されているかどうかを確かめるには、どうすればよいですか？</strong></p> -<p>端末のセキュリティ パッチレベルを確認するには、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Android のバージョンを確認して更新する</a>方法の説明をご覧ください。</p> +<p>端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Android のバージョンを確認して更新する</a>をご覧ください。</p> <ul> <li>セキュリティ パッチレベル 2018-07-01 以降では、セキュリティ パッチレベル 2018-07-01 に関連するすべての問題に対処しています。</li> <li>セキュリティ パッチレベル 2018-07-05 以降では、セキュリティ パッチレベル 2018-07-05、およびそれ以前のすべてのパッチレベルに関連するすべての問題に対処しています。</li> @@ -576,7 +559,7 @@ Android パートナーには、情報公開の少なくとも 1 か月前にす <strong>6. セキュリティの脆弱性が、この公開情報と端末やパートナーのセキュリティに関する公開情報（Pixel / Nexus のセキュリティに関する公開情報など）に分けられているのはなぜですか？</strong> </p> <p> -Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、このセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、端末やパートナーのセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処は必要ありません。Android 搭載端末やチップセットのメーカーは、自社の端末に関して他にも修正がある場合、自社のセキュリティ関連のウェブサイト（たとえば、<a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>、<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>、<a href="/security/bulletin/pixel/">Pixel / Nexus</a> のセキュリティに関する各公開情報）にその情報を掲載することが推奨されています。 +Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、このセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、端末やパートナーのセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処は必須ではありません。<a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>、<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a> などの Android 搭載端末やチップセットのメーカーには、自社の端末に関して他にも修正がある場合は、自社のセキュリティ関連のウェブサイトや <a href="/security/bulletin/pixel/">Pixel / Nexus</a> のセキュリティに関する公開情報にその情報を掲載することが推奨されています。 </p> <h2 id="versions">バージョン</h2> <table> @@ -593,6 +576,16 @@ Android 搭載端末の最新のセキュリティ パッチレベルを宣言 <td>2018 年 7 月 2 日</td> <td>情報公開</td> </tr> + <tr> + <td>1.1</td> + <td>2018 年 7 月 3 日</td> + <td>公開情報を改訂し AOSP リンクを追加</td> + </tr> + <tr> + <td>1.2</td> + <td>2018 年 7 月 11 日</td> + <td>CVE-2018-5855 と CVE-2018-11258 を 2018-07-05 SPL から削除</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/2018-08-01.html b/ja/security/bulletin/2018-08-01.html new file mode 100644 index 00000000..ac5fc43f --- /dev/null +++ b/ja/security/bulletin/2018-08-01.html @@ -0,0 +1,634 @@ +<html devsite><head> + <title>Android のセキュリティに関する公開情報 - 2018 年 8 月</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> +<p><em>2018 年 8 月 6 日公開</em></p> + +<p>Android のセキュリティに関する公開情報には、Android 搭載端末に影響を与えるセキュリティの脆弱性の詳細を掲載しています。セキュリティ パッチレベル 2018-08-05 以降では、下記のすべての問題に対処しています。端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705" class="external">Android のバージョンを確認して更新する</a>をご覧ください。 +</p> +<p> +Android パートナーには、情報公開の 1 か月前までにすべての問題が通知されます。Android オープンソース プロジェクト（AOSP）のレポジトリに、下記の問題に対するソースコードのパッチをリリースしています。また、この公開情報では、これらのパッチへのリンクに加え、AOSP 以外のパッチへのリンクも掲載しています。</p> +<p> +システムの最も重大な脆弱性により、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあります。<a href="/security/overview/updates-resources.html#severity">重大度の評価</a>は、攻撃対象の端末でその脆弱性が悪用された場合の影響に基づくもので、プラットフォームやサービスでのリスク軽減策が開発目的または不正な回避により無効となっていることを前提としています。 +</p> +<p> +この新たに報告された問題によって実際のユーザー端末が不正使用された報告はありません。<a href="/security/enhancements/index.html">Android セキュリティ プラットフォームの保護</a>や Google Play プロテクトについて詳しくは、<a href="#mitigations">Android と Google サービスでのリスク軽減策</a>をご覧ください。こうした保護により、Android プラットフォームのセキュリティが改善されます。 +</p> +<p class="note"> +<strong>注:</strong> 最新の無線（OTA）アップデートと Google 端末のファームウェア イメージについての情報は、<a href="/security/bulletin/pixel/2018-08-01.html">2018 年 8 月の Pixel / Nexus のセキュリティに関する公開情報</a>でご覧いただけます。 +</p> + +<h2 id="mitigations">Android と Google サービスでのリスク軽減策</h2> +<p> +ここでは、<a href="/security/enhancements/index.html">Android セキュリティ プラットフォーム</a>の保護と <a href="https://www.android.com/play-protect">Google Play プロテクト</a>のようなサービスの保護によるリスクの軽減について概説します。こうした機能は、Android でセキュリティの脆弱性が悪用される可能性を減らします。 +</p> +<ul> +<li>機能強化された最新版の Android プラットフォームでは、Android 上の多くの問題について悪用が困難になります。Google では、すべてのユーザーに対し、できる限り最新バージョンの Android に更新することをおすすめしています。</li> +<li>Android セキュリティ チームは、<a href="https://www.android.com/play-protect" class="external">Google Play プロテクト</a>によって脆弱性の悪用を積極的に監視しており、<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">害を及ぼすおそれのあるアプリ</a>についてユーザーに警告しています。Google Play プロテクトは、<a href="http://www.android.com/gms" class="external">Google モバイル サービス</a>を搭載した端末でデフォルトで有効になっており、Google Play 以外からアプリをインストールするユーザーにとっては特に重要です。</li> +</ul> +<h2 id="2018-08-01-details">セキュリティ パッチレベル 2018-08-01 の脆弱性の詳細</h2> +<p> +ここでは、パッチレベル 2018-08-01 に該当するセキュリティ脆弱性の各項目の詳細を説明します。脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。</p> + +<h3 id="framework">フレームワーク</h3> +<p>フレームワークの最も重大な脆弱性により、悪意のあるローカルアプリによって、追加権限を取得するためのユーザー操作の要件が回避されるおそれがあります。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>更新対象の AOSP バージョン</th> + </tr> + <tr> + <td>CVE-2018-9445</td> + <td> + <a href="https://android.googlesource.com/platform/external/e2fsprogs/+/9a2d95e4ed9ec5ab76998654b1c2fba9cc139e50">A-80436257</a> + [<a href="https://android.googlesource.com/platform/system/vold/+/940a1ff70cfc5f2e4de83da9ad84cd9734faadf6">2</a>] + </td> + <td>EoP</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9438</td> + <td> +<a href="https://android.googlesource.com/platform/packages/providers/DownloadProvider/+/b552ebf70913cc79085bcc4212235ea45e036d3b">A-78644887</a> +[<a href="https://android.googlesource.com/platform/frameworks/base/+/e3854655e75d97552140d77cca5d20c121a17ef9">2</a>] +[<a href="https://android.googlesource.com/platform/frameworks/opt/telephony/+/d1ce32b059bed774b41f11413c1d83a1bc412964">3</a>] +[<a href="https://android.googlesource.com/platform/frameworks/base/+/97e1cd61d3040dd366ac9e25cdb6f134c7490846">4</a>] +</td> + <td>DoS</td> + <td>高</td> + <td>8.1</td> + </tr> + <tr> + <td>CVE-2018-9458</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/c4f66f4f607654611b2227827123e016c57a5729">A-71786287</a> +</td> + <td>EoP</td> + <td>高</td> + <td>8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9451</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/a409aa1214d6483efe129a4966f09aa4fdc097ad">A-79488511</a> +[<a href="https://android.googlesource.com/platform/frameworks/base/+/1de25074adb5d9ed572d6a85e77d3df5ac3a7e9e">2</a>] +</td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="media-framework">メディア フレームワーク</h3> +<p>メディア フレームワークの最も重大な脆弱性により、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあります。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>更新対象の AOSP バージョン</th> + </tr> + <tr> + <td>CVE-2018-9427</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/av/+/08d392085c095e227c029f64644bc08ef5a544de">A-77486542</a> +[<a href="https://android.googlesource.com/platform/frameworks/av/+/c9909e5a980f941a5b72477755e09fb4dc57c478">2</a>] +</td> + <td>RCE</td> + <td>重大</td> + <td>8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9444</td> + <td>A-63521984<a href="#asterisk">*</a></td> + <td>DoS</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2</td> + </tr> + <tr> + <td>CVE-2018-9437</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/av/+/017ff33fd419c50734f775d5054e2cbea719700b">A-78656554</a> + </td> + <td>DoS</td> + <td>高</td> + <td>6.0、6.0.1</td> + </tr> +</tbody></table> + +<h3 id="system">システム</h3> +<p>システムの最も重大な脆弱性により、リモートの攻撃者が特別に細工したファイルを使用して、特権プロセス内で任意のコードを実行するおそれがあります。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>更新対象の AOSP バージョン</th> + </tr> + <tr> + <td>CVE-2018-9446</td> + <td> + <a href="https://android.googlesource.com/platform/system/bt/+/49acada519d088d8edf37e48640c76ea5c70e010">A-80145946</a> + </td> + <td>RCE</td> + <td>重大</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9450</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/bc259b4926a6f9b33b9ee2c917cd83a55f360cbf">A-79541338</a> + </td> + <td>RCE</td> + <td>重大</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9459</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/UnifiedEmail/+/76c5261a03c8402e893999196651afc5791ca0fd">A-66230183</a> + </td> + <td>EoP</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9455</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/d56c7ec9e2ecfa8a8ceeb82f37187e5ea21f2101">A-78136677</a> + </td> + <td>DoS</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9436</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/289a49814aef7f0f0bb98aac8246080abdfeac01">A-79164722</a> + </td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9454</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/289a49814aef7f0f0bb98aac8246080abdfeac01">A-78286118</a> + </td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9448</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/13294c70a66347c9e5d05b9f92f8ceb6fe38d7f6">A-79944113</a> +[<a href="https://android.googlesource.com/platform/system/bt/+/f1f1c3e00f8d1baad0215b057e6d894517eeaddb">2</a>] + </td> + <td>ID</td> + <td>高</td> + <td>8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9453</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/cb6a56b1d8cdab7c495ea8f53dcbdb3cfc9477d2">A-78288378</a> + </td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h2 id="2018-08-05-details">セキュリティ パッチレベル 2018-08-05 の脆弱性の詳細</h2> +<p> +ここでは、パッチレベル 2018-08-05 に該当するセキュリティ脆弱性の各項目の詳細を説明します。影響を受けるコンポーネントごとに脆弱性を分類し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、コンポーネント（該当する場合）、更新対象の AOSP バージョン（該当する場合）などの詳細を記載しています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。 +</p> + +<h3 id="kernel-components">カーネル コンポーネント</h3> +<p>カーネル コンポーネントの最も重大な脆弱性により、悪意のあるローカルアプリによって特権プロセス内で任意のコードが実行されるおそれがあります。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>コンポーネント</th> + </tr> + <tr> + <td>CVE-2017-18249</td> + <td>A-78283212<br /> + <a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30a61ddf8117c26ac5b295e1233eaa9629a94ca3"> +アップストリーム カーネル</a></td> + <td>EoP</td> + <td>高</td> + <td>F2FS</td> + </tr> + <tr> + <td>CVE-2018-9465</td> + <td>A-69164715<br /> + <a href="https://patchwork.kernel.org/patch/10058587/">アップストリーム +カーネル</a></td> + <td>EoP</td> + <td>高</td> + <td>binder</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Qualcomm コンポーネント</h3> +<p>Qualcomm コンポーネントの最も重大な脆弱性により、追加の実行権限を必要とすることなく、リモートで情報が漏えいするおそれがあります。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>コンポーネント</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-79421580<a href="#asterisk">*</a><br /> + QC-CR#2209635</td> + <td>ID</td> + <td>高</td> + <td>Bluetooth</td> + </tr> + <tr> + <td>CVE-2017-13077</td> + <td>A-78284758<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=edb507885fc47cf3cdf061bfba1dc77451a6a332"> +QC-CR#2133033</a></td> + <td>ID</td> + <td>高</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18281</td> + <td>A-78242172<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=69f0a80b8cc1333647397d7bc4f267bd3fe22be9"> +QC-CR#856388</a></td> + <td>ID</td> + <td>高</td> + <td>動画</td> + </tr> + <tr> + <td>CVE-2018-11260</td> + <td>A-72997254<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=9fd239116d9cb19a18b3892b8a1f428636ca1453"> +QC-CR#2204872</a></td> + <td>EoP</td> + <td>高</td> + <td>WLAN</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-closed-source-components">Qualcomm クローズドソース コンポーネント</h3> +<p>Qualcomm コンポーネントに影響する脆弱性は次のとおりです。詳細については、該当する Qualcomm AMSS のセキュリティに関する公開情報またはセキュリティ アラートをご覧ください。この一連の問題の重大度は Qualcomm から直接提供されたものです。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>コンポーネント</th> + </tr> + <tr> + <td>CVE-2017-18296</td> + <td>A-78240731<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>重大</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18305</td> + <td>A-78239838<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>重大</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18310</td> + <td>A-62211308<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>重大</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18295</td> + <td>A-78240386<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18283</td> + <td>A-78240411<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18294</td> + <td>A-78240247<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18293</td> + <td>A-78240316<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18292</td> + <td>A-78241027<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18298</td> + <td>A-78239976<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18299</td> + <td>A-78240418<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18304</td> + <td>A-78239975<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18303</td> + <td>A-78240396<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18301</td> + <td>A-78238455<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18302</td> + <td>A-78239233<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18300</td> + <td>A-78239508<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18297</td> + <td>A-78240275<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18280</td> + <td>A-78285512<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18282</td> + <td>A-78241591<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18309</td> + <td>A-73539064<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2017-18308</td> + <td>A-73539310<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2018-11305</td> + <td>A-72951032<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> + <tr> + <td>CVE-2018-11258</td> + <td>A-72951054<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>高</td> + <td>クローズドソース コンポーネント</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">一般的な質問と回答</h2> +<p>上記の公開情報に対する一般的な質問についての回答は以下のとおりです。</p> +<p><strong>1. 上記の問題に対処するように端末が更新されているかどうかを確かめるには、どうすればよいですか？</strong></p> +<p>端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">Android のバージョンを確認して更新する</a>をご覧ください。</p> +<ul> +<li>セキュリティ パッチレベル 2018-08-01 以降では、セキュリティ パッチレベル 2018-08-01 に関連するすべての問題に対処しています。</li> +<li>セキュリティ パッチレベル 2018-08-05 以降では、セキュリティ パッチレベル 2018-08-05、およびそれ以前のすべてのパッチレベルに関連するすべての問題に対処しています。</li> +</ul> +<p>このアップデートを組み込んだ端末メーカーは、パッチレベル文字列を以下に設定する必要があります。</p> +<ul> + <li>[ro.build.version.security_patch]:[2018-08-01]</li> + <li>[ro.build.version.security_patch]:[2018-08-05]</li> +</ul> +<p><strong>2. この公開情報に 2 つのセキュリティ パッチレベルがあるのはなぜですか？</strong></p> +<p> +この公開情報では、2 つのセキュリティ パッチレベルを定義しています。これは、すべての Android 搭載端末で同様の問題が発生する一部の脆弱性をサブセットとし、Android パートナーが迅速かつ柔軟に修正できるようにするためです。Android パートナーには、この公開情報に掲載されている問題をすべて修正し、最新のセキュリティ パッチレベルを使用することが推奨されています。 +</p> +<ul> +<li>2018-08-01 のセキュリティ パッチレベルを使用する端末では、そのセキュリティ パッチレベルに関連するすべての問題と、それ以前のセキュリティに関する公開情報で報告されたすべての問題の修正を含める必要があります。</li> +<li>2018-08-05 以降のセキュリティ パッチレベルを使用する端末には、今回（およびそれ以前）のセキュリティに関する公開情報に掲載された、該当するすべてのパッチを組み込む必要があります。</li> +</ul> +<p> +パートナーには、対処するすべての問題の修正を 1 つのアップデートにまとめて提供することが推奨されています。 +</p> +<p id="type"> +<strong>3. 「タイプ<em></em>」列の項目はどういう意味ですか？</strong> +</p> +<p> +脆弱性の詳細の表で「タイプ<em></em>」列に記載した項目は、セキュリティの脆弱性の分類を示しています。 +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>略語</th> + <th>定義</th> + </tr> + <tr> + <td>RCE</td> + <td>リモートコード実行</td> + </tr> + <tr> + <td>EoP</td> + <td>権限昇格</td> + </tr> + <tr> + <td>ID</td> + <td>情報開示</td> + </tr> + <tr> + <td>DoS</td> + <td>サービス拒否</td> + </tr> + <tr> + <td>N/A</td> + <td>該当する分類なし</td> + </tr> +</tbody></table> +<p> +<strong>4. 「参照<em></em>」列の項目はどういう意味ですか？</strong> +</p> +<p> +脆弱性の詳細の表で「参照<em></em>」列に記載した項目には、その参照番号が属す組織を示す接頭辞が含まれる場合があります。 +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>接頭辞</th> + <th>参照</th> + </tr> + <tr> + <td>A-</td> + <td>Android バグ ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm の参照番号</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek の参照番号</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA の参照番号</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom の参照番号</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>5. 「参照<em></em>」列の Android バグ ID の横にある「*」はどういう意味ですか？</strong> +</p> +<p> +公開されていない問題には、「参照」列の Android バグ ID の横に「*」を付けています。<em></em>この問題のアップデートは、<a href="https://developers.google.com/android/drivers" class="external">Google デベロッパー サイト</a>から入手できる Pixel / Nexus 端末用最新バイナリ ドライバに通常含まれています。 +</p> +<p> +<strong>6. セキュリティの脆弱性が、この公開情報と端末やパートナーのセキュリティに関する公開情報（Pixel / Nexus のセキュリティに関する公開情報など）に分けられているのはなぜですか？</strong> +</p> +<p> +Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、このセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、端末やパートナーのセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処は必要ありません。<a href="https://security.samsungmobile.com/securityUpdate.smsb" class="external">Samsung</a>、<a href="https://lgsecurity.lge.com/security_updates.html" class="external">LGE</a> などの Android 搭載端末やチップセットのメーカーには、自社の端末に関して他にも修正がある場合は、自社のセキュリティ関連のウェブサイトや <a href="/security/bulletin/pixel/" class="external">Pixel / Nexus</a> のセキュリティに関する公開情報にその情報を掲載することが推奨されています。 +</p> + +<h2 id="versions">バージョン</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>バージョン</th> + <th>日付</th> + <th>メモ</th> + </tr> + <tr> + <td>1.0</td> + <td>2018 年 8 月 6 日</td> + <td>情報公開</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/2018.html b/ja/security/bulletin/2018.html index 17f5aa84..2b5600a6 100644 --- a/ja/security/bulletin/2018.html +++ b/ja/security/bulletin/2018.html @@ -33,28 +33,45 @@ <th>公開日</th> <th>セキュリティ パッチレベル</th> </tr> - <tr> + <tr> + <td><a href="/security/bulletin/2018-08-01.html">2018 年 8 月</a></td> + <td>準備中 + <!-- + <a href="/security/bulletin/2018-08-01.html">English</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018 年 8 月 6 日</td> + <td>2018-08-01<br /> + 2018-08-05</td> + </tr> + + <tr> <td><a href="/security/bulletin/2018-07-01.html">2018 年 7 月</a></td> <td> - <a href="/security/bulletin/2018-07-01.html">English</a> / - <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-07-01.html">English</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-07-01.html?hl=zh-tw">中文（台灣）</a> </td> - <td>2018 年 7 月 4 日</td> + <td>2018 年 7 月 2 日</td> <td>2018-07-01<br /> 2018-07-05</td> </tr> <tr> <td><a href="/security/bulletin/2018-06-01.html">2018 年 6 月</a></td> <td> - <a href="/security/bulletin/2018-06-01.html">English</a> / - <a href="/security/bulletin/2018-06-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-06-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-06-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-06-01.html">English</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-06-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-06-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 6 月 4 日</td> @@ -64,11 +81,11 @@ <tr> <td><a href="/security/bulletin/2018-05-01.html">2018 年 5 月</a></td> <td> - <a href="/security/bulletin/2018-05-01.html">English</a> / - <a href="/security/bulletin/2018-05-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-05-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-05-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-05-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-05-01.html">English</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-05-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-05-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 5 月 7 日</td> @@ -78,11 +95,11 @@ <tr> <td><a href="/security/bulletin/2018-04-01.html">2018 年 4 月</a></td> <td> - <a href="/security/bulletin/2018-04-01.html">English</a> / - <a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-04-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-04-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-04-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-04-01.html">English</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-04-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 4 月 2 日</td> @@ -92,11 +109,11 @@ <tr> <td><a href="/security/bulletin/2018-03-01.html">2018 年 3 月</a></td> <td> - <a href="/security/bulletin/2018-03-01.html">English</a> / - <a href="/security/bulletin/2018-03-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-03-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-03-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-03-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-03-01.html">English</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-03-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-03-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 3 月</td> @@ -106,11 +123,11 @@ <tr> <td><a href="/security/bulletin/2018-02-01.html">2018 年 2 月</a></td> <td> - <a href="/security/bulletin/2018-02-01.html">English</a> / - <a href="/security/bulletin/2018-02-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-02-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-02-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-02-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-02-01.html">English</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-02-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-02-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 2 月</td> @@ -120,11 +137,11 @@ <tr> <td><a href="/security/bulletin/2018-01-01.html">2018 年 1 月</a></td> <td> - <a href="/security/bulletin/2018-01-01.html">English</a> / - <a href="/security/bulletin/2018-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-01-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-01-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-01-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-01-01.html">English</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-01-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-01-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 1 月</td> @@ -133,4 +150,4 @@ </tr> </tbody></table> -</body></html> +</body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/index.html b/ja/security/bulletin/index.html index f0eed843..d841f9d4 100644 --- a/ja/security/bulletin/index.html +++ b/ja/security/bulletin/index.html @@ -36,7 +36,7 @@ <h3 id="sources">提供元</h3> -<p>この一般公開の情報には、Android オープンソース プロジェクト（AOSP）、アップストリーム Linux カーネル、システム オン チップ（SOC）メーカーなど、さまざまな提供元からの修正が掲載されます。端末メーカーからは、次のような修正があります。</p> +<p>この一般公開の情報には、Android オープンソース プロジェクト（AOSP）、アップストリーム Linux カーネル、システム オン チップ（SOC）メーカーなど、さまざまな提供元からの修正が掲載されます。端末メーカー向けに以下の修正があります。</p> <ul> <li>Android プラットフォームの修正は、セキュリティに関する公開情報のリリースから 24～48 時間後に AOSP に統合され、AOSP から直接入手できます。</li> <li>アップストリーム Linux カーネルの修正は、リリース時に公開情報から直接リンクされ、そのリンクから入手できます。</li> @@ -55,28 +55,44 @@ <th>公開日</th> <th>セキュリティ パッチレベル</th> </tr> - <tr> + <tr> + <td><a href="/security/bulletin/2018-08-01.html">2018 年 8 月</a></td> + <td>準備中 + <!-- + <a href="/security/bulletin/2018-08-01.html">English</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018 年 8 月 6 日</td> + <td>2018-08-01<br /> + 2018-08-05</td> + </tr> + <tr> <td><a href="/security/bulletin/2018-07-01.html">2018 年 7 月</a></td> <td> - <a href="/security/bulletin/2018-07-01.html">English</a> / - <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-07-01.html">English</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-07-01.html?hl=zh-tw">中文（台灣）</a> </td> - <td>2018 年 7 月 4 日</td> + <td>2018 年 7 月 2 日</td> <td>2018-07-01<br /> 2018-07-05</td> </tr> <tr> <td><a href="/security/bulletin/2018-06-01.html">2018 年 6 月</a></td> <td> - <a href="/security/bulletin/2018-06-01.html">English</a> / - <a href="/security/bulletin/2018-06-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-06-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-06-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-06-01.html">English</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-06-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-06-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 6 月 4 日</td> @@ -86,11 +102,11 @@ <tr> <td><a href="/security/bulletin/2018-05-01.html">2018 年 5 月</a></td> <td> - <a href="/security/bulletin/2018-05-01.html">English</a> / - <a href="/security/bulletin/2018-05-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-05-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-05-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-05-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-05-01.html">English</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-05-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-05-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 5 月 7 日</td> @@ -100,11 +116,11 @@ <tr> <td><a href="/security/bulletin/2018-04-01.html">2018 年 4 月</a></td> <td> - <a href="/security/bulletin/2018-04-01.html">English</a> / - <a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-04-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-04-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-04-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-04-01.html">English</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-04-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 4 月 2 日</td> @@ -114,11 +130,11 @@ <tr> <td><a href="/security/bulletin/2018-03-01.html">2018 年 3 月</a></td> <td> - <a href="/security/bulletin/2018-03-01.html">English</a> / - <a href="/security/bulletin/2018-03-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-03-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-03-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-03-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-03-01.html">English</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-03-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-03-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 3 月 5 日</td> @@ -128,11 +144,11 @@ <tr> <td><a href="/security/bulletin/2018-02-01.html">2018 年 2 月</a></td> <td> - <a href="/security/bulletin/2018-02-01.html">English</a> / - <a href="/security/bulletin/2018-02-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-02-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-02-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-02-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-02-01.html">English</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-02-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-02-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 2 月 5 日</td> @@ -142,11 +158,11 @@ <tr> <td><a href="/security/bulletin/2018-01-01.html">2018 年 1 月</a></td> <td> - <a href="/security/bulletin/2018-01-01.html">English</a> / - <a href="/security/bulletin/2018-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2018-01-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2018-01-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2018-01-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2018-01-01.html">English</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-01-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2018-01-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 1 月 2 日</td> @@ -156,11 +172,11 @@ <tr> <td><a href="/security/bulletin/2017-12-01.html">2017 年 12 月</a></td> <td> - <a href="/security/bulletin/2017-12-01.html">English</a> / - <a href="/security/bulletin/2017-12-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-12-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-12-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-12-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2017-12-01.html">English</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-12-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-12-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 12 月 4 日</td> @@ -170,11 +186,11 @@ <tr> <td><a href="/security/bulletin/2017-11-01.html">2017 年 11 月</a></td> <td> - <a href="/security/bulletin/2017-11-01.html">English</a> / - <a href="/security/bulletin/2017-11-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-11-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-11-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-11-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2017-11-01.html">English</a> / + <a href="/security/bulletin/2017-11-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-11-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-11-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-11-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-11-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 11 月 6 日</td> @@ -185,11 +201,11 @@ <tr> <td><a href="/security/bulletin/2017-10-01.html">2017 年 10 月</a></td> <td> - <a href="/security/bulletin/2017-10-01.html">English</a> / - <a href="/security/bulletin/2017-10-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-10-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-10-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-10-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2017-10-01.html">English</a> / + <a href="/security/bulletin/2017-10-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-10-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-10-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-10-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-10-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 10 月 2 日</td> @@ -199,11 +215,11 @@ <tr> <td><a href="/security/bulletin/2017-09-01.html">2017 年 9 月</a></td> <td> - <a href="/security/bulletin/2017-09-01.html">English</a> / - <a href="/security/bulletin/2017-09-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-09-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-09-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-09-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2017-09-01.html">English</a> / + <a href="/security/bulletin/2017-09-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-09-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-09-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-09-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-09-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 9 月 5 日</td> @@ -213,11 +229,11 @@ <tr> <td><a href="/security/bulletin/2017-08-01.html">2017 年 8 月</a></td> <td> - <a href="/security/bulletin/2017-08-01.html">English</a> / - <a href="/security/bulletin/2017-08-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-08-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-08-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-08-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2017-08-01.html">English</a> / + <a href="/security/bulletin/2017-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-08-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-08-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 8 月 7 日</td> @@ -227,11 +243,11 @@ <tr> <td><a href="/security/bulletin/2017-07-01.html">2017 年 7 月</a></td> <td> - <a href="/security/bulletin/2017-07-01.html">English</a> / - <a href="/security/bulletin/2017-07-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-07-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-07-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-07-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2017-07-01.html">English</a> / + <a href="/security/bulletin/2017-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-07-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-07-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 7 月 5 日</td> @@ -241,11 +257,11 @@ <tr> <td><a href="/security/bulletin/2017-06-01.html">2017 年 6 月</a></td> <td> - <a href="/security/bulletin/2017-06-01.html">English</a> / - <a href="/security/bulletin/2017-06-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-06-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-06-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-06-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2017-06-01.html">English</a> / + <a href="/security/bulletin/2017-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-06-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-06-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 6 月 5 日</td> @@ -255,11 +271,11 @@ <tr> <td><a href="/security/bulletin/2017-05-01.html">2016 年 5 月</a></td> <td> - <a href="/security/bulletin/2017-05-01.html">English</a> / - <a href="/security/bulletin/2017-05-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-05-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-05-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-05-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2017-05-01.html">English</a> / + <a href="/security/bulletin/2017-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-05-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-05-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 5 月 1 日</td> @@ -268,11 +284,11 @@ </tr> <tr> <td><a href="/security/bulletin/2017-04-01.html">2017 年 4 月</a></td> - <td><a href="/security/bulletin/2017-04-01.html">English</a> / - <a href="/security/bulletin/2017-04-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-04-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-04-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-04-01.html?hl=zh-cn">中文（中国）</a>/ + <td><a href="/security/bulletin/2017-04-01.html">English</a> / + <a href="/security/bulletin/2017-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-04-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-04-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 4 月 3 日</td> @@ -281,11 +297,11 @@ </tr> <tr> <td><a href="/security/bulletin/2017-03-01.html">2017 年 3 月</a></td> - <td><a href="/security/bulletin/2017-03-01.html">English</a> / - <a href="/security/bulletin/2017-03-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-03-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-03-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-03-01.html?hl=zh-cn">中文（中国）</a>/ + <td><a href="/security/bulletin/2017-03-01.html">English</a> / + <a href="/security/bulletin/2017-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-03-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-03-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 3 月 6 日</td> @@ -294,11 +310,11 @@ </tr> <tr> <td><a href="/security/bulletin/2017-02-01.html">2017 年 2 月</a></td> - <td><a href="/security/bulletin/2017-02-01.html">English</a> / - <a href="/security/bulletin/2017-02-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-02-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-02-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-02-01.html?hl=zh-cn">中文（中国）</a>/ + <td><a href="/security/bulletin/2017-02-01.html">English</a> / + <a href="/security/bulletin/2017-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-02-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-02-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 2 月 6 日</td> @@ -307,11 +323,11 @@ </tr> <tr> <td><a href="/security/bulletin/2017-01-01.html">2017 年 1 月</a></td> - <td><a href="/security/bulletin/2017-01-01.html">English</a> / - <a href="/security/bulletin/2017-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2017-01-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2017-01-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2017-01-01.html?hl=zh-cn">中文（中国）</a>/ + <td><a href="/security/bulletin/2017-01-01.html">English</a> / + <a href="/security/bulletin/2017-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-01-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2017-01-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 1 月 3 日</td> @@ -321,11 +337,11 @@ <tr> <td><a href="/security/bulletin/2016-12-01.html">2016 年 12 月</a></td> <td> - <a href="/security/bulletin/2016-12-01.html">English</a> / - <a href="/security/bulletin/2016-12-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-12-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-12-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-12-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-12-01.html">English</a> / + <a href="/security/bulletin/2016-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-12-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-12-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 12 月 5 日</td> @@ -335,11 +351,11 @@ <tr> <td><a href="/security/bulletin/2016-11-01.html">2016 年 11 月</a></td> <td> - <a href="/security/bulletin/2016-11-01.html">English</a> / - <a href="/security/bulletin/2016-11-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-11-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-11-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-11-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-11-01.html">English</a> / + <a href="/security/bulletin/2016-11-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-11-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-11-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-11-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-11-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 11 月 7 日</td> @@ -350,11 +366,11 @@ <tr> <td><a href="/security/bulletin/2016-10-01.html">2016 年 10 月</a></td> <td> - <a href="/security/bulletin/2016-10-01.html">English</a> / - <a href="/security/bulletin/2016-10-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-10-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-10-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-10-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-10-01.html">English</a> / + <a href="/security/bulletin/2016-10-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-10-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-10-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-10-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-10-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 10 月 3 日</td> @@ -364,11 +380,11 @@ <tr> <td><a href="/security/bulletin/2016-09-01.html">2016 年 9 月</a></td> <td> - <a href="/security/bulletin/2016-09-01.html">English</a> / - <a href="/security/bulletin/2016-09-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-09-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-09-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-09-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-09-01.html">English</a> / + <a href="/security/bulletin/2016-09-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-09-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-09-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-09-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-09-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 9 月 6 日</td> @@ -379,11 +395,11 @@ <tr> <td><a href="/security/bulletin/2016-08-01.html">2016 年 8 月</a></td> <td> - <a href="/security/bulletin/2016-08-01.html">English</a> / - <a href="/security/bulletin/2016-08-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-08-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-08-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-08-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-08-01.html">English</a> / + <a href="/security/bulletin/2016-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-08-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-08-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 8 月 1 日</td> @@ -393,11 +409,11 @@ <tr> <td><a href="/security/bulletin/2016-07-01.html">2016 年 7 月</a></td> <td> - <a href="/security/bulletin/2016-07-01.html">English</a> / - <a href="/security/bulletin/2016-07-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-07-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-07-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-07-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-07-01.html">English</a> / + <a href="/security/bulletin/2016-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-07-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-07-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 7 月 6 日</td> @@ -407,11 +423,11 @@ <tr> <td><a href="/security/bulletin/2016-06-01.html">2016 年 6 月</a></td> <td> - <a href="/security/bulletin/2016-06-01.html">English</a> / - <a href="/security/bulletin/2016-06-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-06-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-06-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-06-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-06-01.html">English</a> / + <a href="/security/bulletin/2016-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-06-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-06-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 6 月 6 日</td> @@ -420,11 +436,11 @@ <tr> <td><a href="/security/bulletin/2016-05-01.html">2016 年 5 月</a></td> <td> - <a href="/security/bulletin/2016-05-01.html">English</a> / - <a href="/security/bulletin/2016-05-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-05-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-05-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-05-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-05-01.html">English</a> / + <a href="/security/bulletin/2016-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-05-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-05-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 5 月 2 日</td> @@ -433,11 +449,11 @@ <tr> <td><a href="/security/bulletin/2016-04-02.html">2016 年 4 月</a></td> <td> - <a href="/security/bulletin/2016-04-02.html">English</a> / - <a href="/security/bulletin/2016-04-02.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-04-02.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-04-02.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-04-02.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-04-02.html">English</a> / + <a href="/security/bulletin/2016-04-02.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-04-02.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-04-02.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-04-02.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-04-02.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 4 月 4 日</td> @@ -446,11 +462,11 @@ <tr> <td><a href="/security/bulletin/2016-03-01.html">2016 年 3 月</a></td> <td> - <a href="/security/bulletin/2016-03-01.html">English</a> / - <a href="/security/bulletin/2016-03-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-03-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-03-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-03-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-03-01.html">English</a> / + <a href="/security/bulletin/2016-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-03-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-03-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 3 月 7 日</td> @@ -459,11 +475,11 @@ <tr> <td><a href="/security/bulletin/2016-02-01.html">2016 年 2 月</a></td> <td> - <a href="/security/bulletin/2016-02-01.html">English</a> / - <a href="/security/bulletin/2016-02-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-02-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-02-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-02-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-02-01.html">English</a> / + <a href="/security/bulletin/2016-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-02-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-02-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 2 月 1 日</td> @@ -472,11 +488,11 @@ <tr> <td><a href="/security/bulletin/2016-01-01.html">2016 年 1 月</a></td> <td> - <a href="/security/bulletin/2016-01-01.html">English</a> / - <a href="/security/bulletin/2016-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2016-01-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2016-01-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2016-01-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2016-01-01.html">English</a> / + <a href="/security/bulletin/2016-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-01-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2016-01-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2016 年 1 月 4 日</td> @@ -485,11 +501,11 @@ <tr> <td><a href="/security/bulletin/2015-12-01.html">2015 年 12 月</a></td> <td> - <a href="/security/bulletin/2015-12-01.html">English</a> / - <a href="/security/bulletin/2015-12-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2015-12-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2015-12-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2015-12-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2015-12-01.html">English</a> / + <a href="/security/bulletin/2015-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-12-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2015-12-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2015 年 12 月 7 日</td> @@ -498,11 +514,11 @@ <tr> <td><a href="/security/bulletin/2015-11-01.html">2015 年 11 月</a></td> <td> - <a href="/security/bulletin/2015-11-01.html">English</a> / - <a href="/security/bulletin/2015-11-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2015-11-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2015-11-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2015-11-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2015-11-01.html">English</a> / + <a href="/security/bulletin/2015-11-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-11-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-11-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-11-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2015-11-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2015 年 11 月 2 日</td> @@ -511,11 +527,11 @@ <tr> <td><a href="/security/bulletin/2015-10-01.html">2015 年 10 月</a></td> <td> - <a href="/security/bulletin/2015-10-01.html">English</a> / - <a href="/security/bulletin/2015-10-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2015-10-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2015-10-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2015-10-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2015-10-01.html">English</a> / + <a href="/security/bulletin/2015-10-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-10-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-10-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-10-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2015-10-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2015 年 10 月 5 日</td> @@ -524,11 +540,11 @@ <tr> <td><a href="/security/bulletin/2015-09-01.html">2015 年 9 月</a></td> <td> - <a href="/security/bulletin/2015-09-01.html">English</a> / - <a href="/security/bulletin/2015-09-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2015-09-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2015-09-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2015-09-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2015-09-01.html">English</a> / + <a href="/security/bulletin/2015-09-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-09-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-09-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-09-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2015-09-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2015 年 9 月 9 日</td> @@ -537,11 +553,11 @@ <tr> <td><a href="/security/bulletin/2015-08-01.html">2015 年 8 月</a></td> <td> - <a href="/security/bulletin/2015-08-01.html">English</a> / - <a href="/security/bulletin/2015-08-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/2015-08-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/2015-08-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/2015-08-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/2015-08-01.html">English</a> / + <a href="/security/bulletin/2015-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-08-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/2015-08-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2015 年 8 月 13 日</td> @@ -549,4 +565,4 @@ </tr> </tbody></table> -</body></html> +</body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/pixel/2018-03-01.html b/ja/security/bulletin/pixel/2018-03-01.html index 426bb984..0903af5c 100644 --- a/ja/security/bulletin/pixel/2018-03-01.html +++ b/ja/security/bulletin/pixel/2018-03-01.html @@ -633,10 +633,10 @@ QC-CR#2119401</a></td> 公開されていない問題には、「参照」列の Android バグ ID の横に「*」を付けています。<em></em>この問題のアップデートは、通常、<a href="https://developers.google.com/android/nexus/drivers">Google デベロッパー サイト</a>から入手できる Nexus 端末用最新バイナリ ドライバに含まれています。 </p> <p> -<strong>5. セキュリティの脆弱性が、この公開情報と Android のセキュリティに関する公開情報に分けられているのはなぜですか？</strong> +<strong>5. セキュリティの脆弱性が、この公開情報と「Android のセキュリティに関する公開情報」に分けられているのはなぜですか？</strong> </p> <p> -Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、Android のセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、この公開情報などに掲載されているセキュリティの脆弱性への対処は必要ありません。 +Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、「Android のセキュリティに関する公開情報」に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、この公開情報などに掲載されているセキュリティの脆弱性への対処は必要ありません。 </p> <h2 id="versions">バージョン</h2> <table> diff --git a/ja/security/bulletin/pixel/2018-04-01.html b/ja/security/bulletin/pixel/2018-04-01.html index 766185bd..0e2b41d8 100644 --- a/ja/security/bulletin/pixel/2018-04-01.html +++ b/ja/security/bulletin/pixel/2018-04-01.html @@ -23,7 +23,7 @@ <p><em>2018 年 4 月 2 日公開 | 2018 年 4 月 10 日更新</em></p> <p> -Pixel / Nexus のセキュリティに関する公開情報には、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">サポート対象の Google Pixel 端末と Nexus 端末</a>（Google 端末）に影響を与えるセキュリティの脆弱性や機能強化の詳細を掲載しています。Google 端末では、セキュリティ パッチレベル 2018-04-05 以降において、この公開情報に掲載されているすべての問題と、<a href="/security/bulletin/2018-04-01">2018 年 4 月の Android のセキュリティに関する公開情報</a>に掲載されているすべての問題に対処しています。端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705">Android のバージョンを確認して更新する</a>をご覧ください。</p> +Pixel / Nexus のセキュリティに関する公開情報には、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">サポート対象の Google Pixel 端末と Nexus 端末</a>（Google 端末）に影響を及ぼすセキュリティの脆弱性や機能強化の詳細を掲載しています。Google 端末では、セキュリティ パッチレベル 2018-04-05 以降において、この公開情報に掲載されているすべての問題と、<a href="/security/bulletin/2018-04-01">2018 年 4 月の Android のセキュリティに関する公開情報</a>に掲載されているすべての問題に対処しています。端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705">Android のバージョンを確認して更新する</a>をご覧ください。</p> <p> パッチレベル 2018-04-05 へのアップデートは、サポート対象のすべての Google 端末に送信されます。ご利用の端末にこのアップデートを適用することをすべてのユーザーにおすすめします。 </p> @@ -36,7 +36,7 @@ Pixel / Nexus のセキュリティに関する公開情報には、<a href="htt <h2 id="security-patches">セキュリティ パッチ</h2> <p> -脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明とともに、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="https://source.android.com/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP（Android オープンソース プロジェクト）バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。</p> +脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="https://source.android.com/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP（Android オープンソース プロジェクト）バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に記載した番号に、追加の参照へのリンクを設定しています。</p> <h3 id="framework">フレームワーク</h3> @@ -873,8 +873,7 @@ QC-CR#2098332</a></td> </tbody></table> <h2 id="common-questions-and-answers">一般的な質問と回答</h2> -<p> -上記の公開情報に対する一般的な質問とその回答について、以下をご確認ください。 +<p>上記の公開情報に対する一般的な質問とその回答について、以下をご確認ください。 </p> <p> <strong>1. 上記の問題に対処するように端末が更新されているかどうかを確かめるには、どうすればよいですか？ @@ -955,10 +954,10 @@ QC-CR#2098332</a></td> <strong>4. 「参照<em></em>」列の Android バグ ID の横にある「*」はどういう意味ですか？</strong> </p> <p> -公開されていない問題には、「参照」列の Android バグ ID の横に「*」を付けています。<em></em>この問題のアップデートは、通常、<a href="https://developers.google.com/android/nexus/drivers">Google デベロッパー サイト</a>から入手できる Nexus 端末用最新バイナリ ドライバに含まれています。 +公開されていない問題には、「参照<em></em>」列の Android バグ ID の横に「*」を付けています。この問題のアップデートは、通常、<a href="https://developers.google.com/android/nexus/drivers">Google デベロッパー サイト</a>から入手できる Nexus 端末用最新バイナリ ドライバに含まれています。 </p> <p> -<strong>5. セキュリティの脆弱性が、この公開情報と Android のセキュリティに関する公開情報に分けられているのはなぜですか？</strong> +<strong>5. セキュリティの脆弱性が、この公開情報と「Android のセキュリティに関する公開情報」に分けられているのはなぜですか？</strong> </p> <p> Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、Android のセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、この公開情報などに掲載されているセキュリティの脆弱性への対処は必要ありません。 diff --git a/ja/security/bulletin/pixel/2018-05-01.html b/ja/security/bulletin/pixel/2018-05-01.html index dc640e70..be7cf049 100644 --- a/ja/security/bulletin/pixel/2018-05-01.html +++ b/ja/security/bulletin/pixel/2018-05-01.html @@ -548,7 +548,7 @@ QC-CR#2149720</a></td> 公開されていない問題には、「参照<em></em>」列の Android バグ ID の横に「*」を付けています。この問題のアップデートは、通常、<a href="https://developers.google.com/android/nexus/drivers">Google デベロッパー サイト</a>から入手できる Pixel / Nexus 端末用最新バイナリ ドライバに含まれています。 </p> <p> -<strong>5. セキュリティの脆弱性が、この公開情報と Android のセキュリティに関する公開情報に分けられているのはなぜですか？</strong> +<strong>5. セキュリティの脆弱性が、この公開情報と「Android のセキュリティに関する公開情報」に分けられているのはなぜですか？</strong> </p> <p> Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、Android のセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、この公開情報などに掲載されているセキュリティの脆弱性への対処は必要ありません。 diff --git a/ja/security/bulletin/pixel/2018-06-01.html b/ja/security/bulletin/pixel/2018-06-01.html index e39a983e..d2580bd0 100644 --- a/ja/security/bulletin/pixel/2018-06-01.html +++ b/ja/security/bulletin/pixel/2018-06-01.html @@ -852,7 +852,7 @@ A-74058011</td> 公開されていない問題には、「参照<em></em>」列の Android バグ ID の横に「*」を付けています。この問題のアップデートは、通常、<a href="https://developers.google.com/android/nexus/drivers">Google デベロッパー サイト</a>から入手できる Pixel / Nexus 端末用最新バイナリ ドライバに含まれています。 </p> <p> -<strong>5. セキュリティの脆弱性が、この公開情報と Android のセキュリティに関する公開情報に分けられているのはなぜですか？</strong> +<strong>5. セキュリティの脆弱性が、この公開情報と「Android のセキュリティに関する公開情報」に分けられているのはなぜですか？</strong> </p> <p> Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、Android のセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、この公開情報などに掲載されているセキュリティの脆弱性への対処は必要ありません。 diff --git a/ja/security/bulletin/pixel/2018-07-01.html b/ja/security/bulletin/pixel/2018-07-01.html index 500f3c32..b2e214bb 100644 --- a/ja/security/bulletin/pixel/2018-07-01.html +++ b/ja/security/bulletin/pixel/2018-07-01.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p><em>2018 年 7 月 2 日公開</em></p> +<p><em>2018 年 7 月 2 日公開 | 2018 年 7 月 3 日更新</em></p> <p> Pixel / Nexus のセキュリティに関する公開情報には、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">サポート対象の Google Pixel 端末と Nexus 端末</a>（Google 端末）に影響を与えるセキュリティの脆弱性や機能強化の詳細を掲載しています。Google 端末では、セキュリティ パッチレベル 2018-07-05 以降において、この公開情報に掲載されているすべての問題と、2018 年 7 月の Android のセキュリティに関する公開情報に掲載されているすべての問題に対処しています。端末のセキュリティ パッチレベルを確認するには、<a href="https://support.google.com/pixelphone/answer/4457705">Android のバージョンを確認して更新する</a>方法の説明をご覧ください。 @@ -56,21 +56,22 @@ Pixel / Nexus のセキュリティに関する公開情報には、<a href="htt </tr> <tr> <td>CVE-2018-9426</td> - <td>A-79148652</td> + <td><a href="https://android.googlesource.com/platform/external/bouncycastle/+/129a20459ea828c1b05f0d5da57f69a2a3212ad7">A-79148652</a></td> <td>ID</td> <td>中</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9376</td> - <td>A-69981755</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/e6655cb8a78b757e9329b8200a90746ffac3a5a9">A-69981755</a></td> <td>EoP</td> <td>中</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9434</td> - <td>A-29833520</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/ab1fb955acc8bbe6b9086a4ab54beab003a887a9">A-29833520</a> +[<a href="https://android.googlesource.com/platform/frameworks/native/+/c4b7338b1a0995222d229a6f794db02c974ba0d8">2</a>]</td> <td>ID</td> <td>中</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> @@ -94,14 +95,14 @@ Pixel / Nexus のセキュリティに関する公開情報には、<a href="htt </tr> <tr> <td>CVE-2018-9429</td> - <td>A-73927042</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/7306d8b37c00729dc41d663a4b244a00209d537b">A-73927042</a></td> <td>ID</td> <td>中</td> <td>8.1</td> </tr> <tr> <td>CVE-2018-9423</td> - <td>A-77599438</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/e46e5994a80c31f6533384f0f325555f3a87bee3">A-77599438</a></td> <td>ID</td> <td>中</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> @@ -125,35 +126,35 @@ Pixel / Nexus のセキュリティに関する公開情報には、<a href="htt </tr> <tr> <td>CVE-2018-9413</td> - <td>A-73782082</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/97eb2f9cfba4f38d64dffa0558f1c4c3aa91b4f8">A-73782082</a></td> <td>RCE</td> <td>中</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9418</td> - <td>A-73824150</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/8e702ed3539caac44a616243e33aaad1b2b4801f">A-73824150</a></td> <td>RCE</td> <td>中</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9430</td> - <td>A-73963551</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/605ebb3369b3f961196815065a9fe4ba5bc4d659">A-73963551</a></td> <td>RCE</td> <td>中</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9414</td> - <td>A-78787521</td> + <td><a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/98ff9fe7db5a25fa2c772a85f0b9baa3545228bf">A-78787521</a></td> <td>EoP</td> <td>中</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9431</td> - <td>A-77600924</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/5c23facbf802c9b4c88ceb60e1b782abcc55ddc9">A-77600924</a></td> <td>EoP</td> <td>中</td> <td>8.0、8.1</td> @@ -186,7 +187,7 @@ Pixel / Nexus のセキュリティに関する公開情報には、<a href="htt <tr> <td>CVE-2018-9415</td> <td>A-69129004<br /> - <a href="https://patchwork.kernel.org/patch/9946759/">アップストリーム カーネル</a></td> + <a href="https://patchwork.kernel.org/patch/10175615/">アップストリーム カーネル</a></td> <td>EoP</td> <td>中</td> <td>AMBA ドライバ</td> @@ -454,6 +455,11 @@ Android 搭載端末の最新のセキュリティ パッチレベルを宣言 <td>2018 年 7 月 2 日</td> <td>情報公開</td> </tr> + <tr> + <td>1.1</td> + <td>2018 年 7 月 3 日</td> + <td>公開情報を改訂し AOSP リンクを追加</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/pixel/2018-08-01.html b/ja/security/bulletin/pixel/2018-08-01.html new file mode 100644 index 00000000..e94963ad --- /dev/null +++ b/ja/security/bulletin/pixel/2018-08-01.html @@ -0,0 +1,520 @@ +<html devsite><head> + <title>Pixel / Nexus のセキュリティに関する公開情報 - 2018 年 8 月</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + +<p><em>2018 年 8 月 6 日公開</em></p> + +<p> +Pixel / Nexus のセキュリティに関する公開情報には、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">サポート対象の Google Pixel 端末と Nexus 端末</a>（Google 端末）に影響を与えるセキュリティの脆弱性や機能強化の詳細を掲載しています。Google 端末では、セキュリティ パッチレベル 2018-08-05 以降において、この公開情報に掲載されているすべての問題と、2018 年 8 月の Android のセキュリティに関する公開情報に掲載されているすべての問題に対処しています。端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705" class="external">Android のバージョンを確認して更新する</a>をご覧ください。 +</p> +<p> +パッチレベル 2018-08-05 へのアップデートは、サポート対象のすべての Google 端末に送信されます。ご利用の端末で上記の更新を行うことをすべてのユーザーにおすすめします。 +</p> +<p class="note"> +<strong>注:</strong> Google 端末のファームウェア イメージは、<a href="https://developers.google.com/android/images" class="external">Google デベロッパー サイト</a>で入手できます。 +</p> + +<h2 id="announcements">お知らせ</h2> +<p>2018 年 8 月の Android のセキュリティに関する公開情報に掲載されているセキュリティの脆弱性に加えて、Google 端末には、下記のセキュリティの脆弱性に対するパッチも含まれています。パートナーには少なくとも 1 か月前に下記の問題が通知されており、パートナーは端末のアップデートにこうしたパッチを組み込むことができます。</p> + +<h2 id="security-patches">セキュリティ パッチ</h2> +<p> +脆弱性は、影響を受けるコンポーネントごとに分類しています。問題の内容について説明し、CVE、関連する参照先、<a href="#type">脆弱性のタイプ</a>、<a href="/security/overview/updates-resources.html#severity">重大度</a>、更新対象の AOSP（Android オープンソース プロジェクト）バージョン（該当する場合）を表にまとめています。該当する場合は、バグ ID の欄に、その問題に対処した一般公開されている変更（AOSP の変更の一覧など）へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。</p> + +<h3 id="framework">フレームワーク</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>更新対象の AOSP バージョン</th> + </tr> + <tr> + <td>CVE-2017-1000100</td> + <td> +<a href="https://android.googlesource.com/platform/external/curl/+/1506c0316973bd95d7832891b1aa2258b52a793d">A-64610131</a> +</td> + <td>ID</td> + <td>中</td> + <td>7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="system">システム</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>更新対象の AOSP バージョン</th> + </tr> + <tr> + <td>CVE-2018-9435</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/51b05b715024adff4fa59ab2e18c0b56c5d3af5e">A-79591688</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9461</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Messaging/+/17a2579a0aa603a3a7d94e5dc64afeb96e430e8f">A-37629504</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9449</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/27b90f4f6fe3811335e9bb4fac4656bc1df49204">A-79884292</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9457</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Settings/+/a3e94449c8fe0a377b61747b6129fafc930da086">A-72872376</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9441</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/c3c69bed0f76178c640dd8e726967b9cdea5dece">A-74075873</a> +[<a href="https://android.googlesource.com/platform/system/bt/+/3a2799939b2da543ed3a62f29db658cb05f8ad3b">2</a>] +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2017-13322</td> + <td> +<a href="https://android.googlesource.com/platform/packages/services/Telephony/+/c25745addd19b1549b7ec5bdc46d8bf1a1de37ed">A-67862398</a> +</td> + <td>DoS</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9447</td> + <td> +<a href="https://android.googlesource.com/platform/packages/services/Telephony/+/19c48992b79df89c730f3619eb69baf03d449e95">A-79995313</a> +</td> + <td>DoS</td> + <td>中</td> + <td>6.0、6.0.1、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="kernel-components">カーネル コンポーネント</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>コンポーネント</th> + </tr> + <tr> + <td>CVE-2018-9462</td> + <td>A-78364203<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>中</td> + <td>タッチスクリーン</td> + </tr> + <tr> + <td>CVE-2018-9439</td> + <td>A-79377438<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>中</td> + <td>ネットワーク スタック</td> + </tr> + <tr> + <td>CVE-2018-9463</td> + <td>A-78362414<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>中</td> + <td>タッチスクリーン</td> + </tr> + <tr> + <td>CVE-2018-1068</td> + <td>A-77902350<br /> + <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b71812168571fa55e44cdd0254471331b9c4c4c6"> +アップストリーム カーネル</a></td> + <td>EoP</td> + <td>中</td> + <td>Netfilter</td> + </tr> + <tr> + <td>CVE-2018-9464</td> + <td>A-68993267<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>中</td> + <td>Taimen ブートローダー</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Qualcomm コンポーネント</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>コンポーネント</th> + </tr> + <tr> + <td>CVE-2018-11263</td> + <td>A-79422278<a href="#asterisk">*</a><br /> + QC-CR#2209106</td> + <td>EoP</td> + <td>中</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-8261</td> + <td>A-35139833<a href="#asterisk">*</a><br /> + QC-CR#2013631</td> + <td>EoP</td> + <td>中</td> + <td>カメラドライバ</td> + </tr> + <tr> + <td>CVE-2018-5910</td> + <td>A-79422277<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=b67e04e3696f05411b7434c8b194895d273b00c5"> +QC-CR#2175499</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=d9344c2f4b60cf5d4c747c11f3cb0b6f1558db78">2</a>] +</td> + <td>EoP</td> + <td>中</td> + <td>MDSS</td> + </tr> + <tr> + <td>CVE-2018-5909</td> + <td>A-79421262<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=2c1716c5afd660651724b6088f2e6301272f4926"> +QC-CR#2174716</a></td> + <td>EoP</td> + <td>中</td> + <td>ローテーター</td> + </tr> + <tr> + <td>CVE-2018-5908</td> + <td>A-79422409<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=28e5918c60b832091c6b3618747258803cbd3302"> +QC-CR#2171758</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=4689d03e5db548d263232c274bf307956207da27">2</a>] +</td> + <td>EoP</td> + <td>中</td> + <td>MDSS</td> + </tr> + <tr> + <td>CVE-2018-5905</td> + <td>A-79421261<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=6eb2f4f6fde1b210712d6ac66b40b9e7684d77db"> +QC-CR#2169715</a></td> + <td>EoP</td> + <td>中</td> + <td>Diag ドライバ</td> + </tr> + <tr> + <td>CVE-2018-5904</td> + <td>A-79421260<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=88b838c8952ec6414c72449ae15768d15d2606dd"> +QC-CR#2184702</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.9/commit/?id=8e82c0d84ccee87309fd22f8208915f0ba502b26">2</a>] +</td> + <td>EoP</td> + <td>中</td> + <td>電源ドライバ</td> + </tr> + <tr> + <td>CVE-2018-5903</td> + <td>A-79421737<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=20365fa599f42f6e1f175d9d5d60d964927c2160"> +QC-CR#2185477</a></td> + <td>EoP</td> + <td>中</td> + <td>qcacld 3.0</td> + </tr> + <tr> + <td>CVE-2017-18306</td> + <td>A-73889358<a href="#asterisk">*</a><br /> + QC-CR#2216399</td> + <td>ID</td> + <td>中</td> + <td>v4l2</td> + </tr> + <tr> + <td>CVE-2017-18307</td> + <td>A-73888283<a href="#asterisk">*</a><br /> + QC-CR#2026045</td> + <td>ID</td> + <td>中</td> + <td>qcacld-3.0</td> + </tr> + <tr> + <td>CVE-2017-9711</td> + <td>A-36367253<a href="#asterisk">*</a><br /> + QC-CR#2046006</td> + <td>EoP</td> + <td>中</td> + <td>IPA</td> + </tr> + <tr> + <td>CVE-2018-3587</td> + <td>A-65542521<a href="#asterisk">*</a><br /> + QC-CR#2120605</td> + <td>EoP</td> + <td>中</td> + <td>qcacld-2.0</td> + </tr> +</tbody></table> + +<h3 id="update:-framework">更新: フレームワーク</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>更新対象の AOSP バージョン</th> + </tr> + <tr> + <td>CVE-2017-13295</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/da24aa45a8b65a7b9adbe12ff94bf891bdd38825">A-62537081</a> +[<a href="https://android.googlesource.com/platform/packages/apps/PackageInstaller/+/3af01bd93513d902dbb5382b10109fdf3ab29d2d">2</a>] +</td> + <td>DoS</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="update:-system">更新: システム</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>更新対象の AOSP バージョン</th> + </tr> + <tr> + <td>CVE-2017-13242</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Settings/+/f973e707f50adc0c21599e719be06714f808a333">A-62672248</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="update:-qualcomm-components">更新: Qualcomm コンポーネント</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>参照</th> + <th>タイプ</th> + <th>重大度</th> + <th>コンポーネント</th> + </tr> + <tr> + <td>CVE-2017-15817</td> + <td>A-68992394<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=fe43c2b64ac81199de17efc258e95546cb0546f1">QC-CR#2076603</a> +[<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=8ba78e506e5002cdae525dd544dbf1df0ccce1ef">2</a>] +<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=343a3f28338788c5c91289f53171c1f71f293cd7">QC-CR#2084599</a> +<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=0c21aaa2fefa6c5919813fdd287436dddda54227">QC-CR#2096512</a> +</td> + <td>RCE</td> + <td>重大</td> + <td>WLAN</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">一般的な質問と回答</h2> +<p> +上記の公開情報に対する一般的な質問について、以下で回答します。 +</p> +<p> +<strong>1. 上記の問題に対処するように端末が更新されているかどうかを確かめるには、どうすればよいですか？ +</strong> +</p> +<p> +セキュリティ パッチレベル 2018-08-05 以降では、セキュリティ パッチレベル 2018-08-05、およびそれ以前のすべてのパッチレベルに関連するすべての問題に対処しています。端末のセキュリティ パッチレベルを確認する方法については、<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">Pixel および Nexus のアップデート スケジュール</a>に記載されている手順をご覧ください。 +</p> +<p id="type"> +<strong>2. 「タイプ<em></em>」列の項目はどういう意味ですか？</strong> +</p> +<p> +脆弱性の詳細の表で「タイプ<em></em>」列に記載した項目は、セキュリティの脆弱性の分類を示しています。 +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>略語</th> + <th>定義</th> + </tr> + <tr> + <td>RCE</td> + <td>リモートコード実行</td> + </tr> + <tr> + <td>EoP</td> + <td>権限昇格</td> + </tr> + <tr> + <td>ID</td> + <td>情報開示</td> + </tr> + <tr> + <td>DoS</td> + <td>サービス拒否</td> + </tr> + <tr> + <td>N/A</td> + <td>該当する分類なし</td> + </tr> +</tbody></table> +<p> +<strong>3. 「参照<em></em>」列の項目はどういう意味ですか？</strong> +</p> +<p> +脆弱性の詳細の表で「参照<em></em>」列に記載した項目には、その参照番号が属す組織を示す接頭辞が含まれる場合があります。 +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>接頭辞</th> + <th>参照</th> + </tr> + <tr> + <td>A-</td> + <td>Android バグ ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm の参照番号</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek の参照番号</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA の参照番号</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom の参照番号</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>4. 「参照<em></em>」列の Android バグ ID の横にある「*」はどういう意味ですか？</strong> +</p> +<p> +公開されていない問題には、「参照」列の Android バグ ID の横に「*」を付けています。<em></em>この問題のアップデートは、通常、<a href="https://developers.google.com/android/nexus/drivers" class="external">Google デベロッパー サイト</a>から入手できる Pixel / Nexus 端末用最新バイナリ ドライバに含まれています。 +</p> +<p> +<strong>5。セキュリティの脆弱性が、この公開情報と「Android のセキュリティに関する公開情報」に分けられているのはなぜですか？</strong> +</p> +<p> +Android 搭載端末の最新のセキュリティ パッチレベルを宣言するためには、Android のセキュリティに関する公開情報に掲載されているセキュリティの脆弱性への対処が必要です。それ以外の、この公開情報などに掲載されているセキュリティの脆弱性への対処は必要ありません。 +</p> +<h2 id="versions">バージョン</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>バージョン</th> + <th>日付</th> + <th>メモ</th> + </tr> + <tr> + <td>1.0</td> + <td>2018 年 8 月 6 日</td> + <td>情報公開</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/pixel/2018.html b/ja/security/bulletin/pixel/2018.html index ccd99e38..1e370fd0 100644 --- a/ja/security/bulletin/pixel/2018.html +++ b/ja/security/bulletin/pixel/2018.html @@ -33,27 +33,42 @@ <th>公開日</th> <th>セキュリティ パッチレベル</th> </tr> - <tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-08-01.html">2018 年 8 月</a></td> + <td>準備中 + <!-- + <a href="/security/bulletin/pixel/2018-08-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018 年 8 月 6 日</td> + <td>2018-08-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-07-01.html">2018 年 7 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-tw">中文（台灣）</a> </td> - <td>2018 年 7 月 4 日</td> + <td>2018 年 7 月 2 日</td> <td>2018-07-05</td> </tr> <tr> <td><a href="/security/bulletin/pixel/2018-06-01.html">2018 年 6 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-06-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-06-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-06-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-06-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 6 月 4 日</td> @@ -62,11 +77,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-05-01.html">2018 年 5 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-05-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-05-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-05-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-05-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-05-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 5 月 7 日</td> @@ -75,11 +90,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-04-01.html">2018 年 4 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-04-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-04-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 4 月 2 日</td> @@ -88,13 +103,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-03-01.html">2018 年 3 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">ру́сский</a> / - <!-- - <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / - --> + <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 3 月</td> @@ -103,11 +116,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-02-01.html">2018 年 2 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-02-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-02-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 2 月</td> @@ -116,11 +129,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-01-01.html">2018 年 1 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 1 月</td> @@ -128,4 +141,4 @@ </tr> </tbody></table> -</body></html> +</body></html>
\ No newline at end of file diff --git a/ja/security/bulletin/pixel/index.html b/ja/security/bulletin/pixel/index.html index a563eb26..efe4d59b 100644 --- a/ja/security/bulletin/pixel/index.html +++ b/ja/security/bulletin/pixel/index.html @@ -42,27 +42,42 @@ <th>公開日</th> <th>セキュリティ パッチレベル</th> </tr> - <tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-08-01.html">2018 年 8 月</a></td> + <td>準備中 + <!-- + <a href="/security/bulletin/pixel/2018-08-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018 年 8 月 6 日</td> + <td>2018-08-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-07-01.html">2018 年 7 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-tw">中文（台灣）</a> </td> - <td>2018 年 7 月 4 日</td> + <td>2018 年 7 月 2 日</td> <td>2018-07-05</td> </tr> <tr> <td><a href="/security/bulletin/pixel/2018-06-01.html">2018 年 6 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-06-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-06-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-06-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-06-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 6 月 4 日</td> @@ -71,11 +86,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-05-01.html">2018 年 5 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-05-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-05-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-05-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-05-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-05-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 5 月 7 日</td> @@ -84,11 +99,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-04-01.html">2018 年 4 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-04-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-04-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 4 月 2 日</td> @@ -97,11 +112,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-03-01.html">2018 年 3 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 3 月 5 日</td> @@ -110,11 +125,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-02-01.html">2018 年 2 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-02-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-02-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 2 月 5 日</td> @@ -123,11 +138,11 @@ <tr> <td><a href="/security/bulletin/pixel/2018-01-01.html">2018 年 1 月</a></td> <td> - <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2018 年 1 月 2 日</td> @@ -136,11 +151,11 @@ <tr> <td><a href="/security/bulletin/pixel/2017-12-01.html">2017 年 12 月</a></td> <td> - <a href="/security/bulletin/pixel/2017-12-01.html">English</a> / - <a href="/security/bulletin/pixel/2017-12-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2017-12-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2017-12-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2017-12-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2017-12-01.html">English</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2017-12-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 12 月 4 日</td> @@ -149,11 +164,11 @@ <tr> <td><a href="/security/bulletin/pixel/2017-11-01.html">2017 年 11 月</a></td> <td> - <a href="/security/bulletin/pixel/2017-11-01.html">English</a> / - <a href="/security/bulletin/pixel/2017-11-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2017-11-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2017-11-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2017-11-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2017-11-01.html">English</a> / + <a href="/security/bulletin/pixel/2017-11-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2017-11-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2017-11-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2017-11-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2017-11-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 11 月 6 日</td> @@ -162,11 +177,11 @@ <tr> <td><a href="/security/bulletin/pixel/2017-10-01.html">2017 年 10 月</a></td> <td> - <a href="/security/bulletin/pixel/2017-10-01.html">English</a> / - <a href="/security/bulletin/pixel/2017-10-01.html?hl=ja">日本語</a> / - <a href="/security/bulletin/pixel/2017-10-01.html?hl=ko">한국어</a> / - <a href="/security/bulletin/pixel/2017-10-01.html?hl=ru">ру́сский</a> / - <a href="/security/bulletin/pixel/2017-10-01.html?hl=zh-cn">中文（中国）</a>/ + <a href="/security/bulletin/pixel/2017-10-01.html">English</a> / + <a href="/security/bulletin/pixel/2017-10-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2017-10-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2017-10-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2017-10-01.html?hl=zh-cn">中文（中国）</a> / <a href="/security/bulletin/pixel/2017-10-01.html?hl=zh-tw">中文（台灣）</a> </td> <td>2017 年 10 月 2 日</td> @@ -174,4 +189,4 @@ </tr> </tbody></table> -</body></html> +</body></html>
\ No newline at end of file diff --git a/ko/security/bulletin/2018-01-01.html b/ko/security/bulletin/2018-01-01.html index f47dc41d..d151ba2f 100644 --- a/ko/security/bulletin/2018-01-01.html +++ b/ko/security/bulletin/2018-01-01.html @@ -90,12 +90,7 @@ Google에서는 새로운 <li>Android 플랫폼 최신 버전의 향상된 기능으로 Android의 여러 문제를 악용하기가 더욱 어려워졌습니다. 가능하다면 모든 사용자는 최신 버전의 Android로 업데이트하는 것이 좋습니다. -</li><li>Android 보안팀에서는 -<a href="https://www.android.com/play-protect">Google Play 프로텍트</a> -를 통해 악용사례를 적극적으로 모니터링하고 -<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">유해할 수 있는 -애플리케이션</a> -에 관해 사용자에게 경고를 보냅니다. Google Play 프로텍트는 +</li><li>Android 보안팀에서는 <a href="https://www.android.com/play-protect">Google Play 프로텍트</a>를 통해 악용사례를 모니터링하고 <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">잠재적으로 위험한 애플리케이션</a>에 관해 사용자에게 경고를 보냅니다. Google Play 프로텍트는 <a href="http://www.android.com/gms">Google 모바일 서비스</a>가 적용된 기기에 기본적으로 사용 설정되어 있으며 Google Play 외부에서 가져온 앱을 설치하는 사용자에게 특히 중요합니다.</li></ul> <h2 id="2018-01-01-security-patch-level—vulnerability-details">2018-01-01 diff --git a/ko/security/bulletin/2018-02-01.html b/ko/security/bulletin/2018-02-01.html index 2c8dbb6b..6048e993 100644 --- a/ko/security/bulletin/2018-02-01.html +++ b/ko/security/bulletin/2018-02-01.html @@ -56,8 +56,9 @@ AOSP 외부에 있는 패치로 연결되는 링크도 포함되어 있습니다 </p> <h2 id="mitigations">Android 및 Google 서비스 완화</h2> <p> -다음은 <a href="/security/enhancements/index.html">Android 보안 플랫폼</a> 및 <a href="https://www.android.com/play-protect">Google Play 프로텍트</a>와 같은 -서비스 보호 기능에서 제공하는 완화에 관한 요약입니다. 이러한 +다음은 <a href="https://www.android.com/play-protect">Google Play 프로텍트</a>와 같은 +<a href="/security/enhancements/index.html">Android 보안 플랫폼</a> 및 서비스 보호 기능에서 +제공하는 완화에 관한 요약입니다. 이러한 기능을 통해 Android에서 보안 취약성이 악용될 가능성을 줄입니다. </p> diff --git a/ko/security/bulletin/2018-03-01.html b/ko/security/bulletin/2018-03-01.html index 9afda97f..2165f904 100644 --- a/ko/security/bulletin/2018-03-01.html +++ b/ko/security/bulletin/2018-03-01.html @@ -39,8 +39,8 @@ AOSP 외부에 있는 패치로 연결되는 링크도 포함되어 있습니다 특별히 제작된 파일을 사용하는 원격 공격자가 권한이 설정된 프로세스의 컨텍스트 내에서 임의의 코드를 실행할 수 있습니다. <a href="/security/overview/updates-resources.html#severity">심각도 평가</a>는 -개발 목적으로 플랫폼 및 서비스 완화를 사용할 수 없거나 -우회에 성공한 경우 취약성 악용으로 인해 대상 기기가 받는 영향을 +개발 목적으로 플랫폼 및 서비스 완화를 사용할 수 없거나 우회에 성공한 경우 취약성 악용으로 인해 +대상 기기가 받는 영향을 기준으로 합니다. </p> <p> @@ -61,10 +61,10 @@ Pixel&hairsp;/&hairsp;Nexus 보안 게시판</a> <h2 id="mitigations">Android 및 Google 서비스 완화</h2> <p> -다음은 <a href="/security/enhancements/index.html">Android 보안 플랫폼</a> 및 -<a href="https://www.android.com/play-protect">Google Play 프로텍트</a>와 -같은 서비스 보호 기능에서 제공하는 -완화에 관한 요약입니다. +다음은 +<a href="https://www.android.com/play-protect">Google Play 프로텍트</a>와 같은 +<a href="/security/enhancements/index.html">Android 보안 플랫폼</a> 및 서비스 보호 기능에서 +제공하는 완화에 관한 요약입니다. 이러한 기능을 통해 Android에서 보안 취약성이 악용될 가능성을 줄입니다. </p> @@ -72,12 +72,7 @@ Pixel&hairsp;/&hairsp;Nexus 보안 게시판</a> <li>Android 플랫폼 최신 버전의 향상된 기능으로 Android의 여러 문제를 악용하기가 더욱 어려워졌습니다. 가능하다면 모든 사용자는 최신 버전의 Android로 업데이트하는 것이 좋습니다.</li> -<li>Android 보안팀에서는 -<a href="https://www.android.com/play-protect">Google Play 프로텍트</a> -를 통해 악용사례를 적극적으로 모니터링하고 -<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">유해할 수 있는 -애플리케이션</a> -에 관해 사용자에게 경고를 보냅니다. Google Play 프로텍트는 +<li>Android 보안팀에서는 <a href="https://www.android.com/play-protect">Google Play 프로텍트</a>를 통해 악용사례를 모니터링하고 <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">잠재적으로 위험한 애플리케이션</a>에 관해 사용자에게 경고를 보냅니다. Google Play 프로텍트는 <a href="http://www.android.com/gms">Google 모바일 서비스</a>가 적용된 기기에 기본적으로 사용 설정되어 있으며 Google Play 외부에서 가져온 앱을 설치하는 사용자에게 특히 중요합니다.</li> @@ -635,7 +630,7 @@ QC-CR#1055934<a href="#asterisk">*</a></td> <td>서비스 거부</td> </tr> <tr> - <td>해당 없음</td> + <td>N/A</td> <td>분류 없음</td> </tr> </tbody></table> diff --git a/ko/security/bulletin/2018-04-01.html b/ko/security/bulletin/2018-04-01.html index 9cbe2486..b62e08b6 100644 --- a/ko/security/bulletin/2018-04-01.html +++ b/ko/security/bulletin/2018-04-01.html @@ -29,8 +29,7 @@ Android 보안 게시판은 Android 기기에 영향을 미치는 보안 취약 및 업데이트</a>를 참조하세요. </p> <p> -Android 파트너에게는 게시되기 최소 한 달 전에 모든 문제 관련 알림이 -전달되었습니다. +Android 파트너에게는 게시되기 최소 한 달 전에 모든 문제와 관련해 알림이 전달되었습니다. 이러한 문제를 해결하기 위한 소스 코드 패치는 Android 오픈소스 프로젝트(AOSP) 저장소에 배포되었으며 이 게시판에도 링크되어 있습니다. 이 게시판에는 AOSP 외부에 있는 패치로 연결되는 링크도 포함되어 있습니다. @@ -40,35 +39,38 @@ AOSP 외부에 있는 패치로 연결되는 링크도 포함되어 있습니다 특별히 제작된 파일을 사용하는 원격 공격자가 권한이 설정된 프로세스의 컨텍스트 내에서 임의의 코드를 실행할 수 있습니다. <a href="/security/overview/updates-resources.html#severity">심각도 평가</a>는 -개발 목적으로 플랫폼 및 서비스 완화를 사용할 수 없거나 -우회에 성공한 경우 취약성 악용으로 인해 대상 기기가 받는 영향을 +개발 목적으로 플랫폼 및 서비스 완화를 사용할 수 없거나 우회에 성공한 경우 취약성 악용으로 인해 +대상 기기가 받는 영향을 기준으로 합니다. </p> <p> 실제 고객이 새로 보고된 이러한 문제로 인해 악용당했다는 신고는 접수되지 않았습니다. Android 플랫폼의 보안을 개선하는 -<a href="/security/enhancements/index.html">Android 보안 플랫폼 보호</a> 및 +<a href="#mitigations">Android 보안 플랫폼 보호</a> 및 Google Play 프로텍트에 관해 자세히 알아보려면 -<a href="#mitigations">Android 및 Google Play 프로텍트 완화</a> +<a href="/security/enhancements/index.html">Android 및 Google Play 프로텍트 완화</a> 섹션을 참조하세요. </p> <p class="note"> <strong>참고:</strong> Google 기기의 최신 무선 업데이트(OTA) 및 펌웨어 이미지 관련 정보는 -<a href="/security/bulletin/pixel/2018-04-01.html">2018년 4월Pixel&hairsp;/&hairsp;Nexus 보안 게시판</a> +<a href="/security/bulletin/pixel/2018-04-01.html">2018년 4월 +Pixel&hairsp;/&hairsp;Nexus 보안 게시판</a> 을 참조하세요. </p> <h2 id="announcements">공지사항</h2> <p>모바일 기기의 보안 향상에 많은 도움을 주신 -Qualcomm에 감사드립니다. 2018-04-05 SPL에 Qualcomm의 2014~2016 파트너 전용 게시판에서 취합한 해결 완료된 보안 문제의 누적 목록이 포함되어 있으며, 이는 Qualcomm의 지속적인 노력과 헌신의 결과입니다.</p> +Qualcomm에 감사드립니다. 2018-04-05 SPL에 Qualcomm의 2014~2016 파트너 전용 게시판에서 +취합한 해결 완료된 보안 문제의 누적 목록이 포함되어 있으며, +이는 Qualcomm의 지속적인 노력과 헌신의 결과입니다.</p> <h2 id="mitigations">Android 및 Google 서비스 완화</h2> <p> -다음은 <a href="/security/enhancements/index.html">Android 보안 플랫폼</a> 및 -<a href="https://www.android.com/play-protect">Google Play 프로텍트</a>와 -같은 서비스 보호 기능에서 제공하는 -완화에 관한 요약입니다. +다음은 +<a href="/security/enhancements/index.html">Google Play Protect</a>와 같은 +<a href="https://www.android.com/play-protect">Android 보안 플랫폼</a> 및 서비스 보호 기능에서 +제공하는 완화에 관한 요약입니다. 이러한 기능을 통해 Android에서 보안 취약성이 악용될 가능성을 줄입니다. </p> @@ -77,11 +79,10 @@ Qualcomm에 감사드립니다. 2018-04-05 SPL에 Qualcomm의 2014~2016 파트 악용하기가 더욱 어려워졌습니다. 가능하다면 모든 사용자는 최신 버전의 Android로 업데이트하는 것이 좋습니다.</li> <li>Android 보안팀에서는 -<a href="https://www.android.com/play-protect">Google Play 프로텍트</a> -를 통해 악용사례를 적극적으로 모니터링하고 -<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">유해할 수 있는 -애플리케이션</a> -에 관해 사용자에게 경고를 보냅니다. Google Play 프로텍트는 +<a href="https://www.android.com/play-protect">Google Play 프로텍트</a>를 통해 악용사례를 모니터링하고 +<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">잠재적으로 +위험한 애플리케이션</a>에 관해 +사용자에게 경고를 보냅니다. Google Play 프로텍트는 <a href="http://www.android.com/gms">Google 모바일 서비스</a>가 적용된 기기에 기본적으로 사용 설정되어 있으며 Google Play 외부에서 가져온 앱을 설치하는 사용자에게 특히 중요합니다.</li> @@ -90,11 +91,11 @@ Google Play 외부에서 가져온 앱을 설치하는 사용자에게 <p> 다음 섹션에서는 2018-04-01 패치 수준에 적용되는 각 보안 취약성에 관해 자세히 알아볼 수 있습니다. 취약성은 영향을 받는 -구성요소 아래에 분류되어 있습니다. 여기에는 문제 설명 및 CVE, -관련 참조, <a href="#type">취약성 유형</a>, +구성요소 아래에 분류되어 있습니다. 여기에는 +문제 설명 및 CVE, 관련 참조, +<a href="#type">취약성 유형</a>, <a href="/security/overview/updates-resources.html#severity">심각도</a>, -업데이트된 AOSP 버전(해당하는 경우)이 -포함된 표가 제시됩니다. 가능한 경우 AOSP 변경사항 목록과 같이 +업데이트된 AOSP 버전(해당하는 경우)이 포함된 표가 제시됩니다. 가능한 경우 AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 추가 참조가 버그 ID 다음에 오는 번호에 연결됩니다. @@ -321,10 +322,12 @@ Google Play 외부에서 가져온 앱을 설치하는 사용자에게 문제를 해결한 공개 변경사항을 버그 ID에 연결합니다.</p> <p>하나의 버그와 관련된 변경사항이 여러 개인 경우 추가 -참조가 버그 ID 다음에 오는 번호에 연결되어 있습니다.</p> +참조가 버그 ID 다음에 오는 번호에 연결됩니다.</p> <h3 id="broadcom-components">Broadcom 구성요소</h3> -<p>이 섹션의 가장 심각한 취약성으로 인해 특별히 제작된 파일을 사용하는 근접한 공격자가 권한이 설정된 프로세스의 컨텍스트 내에서 임의의 코드를 실행할 수 있습니다.</p> +<p>이 섹션의 가장 심각한 취약성으로 인해 특별히 +제작된 파일을 사용하는 근접한 공격자가 권한이 설정된 +프로세스의 컨텍스트 내에서 임의의 코드를 실행할 수 있습니다.</p> <table> <colgroup><col width="17%" /> @@ -386,7 +389,9 @@ Google Play 외부에서 가져온 앱을 설치하는 사용자에게 </tbody></table> <h3 id="qualcomm-components">Qualcomm 구성요소</h3> -<p>이 섹션의 가장 심각한 취약성으로 인해 특별히 제작된 파일을 사용하는 근접한 공격자가 권한이 설정된 프로세스의 컨텍스트 내에서 임의의 코드를 실행할 수 있습니다.</p> +<p>이 섹션의 가장 심각한 취약성으로 인해 특별히 +제작된 파일을 사용하는 근접한 공격자가 권한이 설정된 +프로세스의 컨텍스트 내에서 임의의 코드를 실행할 수 있습니다.</p> <table> <colgroup><col width="17%" /> @@ -472,7 +477,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18071</td> <td>A-68326813<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>심각</td> <td>비공개 소스 구성요소 </td> @@ -480,7 +485,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-8274</td> <td>A-68141335<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>심각</td> <td>비공개 소스 구성요소 </td> @@ -488,7 +493,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18146</td> <td>A-70221449<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>심각</td> <td>비공개 소스 구성요소 </td> @@ -496,7 +501,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18128</td> <td>A-70221448<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>심각</td> <td>비공개 소스 구성요소 </td> @@ -504,7 +509,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2018-3592</td> <td>A-71501105<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>심각</td> <td>비공개 소스 구성요소 </td> @@ -512,7 +517,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2018-3591</td> <td>A-71501103<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>심각</td> <td>비공개 소스 구성요소 </td> @@ -520,7 +525,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18074</td> <td>A-68326816<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -528,7 +533,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18073</td> <td>A-68326820<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -536,7 +541,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18125</td> <td>A-68326821<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -544,7 +549,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-8275</td> <td>A-68141336<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -552,7 +557,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-11011</td> <td>A-68326823<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -560,7 +565,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18137</td> <td>A-67712318<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -568,7 +573,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18134</td> <td>A-67712320<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -576,7 +581,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18136</td> <td>A-68989810<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -584,7 +589,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18140</td> <td>A-68989811<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -592,7 +597,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18135</td> <td>A-68989813<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -600,7 +605,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18142</td> <td>A-68989814<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -608,7 +613,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18138</td> <td>A-68989815<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -616,7 +621,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18139</td> <td>A-68989819<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -624,7 +629,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18129</td> <td>A-68989822<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -632,7 +637,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18132</td> <td>A-68989825<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -640,7 +645,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18133</td> <td>A-68989826<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -648,7 +653,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18072</td> <td>A-68989828<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -656,7 +661,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18126</td> <td>A-68989829<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -664,7 +669,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18144</td> <td>A-70221450<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -672,7 +677,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18145</td> <td>A-70221453<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -680,7 +685,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18147</td> <td>A-70221456<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -688,7 +693,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18130</td> <td>A-70221460<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -696,7 +701,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18143</td> <td>A-70221461<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -704,7 +709,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2017-18127</td> <td>A-70221462<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소 </td> @@ -712,28 +717,28 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <tr> <td>CVE-2018-3590</td> <td>A-71501106<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2018-3593</td> <td>A-71501107<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2018-3589</td> <td>A-71501108<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2018-3594</td> <td>A-71501112<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> @@ -764,1750 +769,1750 @@ Qualcomm AMSS 보안 게시판 또는 보안 경고를 통해 파트너에게 <tr> <td>CVE-2014-9996</td> <td>A-37535090<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>심각</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9971</td> <td>A-37546253<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9972</td> <td>A-37546853<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10063</td> <td>A-37534948<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10057</td> <td>A-62261099<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10059</td> <td>A-62260706<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10053</td> <td>A-37544066<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10054</td> <td>A-62261100<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10052</td> <td>A-62258372<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10050</td> <td>A-37546901<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10055</td> <td>A-37545605<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10051</td> <td>A-37546302<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10048</td> <td>A-62258088<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10062</td> <td>A-62258373<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10058</td> <td>A-62260741<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10047</td> <td>A-37538492<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10045</td> <td>A-62258536<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10056</td> <td>A-62261338<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9976</td> <td>A-37534895<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10043</td> <td>A-62259947<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10044</td> <td>A-62260777<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10046</td> <td>A-62261408<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9981</td> <td>A-37534949<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9993</td> <td>A-37540928<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9986</td> <td>A-37534645<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9994</td> <td>A-37538493<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9995</td> <td>A-37546303<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9997</td> <td>A-37546854<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9988</td> <td>A-62258089<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9990</td> <td>A-62261216<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9987</td> <td>A-62261293<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9989</td> <td>A-62261380<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9991</td> <td>A-62261409<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-10039</td> <td>A-62261608<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9985</td> <td>A-62261609<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9204</td> <td>A-37540929<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-0574</td> <td>A-37546304<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9205</td> <td>A-37534696<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9221</td> <td>A-37534796<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9212</td> <td>A-37535795<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9210</td> <td>A-62258538<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9211</td> <td>A-62261217<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9207</td> <td>A-62261410<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9202</td> <td>A-37540473<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9213</td> <td>A-37547700<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9209</td> <td>A-38193247<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9203</td> <td>A-62261218<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9206</td> <td>A-62261294<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9215</td> <td>A-62251854<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9216</td> <td>A-62260780<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9169</td> <td>A-37535098<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9173</td> <td>A-37536244<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9179</td> <td>A-37542567<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9177</td> <td>A-37544075<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9187</td> <td>A-37544109<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9162</td> <td>A-37544110<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9172</td> <td>A-37545607<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9181</td> <td>A-37546754<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9219</td> <td>A-37546859<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9183</td> <td>A-37546860<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9182</td> <td>A-37546904<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9185</td> <td>A-37546952<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9184</td> <td>A-37546953<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9170</td> <td>A-37546954<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9175</td> <td>A-37547404<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9171</td> <td>A-37547405<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9192</td> <td>A-37547750<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9208</td> <td>A-62258540<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9224</td> <td>A-62259949<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9201</td> <td>A-62260711<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9200</td> <td>A-62260779<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9198</td> <td>A-62261219<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9196</td> <td>A-62261339<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9199</td> <td>A-62261411<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9174</td> <td>A-62258090<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9178</td> <td>A-62258541<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9180</td> <td>A-62260712<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9176</td> <td>A-62260713<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9189</td> <td>A-62260820<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9188</td> <td>A-62260821<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-0576</td> <td>A-37543715<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9156</td> <td>A-62260743<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9195</td> <td>A-62251855<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9197</td> <td>A-62260742<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9218</td> <td>A-62260781<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9217</td> <td>A-62261295<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9166</td> <td>A-62251856<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9164</td> <td>A-62258542<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9190</td> <td>A-62259744<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9159</td> <td>A-62259745<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9167</td> <td>A-62259950<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9191</td> <td>A-62260394<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9161</td> <td>A-62260462<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9163</td> <td>A-62260822<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9158</td> <td>A-62261381<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9152</td> <td>A-37546305<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9144</td> <td>A-37540474<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9165</td> <td>A-37539224<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9223</td> <td>A-37543718<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9222</td> <td>A-62258374<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9193</td> <td>A-62259951<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9194</td> <td>A-62261296<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9153</td> <td>A-62260395<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9151</td> <td>A-62260396<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9148</td> <td>A-62260463<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9149</td> <td>A-62260744<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9146</td> <td>A-62260745<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9186</td> <td>A-62261340<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9150</td> <td>A-62261341<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9147</td> <td>A-62261488<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-8593</td> <td>A-37535091<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9160</td> <td>A-37546254<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-8594</td> <td>A-37546855<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9145</td> <td>A-37535099<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9143</td> <td>A-62260900<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9157</td> <td>A-62260934<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9141</td> <td>A-62261297<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9140</td> <td>A-62259746<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9135</td> <td>A-37546950<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9138</td> <td>A-62259952<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9136</td> <td>A-62260823<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9137</td> <td>A-62260975<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9131</td> <td>A-37542272<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9139</td> <td>A-62251857<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9130</td> <td>A-62252820<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9129</td> <td>A-62260397<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9133</td> <td>A-62260464<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9127</td> <td>A-62260824<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9132</td> <td>A-62260976<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9134</td> <td>A-62261382<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9128</td> <td>A-62261610<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9065</td> <td>A-37538494<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9064</td> <td>A-37546801<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9063</td> <td>A-37546802<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9126</td> <td>A-62258375<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9124</td> <td>A-62252821<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9142</td> <td>A-62260901<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9066</td> <td>A-37540467<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2014-9998</td> <td>A-62260398<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9220</td> <td>A-62261299<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9122</td> <td>A-62261611<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9123</td> <td>A-62259953<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9118</td> <td>A-62261220<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9120</td> <td>A-62261298<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9119</td> <td>A-62261489<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9116</td> <td>A-37540934<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9115</td> <td>A-37544076<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9113</td> <td>A-37544077<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9112</td> <td>A-62258091<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9114</td> <td>A-62259954<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9111</td> <td>A-62260465<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9108</td> <td>A-62260714<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9109</td> <td>A-62260977<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2015-9110</td> <td>A-62261383<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10492</td> <td>A-62261300<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10482</td> <td>A-62260978<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10483</td> <td>A-62258092<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10489</td> <td>A-62258093<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10487</td> <td>A-62259955<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10477</td> <td>A-62260399<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10485</td> <td>A-62260902<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10478</td> <td>A-62260979<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10476</td> <td>A-62260980<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10475</td> <td>A-62260981<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10474</td> <td>A-62260982<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10494</td> <td>A-62261102<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10484</td> <td>A-62261342<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10491</td> <td>A-62261490<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10486</td> <td>A-62267788<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10472</td> <td>A-62259956<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10490</td> <td>A-62260468<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10480</td> <td>A-62261301<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10467</td> <td>A-37526814<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10495</td> <td>A-62261103<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10481</td> <td>A-62260401<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10479</td> <td>A-62261412<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10384</td> <td>A-37536238<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10385</td> <td>A-37544067<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10452</td> <td>A-37523164<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10423</td> <td>A-37534896<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10424</td> <td>A-37540034<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10449</td> <td>A-37546861<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10454</td> <td>A-37544078<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10450</td> <td>A-62260825<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10451</td> <td>A-62267789<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10386</td> <td>A-37534646<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10469</td> <td>A-37542273<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10440</td> <td>A-37535092<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10499</td> <td>A-62259957<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10446</td> <td>A-37547406<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10473</td> <td>A-62260746<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10466</td> <td>A-62260783<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10457</td> <td>A-62260826<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10442</td> <td>A-62267790<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10433</td> <td>A-37540468<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10430</td> <td>A-37540930<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10445</td> <td>A-37545608<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10426</td> <td>A-62252822<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10435</td> <td>A-62260402<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10425</td> <td>A-62260983<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10438</td> <td>A-62261302<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10436</td> <td>A-62261494<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10439</td> <td>A-62263656<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10431</td> <td>A-37540931<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10434</td> <td>A-37540932<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10432</td> <td>A-37546902<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10462</td> <td>A-37539225<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10443</td> <td>A-37540475<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10427</td> <td>A-62261495<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10387</td> <td>A-32583751<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10390</td> <td>A-37536239<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10498</td> <td>A-32582870<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10419</td> <td>A-32577129<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10420</td> <td>A-32579916<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10429</td> <td>A-32579411<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10493</td> <td>A-32574787<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10447</td> <td>A-37542968<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10444</td> <td>A-37544163<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-5348</td> <td>A-37546905<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10421</td> <td>A-32579095<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10455</td> <td>A-32580964<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10441</td> <td>A-32582927<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10418</td> <td>A-37547407<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10417</td> <td>A-32576287<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10464</td> <td>A-32580243<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10458</td> <td>A-32583424<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10471</td> <td>A-37539226<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10416</td> <td>A-62259747<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10411</td> <td>A-62260404<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10496</td> <td>A-62260469<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10410</td> <td>A-62260936<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10414</td> <td>A-62260937<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10461</td> <td>A-62263657<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10460</td> <td>A-62271227<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10392</td> <td>A-37544068<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10409</td> <td>A-37544164<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10459</td> <td>A-62260716<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10407</td> <td>A-62261222<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10406</td> <td>A-62267791<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10497</td> <td>A-62271228<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10501</td> <td>A-62261303<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>높음</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10381</td> <td>A-37539788<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>보통</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10380</td> <td>A-37541976<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>보통</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10412</td> <td>A-37536245<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>보통</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10415</td> <td>A-62260403<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>보통</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10422</td> <td>A-37542966<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>보통</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10456</td> <td>A-62261413<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>보통</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10428</td> <td>A-37534697<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>보통</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10448</td> <td>A-62261414<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>보통</td> <td>비공개 소스 구성요소</td> </tr> <tr> <td>CVE-2016-10437</td> <td>A-62260715<a href="#asterisk">*</a></td> - <td>해당 없음</td> + <td>N/A</td> <td>보통</td> <td>비공개 소스 구성요소</td> </tr> @@ -2588,7 +2593,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 경고를 통해 파트너에게 <td>서비스 거부</td> </tr> <tr> - <td>해당 없음</td> + <td>N/A</td> <td>분류 없음</td> </tr> </tbody></table> @@ -2647,8 +2652,10 @@ Qualcomm AMSS 보안 게시판 또는 보안 경고를 통해 파트너에게 보안 패치 수준을 선언하는 데 필요합니다. 기기/파트너 보안 게시판에 설명된 추가 보안 취약성은 보안 패치 수준을 선언하는 데 필요하지 않습니다. -Android 기기 및 칩셋 제조업체는 <a href="https://security.samsungmobile.com/securityUpdate.smsb">삼성</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a> 또는 -<a href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus</a> 보안 게시판과 같은 자체 +Android 기기 및 칩셋 제조업체는 <a href="https://security.samsungmobile.com/securityUpdate.smsb">삼성</a>, +<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a> 또는 +<a href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus</a> +보안 게시판과 같은 자체 보안 웹사이트를 통해 기기의 다른 수정사항이 있는지를 설명하는 것이 좋습니다. </p> diff --git a/ko/security/bulletin/2018-05-01.html b/ko/security/bulletin/2018-05-01.html index 51518079..2d1e751e 100644 --- a/ko/security/bulletin/2018-05-01.html +++ b/ko/security/bulletin/2018-05-01.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p><em>2018년 5월 7일 게시됨 | 2018년 5월 11일 업데이트됨</em></p> +<p><em>2018년 5월 7일 게시됨 | 2018년 7월 11일 업데이트됨</em></p> <p> Android 보안 게시판은 Android 기기에 영향을 미치는 보안 취약성 @@ -40,8 +40,8 @@ Android 오픈소스 프로젝트(AOSP) 저장소에 배포되었으며 이 게 특별히 제작된 파일을 사용하는 원격 공격자가 권한이 설정된 프로세스의 컨텍스트 내에서 임의의 코드를 실행할 수 있습니다. <a href="/security/overview/updates-resources.html#severity">심각도 평가</a>는 -개발 목적으로 플랫폼 및 서비스 완화를 사용할 수 없거나 -우회에 성공한 경우 취약성 악용으로 인해 대상 기기가 받는 영향을 +개발 목적으로 플랫폼 및 서비스 완화를 사용할 수 없거나 우회에 성공한 경우 취약성 악용으로 인해 +대상 기기가 받는 영향을 기준으로 합니다. </p> <p> @@ -61,10 +61,8 @@ Android 오픈소스 프로젝트(AOSP) 저장소에 배포되었으며 이 게 <h2 id="mitigations">Android 및 Google 서비스 완화</h2> <p> -다음은 <a href="/security/enhancements/index.html">Android 보안 플랫폼</a> 및 -<a href="https://www.android.com/play-protect">Google Play 프로텍트</a>와 -같은 서비스 보호 기능에서 제공하는 -완화에 관한 요약입니다. +다음은 <a href="/security/enhancements/index.html">Android 보안 플랫폼</a> 및 <a href="https://www.android.com/play-protect">Google Play 프로텍트</a>와 같은 +서비스 보호 기능에서 제공하는 완화에 관한 요약입니다. 이러한 기능을 통해 Android에서 보안 취약성이 악용될 가능성을 줄입니다. </p> @@ -72,12 +70,7 @@ Android 오픈소스 프로젝트(AOSP) 저장소에 배포되었으며 이 게 <li>Android 플랫폼 최신 버전의 향상된 기능으로 Android의 여러 문제를 악용하기가 더욱 어려워졌습니다. 가능하다면 모든 사용자는 최신 버전의 Android로 업데이트하는 것이 좋습니다.</li> -<li>Android 보안팀에서는 -<a href="https://www.android.com/play-protect">Google Play 프로텍트</a> -를 통해 악용사례를 적극적으로 모니터링하고 -<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">유해할 수 있는 -애플리케이션</a> -에 관해 사용자에게 경고를 보냅니다. Google Play 프로텍트는 +<li>Android 보안팀에서는 <a href="https://www.android.com/play-protect">Google Play 프로텍트</a>를 통해 악용사례를 모니터링하고 <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">유해할 수 있는 애플리케이션</a>에 관해 사용자에게 경고를 보냅니다. Google Play 프로텍트는 <a href="http://www.android.com/gms">Google 모바일 서비스</a>가 적용된 기기에 기본적으로 사용 설정되어 있으며 Google Play 외부에서 가져온 앱을 설치하는 사용자에게 특히 중요합니다.</li> diff --git a/ko/security/bulletin/2018-06-01.html b/ko/security/bulletin/2018-06-01.html index 02479e30..5f093a76 100644 --- a/ko/security/bulletin/2018-06-01.html +++ b/ko/security/bulletin/2018-06-01.html @@ -19,7 +19,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>2018년 6월 4일 게시됨 | 2018년 6월 6일 업데이트됨</em></p> +<p><em>2018년 6월 4일 게시됨 | 2018년 7월 24일 업데이트됨</em></p> <p> Android 보안 게시판은 Android 기기에 영향을 미치는 보안 취약성 @@ -54,8 +54,8 @@ Android 오픈소스 프로젝트(AOSP) 저장소에 배포되었으며 이 게 <p class="note"> <strong>참고:</strong> Google 기기의 최신 무선 업데이트(OTA) 및 펌웨어 이미지 관련 정보는 -<a href="/security/bulletin/pixel/2018-06-01.html">2018년 6월Pixel&hairsp;/&hairsp; -Nexus 보안 게시판</a> +<a href="/security/bulletin/pixel/2018-06-01.html">2018년 6월 +Pixel&hairsp;/&hairsp;Nexus 보안 게시판</a> 을 참조하세요. </p> @@ -306,6 +306,37 @@ CVE, 관련 참조, <a href="#type"> 문제를 해결한 공개 변경사항을 버그 ID에 연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 추가 참조가 버그 ID 다음에 오는 번호에 연결되어 있습니다. </p> + +<h3 id="broadcom-components">Broadcom 구성요소</h3> + +<p> +이 섹션의 가장 심각한 취약성으로 인해 원래는 권한을 갖고 있으며 로컬에 설치한 +애플리케이션만 액세스할 수 있는 데이터에 원격 공격자가 액세스하도록 할 수 있습니다. +</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-73665456<a href="#asterisk">*</a><br /> +B-CS4906525</td> + <td>ID</td> + <td>높음</td> + <td>블루투스</td> + </tr> +</tbody></table> + <h3 id="kernel-components">커널 구성요소</h3> <p> @@ -632,7 +663,15 @@ QC-CR#2151241</a></td> <td>높음</td> <td>WLAN</td> </tr> - <tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-73665204<a href="#asterisk">*</a><br /> + QC-CR#2187697</td> + <td>ID</td> + <td>높음</td> + <td>블루투스</td> + </tr> + <tr> <td>CVE-2017-18159</td> <td>A-68992405<br /> <a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=633fa4ffb38bbfb0fad79204e19b9f59d42d7680">QC-CR#2105697</a> @@ -766,6 +805,35 @@ QC-CR#2161310</a></td> </tr> </tbody></table> +<h3 id="system-components">시스템</h3> + +<p> +이 섹션의 가장 심각한 취약성으로 인해 원래는 권한을 갖고 있으며 로컬에 설치한 +애플리케이션만 액세스할 수 있는 데이터에 원격 공격자가 액세스하도록 할 수 있습니다. +</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>업데이트된 AOSP 버전</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/fa3d7e1f784d3bdbf8f9d8b572a60696289211b1">A-72377774</a></td> + <td>ID</td> + <td>높음</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + <h2 id="common-questions-and-answers">일반적인 질문 및 답변</h2> <p>이 섹션에서는 게시판을 읽은 뒤 제기될 수 있는 일반적인 질문의 답변을 제시합니다.</p> <p><strong>1. 내 기기가 업데이트되어 이 문제가 해결되었는지 어떻게 알 수 있나요?</strong></p> @@ -833,7 +901,7 @@ QC-CR#2161310</a></td> <td>서비스 거부</td> </tr> <tr> - <td>해당 없음</td> + <td>N/A</td> <td>분류 없음</td> </tr> </tbody></table> @@ -919,6 +987,11 @@ Android 기기의 최신 보안 패치 수준을 선언하는 데 필요합니 <td>2018년 6월 6일</td> <td>게시판이 수정되어 AOSP 링크 포함됨</td> </tr> + <tr> + <td>1.2</td> + <td>2018년 7월 24일</td> + <td>게시판이 수정되어 합의된 공개 원칙에 따라 CVE-2018-5383에 참조 포함됨</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ko/security/bulletin/2018-07-01.html b/ko/security/bulletin/2018-07-01.html index 2d8fda65..566f341a 100644 --- a/ko/security/bulletin/2018-07-01.html +++ b/ko/security/bulletin/2018-07-01.html @@ -1,5 +1,5 @@ <html devsite><head> - <title>Android 보안 게시판 - 2018년 7월</title> + <title>Android 보안 게시판—2018년 7월</title> <meta name="project_path" value="/_project.yaml"/> <meta name="book_path" value="/_book.yaml"/> </head> @@ -19,7 +19,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>2018년 7월 2일에 게시됨</em></p> +<p><em>2018년 7월 2일에 게시됨 | 2018년 7월 3일에 업데이트됨</em></p> <p> Android 보안 게시판은 Android 기기에 영향을 미치는 보안 취약성 @@ -29,10 +29,10 @@ Android 보안 게시판은 Android 기기에 영향을 미치는 보안 취약 참조하세요. </p> <p> -Android 파트너에게는 게시되기 최소 한 달 전에 모든 문제 관련 알림이 전달되었습니다. -이러한 문제의 해결을 위한 소스 코드 패치는 향후 48시간 동안 -Android 오픈소스 프로젝트(AOSP) 저장소에 배포됩니다. 패치를 사용할 수 -있게 되면 AOSP 링크와 함께 이 게시판을 수정하겠습니다. +Android 파트너에게는 게시되기 최소 한 달 전에 모든 문제 관련 알림이 +전달되었습니다. 이러한 문제를 해결하기 위한 소스 코드 패치는 +Android 오픈소스 프로젝트(AOSP) 저장소에 배포되었으며 이 게시판에도 링크되어 있습니다. +이 게시판에는 AOSP 외부의 패치 링크도 포함되어 있습니다. </p> <p> 이러한 문제 중 가장 심각한 것은 미디어 프레임워크의 심각한 보안 취약성으로, @@ -46,25 +46,25 @@ Android 오픈소스 프로젝트(AOSP) 저장소에 배포됩니다. 패치를 <p> 실제 고객이 새로 보고된 이러한 문제로 인해 악용당했다는 신고는 접수되지 않았습니다. Android 플랫폼의 보안을 개선하는 -<a href="/security/enhancements/index.html">Android 보안 플랫폼 보호</a> +<a href="#mitigations">Android 보안 플랫폼 보호</a> 및 Google Play 프로텍트에 관해 자세히 알아보려면 -<a href="#mitigations">Android 및 Google Play 프로텍트 완화</a> +<a href="/security/enhancements/index.html">Android 및 Google Play 프로텍트 완화</a> 섹션을 참조하세요. </p> <p class="note"> <strong>참고:</strong> Google 기기의 최신 무선 업데이트(OTA) 및 펌웨어 이미지 관련 정보는 -<a href="/security/bulletin/pixel/2018-07-01.html">2018년 6월 +<a href="/security/bulletin/pixel/2018-07-01.html">2018년 7월 Pixel&hairsp;/&hairsp;Nexus 보안 게시판</a> 을 참조하세요. </p> <h2 id="mitigations">Android 및 Google 서비스 완화</h2> <p> -다음은 <a href="/security/enhancements/index.html">Android 보안 플랫폼</a> 및 -<a href="https://www.android.com/play-protect">Google Play 프로텍트</a>와 -같은 서비스 보호 기능에서 제공하는 -완화에 관한 요약입니다. +다음은 +<a href="/security/enhancements/index.html">Google Play Protect</a>와 같은 +<a href="https://www.android.com/play-protect">Android 보안 플랫폼</a> 및 서비스 보호 기능에서 +제공하는 완화에 관한 요약입니다. 이러한 기능을 통해 Android에서 보안 취약성이 악용될 가능성을 줄입니다. </p> @@ -73,11 +73,10 @@ Pixel&hairsp;/&hairsp;Nexus 보안 게시판</a> 악용하기가 더욱 어려워졌습니다. 가능하다면 모든 사용자는 최신 버전의 Android로 업데이트하는 것이 좋습니다.</li> <li>Android 보안팀에서는 -<a href="https://www.android.com/play-protect">Google Play 프로텍트</a> -를 통해 악용사례를 적극적으로 모니터링하고 -<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">유해할 수 있는 -애플리케이션</a> -에 관해 사용자에게 경고를 보냅니다. Google Play 프로텍트는 +<a href="https://www.android.com/play-protect">Google Play 프로텍트</a>를 통해 악용사례를 모니터링하고 +<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">잠재적으로 +위험한 애플리케이션</a>에 관해 +사용자에게 경고를 보냅니다. Google Play 프로텍트는 <a href="http://www.android.com/gms">Google 모바일 서비스</a>가 적용된 기기에 기본적으로 사용 설정되어 있으며 Google Play 외부에서 가져온 앱을 설치하는 사용자에게 특히 중요합니다.</li> @@ -116,14 +115,14 @@ Google Play 외부에서 가져온 앱을 설치하는 사용자에게 </tr> <tr> <td>CVE-2018-9433</td> - <td>A-38196219</td> + <td>A-38196219<a href="#asterisk">*</a></td> <td>RCE</td> <td>심각</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> </tr> <tr> <td>CVE-2018-9410</td> - <td>A-77822336</td> + <td><a href="https://android.googlesource.com/platform/frameworks/minikin/+/62e88b9f3ac35e1e69d79c7a43c6f9ddcd5980a3">A-77822336</a></td> <td>ID</td> <td>높음</td> <td>8.0, 8.1</td> @@ -150,35 +149,35 @@ Google Play 외부에서 가져온 앱을 설치하는 사용자에게 </tr> <tr> <td>CVE-2018-9411</td> - <td>A-79376389</td> + <td><a href="https://android.googlesource.com/platform/system/libhidl/+/e1302cfda34be9dd0a4aeae6bfa9561b44536758">A-79376389</a></td> <td>RCE</td> <td>심각</td> <td>8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9424</td> - <td>A-76221123</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/d3860e51b83296ae1d2921d8109210283573862a">A-76221123</a></td> <td>EoP</td> <td>높음</td> <td>8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9428</td> - <td>A-74122779</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/46bd7c682db5bbc048b177c52448a7999e5740ce">A-74122779</a></td> <td>EoP</td> <td>높음</td> <td>8.1</td> </tr> <tr> <td>CVE-2018-9412</td> - <td>A-78029004</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/fa12c0fcdc6607b746177ccad4f7099098b4849a">A-78029004</a></td> <td>DoS</td> <td>높음</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9421</td> - <td>A-77237570</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/ff2171f2460e3a6d3443ab957732b8b7d4831d40">A-77237570</a></td> <td>ID</td> <td>높음</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -205,28 +204,28 @@ Google Play 외부에서 가져온 앱을 설치하는 사용자에게 </tr> <tr> <td>CVE-2018-9365</td> - <td>A-74121126</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/ae94a4c333417a1829030c4d87a58ab7f1401308">A-74121126</a></td> <td>RCE</td> <td>심각</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9432</td> - <td>A-73173182</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/a6fe2cd18c77c68219fe7159c051bc4e0003fc40">A-73173182</a></td> <td>EoP</td> <td>높음</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9420</td> - <td>A-77238656</td> + <td><a href="https://android.googlesource.com/platform/system/media/+/12df4b05fd918d836636e21f783df7ad9d5e17a3">A-77238656</a></td> <td>ID</td> <td>높음</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9419</td> - <td>A-74121659</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/f1c2c86080bcd7b3142ff821441696fc99c2bc9a">A-74121659</a></td> <td>ID</td> <td>높음</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -239,8 +238,8 @@ Google Play 외부에서 가져온 앱을 설치하는 사용자에게 각 보안 취약성에 관해 자세히 알아볼 수 있습니다. 취약성은 영향을 받는 구성요소 아래에 분류되어 있으며 CVE, 관련 참조, <a href="#type">취약성 유형</a>, -<a href="/security/overview/updates-resources.html#severity">심각도</a> -, 구성요소(해당하는 경우), 업데이트된 AOSP 버전(해당하는 경우)과 같은 세부정보가 포함되어 있습니다. 가능한 +<a href="/security/overview/updates-resources.html#severity">심각도</a>, +구성요소(해당하는 경우), 업데이트된 AOSP 버전(해당하는 경우)과 같은 세부정보가 포함되어 있습니다. 가능한 경우 AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 추가 참조가 버그 ID 다음에 오는 번호에 연결됩니다. @@ -299,7 +298,9 @@ CVE, 관련 참조, </tbody></table> <h3 id="qualcomm-components">Qualcomm 구성요소</h3> -<p>이 섹션의 가장 심각한 취약성으로 인해 특별히 제작된 파일을 사용하는 근접한 공격자가 권한이 설정된 프로세스의 컨텍스트 내에서 임의의 코드를 실행할 수 있습니다.</p> +<p>이 섹션의 가장 심각한 취약성으로 인해 특별히 제작된 파일을 사용하는 근접한 +공격자가 권한이 설정된 프로세스의 컨텍스트 내에서 +임의의 코드를 실행할 수 있습니다.</p> <table> <colgroup><col width="21%" /> @@ -323,14 +324,6 @@ CVE, 관련 참조, <td>WLAN</td> </tr> <tr> - <td>CVE-2018-5855</td> - <td>A-77527719<br /> - <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qca-wifi-host-cmn/commit/?id=61f4a467177afc23bdc1944ec61e52bed156c104">QC-CR#2181685</a></td> - <td>ID</td> - <td>높음</td> - <td>WLAN</td> - </tr> - <tr> <td>CVE-2017-13077, CVE-2017-13078</td> <td>A-78285557<br /> <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=5c671a69c57ce4fd84f0eaf082b336a49d0cf5dd">QC-CR#2133114</a></td> @@ -482,13 +475,6 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <td>비공개 소스 구성요소</td> </tr> <tr> - <td>CVE-2018-11258</td> - <td>A-72951054<a href="#asterisk">*</a></td> - <td>N/A</td> - <td>높음</td> - <td>비공개 소스 구성요소</td> - </tr> - <tr> <td>CVE-2018-11257</td> <td>A-74235874<a href="#asterisk">*</a></td> <td>N/A</td> @@ -606,7 +592,7 @@ Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 <td>서비스 거부</td> </tr> <tr> - <td>해당 없음</td> + <td>N/A</td> <td>분류 없음</td> </tr> </tbody></table> @@ -667,7 +653,7 @@ Android 기기의 최신 보안 패치 수준을 선언하는 데 필요합니 필요하지 않습니다. Android 기기 및 칩셋 제조업체는 <a href="https://security.samsungmobile.com/securityUpdate.smsb">삼성</a>, -<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, 또는 +<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a> 또는 <a href="/security/bulletin/pixel/">Pixel&hairsp;/&hairsp;Nexus</a> 보안 게시판과 같은 자체 보안 웹사이트를 통해 기기의 다른 수정사항이 있는지를 설명하는 것이 좋습니다. @@ -687,6 +673,16 @@ Android 기기의 최신 보안 패치 수준을 선언하는 데 필요합니 <td>2018년 7월 2일</td> <td>게시판이 게시됨</td> </tr> + <tr> + <td>1.1</td> + <td>2018년 7월 3일</td> + <td>게시판이 수정되어 AOSP 링크 포함됨</td> + </tr> + <tr> + <td>1.2</td> + <td>2018년 7월 11일</td> + <td>CVE-2018-5855와 CVE-2018-11258이 2018-07-05 SPL에서 삭제됨</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ko/security/bulletin/2018-08-01.html b/ko/security/bulletin/2018-08-01.html new file mode 100644 index 00000000..8374263e --- /dev/null +++ b/ko/security/bulletin/2018-08-01.html @@ -0,0 +1,729 @@ +<html devsite><head> + <title>Android 보안 게시판—2018년 8월</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> +<p><em>2018년 8월 6일 게시됨</em></p> + +<p> +Android 보안 게시판은 Android 기기에 영향을 미치는 보안 취약성 +세부정보를 다룹니다. 이러한 문제는 2018-08-05 보안 패치 수준 이상에서 +모두 해결되었습니다. 기기의 보안 패치 수준을 확인하는 방법은 +<a href="https://support.google.com/pixelphone/answer/4457705" class="external">Android 버전 확인 및 업데이트</a>를 참조하세요. +</p> +<p> +Android 파트너에게는 게시되기 최소 한 달 전에 모든 문제 관련 알림이 +전달되었습니다. 이러한 문제를 해결하기 위한 소스 코드 패치는 +Android 오픈소스 프로젝트(AOSP) 저장소에 배포되었으며 이 게시판에도 링크되어 있습니다. +이 게시판에는 AOSP 외부의 패치 링크도 포함되어 있습니다. +</p> +<p> +이러한 문제 중 가장 심각한 취약성으로, +특별히 제작된 파일을 사용하는 원격 공격자가 권한이 설정된 프로세스의 컨텍스트 +내에서 임의의 코드를 실행할 수 있습니다. <a href="/security/overview/updates-resources.html#severity">심각도 +평가</a>는 +개발 목적으로 플랫폼 및 서비스 완화를 사용할 수 없거나 우회에 성공한 경우 취약성 악용으로 인해 +대상 기기가 받는 영향을 +기준으로 합니다. +</p> +<p> +실제 고객이 새로 보고된 이러한 문제로 인해 악용당했다는 신고는 +접수되지 않았습니다. Android 플랫폼의 보안을 개선하는 +<a href="/security/enhancements/index.html">Android 보안 플랫폼 보호</a> 및 Google Play 프로텍트에 관해 +자세히 알아보려면 <a href="#mitigations">Android 및 Google Play 프로텍트 완화</a> +섹션을 참조하세요. +</p> +<p class="note"> +<strong>참고:</strong> Google 기기의 최신 무선 업데이트(OTA) +및 펌웨어 이미지 관련 정보는 +<a href="/security/bulletin/pixel/2018-08-01.html">2018년 6월Pixel&hairsp;/&hairsp; +Nexus 보안 게시판</a> +을 참조하세요. +</p> + +<h2 id="mitigations">Android 및 Google 서비스 완화</h2> +<p> +다음은 +<a href="https://www.android.com/play-protect">Google Play 프로텍트</a>와 같은 +<a href="/security/enhancements/index.html">Android 보안 플랫폼</a> 및 서비스 보호 기능에서 +제공하는 완화에 관한 요약입니다. +이러한 기능을 통해 Android에서 +보안 취약성이 악용될 가능성을 줄입니다. +</p> +<ul> +<li>Android 플랫폼 최신 버전의 향상된 기능으로 Android의 여러 문제를 +악용하기가 더욱 어려워졌습니다. 가능하다면 모든 사용자는 최신 버전의 Android로 +업데이트하는 것이 좋습니다.</li> +<li>Android 보안팀에서는 <a href="https://www.android.com/play-protect" class="external">Google Play 프로텍트</a>를 통해 악용사례를 모니터링하고 <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">잠재적으로 위험한 애플리케이션</a>에 관해 사용자에게 경고를 보냅니다. Google Play 프로텍트는 <a href="http://www.android.com/gms" class="external">Google 모바일 서비스</a>가 적용된 기기에 +기본적으로 +사용 설정되어 있으며 Google Play 외부에서 가져온 앱을 설치하는 사용자에게 +특히 중요합니다.</li> +</ul> +<h2 id="2018-08-01-details">2018-08-01 보안 패치 수준 +취약성 세부정보</h2> +<p> +다음 섹션에서는 2018-08-01 패치 수준에 적용되는 각 보안 +취약성에 관해 자세히 알아볼 수 있습니다. 취약성은 영향을 받는 +구성요소 아래에 분류되어 있습니다. 여기에는 +문제 설명 및 CVE, 관련 참조, +<a href="#type">취약성 유형</a>, +<a href="/security/overview/updates-resources.html#severity">심각도</a>, +업데이트된 AOSP 버전(해당하는 경우)이 포함된 표가 제시됩니다. 가능한 경우 AOSP 변경사항 목록과 같이 +문제를 해결한 공개 변경사항을 버그 ID에 연결합니다. 하나의 +버그와 관련된 변경사항이 여러 개인 경우 추가 참조가 버그 ID +다음에 오는 번호에 연결됩니다. +</p> + +<h3 id="framework">프레임워크</h3> +<p>이 섹션에서 가장 심각한 취약성으로 인해 로컬 악성 애플리케이션이 +사용자 상호작용 요구사항을 우회하여 추가적인 권한에 +액세스할 수 있습니다.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>업데이트된 AOSP 버전</th> + </tr> + <tr> + <td>CVE-2018-9445</td> + <td> + <a href="https://android.googlesource.com/platform/external/e2fsprogs/+/9a2d95e4ed9ec5ab76998654b1c2fba9cc139e50">A-80436257</a> + [<a href="https://android.googlesource.com/platform/system/vold/+/940a1ff70cfc5f2e4de83da9ad84cd9734faadf6">2</a>] + </td> + <td>EoP</td> + <td>높음</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9438</td> + <td> +<a href="https://android.googlesource.com/platform/packages/providers/DownloadProvider/+/b552ebf70913cc79085bcc4212235ea45e036d3b">A-78644887</a> +[<a href="https://android.googlesource.com/platform/frameworks/base/+/e3854655e75d97552140d77cca5d20c121a17ef9">2</a>] +[<a href="https://android.googlesource.com/platform/frameworks/opt/telephony/+/d1ce32b059bed774b41f11413c1d83a1bc412964">3</a>] +[<a href="https://android.googlesource.com/platform/frameworks/base/+/97e1cd61d3040dd366ac9e25cdb6f134c7490846">4</a>] +</td> + <td>DoS</td> + <td>높음</td> + <td>8.1</td> + </tr> + <tr> + <td>CVE-2018-9458</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/c4f66f4f607654611b2227827123e016c57a5729">A-71786287</a> +</td> + <td>EoP</td> + <td>높음</td> + <td>8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9451</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/a409aa1214d6483efe129a4966f09aa4fdc097ad">A-79488511</a> +[<a href="https://android.googlesource.com/platform/frameworks/base/+/1de25074adb5d9ed572d6a85e77d3df5ac3a7e9e">2</a>] +</td> + <td>ID</td> + <td>높음</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="media-framework">미디어 프레임워크</h3> +<p>이 섹션의 가장 심각한 취약성으로 인해 특별히 제작된 파일을 사용하는 +원격 공격자가 권한이 설정된 프로세스의 컨텍스트 내에서 임의의 코드를 +실행할 수 있습니다.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>업데이트된 AOSP 버전</th> + </tr> + <tr> + <td>CVE-2018-9427</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/av/+/08d392085c095e227c029f64644bc08ef5a544de">A-77486542</a> +[<a href="https://android.googlesource.com/platform/frameworks/av/+/c9909e5a980f941a5b72477755e09fb4dc57c478">2</a>] +</td> + <td>RCE</td> + <td>심각</td> + <td>8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9444</td> + <td>A-63521984<a href="#asterisk">*</a></td> + <td>DoS</td> + <td>높음</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> + </tr> + <tr> + <td>CVE-2018-9437</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/av/+/017ff33fd419c50734f775d5054e2cbea719700b">A-78656554</a> + </td> + <td>DoS</td> + <td>높음</td> + <td>6.0, 6.0.1</td> + </tr> +</tbody></table> + +<h3 id="system">시스템</h3> +<p>이 섹션의 가장 심각한 취약성으로 인해 특별히 제작된 파일을 사용하는 +원격 공격자가 권한이 설정된 프로세스의 컨텍스트 내에서 임의의 코드를 +실행할 수 있습니다.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>업데이트된 AOSP 버전</th> + </tr> + <tr> + <td>CVE-2018-9446</td> + <td> + <a href="https://android.googlesource.com/platform/system/bt/+/49acada519d088d8edf37e48640c76ea5c70e010">A-80145946</a> + </td> + <td>RCE</td> + <td>심각</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9450</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/bc259b4926a6f9b33b9ee2c917cd83a55f360cbf">A-79541338</a> + </td> + <td>RCE</td> + <td>심각</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9459</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/UnifiedEmail/+/76c5261a03c8402e893999196651afc5791ca0fd">A-66230183</a> + </td> + <td>EoP</td> + <td>높음</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9455</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/d56c7ec9e2ecfa8a8ceeb82f37187e5ea21f2101">A-78136677</a> + </td> + <td>DoS</td> + <td>높음</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9436</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/289a49814aef7f0f0bb98aac8246080abdfeac01">A-79164722</a> + </td> + <td>ID</td> + <td>높음</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9454</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/289a49814aef7f0f0bb98aac8246080abdfeac01">A-78286118</a> + </td> + <td>ID</td> + <td>높음</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9448</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/13294c70a66347c9e5d05b9f92f8ceb6fe38d7f6">A-79944113</a> +[<a href="https://android.googlesource.com/platform/system/bt/+/f1f1c3e00f8d1baad0215b057e6d894517eeaddb">2</a>] + </td> + <td>ID</td> + <td>높음</td> + <td>8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9453</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/cb6a56b1d8cdab7c495ea8f53dcbdb3cfc9477d2">A-78288378</a> + </td> + <td>ID</td> + <td>높음</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h2 id="2018-08-05-details">2018-08-05 보안 패치 수준 취약성 세부정보</h2> +<p> +다음 섹션에서는 2018-08-05 패치 수준에 적용되는 각 보안 +취약성에 관해 자세히 알아볼 수 있습니다. 취약성은 +영향을 받는 구성요소 아래에 분류되어 있으며 +CVE, 관련 참조, <a href="#type">취약성 유형</a>, +<a href="/security/overview/updates-resources.html#severity">심각도</a>, +구성요소(해당하는 경우), 업데이트된 AOSP 버전(해당하는 경우)과 같은 세부정보가 포함되어 있습니다. 가능한 +경우 AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 +연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 +추가 참조가 버그 ID 다음에 오는 번호에 연결됩니다. +</p> + +<h3 id="kernel-components">커널 구성요소</h3> +<p>이 섹션의 가장 심각한 취약성으로 인해 로컬 악성 애플리케이션이 +권한이 설정된 프로세스의 컨텍스트 내에서 임의의 코드를 실행할 수 +있습니다.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2017-18249</td> + <td>A-78283212<br /> + <a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30a61ddf8117c26ac5b295e1233eaa9629a94ca3"> +업스트림 커널</a></td> + <td>EoP</td> + <td>높음</td> + <td>F2FS</td> + </tr> + <tr> + <td>CVE-2018-9465</td> + <td>A-69164715<br /> + <a href="https://patchwork.kernel.org/patch/10058587/">업스트림 +커널</a></td> + <td>EoP</td> + <td>높음</td> + <td>바인더</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Qualcomm 구성요소</h3> +<p>이 섹션의 가장 심각한 취약성으로 인해 추가 실행 권한 없이 원격 정보가 공개될 수 있습니다.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-79421580<a href="#asterisk">*</a><br /> + QC-CR#2209635</td> + <td>ID</td> + <td>높음</td> + <td>블루투스</td> + </tr> + <tr> + <td>CVE-2017-13077</td> + <td>A-78284758<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=edb507885fc47cf3cdf061bfba1dc77451a6a332"> +QC-CR#2133033</a></td> + <td>ID</td> + <td>높음</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18281</td> + <td>A-78242172<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=69f0a80b8cc1333647397d7bc4f267bd3fe22be9"> +QC-CR#856388</a></td> + <td>ID</td> + <td>높음</td> + <td>동영상</td> + </tr> + <tr> + <td>CVE-2018-11260</td> + <td>A-72997254<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=9fd239116d9cb19a18b3892b8a1f428636ca1453"> +QC-CR#2204872</a></td> + <td>EoP</td> + <td>높음</td> + <td>WLAN</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-closed-source-components">Qualcomm 비공개 소스 +구성요소</h3> +<p>다음 취약성은 Qualcomm 구성요소에 영향을 주며 해당 +Qualcomm AMSS 보안 게시판 또는 보안 알림에 자세히 설명되어 +있습니다. 이러한 문제의 심각도 평가는 Qualcomm에서 직접 +제공합니다.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2017-18296</td> + <td>A-78240731<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>심각</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18305</td> + <td>A-78239838<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>심각</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18310</td> + <td>A-62211308<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>심각</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18295</td> + <td>A-78240386<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18283</td> + <td>A-78240411<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18294</td> + <td>A-78240247<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18293</td> + <td>A-78240316<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18292</td> + <td>A-78241027<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18298</td> + <td>A-78239976<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18299</td> + <td>A-78240418<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18304</td> + <td>A-78239975<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18303</td> + <td>A-78240396<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18301</td> + <td>A-78238455<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18302</td> + <td>A-78239233<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18300</td> + <td>A-78239508<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18297</td> + <td>A-78240275<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18280</td> + <td>A-78285512<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18282</td> + <td>A-78241591<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18309</td> + <td>A-73539064<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2017-18308</td> + <td>A-73539310<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2018-11305</td> + <td>A-72951032<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> + <tr> + <td>CVE-2018-11258</td> + <td>A-72951054<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>높음</td> + <td>비공개 소스 구성요소</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">일반적인 질문 및 답변</h2> +<p>이 섹션에서는 게시판을 읽은 뒤 제기될 수 있는 일반적인 질문의 답변을 +제시합니다.</p> +<p><strong>1. 내 기기가 업데이트되어 이 문제가 해결되었는지 어떻게 알 수 +있나요?</strong></p> +<p>기기의 보안 패치 수준을 확인하는 방법은 +<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">Android 버전 확인 및 업데이트</a>를 참조하세요.</p> +<ul> +<li>2018-08-01 보안 패치 수준과 관련된 모든 문제는 2018-08-01 +보안 패치 수준 이상에서 해결되었습니다.</li> +<li>2018-08-05 보안 패치 수준 및 그 이전의 모든 패치 수준과 관련된 +문제는 2018-08-05 보안 패치 수준 이상에서 모두 해결됩니다.</li> +</ul> +<p>이 업데이트를 포함하는 기기 제조업체는 패치 문자열 수준을 다음과 같이 +설정해야 합니다.</p> +<ul> + <li>[ro.build.version.security_patch]:[2018-08-01]</li> + <li>[ro.build.version.security_patch]:[2018-08-05]</li> +</ul> +<p><strong>2. 이 게시판에 두 가지 보안 패치 수준이 있는 이유가 무엇인가요?</strong></p> +<p> +이 게시판에는 Android 파트너가 모든 Android 기기에서 유사하게 발생하는 +취약성 문제의 일부를 더욱 빠르고 유연하게 해결할 수 있도록 두 가지 +보안 패치 수준이 포함되어 있습니다. Android 파트너는 이 게시판에 언급된 문제를 모두 수정하고 +최신 보안 패치 수준을 사용하는 것이 좋습니다. +</p> +<ul> +<li>2018-08-01 보안 패치 수준을 사용하는 기기는 이 보안 패치 수준과 +관련된 모든 문제와 이전 보안 게시판에 보고된 모든 문제의 수정사항을 +포함해야 합니다.</li> +<li>2018-08-05 이후의 보안 패치 수준을 사용하는 기기는 +이 보안 게시판과 이전 게시판의 모든 관련 패치를 +포함해야 합니다.</li> +</ul> +<p> +파트너는 해결하는 모든 문제의 수정사항을 단 한 번의 업데이트에서 번들로 묶는 것이 +좋습니다. +</p> +<p id="type"> +<strong>3. <em>유형</em> 열의 항목은 무엇을 의미하나요?</strong> +</p> +<p> +취약성 세부정보 표의 <em>유형</em> 열에 있는 항목은 +보안 취약성 분류를 참조합니다. +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>약어</th> + <th>정의</th> + </tr> + <tr> + <td>RCE</td> + <td>원격 코드 실행</td> + </tr> + <tr> + <td>EoP </td> + <td>권한 승격</td> + </tr> + <tr> + <td>ID </td> + <td>정보 공개</td> + </tr> + <tr> + <td>DoS</td> + <td>서비스 거부</td> + </tr> + <tr> + <td>N/A</td> + <td>분류 없음</td> + </tr> +</tbody></table> +<p> +<strong>4. <em>참조</em> 열의 항목은 무엇을 의미하나요?</strong> +</p> +<p> +취약성 세부정보 표의 <em>참조</em> 열에 있는 항목은 +참조 값이 속한 조직을 나타내는 접두어를 포함할 수 +있습니다. +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>접두어</th> + <th>참조</th> + </tr> + <tr> + <td>A-</td> + <td>Android 버그 ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm 참조 번호</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek 참조 번호</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA 참조 번호</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom 참조 번호</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>5. <em>참조</em> 열에서 Android 버그 ID 옆에 있는 * 표시는 +무엇을 의미하나요?</strong> +</p> +<p> +공개되지 않은 문제는 <em>참조</em> 열의 Android 버그 ID 옆에 * 표시가 +있습니다. 일반적으로 이러한 문제에 관한 업데이트는 +<a href="https://developers.google.com/android/drivers" class="external">Google 개발자 사이트</a>에서 제공하는 +Pixel&hairsp;/&hairsp;Nexus +기기용 +최신 바이너리 드라이버에 포함되어 있습니다. +</p> +<p> +<strong>6. 보안 취약성이 이 게시판과 Pixel&hairsp;/&hairsp;Nexus 게시판과 +같은 기기/파트너 보안 게시판에 나뉘어져 있는 이유가 +무엇인가요?</strong> +</p> +<p> +이 보안 게시판에 설명되어 있는 보안 취약성은 +Android 기기의 최신 보안 패치 수준을 선언하는 데 +필요합니다. 기기&hairsp;/&hairsp;파트너 +보안 게시판에 설명된 추가 보안 취약성은 보안 패치 수준을 선언하는 데 +필요하지 않습니다. Android 기기 및 칩셋 제조업체는 <a href="https://security.samsungmobile.com/securityUpdate.smsb" class="external">삼성</a>, <a href="https://lgsecurity.lge.com/security_updates.html" class="external">LGE</a> 또는 +<a href="/security/bulletin/pixel/" class="external">Pixel&hairsp;/&hairsp;Nexus</a> 보안 게시판과 같은 자체 +보안 웹사이트를 통해 기기의 다른 수정사항이 있는지를 +설명하는 것이 좋습니다. +</p> + +<h2 id="versions">버전</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>버전</th> + <th>날짜</th> + <th>참고</th> + </tr> + <tr> + <td>1.0</td> + <td>2018년 8월 6일</td> + <td>게시판이 게시됨</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/ko/security/bulletin/2018.html b/ko/security/bulletin/2018.html index 23ca4ea6..52abd0c8 100644 --- a/ko/security/bulletin/2018.html +++ b/ko/security/bulletin/2018.html @@ -34,6 +34,37 @@ <th>보안 패치 수준</th> </tr> <tr> + <td><a href="/security/bulletin/2018-08-01.html">2018년 8월</a></td> + <td>출시 예정 + <!-- + <a href="/security/bulletin/2018-08-01.html">English</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018년 8월 6일</td> + <td>2018-08-01<br /> + 2018-08-05</td> + </tr> + + <tr> + <td><a href="/security/bulletin/2018-07-01.html">2018년 7월</a></td> + <td> + <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-07-01.html">English</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2018년 7월 2일</td> + <td>2018-07-01<br /> + 2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/2018-06-01.html">2018년 6월</a></td> <td> <a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / diff --git a/ko/security/bulletin/index.html b/ko/security/bulletin/index.html index bf772dc0..3ce32766 100644 --- a/ko/security/bulletin/index.html +++ b/ko/security/bulletin/index.html @@ -67,6 +67,36 @@ <th>보안 패치 수준</th> </tr> <tr> + <td><a href="/security/bulletin/2018-08-01.html">2018년 8월</a></td> + <td>출시 예정 + <!-- + <a href="/security/bulletin/2018-08-01.html">English</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018 8월 6일</td> + <td>2018-08-01<br /> + 2018-08-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/2018-07-01.html">2018년 7월</a></td> + <td> + <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-07-01.html">English</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2018년 7월 2일</td> + <td>2018-07-01<br /> + 2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/2018-06-01.html">2018년 6월</a></td> <td> <a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / @@ -79,7 +109,8 @@ <td>2018년 6월 4일</td> <td>2018-06-01<br /> 2018-06-05</td> - </tr><tr> + </tr> + <tr> <td><a href="/security/bulletin/2018-05-01.html">2018년 5월</a></td> <td> <a href="/security/bulletin/2018-05-01.html?hl=ko">한국어</a> / @@ -541,7 +572,7 @@ <a href="/security/bulletin/2015-08-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2015년 8월 13일</td> - <td>해당 없음</td> + <td>N/A</td> </tr> </tbody></table> diff --git a/ko/security/bulletin/pixel/2018-02-01.html b/ko/security/bulletin/pixel/2018-02-01.html index bdedd51a..fc31839d 100644 --- a/ko/security/bulletin/pixel/2018-02-01.html +++ b/ko/security/bulletin/pixel/2018-02-01.html @@ -47,7 +47,7 @@ Pixel&hairsp;/&hairsp;Nexus 보안 게시판에서는 알림이 전송되었으며, 파트너는 이러한 패치를 기기 업데이트의 일부로 포함하도록 선택할 수 있습니다.</p> -<h2 id="security-patches">보안 패치</h2> +<h2 id="security-patches">보안 업데이트</h2> <p> 취약성은 영향을 받는 구성요소 아래에 분류되어 있습니다. 여기에는 문제 설명 및 CVE, 관련 참조, @@ -55,8 +55,8 @@ Pixel&hairsp;/&hairsp;Nexus 보안 게시판에서는 <a href="https://source.android.com/security/overview/updates-resources.html#severity">심각도</a>, 업데이트된 Android 오픈소스 프로젝트(AOSP) 버전(해당하는 경우)이 포함된 표가 제시됩니다. 가능한 경우 AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 -연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 -추가 참조가 버그 ID 다음에 오는 번호에 연결됩니다. +연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 추가 참조가 +버그 ID 다음에 오는 번호에 연결됩니다. </p> <h3 id="framework">프레임워크</h3> diff --git a/ko/security/bulletin/pixel/2018-03-01.html b/ko/security/bulletin/pixel/2018-03-01.html index 6853cf17..608500a3 100644 --- a/ko/security/bulletin/pixel/2018-03-01.html +++ b/ko/security/bulletin/pixel/2018-03-01.html @@ -52,10 +52,10 @@ Google 기기에는 아래 설명된 보안 취약성과 관련된 패치도 문제 설명 및 CVE, 관련 참조, <a href="#type">취약성 유형</a>, <a href="https://source.android.com/security/overview/updates-resources.html#severity">심각도</a>, -업데이트된 Android 오픈소스 프로젝트(AOSP) 버전(해당하는 경우)이 포함된 표가 제시됩니다. 가능한 -경우 AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 -연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 -추가 참조가 버그 ID 다음에 오는 번호에 연결됩니다. +업데이트된 Android 오픈소스 프로젝트(AOSP) 버전(해당하는 경우)이 포함된 표가 제시됩니다. 가능한 경우 +AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 +연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 추가 참조가 +버그 ID 다음에 오는 번호에 연결됩니다. </p> <h3 id="framework">프레임워크</h3> diff --git a/ko/security/bulletin/pixel/2018-04-01.html b/ko/security/bulletin/pixel/2018-04-01.html index 082d6dd8..b07796fc 100644 --- a/ko/security/bulletin/pixel/2018-04-01.html +++ b/ko/security/bulletin/pixel/2018-04-01.html @@ -1,5 +1,5 @@ <html devsite><head> - <title>Pixel / Nexus 보안 게시판—2018년 4월</title> + <title>Pixel / Nexus Security Bulletin—April 2018</title> <meta name="project_path" value="/_project.yaml"/> <meta name="book_path" value="/_book.yaml"/> </head> @@ -50,9 +50,11 @@ Google 기기에는 아래 설명된 보안 취약성과 관련된 패치도 <h2 id="security-patches">보안 패치</h2> <p> -취약성은 영향을 받는 구성요소 아래에 분류되어 있습니다. 여기에는 문제 설명 및 CVE, -관련 참조, <a href="#type">취약성 유형</a>, <a href="https://source.android.com/security/overview/updates-resources.html#severity">심각도</a>, 업데이트된 Android 오픈소스 프로젝트(AOSP) -버전(해당하는 경우)이 포함된 표가 제시됩니다. 가능한 +취약성은 영향을 받는 구성요소 아래에 분류되어 있습니다. 여기에는 +문제 설명 및 CVE, 관련 참조, +<a href="#type">취약성 유형</a>, +<a href="https://source.android.com/security/overview/updates-resources.html#severity">심각도</a>, +업데이트된 Android 오픈소스 프로젝트(AOSP) 버전(해당하는 경우)이 포함된 표가 제시됩니다. 가능한 경우 AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 추가 참조가 버그 ID 다음에 오는 번호에 연결됩니다. @@ -523,9 +525,10 @@ QC-CR#2098332</a></td> <h2 id="functional-updates">기능 업데이트</h2> <p> -다음 업데이트는 영향을 받은 Pixel 기기에서 Pixel 기기의 보안과 관련되지 않은 기능 문제를 해결하기 위해 포함되었습니다. 표에는 -관련 참조, 블루투스나 모바일 데이터 등 영향을 받은 카테고리, -개선 사항, 영향을 받은 기기 등을 포함하고 있습니다. +다음 업데이트는 영향을 받은 Pixel 기기에서 Pixel 기기의 보안과 관련되지 않은 +기능 문제를 해결하기 위해 포함되었습니다. 표에는 관련 참조, +블루투스나 모바일 데이터 등 영향을 받은 카테고리, 문제 요약이 +포함되어 있습니다. </p> <table> @@ -905,9 +908,9 @@ QC-CR#2098332</a></td> </p> <p> 2018-04-05 보안 패치 수준 및 그 이전의 모든 패치 수준과 관련된 -모든 문제는 2018-04-05 보안 패치 수준 이상에서 해결되었습니다. 기기의 보안 패치 수준을 확인하는 -방법을 -알아보려면 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel 및 Nexus 업데이트 일정</a>의 +문제는 2018-04-05 보안 패치 수준 이상에서 모두 해결됩니다. 기기의 +보안 패치 수준을 확인하는 방법을 알아보려면 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel 및 Nexus 업데이트 +일정</a>의 안내를 참조하세요. </p> <p id="type"> @@ -941,7 +944,7 @@ QC-CR#2098332</a></td> <td>서비스 거부</td> </tr> <tr> - <td>N/A</td> + <td>해당 없음</td> <td>분류 없음</td> </tr> </tbody></table> @@ -1010,7 +1013,7 @@ Android 기기의 최신 보안 패치 수준을 선언하는 데 </colgroup><tbody><tr> <th>버전</th> <th>날짜</th> - <th>참고사항</th> + <th>참고</th> </tr> <tr> <td>1.0</td> diff --git a/ko/security/bulletin/pixel/2018-05-01.html b/ko/security/bulletin/pixel/2018-05-01.html index 2563d380..2237a02c 100644 --- a/ko/security/bulletin/pixel/2018-05-01.html +++ b/ko/security/bulletin/pixel/2018-05-01.html @@ -47,16 +47,16 @@ Pixel 및 Nexus 기기에는 아래 설명된 보안 취약성과 관련된 패치도 포함되어 있습니다. 파트너에게는 적어도 1개월 전에 이러한 문제와 관련해 알림이 전송되었으며 이러한 패치를 기기 업데이트의 일부로 포함하도록 선택할 수 있습니다.</p> -<h2 id="security-patches">보안 패치</h2> +<h2 id="security-patches">보안 업데이트</h2> <p> 취약성은 영향을 받는 구성요소 아래에 분류되어 있습니다. 여기에는 문제 설명 및 CVE, 관련 참조, <a href="#type">취약성 유형</a>, <a href="https://source.android.com/security/overview/updates-resources.html#severity">심각도</a>, -업데이트된 Android 오픈소스 프로젝트(AOSP) 버전(해당하는 경우)이 포함된 표가 제시됩니다. 가능한 -경우 AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 -연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 -추가 참조가 버그 ID 다음에 오는 번호에 연결됩니다. +업데이트된 Android 오픈소스 프로젝트(AOSP) 버전(해당하는 경우)이 포함된 표가 제시됩니다. 가능한 경우 +AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 +연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 추가 참조가 +버그 ID 다음에 오는 번호에 연결됩니다. </p> <h3 id="framework">프레임워크</h3> diff --git a/ko/security/bulletin/pixel/2018-06-01.html b/ko/security/bulletin/pixel/2018-06-01.html index d1a0a48e..0474d209 100644 --- a/ko/security/bulletin/pixel/2018-06-01.html +++ b/ko/security/bulletin/pixel/2018-06-01.html @@ -826,11 +826,11 @@ A-74058011</td> <td>원격 코드 실행</td> </tr> <tr> - <td>EoP </td> + <td>EoP</td> <td>권한 승격</td> </tr> <tr> - <td>ID </td> + <td>ID</td> <td>정보 공개</td> </tr> <tr> @@ -838,7 +838,7 @@ A-74058011</td> <td>서비스 거부</td> </tr> <tr> - <td>해당 없음</td> + <td>N/A</td> <td>분류 없음</td> </tr> </tbody></table> diff --git a/ko/security/bulletin/pixel/2018-07-01.html b/ko/security/bulletin/pixel/2018-07-01.html index 98aa4ada..483270a9 100644 --- a/ko/security/bulletin/pixel/2018-07-01.html +++ b/ko/security/bulletin/pixel/2018-07-01.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p><em>2018년 7월 2일에 게시됨</em></p> +<p><em>2018년 7월 2일에 게시됨 | 2018년 7월 3일에 업데이트됨</em></p> <p> Pixel&hairsp;/&hairsp;Nexus 보안 게시판에서는 @@ -78,21 +78,22 @@ Pixel 및 Nexus 기기에는 아래 설명된 보안 취약성과 관련된 </tr> <tr> <td>CVE-2018-9426</td> - <td>A-79148652</td> + <td><a href="https://android.googlesource.com/platform/external/bouncycastle/+/129a20459ea828c1b05f0d5da57f69a2a3212ad7">A-79148652</a></td> <td>ID</td> <td>보통</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9376</td> - <td>A-69981755</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/e6655cb8a78b757e9329b8200a90746ffac3a5a9">A-69981755</a></td> <td>EoP</td> <td>보통</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9434</td> - <td>A-29833520</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/ab1fb955acc8bbe6b9086a4ab54beab003a887a9">A-29833520</a> +[<a href="https://android.googlesource.com/platform/frameworks/native/+/c4b7338b1a0995222d229a6f794db02c974ba0d8">2</a>]</td> <td>ID</td> <td>보통</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -116,14 +117,14 @@ Pixel 및 Nexus 기기에는 아래 설명된 보안 취약성과 관련된 </tr> <tr> <td>CVE-2018-9429</td> - <td>A-73927042</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/7306d8b37c00729dc41d663a4b244a00209d537b">A-73927042</a></td> <td>ID</td> <td>보통</td> <td>8.1</td> </tr> <tr> <td>CVE-2018-9423</td> - <td>A-77599438</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/e46e5994a80c31f6533384f0f325555f3a87bee3">A-77599438</a></td> <td>ID</td> <td>보통</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -147,35 +148,35 @@ Pixel 및 Nexus 기기에는 아래 설명된 보안 취약성과 관련된 </tr> <tr> <td>CVE-2018-9413</td> - <td>A-73782082</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/97eb2f9cfba4f38d64dffa0558f1c4c3aa91b4f8">A-73782082</a></td> <td>RCE</td> <td>보통</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9418</td> - <td>A-73824150</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/8e702ed3539caac44a616243e33aaad1b2b4801f">A-73824150</a></td> <td>RCE</td> <td>보통</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9430</td> - <td>A-73963551</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/605ebb3369b3f961196815065a9fe4ba5bc4d659">A-73963551</a></td> <td>RCE</td> <td>보통</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9414</td> - <td>A-78787521</td> + <td><a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/98ff9fe7db5a25fa2c772a85f0b9baa3545228bf">A-78787521</a></td> <td>EoP</td> <td>보통</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9431</td> - <td>A-77600924</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/5c23facbf802c9b4c88ceb60e1b782abcc55ddc9">A-77600924</a></td> <td>EoP</td> <td>보통</td> <td>8.0, 8.1</td> @@ -208,7 +209,7 @@ Pixel 및 Nexus 기기에는 아래 설명된 보안 취약성과 관련된 <tr> <td>CVE-2018-9415</td> <td>A-69129004<br /> - <a href="https://patchwork.kernel.org/patch/9946759/">업스트림 커널</a></td> + <a href="https://patchwork.kernel.org/patch/10175615/">업스트림 커널</a></td> <td>EoP</td> <td>보통</td> <td>AMBA 드라이버</td> @@ -352,8 +353,7 @@ Pixel 및 Nexus 기기에는 아래 설명된 보안 취약성과 관련된 <h2 id="functional-patches">기능 패치</h2> <p> -다음 업데이트는 영향을 받은 Pixel 기기에서 Pixel 기기의 보안과 관련되지 않은 -기능 문제를 해결하기 위해 포함되었습니다. 표에는 관련 참조, +다음 업데이트는 영향을 받은 Pixel 기기에서 Pixel 기기의 보안과 관련되지 않은 기능 문제를 해결하기 위해 포함되었습니다. 표에는 관련 참조, 블루투스나 모바일 데이터 등 영향을 받은 카테고리, 문제 요약이 포함되어 있습니다. </p> @@ -494,6 +494,11 @@ Android 기기의 최신 보안 패치 수준을 선언하는 데 <td>2018년 7월 2일</td> <td>게시판이 게시됨</td> </tr> + <tr> + <td>1.1</td> + <td>2018년 7월 3일</td> + <td>게시판이 수정되어 AOSP 링크 포함됨</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ko/security/bulletin/pixel/2018-08-01.html b/ko/security/bulletin/pixel/2018-08-01.html new file mode 100644 index 00000000..d398cc5a --- /dev/null +++ b/ko/security/bulletin/pixel/2018-08-01.html @@ -0,0 +1,553 @@ +<html devsite><head> + <title>Pixel / Nexus 보안 게시판—2018년 8월</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + +<p><em>2018년 8월 6일 게시됨</em></p> + +<p> +Pixel&hairsp;/&hairsp;Nexus 보안 게시판에서는 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">지원되는 +Google Pixel 및 Nexus 기기</a>(Google 기기)에 영향을 미치는 +보안 취약성 및 기능 개선을 자세히 다룹니다. +Google 기기의 경우 2018-08-05 보안 패치 수준 이상에서 이 게시판에 언급된 모든 문제와 +2018년 8월 Android 보안 게시판의 모든 문제를 +해결했습니다. 기기의 보안 패치 수준을 확인하는 방법은 <a href="https://support.google.com/pixelphone/answer/4457705" class="external">Android 버전 확인 및 업데이트</a>를 참조하세요. +</p> +<p> +지원되는 모든 Google 기기는 2018-08-05 패치 수준으로 +업데이트됩니다. 모든 고객은 기기에서 이 업데이트를 수락하는 것이 좋습니다. +</p> +<p class="note"> +<strong>참고:</strong> Google 기기 펌웨어 이미지는 <a href="https://developers.google.com/android/images" class="external">Google 개발자 사이트</a> +에 있습니다. +</p> + +<h2 id="announcements">공지사항</h2> +<p>2018년 8월 Android 보안 게시판 +에 설명된 보안 취약성 외에도 +Google 기기에는 아래 설명된 보안 취약성과 관련된 패치도 포함되어 있습니다. 파트너에게는 적어도 1개월 전에 이러한 문제와 관련해 +알림이 전송되었으며 이러한 패치를 기기 업데이트의 일부로 포함하도록 선택할 수 +있습니다.</p> + +<h2 id="security-patches">보안 패치</h2> +<p> +취약성은 영향을 받는 구성요소 아래에 분류되어 있습니다. 여기에는 +문제 설명 및 CVE, 관련 참조, +<a href="#type">취약성 유형</a>, +<a href="/security/overview/updates-resources.html#severity">심각도</a>, +업데이트된 AOSP 버전(해당하는 경우)이 포함된 표가 제시됩니다. +가능한 경우 AOSP 변경사항 목록과 같이 문제를 해결한 공개 변경사항을 버그 ID에 +연결합니다. 하나의 버그와 관련된 변경사항이 여러 개인 경우 +추가 참조가 버그 ID 다음에 오는 번호에 연결됩니다. +</p> + +<h3 id="framework">프레임워크</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>업데이트된 AOSP 버전</th> + </tr> + <tr> + <td>CVE-2017-1000100</td> + <td> +<a href="https://android.googlesource.com/platform/external/curl/+/1506c0316973bd95d7832891b1aa2258b52a793d">A-64610131</a> +</td> + <td>ID</td> + <td>보통</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="system">시스템</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>업데이트된 AOSP 버전</th> + </tr> + <tr> + <td>CVE-2018-9435</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/51b05b715024adff4fa59ab2e18c0b56c5d3af5e">A-79591688</a> +</td> + <td>ID</td> + <td>보통</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9461</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Messaging/+/17a2579a0aa603a3a7d94e5dc64afeb96e430e8f">A-37629504</a> +</td> + <td>ID</td> + <td>보통</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9449</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/27b90f4f6fe3811335e9bb4fac4656bc1df49204">A-79884292</a> +</td> + <td>ID</td> + <td>보통</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9457</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Settings/+/a3e94449c8fe0a377b61747b6129fafc930da086">A-72872376</a> +</td> + <td>ID</td> + <td>보통</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9441</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/c3c69bed0f76178c640dd8e726967b9cdea5dece">A-74075873</a> +[<a href="https://android.googlesource.com/platform/system/bt/+/3a2799939b2da543ed3a62f29db658cb05f8ad3b">2</a>] +</td> + <td>ID</td> + <td>보통</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13322</td> + <td> +<a href="https://android.googlesource.com/platform/packages/services/Telephony/+/c25745addd19b1549b7ec5bdc46d8bf1a1de37ed">A-67862398</a> +</td> + <td>DoS</td> + <td>보통</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9447</td> + <td> +<a href="https://android.googlesource.com/platform/packages/services/Telephony/+/19c48992b79df89c730f3619eb69baf03d449e95">A-79995313</a> +</td> + <td>DoS</td> + <td>보통</td> + <td>6.0, 6.0.1, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="kernel-components">커널 구성요소</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2018-9462</td> + <td>A-78364203<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>보통</td> + <td>터치 스크린</td> + </tr> + <tr> + <td>CVE-2018-9439</td> + <td>A-79377438<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>보통</td> + <td>네트워크 스택</td> + </tr> + <tr> + <td>CVE-2018-9463</td> + <td>A-78362414<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>보통</td> + <td>터치 스크린</td> + </tr> + <tr> + <td>CVE-2018-1068</td> + <td>A-77902350<br /> + <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b71812168571fa55e44cdd0254471331b9c4c4c6"> +업스트림 커널</a></td> + <td>EoP </td> + <td>보통</td> + <td>넷필터</td> + </tr> + <tr> + <td>CVE-2018-9464</td> + <td>A-68993267<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>보통</td> + <td>Taimen 부트로더</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Qualcomm 구성요소</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2018-11263</td> + <td>A-79422278<a href="#asterisk">*</a><br /> + QC-CR#2209106</td> + <td>EoP</td> + <td>보통</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-8261</td> + <td>A-35139833<a href="#asterisk">*</a><br /> + QC-CR#2013631</td> + <td>EoP</td> + <td>보통</td> + <td>카메라 드라이버</td> + </tr> + <tr> + <td>CVE-2018-5910</td> + <td>A-79422277<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=b67e04e3696f05411b7434c8b194895d273b00c5"> +QC-CR#2175499</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=d9344c2f4b60cf5d4c747c11f3cb0b6f1558db78">2</a>] +</td> + <td>EoP</td> + <td>보통</td> + <td>MDSS</td> + </tr> + <tr> + <td>CVE-2018-5909</td> + <td>A-79421262<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=2c1716c5afd660651724b6088f2e6301272f4926"> +QC-CR#2174716</a></td> + <td>EoP</td> + <td>보통</td> + <td>로테이터</td> + </tr> + <tr> + <td>CVE-2018-5908</td> + <td>A-79422409<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=28e5918c60b832091c6b3618747258803cbd3302"> +QC-CR#2171758</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=4689d03e5db548d263232c274bf307956207da27">2</a>] +</td> + <td>EoP</td> + <td>보통</td> + <td>MDSS</td> + </tr> + <tr> + <td>CVE-2018-5905</td> + <td>A-79421261<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=6eb2f4f6fde1b210712d6ac66b40b9e7684d77db"> +QC-CR#2169715</a></td> + <td>EoP</td> + <td>보통</td> + <td>Diag 드라이버</td> + </tr> + <tr> + <td>CVE-2018-5904</td> + <td>A-79421260<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=88b838c8952ec6414c72449ae15768d15d2606dd"> +QC-CR#2184702</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.9/commit/?id=8e82c0d84ccee87309fd22f8208915f0ba502b26">2</a>] +</td> + <td>EoP</td> + <td>보통</td> + <td>전원 드라이버</td> + </tr> + <tr> + <td>CVE-2018-5903</td> + <td>A-79421737<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=20365fa599f42f6e1f175d9d5d60d964927c2160"> +QC-CR#2185477</a></td> + <td>EoP</td> + <td>보통</td> + <td>qcacld 3.0</td> + </tr> + <tr> + <td>CVE-2017-18306</td> + <td>A-73889358<a href="#asterisk">*</a><br /> + QC-CR#2216399</td> + <td>ID</td> + <td>보통</td> + <td>v4l2</td> + </tr> + <tr> + <td>CVE-2017-18307</td> + <td>A-73888283<a href="#asterisk">*</a><br /> + QC-CR#2026045</td> + <td>ID</td> + <td>보통</td> + <td>qcacld-3.0</td> + </tr> + <tr> + <td>CVE-2017-9711</td> + <td>A-36367253<a href="#asterisk">*</a><br /> + QC-CR#2046006</td> + <td>EoP</td> + <td>보통</td> + <td>IPA</td> + </tr> + <tr> + <td>CVE-2018-3587</td> + <td>A-65542521<a href="#asterisk">*</a><br /> + QC-CR#2120605</td> + <td>EoP</td> + <td>보통</td> + <td>qcacld-2.0</td> + </tr> +</tbody></table> + +<h3 id="update:-framework">업데이트: 프레임워크</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>업데이트된 AOSP 버전</th> + </tr> + <tr> + <td>CVE-2017-13295</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/da24aa45a8b65a7b9adbe12ff94bf891bdd38825">A-62537081</a> +[<a href="https://android.googlesource.com/platform/packages/apps/PackageInstaller/+/3af01bd93513d902dbb5382b10109fdf3ab29d2d">2</a>] +</td> + <td>DoS</td> + <td>보통</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="update:-system">업데이트: 시스템</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>업데이트된 AOSP 버전</th> + </tr> + <tr> + <td>CVE-2017-13242</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Settings/+/f973e707f50adc0c21599e719be06714f808a333">A-62672248</a> +</td> + <td>ID</td> + <td>보통</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="update:-qualcomm-components">업데이트: Qualcomm 구성요소</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>참조</th> + <th>유형</th> + <th>심각도</th> + <th>구성요소</th> + </tr> + <tr> + <td>CVE-2017-15817</td> + <td>A-68992394<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=fe43c2b64ac81199de17efc258e95546cb0546f1">QC-CR#2076603</a> +[<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=8ba78e506e5002cdae525dd544dbf1df0ccce1ef">2</a>] +<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=343a3f28338788c5c91289f53171c1f71f293cd7">QC-CR#2084599</a> +<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=0c21aaa2fefa6c5919813fdd287436dddda54227">QC-CR#2096512</a> +</td> + <td>RCE</td> + <td>심각</td> + <td>WLAN</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">일반적인 질문 및 답변</h2> +<p> +이 섹션에서는 게시판을 읽은 뒤 제기될 수 있는 일반적인 질문의 답변을 +제시합니다. +</p> +<p> +<strong>1. 내 기기가 업데이트되어 이 문제가 해결되었는지 어떻게 알 수 있나요? +</strong> +</p> +<p> +2018-08-05 보안 패치 수준 및 그 이전의 모든 패치 수준과 관련된 +문제는 2018-08-05 보안 패치 수준 이상에서 모두 해결됩니다. 기기의 +보안 패치 수준을 확인하는 방법을 알아보려면 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">Pixel 및 Nexus 업데이트 일정</a>의 안내를 참조하세요. +</p> +<p id="type"> +<strong>2. <em>유형</em> 열의 항목은 무엇을 의미하나요?</strong> +</p> +<p> +취약성 세부정보 표의 <em>유형</em> 열에 있는 항목은 +보안 취약성 분류를 참조합니다. +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>약어</th> + <th>정의</th> + </tr> + <tr> + <td>RCE</td> + <td>원격 코드 실행</td> + </tr> + <tr> + <td>EoP </td> + <td>권한 승격</td> + </tr> + <tr> + <td>ID </td> + <td>정보 공개</td> + </tr> + <tr> + <td>DoS</td> + <td>서비스 거부</td> + </tr> + <tr> + <td>N/A</td> + <td>분류 없음</td> + </tr> +</tbody></table> +<p> +<strong>3. <em>참조</em> 열의 항목은 무엇을 의미하나요?</strong> +</p> +<p> +취약성 세부정보 표의 <em>참조</em> 열에 있는 항목은 +참조 값이 속한 조직을 나타내는 접두어를 포함할 수 +있습니다. +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>접두어</th> + <th>참조</th> + </tr> + <tr> + <td>A-</td> + <td>Android 버그 ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm 참조 번호</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek 참조 번호</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA 참조 번호</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom 참조 번호</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>4. <em>참조</em> 열에서 Android 버그 ID 옆에 있는 * 표시는 +무엇을 의미하나요?</strong> +</p> +<p> +공개되지 않은 문제는 <em>참조</em> 열의 Android 버그 ID 옆에 * 표시가 +있습니다. 일반적으로 이러한 문제에 관한 업데이트는 <a href="https://developers.google.com/android/nexus/drivers" class="external">Google +개발자 사이트</a>에서 제공되는 Pixel / Nexus 기기용 최신 바이너리 +드라이버에 포함되어 있습니다. +</p> +<p> +<strong>5 보안 취약성이 이 게시판과 Android 보안 게시판에 나뉘어져 있는 이유가 +무엇인가요?</strong> +</p> +<p> +Android 보안 게시판에 설명되어 있는 보안 취약성은 +Android 기기의 최신 보안 패치 수준을 선언하는 데 +필요합니다. 이 게시판에 설명된 것과 같은 추가적인 보안 취약성은 +보안 패치 수준을 선언하는 데 필요하지 않습니다. +</p> +<h2 id="versions">버전</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>버전</th> + <th>날짜</th> + <th>참고</th> + </tr> + <tr> + <td>1.0</td> + <td>2018년 8월 6일</td> + <td>게시판이 게시됨</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/ko/security/bulletin/pixel/2018.html b/ko/security/bulletin/pixel/2018.html index 82161c39..a82aff75 100644 --- a/ko/security/bulletin/pixel/2018.html +++ b/ko/security/bulletin/pixel/2018.html @@ -37,6 +37,34 @@ <th>보안 패치 수준</th> </tr> <tr> + <td><a href="/security/bulletin/pixel/2018-08-01.html">2018년 8월</a></td> + <td>출시 예정 + <!-- + <a href="/security/bulletin/pixel/2018-08-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018년 8월 6일</td> + <td>2018-08-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-07-01.html">2018년 7월</a></td> + <td> + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2018년 7월 2일</td> + <td>2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-06-01.html">2018년 6월</a></td> <td> <a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / @@ -82,9 +110,7 @@ <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">ру́сский</a> / - <!-- - <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / - --> + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2018년 3월</td> diff --git a/ko/security/bulletin/pixel/index.html b/ko/security/bulletin/pixel/index.html index c7cee488..2b60f0b3 100644 --- a/ko/security/bulletin/pixel/index.html +++ b/ko/security/bulletin/pixel/index.html @@ -57,6 +57,34 @@ Pixel&hairsp;/&hairsp;Nexus 게시판이 게시된 후 24~48시간 내 <th>보안 패치 수준</th> </tr> <tr> + <td><a href="/security/bulletin/pixel/2018-08-01.html">2018년 8월</a></td> + <td>출시 예정 + <!-- + <a href="/security/bulletin/pixel/2018-08-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018년 8월 6일</td> + <td>2018-08-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-07-01.html">2018년 7월</a></td> + <td> + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2018년 7월 2일</td> + <td>2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-06-01.html">2018년 6월</a></td> <td> <a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / diff --git a/ru/security/bulletin/2018-01-01.html b/ru/security/bulletin/2018-01-01.html index 77626d9d..2800179c 100644 --- a/ru/security/bulletin/2018-01-01.html +++ b/ru/security/bulletin/2018-01-01.html @@ -50,7 +50,7 @@ </p> <h2 id="mitigations">Предотвращение атак</h2> <p> -Ниже рассказывается, как <a href="/security/enhancements/index.html">платформа безопасности</a> и средства защиты сервисов, например <a href="https://www.android.com/play-protect">Google Play Защита</a>, позволяют снизить вероятность атак на Android. +Ниже рассказано, как <a href="/security/enhancements/index.html">платформа безопасности</a> и средства защиты сервисов, например <a href="https://www.android.com/play-protect">Google Play Защита</a>, позволяют снизить вероятность атак на Android. </p><ul> <li>В новых версиях Android сложнее использовать многие уязвимости, поэтому мы рекомендуем всем пользователям своевременно обновлять систему. </li><li>Команда, отвечающая за безопасность Android, активно отслеживает злоупотребления с помощью <a href="https://www.android.com/play-protect">Google Play Защиты</a> и предупреждает пользователей об установке <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">потенциально опасных приложений</a>. Google Play Защита включена по умолчанию на всех устройствах с <a href="http://www.android.com/gms">сервисами Google для мобильных устройств</a>. Она особенно важна, если пользователь устанавливает ПО из сторонних источников.</li></ul> @@ -249,7 +249,10 @@ </tr> <tr> <td>CVE-2017-13209</td> - <td><a href="https://android.googlesource.com/platform/system/libhidl/+/a4d0252ab5b6f6cc52a221538e1536c5b55c1fa7">A-68217907</a> [<a href="https://android.googlesource.com/platform/system/tools/hidl/+/8539fc8ac94d5c92ef9df33675844ab294f68d61">2</a>] [<a href="https://android.googlesource.com/platform/system/hwservicemanager/+/e1b4a889e8b84f5c13b76333d4de90dbe102a0de">3</a>]</td> + <td><a href="https://android.googlesource.com/platform/system/libhidl/+/a4d0252ab5b6f6cc52a221538e1536c5b55c1fa7"> + A-68217907</a> +[<a href="https://android.googlesource.com/platform/system/tools/hidl/+/8539fc8ac94d5c92ef9df33675844ab294f68d61">2</a>] +[<a href="https://android.googlesource.com/platform/system/hwservicemanager/+/e1b4a889e8b84f5c13b76333d4de90dbe102a0de">3</a>]</td> <td>ПП</td> <td>Высокий</td> <td>8.0, 8.1</td> @@ -646,7 +649,7 @@ QC-CR#2060780</a></td> <p> В этом бюллетене описаны уязвимости, которые были устранены в последнем обновлении системы безопасности для устройств Android. Решать дополнительные проблемы, перечисленные в бюллетенях по безопасности партнеров, для этого не потребовалось. -Мы рекомендуем производителям чипсетов и устройств Android рассказывать об исправлениях для своих устройств в бюллетенях по безопасности на собственных сайтах, например <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, а также <a href="/security/bulletin/pixel/">Pixel и Nexus</a>. +Мы рекомендуем производителям чипсетов и устройств Android рассказывать об исправлениях для своих устройств в бюллетенях по безопасности на собственных сайтах. Примеры таких бюллетеней: <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, <a href="/security/bulletin/pixel/">Pixel и Nexus</a>. </p> <h2 id="versions">Версии</h2> <table> diff --git a/ru/security/bulletin/2018-02-01.html b/ru/security/bulletin/2018-02-01.html index a5be4b68..51d5de93 100644 --- a/ru/security/bulletin/2018-02-01.html +++ b/ru/security/bulletin/2018-02-01.html @@ -370,7 +370,7 @@ QC-CR#2114187</a></td> </tbody></table> <h3 id="qualcomm-closed-source-components">Компоненты Qualcomm с закрытым исходным кодом</h3> -<p>Эти уязвимости затрагивают компоненты Qualcomm и описаны в бюллетенях по безопасности Qualcomm AMSS или оповещениях системы безопасности. Уровень серьезности этих уязвимостей определяется непосредственно компанией Qualcomm.</p> +<p>Эти уязвимости затрагивают компоненты Qualcomm. Они описаны в бюллетенях по безопасности Qualcomm AMSS и оповещениях системы безопасности. Уровень серьезности этих уязвимостей определяется непосредственно компанией Qualcomm.</p> <table> <colgroup><col width="17%" /> @@ -534,7 +534,7 @@ QC-CR#2114187</a></td> <tr> <td>1.3</td> <td>2 апреля 2018 г.</td> - <td>Уязвимость CVE-2017-15817 перемещена из этого бюллетеня в бюллетень по безопасности Pixel и Nexus за февраль.</td> + <td>Сведения об уязвимости CVE-2017-15817 перенесены из этого бюллетеня в бюллетень по безопасности Pixel и Nexus за февраль.</td> </tr> </tbody></table> diff --git a/ru/security/bulletin/2018-03-01.html b/ru/security/bulletin/2018-03-01.html index 6369f314..e278b38e 100644 --- a/ru/security/bulletin/2018-03-01.html +++ b/ru/security/bulletin/2018-03-01.html @@ -32,7 +32,7 @@ Самая серьезная из проблем – критическая уязвимость в Media Framework, которая позволяет злоумышленнику выполнять произвольный код в контексте привилегированного процесса с помощью специально созданного файла. <a href="/security/overview/updates-resources.html#severity">Уровень серьезности</a> зависит от того, какой ущерб будет нанесен устройству при атаке с использованием уязвимости, если средства защиты будут отключены разработчиком или взломаны. </p> <p> -У нас нет информации о том, что обнаруженные уязвимости эксплуатировались. В разделе <a href="#mitigations">Предотвращение атак</a> рассказывается, как <a href="/security/enhancements/index.html">платформа безопасности</a> и Google Play Защита помогают снизить вероятность атак на Android. +У нас нет информации о том, что обнаруженные уязвимости эксплуатировались. В разделе <a href="#mitigations">Предотвращение атак</a> рассказано о том, как <a href="/security/enhancements/index.html">платформа безопасности</a> и Google Play Защита помогают снизить вероятность атак на Android. </p> <p class="note"> <strong>Примечание.</strong> Информация о последних автоматических обновлениях (OTA) и образах встроенного ПО для устройств Google содержится в <a href="/security/bulletin/pixel/2018-03-01.html">бюллетене по безопасности Pixel и Nexus</a> за март 2018 года. @@ -40,7 +40,7 @@ <h2 id="mitigations">Предотвращение атак</h2> <p> -Ниже рассказывается, как <a href="/security/enhancements/index.html">платформа безопасности</a> и средства защиты сервисов, например <a href="https://www.android.com/play-protect">Google Play Защита</a>, +Ниже рассказано о том, как <a href="/security/enhancements/index.html">платформа безопасности</a> и средства защиты сервисов, например <a href="https://www.android.com/play-protect">Google Play Защита</a>, позволяют снизить вероятность атак на Android. </p> <ul> @@ -157,7 +157,9 @@ </tr> <tr> <td>CVE-2017-13272</td> - <td><a href="https://android.googlesource.com/platform/system/bt/+/935ee775421e0c8a14f26669d9ab99f110ceb7d5">A-67110137</a> [<a href="https://android.googlesource.com/platform/system/bt/+/ec16f7d8c7e359a68ffe6b76e88add2210bf2cbd">2</a>]</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/935ee775421e0c8a14f26669d9ab99f110ceb7d5"> + A-67110137</a> + [<a href="https://android.googlesource.com/platform/system/bt/+/ec16f7d8c7e359a68ffe6b76e88add2210bf2cbd">2</a>]</td> <td>УВК</td> <td>Критический</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -191,7 +193,9 @@ </tr> <tr> <td>CVE-2017-13259</td> - <td><a href="https://android.googlesource.com/platform/system/bt/+/0627e76edefd948dc3efe11564d7e53d56aac80c">A-68161546</a> [<a href="https://android.googlesource.com/platform/system/bt/+/1313abd1761c39e8619a77964f8c42e3e72b5fee">2</a>] + <td><a href="https://android.googlesource.com/platform/system/bt/+/0627e76edefd948dc3efe11564d7e53d56aac80c"> + A-68161546</a> + [<a href="https://android.googlesource.com/platform/system/bt/+/1313abd1761c39e8619a77964f8c42e3e72b5fee">2</a>] </td> <td>РИ</td> <td>Высокий</td> @@ -356,7 +360,9 @@ Upstream kernel</a></td> <tr> <td>CVE-2017-18067</td> <td>A-68992411<br /> - <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=e1e9d0cb8a0bc33965d112725e205a78aab82986">QC-CR#2081734</a> [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=4201fc6c8c7eb7dddcfb7f06b5f1012d7c5cf451">2</a>]</td> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=e1e9d0cb8a0bc33965d112725e205a78aab82986"> +QC-CR#2081734</a> + [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=4201fc6c8c7eb7dddcfb7f06b5f1012d7c5cf451">2</a>]</td> <td>УВК</td> <td>Критический</td> <td>Драйвер адаптера беспроводной сети</td> @@ -444,7 +450,10 @@ QC-CR#2101439</a></td> <tr> <td>CVE-2017-14878</td> <td>A-70237706<br /> - <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=27f1c544d6737bcb3dc4bb114badcd47ce946a8b">QC-CR#2064580</a> [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=2167cc91261a50bf145467f4d03c8730a0d23709">2</a>] [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=8952decf05939fad1cba625290ee7ae2ed528e12">3</a>]</td> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=27f1c544d6737bcb3dc4bb114badcd47ce946a8b"> + QC-CR#2064580</a> + [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=2167cc91261a50bf145467f4d03c8730a0d23709">2</a>] + [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=8952decf05939fad1cba625290ee7ae2ed528e12">3</a>]</td> <td>ОО</td> <td>Высокий</td> <td>Драйвер адаптера беспроводной сети</td> @@ -592,7 +601,7 @@ QC-CR#2101439</a></td> </p> <p> В этом бюллетене описаны уязвимости, которые были устранены в последнем обновлении системы безопасности для устройств Android. -Решать дополнительные проблемы, перечисленные в бюллетенях по безопасности партнеров, для этого не потребовалось. Мы рекомендуем производителям чипсетов и устройств Android рассказывать о внесенных ими исправлениях в бюллетенях по безопасности на собственных сайтах, например <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, а также <a href="/security/bulletin/pixel/">Pixel и Nexus</a>. +Решать дополнительные проблемы, перечисленные в бюллетенях по безопасности партнеров, для этого не потребовалось. Мы рекомендуем производителям чипсетов и устройств Android рассказывать об исправлениях для своих устройств в бюллетенях по безопасности на собственных сайтах, например <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, а также <a href="/security/bulletin/pixel/">Pixel и Nexus</a>. </p> <h2 id="versions">Версии</h2> <table> diff --git a/ru/security/bulletin/2018-04-01.html b/ru/security/bulletin/2018-04-01.html index 24414dec..785bd7fe 100644 --- a/ru/security/bulletin/2018-04-01.html +++ b/ru/security/bulletin/2018-04-01.html @@ -26,7 +26,7 @@ </p> <p> Мы сообщили партнерам обо всех проблемах по крайней мере за месяц до выхода бюллетеня. -Исправления уязвимостей доступны в хранилище Android Open Source Project (AOSP). В этом бюллетене также приведены ссылки на исправления вне AOSP. +Исправления уязвимостей доступны в хранилище Android Open Source Project (AOSP). В бюллетене также приведены ссылки на исправления вне AOSP. </p> <p> Самая серьезная из проблем – критическая уязвимость в Media Framework, которая позволяет злоумышленнику выполнять произвольный код в контексте привилегированного процесса с помощью специально созданного файла. <a href="/security/overview/updates-resources.html#severity">Уровень серьезности</a> зависит от того, какой ущерб будет нанесен устройству при атаке с использованием уязвимости, если средства защиты будут отключены разработчиком или взломаны. @@ -388,7 +388,7 @@ QC-CR#2129237</a></td> </tbody></table> <h3 id="qualcomm-closed-source-components">Компоненты Qualcomm с закрытым исходным кодом</h3> -<p>Эти уязвимости затрагивают компоненты Qualcomm и описаны в бюллетенях по безопасности Qualcomm AMSS или оповещениях системы безопасности. Уровень серьезности этих уязвимостей определяется непосредственно компанией Qualcomm.</p> +<p>Эти уязвимости затрагивают компоненты Qualcomm. Они описаны в бюллетенях по безопасности Qualcomm AMSS и оповещениях системы безопасности. Уровень серьезности этих уязвимостей определяется непосредственно компанией Qualcomm.</p> <table> <colgroup><col width="17%" /> @@ -673,7 +673,7 @@ QC-CR#2129237</a></td> </tr> </tbody></table> -<h3 id="qualcomm-closed-source-components-2014-2016-cumulative-update">Сводный список уязвимостей, найденных в закрытых компонентах Qualcomm за 2014–2016 годы</h3> +<h3 id="qualcomm-closed-source-components-2014-2016-cumulative-update">Сводный список уязвимостей, найденных в компонентах Qualcomm с закрытым исходным кодом за 2014–2016 годы</h3> <p>Эти уязвимости затрагивают компоненты Qualcomm. Они описаны в оповещениях системы безопасности и бюллетенях по безопасности Qualcomm AMSS за 2014–2016 годы. Уязвимости включены в этот бюллетень по безопасности Android, чтобы связать их с обновлением системы безопасности (на многих устройствах Android они уже были исправлены ранее). Уровень серьезности уязвимостей определяется непосредственно компанией Qualcomm.</p> <table> diff --git a/ru/security/bulletin/2018-05-01.html b/ru/security/bulletin/2018-05-01.html index 5444bcb9..ee271828 100644 --- a/ru/security/bulletin/2018-05-01.html +++ b/ru/security/bulletin/2018-05-01.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p><em>Опубликовано 7 мая 2018 г. | Обновлено 9 мая 2018 г.</em></p> +<p><em>Опубликовано 7 мая 2018 г. | Обновлено 11 июля 2018 г.</em></p> <p> В этом бюллетене содержится информация об уязвимостях в защите устройств Android. Все актуальные проблемы, перечисленные здесь, устранены в исправлении от 5 мая 2018 года или более новом. Информацию о том, как проверить обновления системы безопасности, можно найти в <a href="https://support.google.com/pixelphone/answer/4457705">Справочном центре</a>. @@ -33,7 +33,7 @@ Самая серьезная из проблем – критическая уязвимость в Media Framework, которая позволяет злоумышленнику выполнять произвольный код в контексте привилегированного процесса с помощью специально созданного файла. <a href="/security/overview/updates-resources.html#severity">Уровень серьезности</a> зависит от того, какой ущерб будет нанесен устройству при атаке с использованием уязвимости, если средства защиты будут отключены разработчиком или взломаны. </p> <p> -У нас нет информации о том, что обнаруженные уязвимости эксплуатировались. В разделе <a href="#mitigations">Предотвращение атак</a> рассказывается, как <a href="/security/enhancements/index.html">платформа безопасности</a> и Google Play Защита помогают снизить вероятность атак на Android. +У нас нет информации о том, что обнаруженные уязвимости эксплуатировались. В разделе <a href="#mitigations">Предотвращение атак</a> рассказано о том, как <a href="/security/enhancements/index.html">платформа безопасности</a> и Google Play Защита помогают снизить вероятность атак на Android. </p> <p class="note"> <strong>Примечание.</strong> Информация о последних автоматических обновлениях (OTA) и образах встроенного ПО для устройств Google содержится в <a href="/security/bulletin/pixel/2018-05-01.html">бюллетене по безопасности Pixel и Nexus</a> за май 2018 года. @@ -42,7 +42,7 @@ <h2 id="mitigations">Предотвращение атак</h2> <p> -Ниже рассказывается, как <a href="/security/enhancements/index.html">платформа безопасности</a> и средства защиты сервисов, например <a href="https://www.android.com/play-protect">Google Play Защита</a>, +Ниже рассказано о том, как <a href="/security/enhancements/index.html">платформа безопасности</a> и средства защиты сервисов, например <a href="https://www.android.com/play-protect">Google Play Защита</a>, позволяют снизить вероятность атак на Android. </p> <ul> @@ -209,13 +209,6 @@ Upstream kernel</a></td> <td>Высокий</td> <td>USB-драйвер</td> </tr> - <tr> - <td>CVE-2017-5754</td> - <td>A-69856074<a href="#asterisk">*</a></td> - <td>РИ</td> - <td>Высокий</td> - <td>Отображение файлов в память</td> - </tr> </tbody></table> <h3 id="nvidia-components">Компоненты NVIDIA</h3> @@ -363,7 +356,8 @@ QC-CR#2138555</a></td> <tr> <td>CVE-2018-3562</td> <td>A-72957526<br /> - <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=7e82edc9f1ed60fa99dd4da29f91c4ad79470d7e">QC-CR#2147955</a> [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=70a5ee609ef6199dfcd8cce6198edc6f48b16bec">2</a>]</td> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=7e82edc9f1ed60fa99dd4da29f91c4ad79470d7e">QC-CR#2147955</a> + [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=70a5ee609ef6199dfcd8cce6198edc6f48b16bec">2</a>]</td> <td>ОО</td> <td>Высокий</td> <td>WLAN</td> @@ -480,7 +474,7 @@ QC-CR#2138555</a></td> </p> <p> В этом бюллетене описаны уязвимости, которые были устранены в последнем обновлении системы безопасности для устройств Android. -Решать дополнительные проблемы, перечисленные в бюллетенях по безопасности партнеров, для этого не потребовалось. Мы рекомендуем производителям чипсетов и устройств Android рассказывать об исправлениях для своих устройств в бюллетенях по безопасности на собственных сайтах, например <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, а также <a href="/security/bulletin/pixel/">Pixel и Nexus</a>. +Решать дополнительные проблемы, перечисленные в бюллетенях по безопасности партнеров, для этого не потребовалось. Мы рекомендуем производителям чипсетов и устройств Android рассказывать об исправлениях для своих устройств в бюллетенях по безопасности на собственных сайтах. Примеры таких бюллетеней: <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, <a href="/security/bulletin/pixel/">Pixel и Nexus</a>. </p> <h2 id="versions">Версии</h2> <table> @@ -502,6 +496,11 @@ QC-CR#2138555</a></td> <td>9 мая 2018 г.</td> <td>Добавлены ссылки на AOSP.</td> </tr> + <tr> + <td>1.2</td> + <td>11 июля 2018 г.</td> + <td>Удалена информация об уязвимости CVE-2017-5754 из обновления 2018-05-05.</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ru/security/bulletin/2018-06-01.html b/ru/security/bulletin/2018-06-01.html index 9355df67..326c0282 100644 --- a/ru/security/bulletin/2018-06-01.html +++ b/ru/security/bulletin/2018-06-01.html @@ -19,7 +19,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>Опубликовано 4 июня 2018 г. | Обновлено 6 июня 2018 г.</em></p> +<p><em>Опубликовано 4 июня 2018 г. | Обновлено 24 июля 2018 г.</em></p> <p> В этом бюллетене содержится информация об уязвимостях в защите устройств Android. Все актуальные проблемы, перечисленные здесь, устранены в исправлении от 5 июня 2018 года или более новом. Информацию о том, как проверить обновления системы безопасности, можно найти в <a href="https://support.google.com/pixelphone/answer/4457705">Справочном центре</a>. @@ -32,7 +32,7 @@ Самая серьезная из проблем – критическая уязвимость в Media Framework, которая позволяет злоумышленнику выполнять произвольный код в контексте привилегированного процесса с помощью специально созданного файла. <a href="/security/overview/updates-resources.html#severity">Уровень серьезности</a> зависит от того, какой ущерб будет нанесен устройству при атаке с использованием уязвимости, если средства защиты будут отключены разработчиком или взломаны. </p> <p> -У нас нет информации о том, что обнаруженные уязвимости эксплуатировались. В разделе <a href="#mitigations">Предотвращение атак</a> рассказывается, как <a href="/security/enhancements/index.html">платформа безопасности</a> и Google Play Защита помогают снизить вероятность атак на Android. +У нас нет информации о том, что обнаруженные уязвимости эксплуатировались. В разделе <a href="#mitigations">Предотвращение атак</a> рассказано о том, как <a href="/security/enhancements/index.html">платформа безопасности</a> и Google Play Защита помогают снизить вероятность атак на Android. </p> <p class="note"> <strong>Примечание.</strong> Информация о последних автоматических обновлениях (OTA) и образах встроенного ПО для устройств Google приведена в <a href="/security/bulletin/pixel/2018-06-01.html">бюллетене по безопасности Pixel и Nexus</a> за июнь 2018 года. @@ -40,7 +40,7 @@ <h2 id="mitigations">Предотвращение атак</h2> <p> -Ниже рассказывается, как <a href="/security/enhancements/index.html">платформа безопасности</a> и средства защиты сервисов, например <a href="https://www.android.com/play-protect">Google Play Защита</a>, +Ниже рассказано о том, как <a href="/security/enhancements/index.html">платформа безопасности</a> и средства защиты сервисов, например <a href="https://www.android.com/play-protect">Google Play Защита</a>, позволяют снизить вероятность атак на Android. </p> <ul> @@ -261,6 +261,36 @@ В этом разделе вы найдете подробную информацию обо всех уязвимостях, устраненных в обновлении системы безопасности 2018-06-05. Проблемы сгруппированы по компонентам, которые они затрагивают. Для каждого приведена таблица с CVE, ссылками, <a href="#type">типом</a>, <a href="/security/overview/updates-resources.html#severity">уровнем серьезности</a>, а также версиями AOSP (при наличии). Где возможно, мы приводим основную ссылку на опубликованное изменение, связанное с идентификатором ошибки (например, список AOSP), и дополнительные ссылки в квадратных скобках. </p> + +<h3 id="broadcom-components">Компоненты Broadcom</h3> + +<p> +Самая серьезная уязвимость позволяет злоумышленнику удаленно получать доступ к данным, открытым только для установленных на устройстве приложений, которые обладают необходимыми разрешениями. +</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-73665456<a href="#asterisk">*</a><br /> +B-CS4906525</td> + <td>РИ</td> + <td>Высокий</td> + <td>Bluetooth</td> + </tr> +</tbody></table> + <h3 id="kernel-components">Компоненты ядра</h3> <p> @@ -581,10 +611,26 @@ QC-CR#2151241</a></td> <td>Высокий</td> <td>WLAN</td> </tr> - <tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-73665204<a href="#asterisk">*</a><br /> + QC-CR#2187697</td> + <td>РИ</td> + <td>Высокий</td> + <td>Bluetooth</td> + </tr> + <tr> <td>CVE-2017-18159</td> <td>A-68992405<br /> - <a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=633fa4ffb38bbfb0fad79204e19b9f59d42d7680">QC-CR#2105697</a> [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=3129148e5a4cfe83003449a1048660823bfddc51">2</a>] [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=bcceb2ceeea07aedaa5f97207cc88f9d8b4416ea">3</a>] [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=04f23441b8c0c897644f9bf391b691039fa0ab70">4</a>] [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=b6b318431983f35a7734cae227478df3dc93a818">5</a>] [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=7dcbee530800b16534d0f3e8db375492c03b3e0a">6</a>] [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=9057a8b3339abc4eb2c4e462279f34bbe6410e7c">7</a>] [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=4a63a848c062851776123d4bc7ec10eb498a70dd">8</a>] [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=5471b0cdf4bace12d872d074b97eae29f1317e6a">9</a>]</td> + <a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=633fa4ffb38bbfb0fad79204e19b9f59d42d7680">QC-CR#2105697</a> + [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=3129148e5a4cfe83003449a1048660823bfddc51">2</a>] + [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=bcceb2ceeea07aedaa5f97207cc88f9d8b4416ea">3</a>] + [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=04f23441b8c0c897644f9bf391b691039fa0ab70">4</a>] + [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=b6b318431983f35a7734cae227478df3dc93a818">5</a>] + [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=7dcbee530800b16534d0f3e8db375492c03b3e0a">6</a>] + [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=9057a8b3339abc4eb2c4e462279f34bbe6410e7c">7</a>] + [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=4a63a848c062851776123d4bc7ec10eb498a70dd">8</a>] + [<a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=5471b0cdf4bace12d872d074b97eae29f1317e6a">9</a>]</td> <td>ПП</td> <td>Высокий</td> <td>Загрузчик</td> @@ -627,7 +673,8 @@ QC-CR#2161310</a></td> <tr> <td>CVE-2018-5830</td> <td>A-74237532<br /> - <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=129e76e0ea923b319555f37ea601dfb974a06bfe">QC-CR#2157917</a> [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=8174eb0235a7e581153ea1d4a401e7ea8354cc08">2</a>]</td> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=129e76e0ea923b319555f37ea601dfb974a06bfe">QC-CR#2157917</a> + [<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=8174eb0235a7e581153ea1d4a401e7ea8354cc08">2</a>]</td> <td>ПП</td> <td>Высокий</td> <td>Хост WLAN</td> @@ -700,7 +747,35 @@ QC-CR#2161310</a></td> <td>A-74235510<a href="#asterisk">*</a></td> <td>Н/Д</td> <td>Высокий</td> - <td>Компонент с закрытым исходным кодом</td> + <td>Закрытый компонент</td> + </tr> +</tbody></table> + +<h3 id="system-components">Система</h3> + +<p> +Самая серьезная уязвимость позволяет злоумышленнику удаленно получать доступ к данным, открытым только для установленных на устройстве приложений, которые обладают необходимыми разрешениями. +</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Обновленные версии AOSP</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/fa3d7e1f784d3bdbf8f9d8b572a60696289211b1">A-72377774</a></td> + <td>РИ</td> + <td>Высокий</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> </tbody></table> @@ -807,7 +882,7 @@ QC-CR#2161310</a></td> </p> <p> В этом бюллетене описаны уязвимости, которые были устранены в последнем обновлении системы безопасности для устройств Android. -Решать дополнительные проблемы, перечисленные в бюллетенях по безопасности партнеров, для этого не потребовалось. Мы рекомендуем производителям чипсетов и устройств Android рассказывать о внесенных ими исправлениях в бюллетенях по безопасности на собственных сайтах, например <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, а также <a href="/security/bulletin/pixel/">Pixel и Nexus</a>. +Решать дополнительные проблемы, перечисленные в бюллетенях по безопасности партнеров, для этого не потребовалось. Мы рекомендуем производителям чипсетов и устройств Android рассказывать об исправлениях для своих устройств в бюллетенях по безопасности на собственных сайтах. Примеры таких бюллетеней: <a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, <a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, <a href="/security/bulletin/pixel/">Pixel и Nexus</a>. </p> <h2 id="versions">Версии</h2> <table> @@ -829,6 +904,11 @@ QC-CR#2161310</a></td> <td>6 июня 2018 г.</td> <td>Добавлены ссылки на AOSP.</td> </tr> + <tr> + <td>1.2</td> + <td>24 июля 2018 г.</td> + <td>Добавлены сведения об уязвимости CVE-2018-5383 в рамках согласованного раскрытия информации.</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ru/security/bulletin/2018-07-01.html b/ru/security/bulletin/2018-07-01.html index 63fb71a9..e44e1354 100644 --- a/ru/security/bulletin/2018-07-01.html +++ b/ru/security/bulletin/2018-07-01.html @@ -19,17 +19,17 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>Опубликовано 2 июля 2018 г.</em></p> +<p><em>Опубликовано 2 июля 2018 г. | Обновлено 3 июля 2018 г.</em></p> <p> В этом бюллетене содержится информация об уязвимостях в защите устройств Android. Все актуальные проблемы, перечисленные здесь, устранены в исправлении от 5 июля 2018 года или более новом. Информацию о том, как проверить обновления системы безопасности, можно найти в <a href="https://support.google.com/pixelphone/answer/4457705">Справочном центре</a>. </p> <p> -Мы сообщили партнерам обо всех проблемах по крайней мере за месяц до выхода бюллетеня. -Исправления уязвимостей будут добавлены в хранилище Android Open Source Project (AOSP) в течение 48 часов. Ссылки на AOSP появятся в этом бюллетене позже. +Мы сообщили партнерам обо всех проблемах по крайней мере за месяц до выхода бюллетеня. Исправления уязвимостей доступны в хранилище Android Open Source Project (AOSP). +В бюллетене также приведены ссылки на исправления вне AOSP. </p> <p> -Самая серьезная из этих проблем – критическая уязвимость в Media Framework, которая позволяет злоумышленнику выполнять произвольный код в контексте привилегированного процесса с помощью специально созданного файла. <a href="/security/overview/updates-resources.html#severity">Уровень серьезности</a> зависит от того, какой ущерб будет нанесен устройству при атаке с использованием уязвимости, если средства защиты будут отключены разработчиком или взломаны. +Самая серьезная из проблем – критическая уязвимость в Media Framework, которая позволяет злоумышленнику выполнять произвольный код в контексте привилегированного процесса с помощью специально созданного файла. <a href="/security/overview/updates-resources.html#severity">Уровень серьезности</a> зависит от того, какой ущерб будет нанесен устройству при атаке с использованием уязвимости, если средства защиты будут отключены разработчиком или взломаны. </p> <p> У нас нет информации о том, что обнаруженные уязвимости эксплуатировались. В разделе <a href="#mitigations">Предотвращение атак</a> рассказывается, как <a href="/security/enhancements/index.html">платформа безопасности</a> и Google Play Защита помогают снизить вероятность атак на Android. @@ -70,14 +70,14 @@ </tr> <tr> <td>CVE-2018-9433</td> - <td>A-38196219</td> + <td>A-38196219<a href="#asterisk">*</a></td> <td>УВК</td> <td>Критический</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> </tr> <tr> <td>CVE-2018-9410</td> - <td>A-77822336</td> + <td><a href="https://android.googlesource.com/platform/frameworks/minikin/+/62e88b9f3ac35e1e69d79c7a43c6f9ddcd5980a3">A-77822336</a></td> <td>РИ</td> <td>Высокий</td> <td>8.0, 8.1</td> @@ -102,35 +102,35 @@ </tr> <tr> <td>CVE-2018-9411</td> - <td>A-79376389</td> + <td><a href="https://android.googlesource.com/platform/system/libhidl/+/e1302cfda34be9dd0a4aeae6bfa9561b44536758">A-79376389</a></td> <td>УВК</td> <td>Критический</td> <td>8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9424</td> - <td>A-76221123</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/d3860e51b83296ae1d2921d8109210283573862a">A-76221123</a></td> <td>ПП</td> <td>Высокий</td> <td>8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9428</td> - <td>A-74122779</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/46bd7c682db5bbc048b177c52448a7999e5740ce">A-74122779</a></td> <td>ПП</td> <td>Высокий</td> <td>8.1</td> </tr> <tr> <td>CVE-2018-9412</td> - <td>A-78029004</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/fa12c0fcdc6607b746177ccad4f7099098b4849a">A-78029004</a></td> <td>ОО</td> <td>Высокий</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9421</td> - <td>A-77237570</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/ff2171f2460e3a6d3443ab957732b8b7d4831d40">A-77237570</a></td> <td>РИ</td> <td>Высокий</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -155,28 +155,28 @@ </tr> <tr> <td>CVE-2018-9365</td> - <td>A-74121126</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/ae94a4c333417a1829030c4d87a58ab7f1401308">A-74121126</a></td> <td>УВК</td> <td>Критический</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9432</td> - <td>A-73173182</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/a6fe2cd18c77c68219fe7159c051bc4e0003fc40">A-73173182</a></td> <td>ПП</td> <td>Высокий</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9420</td> - <td>A-77238656</td> + <td><a href="https://android.googlesource.com/platform/system/media/+/12df4b05fd918d836636e21f783df7ad9d5e17a3">A-77238656</a></td> <td>РИ</td> <td>Высокий</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9419</td> - <td>A-74121659</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/f1c2c86080bcd7b3142ff821441696fc99c2bc9a">A-74121659</a></td> <td>РИ</td> <td>Высокий</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -263,14 +263,6 @@ <td>WLAN</td> </tr> <tr> - <td>CVE-2018-5855</td> - <td>A-77527719<br /> - <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qca-wifi-host-cmn/commit/?id=61f4a467177afc23bdc1944ec61e52bed156c104">QC-CR#2181685</a></td> - <td>РИ</td> - <td>Высокий</td> - <td>WLAN</td> - </tr> - <tr> <td>CVE-2017-13077, CVE-2017-13078</td> <td>A-78285557<br /> <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=5c671a69c57ce4fd84f0eaf082b336a49d0cf5dd">QC-CR#2133114</a></td> @@ -292,7 +284,7 @@ QC-CR#2151011</td> <td>ПП</td> <td>Высокий</td> - <td>Драйвер OpenGL ES</td> + <td>Драйвер OpenGL ES</td> </tr> <tr> <td>CVE-2018-3586</td> @@ -306,7 +298,7 @@ </tbody></table> <h3 id="qualcomm-closed-source-components">Компоненты Qualcomm с закрытым исходным кодом</h3> -<p>Эти уязвимости затрагивают компоненты Qualcomm и описаны в бюллетенях по безопасности Qualcomm AMSS или оповещениях системы безопасности. Уровень серьезности этих уязвимостей определяется непосредственно компанией Qualcomm.</p> +<p>Эти уязвимости затрагивают компоненты Qualcomm. Они описаны в бюллетенях по безопасности Qualcomm AMSS и оповещениях системы безопасности. Уровень серьезности этих уязвимостей определяется непосредственно компанией Qualcomm.</p> <table> <colgroup><col width="21%" /> @@ -420,13 +412,6 @@ <td>Компонент с закрытым исходным кодом</td> </tr> <tr> - <td>CVE-2018-11258</td> - <td>A-72951054<a href="#asterisk">*</a></td> - <td>Н/Д</td> - <td>Высокий</td> - <td>Компонент с закрытым исходным кодом</td> - </tr> - <tr> <td>CVE-2018-11257</td> <td>A-74235874<a href="#asterisk">*</a></td> <td>Н/Д</td> @@ -597,6 +582,16 @@ <td>2 июля 2018 г.</td> <td>Бюллетень опубликован.</td> </tr> + <tr> + <td>1.1</td> + <td>3 июля 2018 г.</td> + <td>Добавлены ссылки на AOSP.</td> + </tr> + <tr> + <td>1.2</td> + <td>11 июля 2018 г.</td> + <td>Сведения об уязвимостях CVE-2018-5855 и CVE-2018-11258 удалены из раздела, посвященного обновлению системы безопасности 2018-07-05.</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ru/security/bulletin/2018-08-01.html b/ru/security/bulletin/2018-08-01.html new file mode 100644 index 00000000..5062e75d --- /dev/null +++ b/ru/security/bulletin/2018-08-01.html @@ -0,0 +1,639 @@ +<html devsite><head> + <title>Бюллетень по безопасности Android – август 2018 г.</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> +<p><em>Опубликовано 6 августа 2018 г.</em></p> + +<p> +В этом бюллетене содержится информация об уязвимостях в защите устройств Android. Все актуальные проблемы, перечисленные здесь, устранены в исправлении от 5 августа 2018 года или более новом. Информацию о том, как проверить обновления системы безопасности, можно найти в статье <a href="https://support.google.com/pixelphone/answer/4457705" class="external">Как проверить и обновить версию Android</a>. +</p> +<p> +Мы сообщили партнерам обо всех проблемах по крайней мере за месяц до выхода бюллетеня. Исправления уязвимостей доступны в хранилище Android Open Source Project (AOSP). +В бюллетене также приведены ссылки на исправления вне AOSP. +</p> +<p> +Самая серьезная уязвимость позволяет злоумышленнику выполнять произвольный код в контексте привилегированного процесса с помощью специально созданного файла. <a href="/security/overview/updates-resources.html#severity">Уровень серьезности</a> зависит от того, какой ущерб будет нанесен устройству при атаке с использованием уязвимости, если средства защиты будут отключены разработчиком или взломаны. +</p> +<p> +У нас нет информации о том, что обнаруженные уязвимости эксплуатировались. В разделе <a href="#mitigations">Предотвращение атак</a> рассказывается, как <a href="/security/enhancements/index.html">платформа безопасности</a> и Google Play Защита помогают снизить вероятность атак на Android. +</p> +<p class="note"> +<strong>Примечание.</strong> Информация о последних автоматических обновлениях (OTA) и образах встроенного ПО для устройств Google содержится в <a href="/security/bulletin/pixel/2018-08-01.html">бюллетене по безопасности Pixel и Nexus</a> за август 2018 г. +</p> + +<h2 id="mitigations">Предотвращение атак</h2> +<p> +Ниже рассказано о том, как <a href="/security/enhancements/index.html">платформа безопасности</a> и средства защиты сервисов, например <a href="https://www.android.com/play-protect">Google Play Защита</a>, +позволяют снизить вероятность атак на Android. +</p> +<ul> +<li>В новых версиях Android сложнее использовать многие уязвимости, поэтому мы рекомендуем всем пользователям своевременно обновлять систему.</li> +<li>Команда, отвечающая за безопасность Android, с помощью <a href="https://www.android.com/play-protect" class="external">Google Play Защиты</a> активно отслеживает злоупотребления и предупреждает пользователей об установке <a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">потенциально опасных приложений</a>. Google Play Защита включена по умолчанию на всех телефонах и планшетах, использующих <a href="http://www.android.com/gms" class="external">сервисы Google для мобильных устройств</a>. Она особенно важна, если устанавливается ПО из сторонних источников.</li> +</ul> +<h2 id="2018-08-01-details">Описание уязвимостей (обновление системы безопасности 2018-08-01)</h2> +<p> +В этом разделе вы найдете подробную информацию обо всех уязвимостях, устраненных в обновлении системы безопасности 2018-08-01. Проблемы сгруппированы по компонентам, которые они затрагивают. Для каждого приведены описание и таблица с CVE, ссылками, <a href="#type">типом</a>, <a href="/security/overview/updates-resources.html#severity">уровнем серьезности</a>, а также версиями AOSP (при наличии). Где возможно, мы приводим основную ссылку на опубликованное изменение, связанное с идентификатором ошибки (например, список AOSP), и дополнительные ссылки в квадратных скобках. +</p> + +<h3 id="framework">Framework</h3> +<p>Самая серьезная уязвимость позволяет локальному вредоносному ПО обойти требования к взаимодействию с пользователем и получить доступ к дополнительным разрешениям.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Обновленные версии AOSP</th> + </tr> + <tr> + <td>CVE-2018-9445</td> + <td> + <a href="https://android.googlesource.com/platform/external/e2fsprogs/+/9a2d95e4ed9ec5ab76998654b1c2fba9cc139e50">A-80436257</a> + [<a href="https://android.googlesource.com/platform/system/vold/+/940a1ff70cfc5f2e4de83da9ad84cd9734faadf6">2</a>] + </td> + <td>ПП</td> + <td>Высокий</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9438</td> + <td> +<a href="https://android.googlesource.com/platform/packages/providers/DownloadProvider/+/b552ebf70913cc79085bcc4212235ea45e036d3b">A-78644887</a> +[<a href="https://android.googlesource.com/platform/frameworks/base/+/e3854655e75d97552140d77cca5d20c121a17ef9">2</a>] +[<a href="https://android.googlesource.com/platform/frameworks/opt/telephony/+/d1ce32b059bed774b41f11413c1d83a1bc412964">3</a>] +[<a href="https://android.googlesource.com/platform/frameworks/base/+/97e1cd61d3040dd366ac9e25cdb6f134c7490846">4</a>] +</td> + <td>ОО</td> + <td>Высокий</td> + <td>8.1</td> + </tr> + <tr> + <td>CVE-2018-9458</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/c4f66f4f607654611b2227827123e016c57a5729">A-71786287</a> +</td> + <td>ПП</td> + <td>Высокий</td> + <td>8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9451</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/a409aa1214d6483efe129a4966f09aa4fdc097ad">A-79488511</a> +[<a href="https://android.googlesource.com/platform/frameworks/base/+/1de25074adb5d9ed572d6a85e77d3df5ac3a7e9e">2</a>] +</td> + <td>РИ</td> + <td>Высокий</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="media-framework">Media Framework</h3> +<p>Самая серьезная уязвимость позволяет злоумышленнику выполнять произвольный код в контексте привилегированного процесса с помощью специально созданного файла.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Обновленные версии AOSP</th> + </tr> + <tr> + <td>CVE-2018-9427</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/av/+/08d392085c095e227c029f64644bc08ef5a544de">A-77486542</a> +[<a href="https://android.googlesource.com/platform/frameworks/av/+/c9909e5a980f941a5b72477755e09fb4dc57c478">2</a>] +</td> + <td>УВК</td> + <td>Критический</td> + <td>8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9444</td> + <td>A-63521984<a href="#asterisk">*</a></td> + <td>ОО</td> + <td>Высокий</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> + </tr> + <tr> + <td>CVE-2018-9437</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/av/+/017ff33fd419c50734f775d5054e2cbea719700b">A-78656554</a> + </td> + <td>ОО</td> + <td>Высокий</td> + <td>6.0, 6.0.1</td> + </tr> +</tbody></table> + +<h3 id="system">Система</h3> +<p>Самая серьезная уязвимость позволяет злоумышленнику выполнять произвольный код в контексте привилегированного процесса с помощью специально созданного файла.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Обновленные версии AOSP</th> + </tr> + <tr> + <td>CVE-2018-9446</td> + <td> + <a href="https://android.googlesource.com/platform/system/bt/+/49acada519d088d8edf37e48640c76ea5c70e010">A-80145946</a> + </td> + <td>УВК</td> + <td>Критический</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9450</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/bc259b4926a6f9b33b9ee2c917cd83a55f360cbf">A-79541338</a> + </td> + <td>УВК</td> + <td>Критический</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9459</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/UnifiedEmail/+/76c5261a03c8402e893999196651afc5791ca0fd">A-66230183</a> + </td> + <td>ПП</td> + <td>Высокий</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9455</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/d56c7ec9e2ecfa8a8ceeb82f37187e5ea21f2101">A-78136677</a> + </td> + <td>ОО</td> + <td>Высокий</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9436</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/289a49814aef7f0f0bb98aac8246080abdfeac01">A-79164722</a> + </td> + <td>РИ</td> + <td>Высокий</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9454</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/289a49814aef7f0f0bb98aac8246080abdfeac01">A-78286118</a> + </td> + <td>РИ</td> + <td>Высокий</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9448</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/13294c70a66347c9e5d05b9f92f8ceb6fe38d7f6">A-79944113</a> +[<a href="https://android.googlesource.com/platform/system/bt/+/f1f1c3e00f8d1baad0215b057e6d894517eeaddb">2</a>] + </td> + <td>РИ</td> + <td>Высокий</td> + <td>8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9453</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/cb6a56b1d8cdab7c495ea8f53dcbdb3cfc9477d2">A-78288378</a> + </td> + <td>РИ</td> + <td>Высокий</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h2 id="2018-08-05-details">Описание уязвимостей (обновление системы безопасности 2018-08-05)</h2> +<p> +В этом разделе вы найдете подробную информацию обо всех уязвимостях, устраненных в обновлении системы безопасности 2018-08-05. Проблемы сгруппированы по компонентам, которые они затрагивают. Для каждого приведена таблица с CVE, ссылками, <a href="#type">типом</a>, <a href="/security/overview/updates-resources.html#severity">уровнем серьезности</a>, а также версиями AOSP (при наличии). Где возможно, мы приводим основную ссылку на опубликованное изменение, связанное с идентификатором ошибки (например, список AOSP), и дополнительные ссылки в квадратных скобках. +</p> + +<h3 id="kernel-components">Компоненты ядра</h3> +<p>Самая серьезная уязвимость позволяет локальному вредоносному ПО выполнять произвольный код в контексте привилегированного процесса.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2017-18249</td> + <td>A-78283212<br /> + <a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30a61ddf8117c26ac5b295e1233eaa9629a94ca3"> +Upstream kernel</a></td> + <td>ПП</td> + <td>Высокий</td> + <td>F2FS</td> + </tr> + <tr> + <td>CVE-2018-9465</td> + <td>A-69164715<br /> + <a href="https://patchwork.kernel.org/patch/10058587/">Upstream +kernel</a></td> + <td>ПП</td> + <td>Высокий</td> + <td>Binder</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Компоненты Qualcomm</h3> +<p>Самая серьезная уязвимость</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-79421580<a href="#asterisk">*</a><br /> + QC-CR#2209635</td> + <td>РИ</td> + <td>Высокий</td> + <td>Bluetooth</td> + </tr> + <tr> + <td>CVE-2017-13077</td> + <td>A-78284758<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=edb507885fc47cf3cdf061bfba1dc77451a6a332"> +QC-CR#2133033</a></td> + <td>РИ</td> + <td>Высокий</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18281</td> + <td>A-78242172<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=69f0a80b8cc1333647397d7bc4f267bd3fe22be9"> +QC-CR#856388</a></td> + <td>РИ</td> + <td>Высокий</td> + <td>Видео</td> + </tr> + <tr> + <td>CVE-2018-11260</td> + <td>A-72997254<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=9fd239116d9cb19a18b3892b8a1f428636ca1453"> +QC-CR#2204872</a></td> + <td>ПП</td> + <td>Высокий</td> + <td>WLAN</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-closed-source-components">Компоненты Qualcomm с закрытым исходным кодом</h3> +<p>Эти уязвимости затрагивают компоненты Qualcomm и описаны в бюллетенях по безопасности Qualcomm AMSS или оповещениях системы безопасности. Уровень серьезности этих уязвимостей определяется непосредственно компанией Qualcomm.</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2017-18296</td> + <td>A-78240731<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Критический</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18305</td> + <td>A-78239838<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Критический</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18310</td> + <td>A-62211308<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Критический</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18295</td> + <td>A-78240386<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18283</td> + <td>A-78240411<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18294</td> + <td>A-78240247<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18293</td> + <td>A-78240316<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18292</td> + <td>A-78241027<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18298</td> + <td>A-78239976<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18299</td> + <td>A-78240418<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18304</td> + <td>A-78239975<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18303</td> + <td>A-78240396<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18301</td> + <td>A-78238455<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18302</td> + <td>A-78239233<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18300</td> + <td>A-78239508<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18297</td> + <td>A-78240275<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18280</td> + <td>A-78285512<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18282</td> + <td>A-78241591<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18309</td> + <td>A-73539064<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2017-18308</td> + <td>A-73539310<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2018-11305</td> + <td>A-72951032<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> + <tr> + <td>CVE-2018-11258</td> + <td>A-72951054<a href="#asterisk">*</a></td> + <td>Н/Д</td> + <td>Высокий</td> + <td>Компонент с закрытым исходным кодом</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">Часто задаваемые вопросы</h2> +<p>В этом разделе мы отвечаем на вопросы, которые могут возникнуть после прочтения бюллетеня.</p> +<p><strong>1. Как определить, установлено ли на устройство обновление, в котором устранены перечисленные проблемы?</strong></p> +<p>Информацию о том, как проверить обновления системы безопасности, можно найти в <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">Справочном центре</a>.</p> +<ul> +<li>В исправлении от 1 августа 2018 года или более новом устранены все проблемы, связанные с обновлением 2018-08-01.</li> +<li>В исправлении от 5 августа 2018 года или более новом устранены все проблемы, связанные с обновлением 2018-08-05.</li> +</ul> +<p>Производители устройств, позволяющие установить эти обновления, должны присвоить им один из этих уровней:</p> +<ul> + <li>[ro.build.version.security_patch]:[2018-08-01]</li> + <li>[ro.build.version.security_patch]:[2018-08-05]</li> +</ul> +<p><strong>2. Почему в этом бюллетене говорится о двух обновлениях системы безопасности?</strong></p> +<p> +Мы включили в этот бюллетень сведения о двух обновлениях, чтобы помочь нашим партнерам как можно скорее устранить уязвимости, затрагивающие все устройства Android. Рекомендуем партнерам Android исправить все вышеперечисленные проблемы и установить последнее обновление системы безопасности. +</p> +<ul> +<li>На устройствах с установленным обновлением 2018-08-01 должны быть исправлены все проблемы, упомянутые в соответствующем разделе этого бюллетеня, а также в предыдущих выпусках.</li> +<li>На устройствах с установленным обновлением 2018-08-05 или более новым должны быть исправлены все проблемы, упомянутые в этом бюллетене и предыдущих выпусках.</li> +</ul> +<p> +Рекомендуем партнерам собрать все исправления проблем в одно обновление. +</p> +<p id="type"> +<strong>3. Что означают сокращения в столбце <em>Тип</em>?</strong> +</p> +<p> +В этом столбце указан тип уязвимости по следующей классификации:<em></em> +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>Сокращение</th> + <th>Описание</th> + </tr> + <tr> + <td>УВК</td> + <td>Удаленное выполнение кода</td> + </tr> + <tr> + <td>ПП</td> + <td>Повышение привилегий</td> + </tr> + <tr> + <td>РИ</td> + <td>Раскрытие информации</td> + </tr> + <tr> + <td>ОО</td> + <td>Отказ в обслуживании</td> + </tr> + <tr> + <td>Н/Д</td> + <td>Классификация недоступна</td> + </tr> +</tbody></table> +<p> +<strong>4. На что указывают записи в столбце <em>Ссылки</em>?</strong> +</p> +<p> +В таблицах с описанием уязвимостей есть столбец <em>Ссылки</em>. Каждая запись в нем может содержать префикс, указывающий на источник ссылки, а именно: +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>Префикс</th> + <th>Значение</th> + </tr> + <tr> + <td>A-</td> + <td>Идентификатор ошибки Android</td> + </tr> + <tr> + <td>QC-</td> + <td>Ссылочный номер Qualcomm</td> + </tr> + <tr> + <td>M-</td> + <td>Ссылочный номер MediaTek</td> + </tr> + <tr> + <td>N-</td> + <td>Ссылочный номер NVIDIA</td> + </tr> + <tr> + <td>B-</td> + <td>Ссылочный номер Broadcom</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>5. Что означает символ * рядом с идентификатором ошибки Android в столбце <em>Ссылки</em>?</strong> +</p> +<p> +Символ * означает, что исправление для уязвимости не опубликовано.<em></em> Необходимое обновление содержится в последних бинарных драйверах для устройств Pixel и Nexus, которые можно скачать на <a href="https://developers.google.com/android/drivers" class="external">сайте Google Developers</a>. +</p> +<p> +<strong>6. Почему теперь одни уязвимости описываются в этих бюллетенях, а другие – в бюллетенях по безопасности Pixel и Nexus, а также в остальных бюллетенях партнеров?</strong> +</p> +<p> +В этом бюллетене описаны уязвимости, которые были устранены в последнем обновлении системы безопасности для устройств Android. Решать дополнительные проблемы, перечисленные в бюллетенях по безопасности партнеров, для этого не потребовалось. Мы рекомендуем производителям чипсетов и устройств Android рассказывать об исправлениях для своих устройств в бюллетенях по безопасности на собственных сайтах, например <a href="https://security.samsungmobile.com/securityUpdate.smsb" class="external">Samsung</a>, <a href="https://lgsecurity.lge.com/security_updates.html" class="external">LGE</a>, а также <a href="/security/bulletin/pixel/" class="external">Pixel и Nexus</a>. +</p> + +<h2 id="versions">Версии</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>Версия</th> + <th>Дата</th> + <th>Примечания</th> + </tr> + <tr> + <td>1.0</td> + <td>6 августа 2018 г.</td> + <td>Бюллетень опубликован.</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/ru/security/bulletin/2018.html b/ru/security/bulletin/2018.html index f56760e5..5b7e1e4c 100644 --- a/ru/security/bulletin/2018.html +++ b/ru/security/bulletin/2018.html @@ -34,14 +34,44 @@ <th>Обновление системы безопасности</th> </tr> <tr> + <td><a href="/security/bulletin/2018-08-01.html">Август 2018 г.</a></td> + <td>Готовится к публикации <!-- + <a href="/security/bulletin/2018-08-01.html">English</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>6 августа 2018 г.</td> + <td>2018-08-01<br /> + 2018-08-05</td> + </tr> + + <tr> + <td><a href="/security/bulletin/2018-07-01.html">Июль 2018 г.</a></td> + <td> + <a href="/security/bulletin/2018-07-01.html">English</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2 июля 2018 г.</td> + <td>2018-07-01<br /> + 2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/2018-06-01.html">Июнь 2018 г.</a></td> <td> <a href="/security/bulletin/2018-06-01.html">English</a> / -<a href="/security/bulletin/2018-06-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-06-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-06-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-06-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-06-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-06-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>4 июня 2018 г.</td> <td>2018-06-01<br /> @@ -51,11 +81,11 @@ <td><a href="/security/bulletin/2018-05-01.html">Май 2018 г.</a></td> <td> <a href="/security/bulletin/2018-05-01.html">English</a> / -<a href="/security/bulletin/2018-05-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-05-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-05-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-05-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-05-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-05-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-05-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>7 мая 2018 г.</td> <td>2018-05-01<br /> @@ -65,11 +95,11 @@ <td><a href="/security/bulletin/2018-04-01.html">Апрель 2018 г.</a></td> <td> <a href="/security/bulletin/2018-04-01.html">English</a> / -<a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-04-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-04-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-04-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-04-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 апреля 2018 г.</td> <td>2018-04-01<br /> @@ -79,11 +109,11 @@ <td><a href="/security/bulletin/2018-03-01.html">Март 2018 г.</a></td> <td> <a href="/security/bulletin/2018-03-01.html">English</a> / -<a href="/security/bulletin/2018-03-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-03-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-03-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>Март 2018 г.</td> <td>2018-03-01<br /> @@ -93,11 +123,11 @@ <td><a href="/security/bulletin/2018-02-01.html">Февраль 2018 г.</a></td> <td> <a href="/security/bulletin/2018-02-01.html">English</a> / -<a href="/security/bulletin/2018-02-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-02-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-02-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-02-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-02-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-02-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-02-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>Февраль 2018 г.</td> <td>2018-02-01<br /> @@ -107,11 +137,11 @@ <td><a href="/security/bulletin/2018-01-01.html">Январь 2018 г.</a></td> <td> <a href="/security/bulletin/2018-01-01.html">English</a> / -<a href="/security/bulletin/2018-01-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-01-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-01-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-01-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-01-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-01-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-01-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>Январь 2018 г.</td> <td>2018-01-01<br /> diff --git a/ru/security/bulletin/index.html b/ru/security/bulletin/index.html index b8b52e16..76ddc119 100644 --- a/ru/security/bulletin/index.html +++ b/ru/security/bulletin/index.html @@ -56,27 +56,57 @@ <th>Обновление системы безопасности</th> </tr> <tr> + <td><a href="/security/bulletin/2018-08-01.html">Август 2018 г.</a></td> + <td>Готовится к публикации <!-- + <a href="/security/bulletin/2018-08-01.html">English</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>6 августа 2018 г.</td> + <td>2018-08-01<br /> + 2018-08-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/2018-07-01.html">Июль 2018 г.</a></td> + <td> + <a href="/security/bulletin/2018-07-01.html">English</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2 июля 2018 г.</td> + <td>2018-07-01<br /> + 2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/2018-06-01.html">Июнь 2018 г.</a></td> <td> <a href="/security/bulletin/2018-06-01.html">English</a> / -<a href="/security/bulletin/2018-06-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-06-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-06-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-06-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-06-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-06-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>4 июня 2018 г.</td> <td>2018-06-01<br /> 2018-06-05</td> - </tr><tr> + </tr> + <tr> <td><a href="/security/bulletin/2018-05-01.html">Май 2018 г.</a></td> <td> <a href="/security/bulletin/2018-05-01.html">English</a> / -<a href="/security/bulletin/2018-05-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-05-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-05-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-05-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-05-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-05-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-05-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>7 мая 2018 г.</td> <td>2018-05-01<br /> @@ -86,11 +116,11 @@ <td><a href="/security/bulletin/2018-04-01.html">Апрель 2018 г.</a></td> <td> <a href="/security/bulletin/2018-04-01.html">English</a> / -<a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-04-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-04-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-04-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-04-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-04-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 апреля 2018 г.</td> <td>2018-04-01<br /> @@ -100,11 +130,11 @@ <td><a href="/security/bulletin/2018-03-01.html">Март 2018 г.</a></td> <td> <a href="/security/bulletin/2018-03-01.html">English</a> / -<a href="/security/bulletin/2018-03-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-03-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-03-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>5 марта 2018 г.</td> <td>2018-03-01<br /> @@ -114,11 +144,11 @@ <td><a href="/security/bulletin/2018-02-01.html">Февраль 2018 г.</a></td> <td> <a href="/security/bulletin/2018-02-01.html">English</a> / -<a href="/security/bulletin/2018-02-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-02-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-02-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-02-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-02-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-02-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-02-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>5 февраля 2018 г.</td> <td>2018-02-01<br /> @@ -128,11 +158,11 @@ <td><a href="/security/bulletin/2018-01-01.html">Январь 2018 г.</a></td> <td> <a href="/security/bulletin/2018-01-01.html">English</a> / -<a href="/security/bulletin/2018-01-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2018-01-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2018-01-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2018-01-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2018-01-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-01-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-01-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 января 2018 г.</td> <td>2018-01-01<br /> @@ -142,11 +172,11 @@ <td><a href="/security/bulletin/2017-12-01.html">Декабрь 2017 г.</a></td> <td> <a href="/security/bulletin/2017-12-01.html">English</a> / -<a href="/security/bulletin/2017-12-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-12-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-12-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-12-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-12-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-12-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-12-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>4 декабря 2017 г.</td> <td>2017-12-01<br /> @@ -156,11 +186,11 @@ <td><a href="/security/bulletin/2017-11-01.html">Ноябрь 2017 г.</a></td> <td> <a href="/security/bulletin/2017-11-01.html">English</a> / -<a href="/security/bulletin/2017-11-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-11-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-11-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-11-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-11-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-11-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-11-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-11-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-11-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-11-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>6 ноября 2017 г.</td> <td>2017-11-01<br /> @@ -171,11 +201,11 @@ <td><a href="/security/bulletin/2017-10-01.html">Октябрь 2017 г.</a></td> <td> <a href="/security/bulletin/2017-10-01.html">English</a> / -<a href="/security/bulletin/2017-10-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-10-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-10-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-10-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-10-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-10-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-10-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-10-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-10-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-10-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 октября 2017 г.</td> <td>2017-10-01<br /> @@ -185,11 +215,11 @@ <td><a href="/security/bulletin/2017-09-01.html">Сентябрь 2017 г.</a></td> <td> <a href="/security/bulletin/2017-09-01.html">English</a> / -<a href="/security/bulletin/2017-09-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-09-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-09-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-09-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-09-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-09-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-09-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-09-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-09-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-09-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>5 сентября 2017 г.</td> <td>2017-09-01<br /> @@ -199,11 +229,11 @@ <td><a href="/security/bulletin/2017-08-01.html">Август 2017 г.</a></td> <td> <a href="/security/bulletin/2017-08-01.html">English</a> / -<a href="/security/bulletin/2017-08-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-08-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-08-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-08-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-08-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-08-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>7 августа 2017 г.</td> <td>2017-08-01<br /> @@ -213,11 +243,11 @@ <td><a href="/security/bulletin/2017-07-01.html">Июль 2017 г.</a></td> <td> <a href="/security/bulletin/2017-07-01.html">English</a> / -<a href="/security/bulletin/2017-07-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-07-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-07-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-07-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-07-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-07-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>5 июля 2017 г.</td> <td>2017-07-01<br /> @@ -227,11 +257,11 @@ <td><a href="/security/bulletin/2017-06-01.html">Июнь 2017 г.</a></td> <td> <a href="/security/bulletin/2017-06-01.html">English</a> / -<a href="/security/bulletin/2017-06-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-06-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-06-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-06-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-06-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-06-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-06-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>5 июня 2017 г.</td> <td>2017-06-01<br /> @@ -241,11 +271,11 @@ <td><a href="/security/bulletin/2017-05-01.html">Май 2017 г.</a></td> <td> <a href="/security/bulletin/2017-05-01.html">English</a> / -<a href="/security/bulletin/2017-05-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-05-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-05-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-05-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-05-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-05-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-05-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>1 мая 2017 г.</td> <td>2017-05-01<br /> @@ -254,11 +284,11 @@ <tr> <td><a href="/security/bulletin/2017-04-01.html">Апрель 2017 г.</a></td> <td><a href="/security/bulletin/2017-04-01.html">English</a> / -<a href="/security/bulletin/2017-04-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-04-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-04-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-04-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-04-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-04-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-04-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>3 апреля 2017 г.</td> <td>2017-04-01<br /> @@ -267,11 +297,11 @@ <tr> <td><a href="/security/bulletin/2017-03-01.html">Март 2017 г.</a></td> <td><a href="/security/bulletin/2017-03-01.html">English</a> / -<a href="/security/bulletin/2017-03-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-03-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-03-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-03-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-03-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-03-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-03-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>6 марта 2017 г.</td> <td>2017-03-01<br /> @@ -280,11 +310,11 @@ <tr> <td><a href="/security/bulletin/2017-02-01.html">Февраль 2017 г.</a></td> <td><a href="/security/bulletin/2017-02-01.html">English</a> / -<a href="/security/bulletin/2017-02-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-02-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-02-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-02-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-02-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-02-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-02-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>6 февраля 2017 г.</td> <td>2017-02-01<br /> @@ -293,11 +323,11 @@ <tr> <td><a href="/security/bulletin/2017-01-01.html">Январь 2017 г.</a></td> <td><a href="/security/bulletin/2017-01-01.html">English</a> / -<a href="/security/bulletin/2017-01-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2017-01-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2017-01-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2017-01-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2017-01-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2017-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-01-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-01-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>3 января 2017 г.</td> <td>2017-01-01<br /> @@ -307,11 +337,11 @@ <td><a href="/security/bulletin/2016-12-01.html">Декабрь 2016 г.</a></td> <td> <a href="/security/bulletin/2016-12-01.html">English</a> / -<a href="/security/bulletin/2016-12-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-12-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-12-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-12-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-12-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-12-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-12-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>5 декабря 2016 г.</td> <td>2016-12-01<br /> @@ -321,11 +351,11 @@ <td><a href="/security/bulletin/2016-11-01.html">Ноябрь 2016 г.</a></td> <td> <a href="/security/bulletin/2016-11-01.html">English</a> / -<a href="/security/bulletin/2016-11-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-11-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-11-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-11-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-11-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-11-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-11-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-11-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-11-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-11-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>7 ноября 2016 г.</td> <td>2016-11-01<br /> @@ -336,11 +366,11 @@ <td><a href="/security/bulletin/2016-10-01.html">Октябрь 2016 г.</a></td> <td> <a href="/security/bulletin/2016-10-01.html">English</a> / -<a href="/security/bulletin/2016-10-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-10-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-10-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-10-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-10-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-10-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-10-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-10-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-10-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-10-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>3 октября 2016 г.</td> <td>2016-10-01<br /> @@ -350,11 +380,11 @@ <td><a href="/security/bulletin/2016-09-01.html">Сентябрь 2016 г.</a></td> <td> <a href="/security/bulletin/2016-09-01.html">English</a> / -<a href="/security/bulletin/2016-09-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-09-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-09-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-09-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-09-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-09-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-09-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-09-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-09-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-09-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>6 сентября 2016 г.</td> <td>2016-09-01<br /> @@ -365,11 +395,11 @@ <td><a href="/security/bulletin/2016-08-01.html">Август 2016 г.</a></td> <td> <a href="/security/bulletin/2016-08-01.html">English</a> / -<a href="/security/bulletin/2016-08-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-08-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-08-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-08-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-08-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-08-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>1 августа 2016 г.</td> <td>2016-08-01<br /> @@ -379,11 +409,11 @@ <td><a href="/security/bulletin/2016-07-01.html">Июль 2016 г.</a></td> <td> <a href="/security/bulletin/2016-07-01.html">English</a> / -<a href="/security/bulletin/2016-07-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-07-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-07-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-07-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-07-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-07-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>6 июля 2016 г.</td> <td>2016-07-01<br /> @@ -393,11 +423,11 @@ <td><a href="/security/bulletin/2016-06-01.html">Июнь 2016 г.</a></td> <td> <a href="/security/bulletin/2016-06-01.html">English</a> / -<a href="/security/bulletin/2016-06-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-06-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-06-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-06-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-06-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-06-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-06-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>6 июня 2016 г.</td> <td>2016-06-01</td> @@ -406,11 +436,11 @@ <td><a href="/security/bulletin/2016-05-01.html">Май 2016 г.</a></td> <td> <a href="/security/bulletin/2016-05-01.html">English</a> / -<a href="/security/bulletin/2016-05-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-05-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-05-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-05-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-05-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-05-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-05-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 мая 2016 г.</td> <td>2016-05-01</td> @@ -419,11 +449,11 @@ <td><a href="/security/bulletin/2016-04-02.html">Апрель 2016 г.</a></td> <td> <a href="/security/bulletin/2016-04-02.html">English</a> / -<a href="/security/bulletin/2016-04-02.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-04-02.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-04-02.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-04-02.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-04-02.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-04-02.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-04-02.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-04-02.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-04-02.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-04-02.html?hl=zh-tw">中文 (台灣)</a> </td> <td>4 апреля 2016 г.</td> <td>2016-04-02</td> @@ -432,11 +462,11 @@ <td><a href="/security/bulletin/2016-03-01.html">Март 2016 г.</a></td> <td> <a href="/security/bulletin/2016-03-01.html">English</a> / -<a href="/security/bulletin/2016-03-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-03-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-03-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-03-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-03-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-03-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-03-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>7 марта 2016 г.</td> <td>2016-03-01</td> @@ -445,11 +475,11 @@ <td><a href="/security/bulletin/2016-02-01.html">Февраль 2016 г.</a></td> <td> <a href="/security/bulletin/2016-02-01.html">English</a> / -<a href="/security/bulletin/2016-02-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-02-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-02-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-02-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-02-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-02-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-02-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>1 февраля 2016 г.</td> <td>2016-02-01</td> @@ -458,11 +488,11 @@ <td><a href="/security/bulletin/2016-01-01.html">Январь 2016 г.</a></td> <td> <a href="/security/bulletin/2016-01-01.html">English</a> / -<a href="/security/bulletin/2016-01-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2016-01-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2016-01-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2016-01-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2016-01-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2016-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2016-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2016-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2016-01-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2016-01-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>4 января 2016 г.</td> <td>2016-01-01</td> @@ -471,11 +501,11 @@ <td><a href="/security/bulletin/2015-12-01.html">Декабрь 2015 г.</a></td> <td> <a href="/security/bulletin/2015-12-01.html">English</a> / -<a href="/security/bulletin/2015-12-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2015-12-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2015-12-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2015-12-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2015-12-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2015-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-12-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2015-12-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>7 декабря 2015 г.</td> <td>2015-12-01</td> @@ -484,11 +514,11 @@ <td><a href="/security/bulletin/2015-11-01.html">Ноябрь 2015 г.</a></td> <td> <a href="/security/bulletin/2015-11-01.html">English</a> / -<a href="/security/bulletin/2015-11-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2015-11-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2015-11-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2015-11-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2015-11-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2015-11-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-11-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-11-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-11-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2015-11-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 ноября 2015 г.</td> <td>2015-11-01</td> @@ -497,11 +527,11 @@ <td><a href="/security/bulletin/2015-10-01.html">Октябрь 2015 г.</a></td> <td> <a href="/security/bulletin/2015-10-01.html">English</a> / -<a href="/security/bulletin/2015-10-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2015-10-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2015-10-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2015-10-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2015-10-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2015-10-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-10-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-10-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-10-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2015-10-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>5 октября 2015 г.</td> <td>2015-10-01</td> @@ -510,11 +540,11 @@ <td><a href="/security/bulletin/2015-09-01.html">Сентябрь 2015 г.</a></td> <td> <a href="/security/bulletin/2015-09-01.html">English</a> / -<a href="/security/bulletin/2015-09-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2015-09-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2015-09-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2015-09-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2015-09-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2015-09-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-09-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-09-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-09-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2015-09-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>9 сентября 2015 г.</td> <td>Нет данных</td> @@ -523,14 +553,14 @@ <td><a href="/security/bulletin/2015-08-01.html">Август 2015 г.</a></td> <td> <a href="/security/bulletin/2015-08-01.html">English</a> / -<a href="/security/bulletin/2015-08-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/2015-08-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/2015-08-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/2015-08-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/2015-08-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/2015-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2015-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2015-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2015-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2015-08-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>13 августа 2015 г.</td> - <td>Нет данных</td> + <td>Н/Д</td> </tr> </tbody></table> diff --git a/ru/security/bulletin/pixel/2018-04-01.html b/ru/security/bulletin/pixel/2018-04-01.html index e5f49a87..2eb71611 100644 --- a/ru/security/bulletin/pixel/2018-04-01.html +++ b/ru/security/bulletin/pixel/2018-04-01.html @@ -218,14 +218,14 @@ <td>A-70576999<a href="#asterisk">*</a></td> <td>РИ</td> <td>Средний</td> - <td>Драйвер Mnh_sm</td> + <td>Драйвер mnh_sm</td> </tr> <tr> <td>CVE-2017-13305</td> <td>A-70526974<a href="#asterisk">*</a></td> <td>РИ</td> <td>Средний</td> - <td>Зашифрованные ключи</td> + <td>encrypted-keys</td> </tr> <tr> <td>CVE-2017-17449</td> @@ -240,7 +240,7 @@ <td>A-70295063<a href="#asterisk">*</a></td> <td>ПП</td> <td>Средний</td> - <td>Драйвер Mnh</td> + <td>Драйвер mnh</td> </tr> <tr> <td>CVE-2017-13307</td> @@ -600,7 +600,7 @@ QC-CR#2098332</a></td> <tr> <td>A-67634615</td> <td>Стабильность</td> - <td>Повышена стабильность работы модема на телефонах Pixel и Pixel 2.</td> + <td>Повышена стабильность работы модема.</td> <td>Pixel, Pixel XL, Pixel 2, Pixel 2 XL</td> </tr> <tr> diff --git a/ru/security/bulletin/pixel/2018-06-01.html b/ru/security/bulletin/pixel/2018-06-01.html index b9d87dc7..a2fa6c70 100644 --- a/ru/security/bulletin/pixel/2018-06-01.html +++ b/ru/security/bulletin/pixel/2018-06-01.html @@ -30,7 +30,7 @@ Обновление системы безопасности 2018-06-05 получат все поддерживаемые устройства Google. Мы настоятельно рекомендуем пользователям установить это обновление. </p> <p class="note"> -<strong>Примечание.</strong> Образы встроенного ПО для устройств Google можно найти на <a href="https://developers.google.com/android/images">сайте для разработчиков</a>. +<strong>Примечание.</strong> Образы встроенного ПО для устройств Google можно найти на <a href="https://developers.google.com/android/images">сайте Google Developers</a>. </p> <h2 id="announcements">Объявления</h2> <p>Помимо исправлений уязвимостей, описанных в бюллетене по безопасности Android за июнь 2018 года, обновления для устройств Pixel и Nexus содержат также исправления проблем, перечисленных ниже. Мы сообщили партнерам об этих проблемах не менее месяца назад. Они могут включить эти исправления в свои обновления безопасности.</p> @@ -101,7 +101,8 @@ </tr> <tr> <td>CVE-2018-9379</td> - <td><a href="https://android.googlesource.com/platform/frameworks/base/+/42e5aed1d106bef1f8913ffe87aa1f9df6aae90c">A-63766886</a> [<a href="https://android.googlesource.com/platform/packages/providers/MediaProvider/+/76ffd8258c483b7170af49a8a67702426df07f2f">2</a>]</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/42e5aed1d106bef1f8913ffe87aa1f9df6aae90c">A-63766886</a> + [<a href="https://android.googlesource.com/platform/packages/providers/MediaProvider/+/76ffd8258c483b7170af49a8a67702426df07f2f">2</a>]</td> <td>РИ</td> <td>Средний</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -144,7 +145,8 @@ </tr> <tr> <td rowspan="2">CVE-2018-9352</td> - <td rowspan="2"><a href="https://android.googlesource.com/platform/external/libhevc/+/a7303e887a40ab164b19b310068e13ac4f123edc">A-73965867</a> [<a href="https://android.googlesource.com/platform/external/libhevc/+/9434d4d8846241f0575aaf48ee7d4342e926ae77">2</a>]</td> + <td rowspan="2"><a href="https://android.googlesource.com/platform/external/libhevc/+/a7303e887a40ab164b19b310068e13ac4f123edc">A-73965867</a> + [<a href="https://android.googlesource.com/platform/external/libhevc/+/9434d4d8846241f0575aaf48ee7d4342e926ae77">2</a>]</td> <td>РИ</td> <td>Средний</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> diff --git a/ru/security/bulletin/pixel/2018-07-01.html b/ru/security/bulletin/pixel/2018-07-01.html index d383a7ab..e61a52a6 100644 --- a/ru/security/bulletin/pixel/2018-07-01.html +++ b/ru/security/bulletin/pixel/2018-07-01.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p><em>Опубликовано 2 июля 2018 г.</em></p> +<p><em>Опубликовано 2 июля 2018 г. | Обновлено 3 июля 2018 г.</em></p> <p> В этом бюллетене содержится информация об уязвимостях в защите и об улучшениях функциональных возможностей <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">поддерживаемых устройств Pixel и Nexus</a> (устройства Google). @@ -58,21 +58,21 @@ </tr> <tr> <td>CVE-2018-9426</td> - <td>A-79148652</td> + <td><a href="https://android.googlesource.com/platform/external/bouncycastle/+/129a20459ea828c1b05f0d5da57f69a2a3212ad7">A-79148652</a></td> <td>РИ</td> <td>Средний</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9376</td> - <td>A-69981755</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/e6655cb8a78b757e9329b8200a90746ffac3a5a9">A-69981755</a></td> <td>ПП</td> <td>Средний</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9434</td> - <td>A-29833520</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/ab1fb955acc8bbe6b9086a4ab54beab003a887a9">A-29833520</a> [<a href="https://android.googlesource.com/platform/frameworks/native/+/c4b7338b1a0995222d229a6f794db02c974ba0d8">2</a>]</td> <td>РИ</td> <td>Средний</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -96,14 +96,14 @@ </tr> <tr> <td>CVE-2018-9429</td> - <td>A-73927042</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/7306d8b37c00729dc41d663a4b244a00209d537b">A-73927042</a></td> <td>РИ</td> <td>Средний</td> <td>8.1</td> </tr> <tr> <td>CVE-2018-9423</td> - <td>A-77599438</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/e46e5994a80c31f6533384f0f325555f3a87bee3">A-77599438</a></td> <td>РИ</td> <td>Средний</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> @@ -127,35 +127,35 @@ </tr> <tr> <td>CVE-2018-9413</td> - <td>A-73782082</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/97eb2f9cfba4f38d64dffa0558f1c4c3aa91b4f8">A-73782082</a></td> <td>УВК</td> <td>Средний</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9418</td> - <td>A-73824150</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/8e702ed3539caac44a616243e33aaad1b2b4801f">A-73824150</a></td> <td>УВК</td> <td>Средний</td> <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9430</td> - <td>A-73963551</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/605ebb3369b3f961196815065a9fe4ba5bc4d659">A-73963551</a></td> <td>УВК</td> <td>Средний</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9414</td> - <td>A-78787521</td> + <td><a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/98ff9fe7db5a25fa2c772a85f0b9baa3545228bf">A-78787521</a></td> <td>ПП</td> <td>Средний</td> <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> </tr> <tr> <td>CVE-2018-9431</td> - <td>A-77600924</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/5c23facbf802c9b4c88ceb60e1b782abcc55ddc9">A-77600924</a></td> <td>ПП</td> <td>Средний</td> <td>8.0, 8.1</td> @@ -188,7 +188,7 @@ <tr> <td>CVE-2018-9415</td> <td>A-69129004<br /> - <a href="https://patchwork.kernel.org/patch/9946759/">Upstream kernel</a></td> + <a href="https://patchwork.kernel.org/patch/10175615/">Upstream kernel</a></td> <td>ПП</td> <td>Средний</td> <td>Драйвер AMBA</td> @@ -260,7 +260,7 @@ <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=9c042f7827e0d21e5b93c04b418bca0230de91dc">QC-CR#2170392</a></td> <td>РИ</td> <td>Средний</td> - <td>wma</td> + <td>WMA</td> </tr> <tr> <td>CVE-2018-11304</td> @@ -343,7 +343,7 @@ </tr> <tr> <td>A-73204553</td> - <td>Сеть</td> + <td>Подключение</td> <td>Повышена стабильность подключений к сетям Wi-Fi, создаваемым некоторыми маршрутизаторами.</td> <td>Pixel 2, Pixel 2 XL</td> </tr> @@ -455,6 +455,11 @@ <td>2 июля 2018 г.</td> <td>Бюллетень опубликован.</td> </tr> + <tr> + <td>1.1</td> + <td>3 июля 2018 г.</td> + <td>Добавлены ссылки на AOSP.</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/ru/security/bulletin/pixel/2018-08-01.html b/ru/security/bulletin/pixel/2018-08-01.html new file mode 100644 index 00000000..4f90055f --- /dev/null +++ b/ru/security/bulletin/pixel/2018-08-01.html @@ -0,0 +1,523 @@ +<html devsite><head> + <title>Бюллетень по безопасности Pixel и Nexus – август 2018 г.</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + +<p><em>Опубликовано 6 августа 2018 г.</em></p> + +<p> +В этом бюллетене содержится информация об уязвимостях в защите и улучшениях функциональных возможностей <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">поддерживаемых устройств Pixel и Nexus</a> (устройства Google). +Все проблемы, перечисленные здесь и в бюллетене по безопасности Android за август 2018 года, устранены в исправлении от 5 августа 2018 года или более новом. Информацию о том, как проверить обновления системы безопасности, можно найти в статье <a href="https://support.google.com/pixelphone/answer/4457705" class="external">Как проверить и обновить версию Android</a>. +</p> +<p> +Обновление системы безопасности 2018-08-05 получат все поддерживаемые устройства Google. Мы настоятельно рекомендуем пользователям установить это обновление. +</p> +<p class="note"> +<strong>Примечание.</strong> Образы встроенного ПО для устройств Google можно найти на сайте <a href="https://developers.google.com/android/images" class="external">Google Developers</a>. +</p> + +<h2 id="announcements">Новости</h2> +<p>Помимо исправлений уязвимостей, описанных в бюллетене по безопасности Android за август 2018 года, обновления для устройств Google содержат также исправления проблем, перечисленных ниже. Мы сообщили партнерам об этих проблемах по крайней мере месяц назад. Они могут включить их исправления в свои обновления устройств.</p> + +<h2 id="security-patches">Обновления системы безопасности</h2> +<p> +Уязвимости сгруппированы по компонентам, которые они затрагивают. Для каждого приведены описание и таблица с CVE, ссылками, <a href="#type">типом</a>, <a href="/security/overview/updates-resources.html#severity">уровнем серьезности</a>, а также версиями AOSP (при наличии). +Где возможно, идентификаторы ошибки содержат ссылку на опубликованное изменение (например, список AOSP). Если опубликованных изменений несколько, дополнительные ссылки указаны в квадратных скобках. +</p> + +<h3 id="framework">Framework</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Обновленные версии AOSP</th> + </tr> + <tr> + <td>CVE-2017-1000100</td> + <td> +<a href="https://android.googlesource.com/platform/external/curl/+/1506c0316973bd95d7832891b1aa2258b52a793d">A-64610131</a> +</td> + <td>РИ</td> + <td>Средний</td> + <td>7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="system">Система</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Обновленные версии AOSP</th> + </tr> + <tr> + <td>CVE-2018-9435</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/51b05b715024adff4fa59ab2e18c0b56c5d3af5e">A-79591688</a> +</td> + <td>РИ</td> + <td>Средний</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9461</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Messaging/+/17a2579a0aa603a3a7d94e5dc64afeb96e430e8f">A-37629504</a> +</td> + <td>РИ</td> + <td>Средний</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9449</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/27b90f4f6fe3811335e9bb4fac4656bc1df49204">A-79884292</a> +</td> + <td>РИ</td> + <td>Средний</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9457</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Settings/+/a3e94449c8fe0a377b61747b6129fafc930da086">A-72872376</a> +</td> + <td>РИ</td> + <td>Средний</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9441</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/c3c69bed0f76178c640dd8e726967b9cdea5dece">A-74075873</a> +[<a href="https://android.googlesource.com/platform/system/bt/+/3a2799939b2da543ed3a62f29db658cb05f8ad3b">2</a>] +</td> + <td>РИ</td> + <td>Средний</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2017-13322</td> + <td> +<a href="https://android.googlesource.com/platform/packages/services/Telephony/+/c25745addd19b1549b7ec5bdc46d8bf1a1de37ed">A-67862398</a> +</td> + <td>ОО</td> + <td>Средний</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> + <tr> + <td>CVE-2018-9447</td> + <td> +<a href="https://android.googlesource.com/platform/packages/services/Telephony/+/19c48992b79df89c730f3619eb69baf03d449e95">A-79995313</a> +</td> + <td>ОО</td> + <td>Средний</td> + <td>6.0, 6.0.1, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="kernel-components">Компоненты ядра</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2018-9462</td> + <td>A-78364203<a href="#asterisk">*</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Сенсорный экран</td> + </tr> + <tr> + <td>CVE-2018-9439</td> + <td>A-79377438<a href="#asterisk">*</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Стек протоколов</td> + </tr> + <tr> + <td>CVE-2018-9463</td> + <td>A-78362414<a href="#asterisk">*</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Сенсорный экран</td> + </tr> + <tr> + <td>CVE-2018-1068</td> + <td>A-77902350<br /> + <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b71812168571fa55e44cdd0254471331b9c4c4c6"> +Upstream kernel</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Система сетевой фильтрации Netfilter</td> + </tr> + <tr> + <td>CVE-2018-9464</td> + <td>A-68993267<a href="#asterisk">*</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Загрузчик операционной системы Taimen</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Компоненты Qualcomm</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2018-11263</td> + <td>A-79422278<a href="#asterisk">*</a><br /> + QC-CR#2209106</td> + <td>ПП</td> + <td>Средний</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-8261</td> + <td>A-35139833<a href="#asterisk">*</a><br /> + QC-CR#2013631</td> + <td>ПП</td> + <td>Средний</td> + <td>Драйвер камеры</td> + </tr> + <tr> + <td>CVE-2018-5910</td> + <td>A-79422277<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=b67e04e3696f05411b7434c8b194895d273b00c5"> +QC-CR#2175499</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=d9344c2f4b60cf5d4c747c11f3cb0b6f1558db78">2</a>] +</td> + <td>ПП</td> + <td>Средний</td> + <td>MDSS</td> + </tr> + <tr> + <td>CVE-2018-5909</td> + <td>A-79421262<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=2c1716c5afd660651724b6088f2e6301272f4926"> +QC-CR#2174716</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Ротатор</td> + </tr> + <tr> + <td>CVE-2018-5908</td> + <td>A-79422409<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=28e5918c60b832091c6b3618747258803cbd3302"> +QC-CR#2171758</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=4689d03e5db548d263232c274bf307956207da27">2</a>] +</td> + <td>ПП</td> + <td>Средний</td> + <td>MDSS</td> + </tr> + <tr> + <td>CVE-2018-5905</td> + <td>A-79421261<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=6eb2f4f6fde1b210712d6ac66b40b9e7684d77db"> +QC-CR#2169715</a></td> + <td>ПП</td> + <td>Средний</td> + <td>Драйвер diag</td> + </tr> + <tr> + <td>CVE-2018-5904</td> + <td>A-79421260<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=88b838c8952ec6414c72449ae15768d15d2606dd"> +QC-CR#2184702</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.9/commit/?id=8e82c0d84ccee87309fd22f8208915f0ba502b26">2</a>] +</td> + <td>ПП</td> + <td>Средний</td> + <td>Драйвер питания</td> + </tr> + <tr> + <td>CVE-2018-5903</td> + <td>A-79421737<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=20365fa599f42f6e1f175d9d5d60d964927c2160"> +QC-CR#2185477</a></td> + <td>ПП</td> + <td>Средний</td> + <td>qcacld 3.0</td> + </tr> + <tr> + <td>CVE-2017-18306</td> + <td>A-73889358<a href="#asterisk">*</a><br /> + QC-CR#2216399</td> + <td>РИ</td> + <td>Средний</td> + <td>v4l2</td> + </tr> + <tr> + <td>CVE-2017-18307</td> + <td>A-73888283<a href="#asterisk">*</a><br /> + QC-CR#2026045</td> + <td>РИ</td> + <td>Средний</td> + <td>qcacld-3.0</td> + </tr> + <tr> + <td>CVE-2017-9711</td> + <td>A-36367253<a href="#asterisk">*</a><br /> + QC-CR#2046006</td> + <td>ПП</td> + <td>Средний</td> + <td>IPA</td> + </tr> + <tr> + <td>CVE-2018-3587</td> + <td>A-65542521<a href="#asterisk">*</a><br /> + QC-CR#2120605</td> + <td>ПП</td> + <td>Средний</td> + <td>qcacld-2.0</td> + </tr> +</tbody></table> + +<h3 id="update:-framework">Обновление: Framework</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Обновленные версии AOSP</th> + </tr> + <tr> + <td>CVE-2017-13295</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/da24aa45a8b65a7b9adbe12ff94bf891bdd38825">A-62537081</a> +[<a href="https://android.googlesource.com/platform/packages/apps/PackageInstaller/+/3af01bd93513d902dbb5382b10109fdf3ab29d2d">2</a>] +</td> + <td>ОО</td> + <td>Средний</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="update:-system">Обновление: система</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Обновленные версии AOSP</th> + </tr> + <tr> + <td>CVE-2017-13242</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Settings/+/f973e707f50adc0c21599e719be06714f808a333">A-62672248</a> +</td> + <td>РИ</td> + <td>Средний</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1</td> + </tr> +</tbody></table> + +<h3 id="update:-qualcomm-components">Обновление: компоненты Qualcomm</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>Ссылки</th> + <th>Тип</th> + <th>Уровень серьезности</th> + <th>Компонент</th> + </tr> + <tr> + <td>CVE-2017-15817</td> + <td>A-68992394<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=fe43c2b64ac81199de17efc258e95546cb0546f1">QC-CR#2076603</a> +[<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=8ba78e506e5002cdae525dd544dbf1df0ccce1ef">2</a>] +<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=343a3f28338788c5c91289f53171c1f71f293cd7">QC-CR#2084599</a> +<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=0c21aaa2fefa6c5919813fdd287436dddda54227">QC-CR#2096512</a> +</td> + <td>УВК</td> + <td>Критический</td> + <td>WLAN</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">Часто задаваемые вопросы</h2> +<p> +В этом разделе мы отвечаем на вопросы, которые могут возникнуть после прочтения бюллетеня. +</p> +<p> +<strong>1. Как определить, установлено ли на устройство обновление, в котором устранены перечисленные проблемы? +</strong> +</p> +<p> +В исправлении от 5 августа 2018 года или более новом устранены все проблемы, связанные с обновлением 2018-08-05. Информацию о том, как проверить обновления системы безопасности, можно найти в статье <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">Обновления системы безопасности</a>. +</p> +<p id="type"> +<strong>2. Что означают сокращения в столбце <em>Тип</em>?</strong> +</p> +<p> +В этом столбце указан тип уязвимости по следующей классификации:<em></em> +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>Сокращение</th> + <th>Описание</th> + </tr> + <tr> + <td>УВК</td> + <td>Удаленное выполнение кода</td> + </tr> + <tr> + <td>ПП</td> + <td>Повышение привилегий</td> + </tr> + <tr> + <td>РИ</td> + <td>Раскрытие информации</td> + </tr> + <tr> + <td>ОО</td> + <td>Отказ в обслуживании</td> + </tr> + <tr> + <td>Н/Д</td> + <td>Классификация недоступна</td> + </tr> +</tbody></table> +<p> +<strong>3. Что означает информация в столбце <em>Ссылки</em>?</strong> +</p> +<p> +В таблицах с описанием уязвимостей есть столбец <em>Ссылки</em>. Каждая запись в нем может содержать префикс, указывающий на источник ссылки, а именно: +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>Префикс</th> + <th>Значение</th> + </tr> + <tr> + <td>A-</td> + <td>Идентификатор ошибки Android</td> + </tr> + <tr> + <td>QC-</td> + <td>Ссылочный номер Qualcomm</td> + </tr> + <tr> + <td>M-</td> + <td>Ссылочный номер MediaTek</td> + </tr> + <tr> + <td>N-</td> + <td>Ссылочный номер NVIDIA</td> + </tr> + <tr> + <td>B-</td> + <td>Ссылочный номер Broadcom</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>4. Что означает символ * рядом с идентификатором ошибки Android в столбце <em>Ссылки</em>?</strong> +</p> +<p> +Символ * означает, что исправление для уязвимости не опубликовано.<em></em> Необходимое обновление содержится в последних бинарных драйверах для устройств Pixel и Nexus, которые можно скачать на <a href="https://developers.google.com/android/nexus/drivers" class="external">сайте Google Developers</a>. +</p> +<p> +<strong>5. Почему теперь одни уязвимости описываются в этом бюллетене, а другие – в бюллетенях по безопасности Android?</strong> +</p> +<p> +В бюллетене по безопасности Android описаны уязвимости, которые необходимо устранить в последнем обновлении системы безопасности для устройств Android. Исправление дополнительных проблем, перечисленных здесь, для выпуска этого обновления не требуется. +</p> +<h2 id="versions">Версии</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>Версия</th> + <th>Дата</th> + <th>Примечания</th> + </tr> + <tr> + <td>1.0</td> + <td>6 августа 2018 г.</td> + <td>Бюллетень опубликован.</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/ru/security/bulletin/pixel/2018.html b/ru/security/bulletin/pixel/2018.html index 51c46557..85826d2b 100644 --- a/ru/security/bulletin/pixel/2018.html +++ b/ru/security/bulletin/pixel/2018.html @@ -34,14 +34,41 @@ <th>Обновление системы безопасности</th> </tr> <tr> + <td><a href="/security/bulletin/pixel/2018-08-01.html">Август 2018 г.</a></td> + <td>Готовится к публикации <!-- + <a href="/security/bulletin/pixel/2018-08-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>6 августа 2018 г.</td> + <td>2018-08-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-07-01.html">Июль 2018 г.</a></td> + <td> + <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2 июля 2018 г.</td> + <td>2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-06-01.html">Июнь 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-06-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>4 июня 2018 г.</td> <td>2018-06-05</td> @@ -50,11 +77,11 @@ <td><a href="/security/bulletin/pixel/2018-05-01.html">Май 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-05-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>7 мая 2018 г.</td> <td>2018-05-05</td> @@ -63,11 +90,11 @@ <td><a href="/security/bulletin/pixel/2018-04-01.html">Апрель 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-04-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 апреля 2018 г.</td> <td>2018-04-05</td> @@ -76,13 +103,11 @@ <td><a href="/security/bulletin/pixel/2018-03-01.html">Март 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">русский</a> / -<!-- - <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / - --> -<a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>Март 2018 г.</td> <td>2018-03-05</td> @@ -91,11 +116,11 @@ <td><a href="/security/bulletin/pixel/2018-02-01.html">Февраль 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-02-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>Февраль 2018 г.</td> <td>2018-02-05</td> @@ -104,11 +129,11 @@ <td><a href="/security/bulletin/pixel/2018-01-01.html">Январь 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>Январь 2018 г.</td> <td>2018-01-05</td> diff --git a/ru/security/bulletin/pixel/index.html b/ru/security/bulletin/pixel/index.html index 082798c0..1c798ab5 100644 --- a/ru/security/bulletin/pixel/index.html +++ b/ru/security/bulletin/pixel/index.html @@ -43,14 +43,41 @@ <th>Обновление системы безопасности</th> </tr> <tr> + <td><a href="/security/bulletin/pixel/2018-08-01.html">Август 2018 г.</a></td> + <td>Готовится к публикации <!-- + <a href="/security/bulletin/pixel/2018-08-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>6 августа 2018 г.</td> + <td>2018-08-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-07-01.html">Июль 2018 г.</a></td> + <td> + <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2 июля 2018 г.</td> + <td>2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-06-01.html">Июнь 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-06-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-06-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>4 июня 2018 г.</td> <td>2018-06-05</td> @@ -59,11 +86,11 @@ <td><a href="/security/bulletin/pixel/2018-05-01.html">Май 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-05-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-05-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>7 мая 2018 г.</td> <td>2018-05-05</td> @@ -72,11 +99,11 @@ <td><a href="/security/bulletin/pixel/2018-04-01.html">Апрель 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-04-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-04-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 апреля 2018 г.</td> <td>2018-04-05</td> @@ -85,11 +112,11 @@ <td><a href="/security/bulletin/pixel/2018-03-01.html">Март 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-03-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>5 марта 2018 г.</td> <td>2018-03-05</td> @@ -98,11 +125,11 @@ <td><a href="/security/bulletin/pixel/2018-02-01.html">Февраль 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-02-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-02-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>5 февраля 2018 г.</td> <td>2018-02-05</td> @@ -111,11 +138,11 @@ <td><a href="/security/bulletin/pixel/2018-01-01.html">Январь 2018 г.</a></td> <td> <a href="/security/bulletin/pixel/2018-01-01.html">English</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-01-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 января 2018 г.</td> <td>2018-01-05</td> @@ -124,11 +151,11 @@ <td><a href="/security/bulletin/pixel/2017-12-01.html">Декабрь 2017 г.</a></td> <td> <a href="/security/bulletin/pixel/2017-12-01.html">English</a> / -<a href="/security/bulletin/pixel/2017-12-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2017-12-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2017-12-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2017-12-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2017-12-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2017-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>4 декабря 2017 г.</td> <td>2017-12-05</td> @@ -137,11 +164,11 @@ <td><a href="/security/bulletin/pixel/2017-11-01.html">Ноябрь 2017 г.</a></td> <td> <a href="/security/bulletin/pixel/2017-11-01.html">English</a> / -<a href="/security/bulletin/pixel/2017-11-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2017-11-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2017-11-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2017-11-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2017-11-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2017-11-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2017-11-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2017-11-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2017-11-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2017-11-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>6 ноября 2017 г.</td> <td>2017-11-05</td> @@ -150,11 +177,11 @@ <td><a href="/security/bulletin/pixel/2017-10-01.html">Октябрь 2017 г.</a></td> <td> <a href="/security/bulletin/pixel/2017-10-01.html">English</a> / -<a href="/security/bulletin/pixel/2017-10-01.html?hl=ja">日本語</a> / -<a href="/security/bulletin/pixel/2017-10-01.html?hl=ko">한국어</a> / -<a href="/security/bulletin/pixel/2017-10-01.html?hl=ru">русский</a> / -<a href="/security/bulletin/pixel/2017-10-01.html?hl=zh-cn">中文 (中国)</a> / -<a href="/security/bulletin/pixel/2017-10-01.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/bulletin/pixel/2017-10-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2017-10-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2017-10-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2017-10-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2017-10-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2 октября 2017 г.</td> <td>2017-10-05</td> diff --git a/zh-cn/_book.yaml b/zh-cn/_book.yaml index 4c604ace..385b7f60 100644 --- a/zh-cn/_book.yaml +++ b/zh-cn/_book.yaml @@ -4,74 +4,449 @@ upper_tabs: - contents: - path: /setup/ title: 概览 + name: 概览 + - contents: + - path: /setup/start/codelines + title: 代码行、分支和版本 + - path: /setup/start/build-numbers + title: 代号、标签和版本号 + - path: /setup/start/roles + title: 项目角色 + - path: /setup/start/brands + title: 品牌使用准则 + - path: /setup/start/licenses + title: 许可 + - path: /setup/start/faqs + title: 常见问题解答 + - path: /setup/start/p-release-notes + title: Android 9 版本说明 + - path: /setup/start/site-updates + title: 网站更新 + name: 开始 + - contents: + - path: /setup/build/requirements + title: 要求 + - path: /setup/build/initializing + title: 搭建编译环境 + - path: /setup/build/downloading + title: 下载源代码 + - path: /setup/build/building + title: 准备编译 + name: 下载 + - contents: + - path: /setup/build/devices + title: 使用参考开发板 + - path: /setup/build/gsi + title: 查找通用系统映像 + - path: /setup/build/jack + title: 使用 Jack 编译 + - path: /setup/build/running + title: 运行编译系统 + - path: /setup/build/building-kernels + title: 编译内核 + - path: /setup/build/known-issues + title: 查看已知问题 + name: 细分版本 + - contents: + - path: /setup/develop/ + title: 概览 + - path: /setup/develop/repo + title: 使用 Repo + - path: /setup/develop/new-device + title: 添加新设备 + - path: /setup/develop/64-bit-builds + title: 了解 64 位版本 + name: 开发 + - contents: + - path: /setup/contribute/ + title: 概览 + - path: /setup/contribute/life-of-a-patch + title: 补丁程序的生命周期 + - path: /setup/contribute/submit-patches + title: 提交补丁程序 + - path: /setup/contribute/view-patches + title: 查看补丁程序 + - path: /setup/contribute/life-of-a-bug + title: Bug 的生命周期 + - path: /setup/contribute/report-bugs + title: 报告 Bug + - path: /setup/contribute/read-bug-reports + title: 阅读 Bug 报告 + - path: /setup/contribute/code-style + title: Java 代码样式规则 + name: 做出贡献 + - contents: + - path: /setup/community + title: 社区 + name: 联系信息 + name: 设置 +- lower_tabs: + other: + - contents: + - path: /compatibility/ + title: 设计 Android 设备 + name: 概览 + - contents: + - path: /devices/architecture/ + title: 概览 - section: - - path: /setup/start/codelines - title: 代码行、分支和版本 - - path: /setup/start/build-numbers - title: 代号、标签和版本号 - - path: /setup/start/roles - title: 项目角色 - - path: /setup/start/brands - title: 品牌使用准则 - - path: /setup/start/licenses - title: 许可 - - path: /setup/start/faqs - title: 常见问题解答 - - path: /setup/start/site-updates - title: 网站动态 - title: 开始使用 - - section: - - path: /setup/build/requirements - title: 要求 - - path: /setup/build/initializing - title: 搭建编译环境 - - path: /setup/build/downloading - title: 下载源代码 - - path: /setup/build/building - title: 准备编译 - - path: /setup/build/jack - title: 使用 Jack 编译 - - path: /setup/build/devices - title: 使用参考开发板 - - path: /setup/build/running - title: 运行版本 - - path: /setup/build/building-kernels - title: 编译内核 - - path: /setup/build/known-issues - title: 已知问题 - title: 下载和编译 - - section: - - path: /setup/develop/ + - path: /devices/architecture/hal + title: HAL + - path: /devices/architecture/hal-types + title: HAL 类型 + - path: /devices/architecture/hal/framework-testing + title: 框架测试 + - path: /devices/architecture/hal/dynamic-lifecycle + title: 动态生命周期 + title: 硬件抽象层 (HAL) + - section: + - path: /devices/architecture/kernel/ title: 概览 - - path: /setup/develop/repo - title: 使用 Repo - - path: /setup/develop/new-device - title: 添加新设备 - - path: /setup/develop/64-bit-builds - title: 了解 64 位版本 - title: 开发 - - section: - - path: /setup/contribute/ + - path: /devices/architecture/kernel/releases + title: 稳定版本和更新 + - path: /devices/architecture/kernel/android-common + title: Android 通用内核 + - path: /devices/architecture/kernel/modular-kernels + title: 模块化内核要求 + - path: /devices/architecture/kernel/reqs-interfaces + title: 接口要求 + - path: /devices/architecture/kernel/config + title: 配置 + - path: /devices/architecture/kernel/hardening + title: 内核加固 + - path: /devices/architecture/kernel/squashfs + title: SquashFS + - path: /devices/architecture/kernel/lldb-debug + title: LLDB 调试 + - path: /devices/architecture/kernel/network_tests + title: 网络测试 + title: 内核 + - section: + - path: /devices/architecture/hidl/ title: 概览 - - path: /setup/contribute/life-of-a-patch - title: 补丁程序的生命周期 - - path: /setup/contribute/submit-patches - title: 提交补丁程序 - - path: /setup/contribute/view-patches - title: 查看补丁程序 - - path: /setup/contribute/life-of-a-bug - title: Bug 的生命周期 - - path: /setup/contribute/report-bugs - title: 报告 Bug - - path: /setup/contribute/read-bug-reports - title: 阅读 Bug 报告 - - path: /setup/contribute/code-style - title: Java 代码样式规则 - title: 赋值 - - path: /setup/community - title: 社区 + - path: /devices/architecture/hidl/interfaces + title: 接口和软件包 + - path: /devices/architecture/hidl/hashing + title: 接口哈希 + - path: /devices/architecture/hidl/services + title: 服务和数据转移 + - path: /devices/architecture/hidl/fmq + title: 快速消息队列 + - path: /devices/architecture/hidl/binder-ipc + title: 使用 Binder IPC + - path: /devices/architecture/hidl/memoryblock + title: 使用 MemoryBlock + - path: /devices/architecture/hidl/network-stack + title: 网络堆栈配置工具 + - path: /devices/architecture/hidl/threading + title: 线程模型 + - path: /devices/architecture/hidl/converting + title: 转换模块 + - path: /devices/architecture/hidl/types + title: 数据类型 + - path: /devices/architecture/hidl/versioning + title: 版本控制 + - path: /devices/architecture/hidl/code-style + title: 代码样式指南 + title: HIDL（一般信息） + - section: + - path: /devices/architecture/hidl-cpp/ + title: 概览 + - path: /devices/architecture/hidl-cpp/packages + title: 软件包 + - path: /devices/architecture/hidl-cpp/interfaces + title: 接口 + - path: /devices/architecture/hidl-cpp/types + title: 数据类型 + - path: /devices/architecture/hidl-cpp/functions + title: 函数 + title: HIDL (C++) + - section: + - path: /devices/architecture/hidl-java/ + title: 概览 + - path: /devices/architecture/hidl-java/types + title: 数据类型 + - path: /devices/architecture/hidl-java/interfaces + title: 接口错误和方法 + - path: /devices/architecture/hidl-java/constants + title: 导出常量 + title: HIDL (Java) + - section: + - path: /devices/architecture/configstore/ + title: 概览 + - path: /devices/architecture/configstore/interface + title: 创建 HAL 接口 + - path: /devices/architecture/configstore/service + title: 实现服务 + - path: /devices/architecture/configstore/client + title: 客户端使用情况 + - path: /devices/architecture/configstore/add-class-item + title: 添加类和项 + title: ConfigStore HAL + - section: + - path: /devices/architecture/dto/ + title: 概览 + - path: /devices/architecture/dto/implement + title: 实现 DTO + - path: /devices/architecture/dto/syntax + title: DTO 语法 + - path: /devices/architecture/dto/compile + title: 编译和验证 + - path: /devices/architecture/dto/multiple + title: 使用多个 DT + - path: /devices/architecture/dto/partitions + title: DTB/DTBO 分区格式 + - path: /devices/architecture/dto/optimize + title: 优化 DTO + title: 设备树叠加层 + - section: + - path: /devices/architecture/vndk/ + title: 概览 + - path: /devices/architecture/vndk/enabling + title: 启用 VNDK + - path: /devices/architecture/vndk/build-system + title: VNDK 编译系统支持 + - path: /devices/architecture/vndk/extensions + title: VNDK 扩展 + - path: /devices/architecture/vndk/deftool + title: VNDK 定义工具 + - path: /devices/architecture/vndk/snapshot-design + title: VNDK 快照设计 + - path: /devices/architecture/vndk/snapshot-generate + title: 生成 VNDK 快照 + - path: /devices/architecture/vndk/linker-namespace + title: 链接器命名空间 + - path: /devices/architecture/vndk/dir-rules-sepolicy + title: 目录、规则和 sepolicy + - path: /devices/architecture/vndk/renderscript + title: Renderscript + - path: /devices/architecture/vndk/abi-stability + title: ABI 稳定性 + title: 供应商 NDK + - section: + - path: /devices/architecture/vintf/ + title: 概览 + - path: /devices/architecture/vintf/objects + title: 清单 + - path: /devices/architecture/vintf/comp-matrices + title: 兼容性矩阵 + - path: /devices/architecture/vintf/fcm + title: FCM 生命周期 + - path: /devices/architecture/vintf/dm + title: 制定设备清单 + - path: /devices/architecture/vintf/match-rules + title: 匹配规则 + - path: /devices/architecture/vintf/resources + title: 资源 + title: 供应商接口对象 + - section: + - path: /devices/bootloader + title: 概览 + - path: /devices/bootloader/boot-reason + title: 启动原因 + - path: /devices/bootloader/boot-image-header + title: 启动映像标头 + - path: /devices/bootloader/system-as-root + title: system-as-root + - path: /devices/bootloader/partitions-images + title: 分区和映像 + - path: /devices/bootloader/product-partitions + title: /product 分区 + - path: /devices/bootloader/recovery-image + title: 恢复映像 + - path: /devices/bootloader/flashing-updating + title: 刷写和更新 + - path: /devices/bootloader/unlock-trusty + title: 解锁和 Trusty + title: 引导加载程序 + name: 架构 + - contents: + - path: /compatibility/overview + title: 概览 + - path: /compatibility/cdd/ + title: 兼容性定义文档 + - path: /compatibility/android-cdd + title: 兼容性定义文档（HTML 格式） + - path: /compatibility/android-cdd.pdf + title: 兼容性定义文档（PDF 格式） + name: 兼容性 + - contents: + - path: /devices/tech/display/ + title: 概览 + - path: /devices/tech/display/adaptive-icons + title: 自适应图标 + - path: /devices/tech/display/app-shortcuts + title: 应用快捷方式 + - path: /devices/tech/display/circular-icons + title: 圆形图标 + - path: /devices/tech/display/color-mgmt + title: 颜色管理 + - path: /devices/tech/display/display-cutouts + title: 显示屏凹口 + - path: /devices/tech/display/dnd + title: 勿扰 + - path: /devices/tech/display/hdr + title: HDR 视频 + - path: /devices/tech/display/multi-window + title: 多窗口模式 + - path: /devices/tech/display/night-light + title: 夜间模式 + - path: /devices/tech/display/pip + title: 画中画 + - path: /devices/tech/display/retail-mode + title: 零售演示模式 + - path: /devices/tech/display/rotate-suggestions + title: 旋转建议 + - path: /devices/tech/display/split-screen + title: 分屏交互 + - path: /devices/tech/display/synched-app-transitions + title: 同步应用转换 + - path: /devices/tech/display/textclassifier + title: 文本分类 + - path: /devices/tech/display/widgets-shortcuts + title: 微件和快捷方式 + name: 显示 + - contents: + - path: /devices/tech/settings/settings-guidelines + title: 设计指南 + - path: /devices/tech/settings/patterns-components + title: 模式和组件 + - path: /devices/tech/settings/info-architecture + title: 信息架构 + - path: /devices/tech/settings/personalized + title: 个性化设置 + - path: /devices/tech/settings/universal-search + title: 通用搜索 name: 设置 - name: 设置 + - contents: + - path: /compatibility/tests + title: 概览 + - section: + - path: /compatibility/cts/ + title: 概览 + - path: /compatibility/cts/setup + title: 设置 CTS + - path: /compatibility/cts/run + title: 运行 CTS + - section: + - path: /compatibility/cts/verifier + title: 概览 + - path: /compatibility/cts/audio-framework + title: 音频框架 + - path: /compatibility/cts/near-ultrasound + title: 近超声测试 + - path: /compatibility/cts/rotation-vector + title: 旋转矢量交叉检验 + - path: /compatibility/cts/usb-audio + title: USB 音频 CTS 测试 + title: 运行 CTS 验证程序 + - section: + - path: /compatibility/cts/camera-hal + title: 相机 HAL 测试 + - path: /compatibility/cts/camera-its-box + title: 相机盒装 ITS + - path: /compatibility/cts/camera-its-box-assembly + title: 组装相机盒装 ITS + - path: /compatibility/cts/sensor-fusion-quick-start + title: 传感器融合盒快速入门 + - path: /compatibility/cts/sensor-fusion-box-assembly + title: 组装传感器融合盒 + title: 相机测试 + - path: /compatibility/cts/secure-element + title: 安全要素 + - path: /compatibility/cts/interpret + title: 解读结果 + - path: /compatibility/cts/development + title: CTS 开发 + - path: /compatibility/cts/downloads + title: 下载 + title: 兼容性测试套件 + - section: + - path: /compatibility/vts/ + title: 概览 + - path: /compatibility/vts/systems + title: 使用 VTS 进行系统测试 + - section: + - path: /compatibility/vts/shell-commands + title: 设备 shell 命令 + - path: /compatibility/vts/test-templates + title: 测试模板 + - path: /compatibility/vts/sna-hal-testing + title: 服务名称感知 HAL 测试 + - path: /compatibility/vts/hal-testability + title: HAL 可测试性检查 + - path: /compatibility/vts/multi-device-testing + title: 多设备测试 + title: 测试框架 + - section: + - path: /compatibility/vts/setup + title: 设置 + - path: /compatibility/vts/database + title: 数据库 + - path: /compatibility/vts/ui + title: 界面 + title: VTS 信息中心 + - section: + - path: /compatibility/vts/automated-test-infra + title: 自动化测试基础架构 + - path: /compatibility/vts/host-controller + title: 主机控制器架构 + title: 实验室基础架构 + - path: /compatibility/vts/performance + title: 性能测试 + title: 供应商测试套件 (VTS) + - section: + - path: /devices/tech/test_infra/tradefed/ + title: 概览 + - path: /devices/tech/test_infra/tradefed/fundamentals + title: 开始使用 + - path: /devices/tech/test_infra/tradefed/fundamentals/machine_setup + title: 机器设置 + - path: /devices/tech/test_infra/tradefed/fundamentals/devices + title: 测试设备 + - path: /devices/tech/test_infra/tradefed/fundamentals/lifecycle + title: 测试生命周期 + - path: /devices/tech/test_infra/tradefed/fundamentals/options + title: 选项处理 + - path: /devices/tech/test_infra/tradefed/full_example + title: 端到端示例 + - path: /reference/tradefed/ + title: 软件包索引 + title: 测试基础架构 + - section: + - path: /devices/tech/debug/ + title: 概览 + - path: /devices/tech/debug/native-crash + title: 诊断原生代码崩溃问题 + - section: + - path: /devices/tech/debug/eval_perf + title: 概览 + - path: /devices/tech/debug/systrace + title: 了解 systrace + - path: /devices/tech/debug/ftrace + title: 使用 ftrace + - path: /devices/tech/debug/jank_capacity + title: 识别与负载能力相关的卡顿 + - path: /devices/tech/debug/jank_jitter + title: 识别与系统行为相关的卡顿 + title: 评估性能 + - path: /devices/tech/debug/gdb + title: 使用 GDB + - path: /devices/tech/debug/native-memory + title: 本地内存使用情况 + - path: /devices/tech/connect/connect_tests + title: 网络连接测试 + - path: /devices/tech/debug/rescue-party + title: 救援程序 + - path: /devices/tech/debug/storaged + title: Storaged + - path: /devices/tech/debug/strace + title: Strace + - path: /devices/tech/debug/valgrind + title: Valgrind + title: 调试 + name: 测试 + name: 设计 - lower_tabs: other: - contents: @@ -90,6 +465,8 @@ upper_tabs: - section: - path: /security/enhancements/ title: 概览 + - path: /security/enhancements/enhancements9 + title: Android 9 - path: /security/enhancements/enhancements80 title: Android 8.0 - path: /security/enhancements/enhancements70 @@ -109,143 +486,153 @@ upper_tabs: title: 增强功能 - path: /security/overview/acknowledgements title: 致谢 + name: 概览 + - contents: + - path: /security/bulletin/ + title: 概览 - section: - - path: /security/bulletin/ + - path: /security/advisory/ title: 概览 + - path: /security/advisory/2016-03-18 + title: 2016 年 3 月 + title: 公告 + - section: - section: - - path: /security/advisory/ - title: 概览 - - path: /security/advisory/2016-03-18 - title: 2016 年 3 月 - title: 公告 + - path: /security/bulletin/2018-08-01 + title: 8 月 + - path: /security/bulletin/2018-07-01 + title: 7 月 + - path: /security/bulletin/2018-06-01 + title: 6 月 + - path: /security/bulletin/2018-05-01 + title: 5 月 + - path: /security/bulletin/2018-04-01 + title: 4 月 + - path: /security/bulletin/2018-03-01 + title: 3 月 + - path: /security/bulletin/2018-02-01 + title: 2 月 + - path: /security/bulletin/2018-01-01 + title: 1 月 + - path: /security/bulletin/2018 + title: 索引 + title: 2018 年公告 - section: - - section: - - path: /security/bulletin/2018-07-01 - title: 7 月 - - path: /security/bulletin/2018-06-01 - title: 6 月 - - path: /security/bulletin/2018-05-01 - title: 5 月 - - path: /security/bulletin/2018-04-01 - title: 4 月 - - path: /security/bulletin/2018-03-01 - title: 3 月 - - path: /security/bulletin/2018-02-01 - title: 2 月 - - path: /security/bulletin/2018-01-01 - title: 1 月 - - path: /security/bulletin/2018 - title: 索引 - title: 2018 年公告 - - section: - - path: /security/bulletin/2017-12-01 - title: 12 月 - - path: /security/bulletin/2017-11-01 - title: 11 月 - - path: /security/bulletin/2017-10-01 - title: 10 月 - - path: /security/bulletin/2017-09-01 - title: 9 月 - - path: /security/bulletin/2017-08-01 - title: 8 月 - - path: /security/bulletin/2017-07-01 - title: 7 月 - - path: /security/bulletin/2017-06-01 - title: 6 月 - - path: /security/bulletin/2017-05-01 - title: 5 月 - - path: /security/bulletin/2017-04-01 - title: 4 月 - - path: /security/bulletin/2017-03-01 - title: 3 月 - - path: /security/bulletin/2017-02-01 - title: 2 月 - - path: /security/bulletin/2017-01-01 - title: 1 月 - - path: /security/bulletin/2017 - title: 索引 - title: 2017 年公告 - - section: - - path: /security/bulletin/2016-12-01 - title: 12 月 - - path: /security/bulletin/2016-11-01 - title: 11 月 - - path: /security/bulletin/2016-10-01 - title: 10 月 - - path: /security/bulletin/2016-09-01 - title: 9 月 - - path: /security/bulletin/2016-08-01 - title: 8 月 - - path: /security/bulletin/2016-07-01 - title: 7 月 - - path: /security/bulletin/2016-06-01 - title: 6 月 - - path: /security/bulletin/2016-05-01 - title: 5 月 - - path: /security/bulletin/2016-04-02 - title: 4 月 - - path: /security/bulletin/2016-03-01 - title: 3 月 - - path: /security/bulletin/2016-02-01 - title: 2 月 - - path: /security/bulletin/2016-01-01 - title: 1 月 - - path: /security/bulletin/2016 - title: 索引 - title: 2016 年公告 - - section: - - path: /security/bulletin/2015-12-01 - title: 12 月 - - path: /security/bulletin/2015-11-01 - title: 11 月 - - path: /security/bulletin/2015-10-01 - title: 10 月 - - path: /security/bulletin/2015-09-01 - title: 9 月 - - path: /security/bulletin/2015-08-01 - title: 8 月 - - path: /security/bulletin/2015 - title: 索引 - title: 2015 年公告 - title: Android 公告 + - path: /security/bulletin/2017-12-01 + title: 12 月 + - path: /security/bulletin/2017-11-01 + title: 11 月 + - path: /security/bulletin/2017-10-01 + title: 10 月 + - path: /security/bulletin/2017-09-01 + title: 9 月 + - path: /security/bulletin/2017-08-01 + title: 8 月 + - path: /security/bulletin/2017-07-01 + title: 7 月 + - path: /security/bulletin/2017-06-01 + title: 6 月 + - path: /security/bulletin/2017-05-01 + title: 5 月 + - path: /security/bulletin/2017-04-01 + title: 4 月 + - path: /security/bulletin/2017-03-01 + title: 3 月 + - path: /security/bulletin/2017-02-01 + title: 2 月 + - path: /security/bulletin/2017-01-01 + title: 1 月 + - path: /security/bulletin/2017 + title: 索引 + title: 2017 年公告 - section: - - path: /security/bulletin/pixel/index - title: 概览 - - section: - - path: /security/bulletin/pixel/2018-07-01 - title: 7 月 - - path: /security/bulletin/pixel/2018-06-01 - title: 6 月 - - path: /security/bulletin/pixel/2018-05-01 - title: 5 月 - - path: /security/bulletin/pixel/2018-04-01 - title: 4 月 - - path: /security/bulletin/pixel/2018-03-01 - title: 3 月 - - path: /security/bulletin/pixel/2018-02-01 - title: 2 月 - - path: /security/bulletin/pixel/2018-01-01 - title: 1 月 - - path: /security/bulletin/pixel/2018 - title: 索引 - title: 2018 年公告 - - section: - - path: /security/bulletin/pixel/2017-12-01 - title: 12 月 - - path: /security/bulletin/pixel/2017-11-01 - title: 11 月 - - path: /security/bulletin/pixel/2017-10-01 - title: 10 月 - - path: /security/bulletin/pixel/2017 - title: 索引 - title: 2017 年公告 - title: Pixel/Nexus 公告 - title: 公告 + - path: /security/bulletin/2016-12-01 + title: 12 月 + - path: /security/bulletin/2016-11-01 + title: 11 月 + - path: /security/bulletin/2016-10-01 + title: 10 月 + - path: /security/bulletin/2016-09-01 + title: 9 月 + - path: /security/bulletin/2016-08-01 + title: 8 月 + - path: /security/bulletin/2016-07-01 + title: 7 月 + - path: /security/bulletin/2016-06-01 + title: 6 月 + - path: /security/bulletin/2016-05-01 + title: 5 月 + - path: /security/bulletin/2016-04-02 + title: 4 月 + - path: /security/bulletin/2016-03-01 + title: 3 月 + - path: /security/bulletin/2016-02-01 + title: 2 月 + - path: /security/bulletin/2016-01-01 + title: 1 月 + - path: /security/bulletin/2016 + title: 索引 + title: 2016 年公告 + - section: + - path: /security/bulletin/2015-12-01 + title: 12 月 + - path: /security/bulletin/2015-11-01 + title: 11 月 + - path: /security/bulletin/2015-10-01 + title: 10 月 + - path: /security/bulletin/2015-09-01 + title: 9 月 + - path: /security/bulletin/2015-08-01 + title: 8 月 + - path: /security/bulletin/2015 + title: 索引 + title: 2015 年公告 + title: Android 公告 + - section: + - path: /security/bulletin/pixel/index + title: 概览 + - section: + - path: /security/bulletin/pixel/2018-08-01 + title: 8 月 + - path: /security/bulletin/pixel/2018-07-01 + title: 7 月 + - path: /security/bulletin/pixel/2018-06-01 + title: 6 月 + - path: /security/bulletin/pixel/2018-05-01 + title: 5 月 + - path: /security/bulletin/pixel/2018-04-01 + title: 4 月 + - path: /security/bulletin/pixel/2018-03-01 + title: 3 月 + - path: /security/bulletin/pixel/2018-02-01 + title: 2 月 + - path: /security/bulletin/pixel/2018-01-01 + title: 1 月 + - path: /security/bulletin/pixel/2018 + title: 索引 + title: 2018 年公告 + - section: + - path: /security/bulletin/pixel/2017-12-01 + title: 12 月 + - path: /security/bulletin/pixel/2017-11-01 + title: 11 月 + - path: /security/bulletin/pixel/2017-10-01 + title: 10 月 + - path: /security/bulletin/pixel/2017 + title: 索引 + title: 2017 年公告 + title: Pixel/Nexus 公告 + name: 公告 + - contents: + - path: /security/app-sandbox + title: 应用沙盒 - section: - path: /security/apksigning/ title: 概览 - path: /security/apksigning/v2 - title: APK 签名架构 v2 + title: APK 签名方案 v2 + - path: /security/apksigning/v3 + title: APK 签名方案 v3 title: 应用签名 - section: - path: /security/authentication/ @@ -255,7 +642,11 @@ upper_tabs: - path: /security/authentication/gatekeeper title: Gatekeeper title: 身份验证 - - path: /security/biometric/ + - section: + - path: /security/biometric/ + title: 概览 + - path: /security/biometric/measure + title: 衡量生物识别安全性 title: 生物识别解锁 - section: - path: /security/keystore/ @@ -284,6 +675,8 @@ upper_tabs: title: 文件级加密 - path: /security/encryption/full-disk title: 全盘加密 + - path: /security/encryption/metadata + title: 元数据加密 title: 加密 - section: - path: /security/selinux/ @@ -294,334 +687,282 @@ upper_tabs: title: 实现 - path: /security/selinux/customize title: 自定义 + - path: /security/selinux/build + title: 编译 sepolicy + - path: /security/selinux/compatibility + title: 兼容性 - path: /security/selinux/validate title: 验证 - path: /security/selinux/device-policy - title: 撰写策略 + title: 编写策略 + - path: /security/selinux/vendor-init + title: 供应商初始化 title: SELinux - section: - path: /security/verifiedboot/ title: 概览 + - path: /security/verifiedboot/device-state + title: 设备状态 - path: /security/verifiedboot/verified-boot title: 验证启动 + - path: /security/verifiedboot/boot-flow + title: 启动流程 - path: /security/verifiedboot/dm-verity title: 实现 dm-verity + - path: /security/verifiedboot/avb + title: 参考实现 title: 验证启动 - name: 安全性 + name: 功能 + - contents: + - path: /devices/tech/debug/fuzz-sanitize + title: 概览 + - path: /devices/tech/debug/asan + title: AddressSanitizer + - path: /devices/tech/debug/sanitizers + title: LLVM 排错程序 + - path: /devices/tech/debug/kasan-kcov + title: 使用 KASAN + KCOV 编译内核 + - path: /devices/tech/debug/libfuzzer + title: 通过 libFuzzer 进行模糊测试 + - path: /devices/tech/debug/cfi + title: 控制流完整性 (CFI) + - path: /devices/tech/debug/kcfi + title: 内核 CFI + - path: /devices/tech/debug/intsan + title: 整数溢出清理 + name: 动态分析 name: 安全性 - lower_tabs: other: - contents: - - path: /devices/ + - path: /devices/audio/ title: 概览 + - path: /devices/audio/terminology + title: 术语 - section: - - path: /devices/architecture/ + - path: /devices/audio/implement title: 概览 - - path: /devices/architecture/hal - title: 硬件抽象层 (HAL) - - path: /devices/architecture/hal-types - title: HAL 类型 - - section: - - path: /devices/architecture/kernel/ - title: 概览 - - path: /devices/architecture/kernel/releases - title: 稳定版本和更新 - - path: /devices/architecture/kernel/android-common - title: Android 通用内核 - - path: /devices/architecture/kernel/modular-kernels - title: 模块化内核要求 - - path: /devices/architecture/kernel/reqs-interfaces - title: 接口要求 - - path: /devices/architecture/kernel/config - title: 配置 - - path: /devices/architecture/kernel/hardening - title: 内核加固 - - path: /devices/architecture/kernel/squashfs - title: SquashFS - - path: /devices/architecture/kernel/lldb-debug - title: LLDB 调试 - - path: /devices/architecture/kernel/network_tests - title: 网络测试 - title: 内核 - - section: - - path: /devices/architecture/hidl/ - title: 概览 - - path: /devices/architecture/hidl/interfaces - title: 接口和软件包 - - path: /devices/architecture/hidl/hashing - title: 接口哈希 - - path: /devices/architecture/hidl/services - title: 服务和数据转移 - - path: /devices/architecture/hidl/fmq - title: 快速消息队列 - - path: /devices/architecture/hidl/binder-ipc - title: 使用 Binder IPC - - path: /devices/architecture/hidl/network-stack - title: 网络堆栈配置工具 - - path: /devices/architecture/hidl/threading - title: 线程模型 - - path: /devices/architecture/hidl/converting - title: 转换模块 - - path: /devices/architecture/hidl/types - title: 数据类型 - - path: /devices/architecture/hidl/versioning - title: 版本控制 - - path: /devices/architecture/hidl/code-style - title: 代码样式指南 - title: HIDL（一般信息） - - section: - - path: /devices/architecture/hidl-cpp/ - title: 概览 - - path: /devices/architecture/hidl-cpp/packages - title: 软件包 - - path: /devices/architecture/hidl-cpp/interfaces - title: 接口 - - path: /devices/architecture/hidl-cpp/types - title: 数据类型 - - path: /devices/architecture/hidl-cpp/functions - title: 函数 - title: HIDL (C++) - - section: - - path: /devices/architecture/hidl-java/ - title: 概览 - - path: /devices/architecture/hidl-java/types - title: 数据类型 - - path: /devices/architecture/hidl-java/interfaces - title: 接口错误和方法 - - path: /devices/architecture/hidl-java/constants - title: 导出常量 - title: HIDL (Java) - - section: - - path: /devices/architecture/configstore/ - title: 概览 - - path: /devices/architecture/configstore/interface - title: 创建 HAL 接口 - - path: /devices/architecture/configstore/service - title: 实现服务 - - path: /devices/architecture/configstore/client - title: 客户端使用情况 - - path: /devices/architecture/configstore/add-class-item - title: 添加类和项 - title: ConfigStore HAL - - section: - - path: /devices/architecture/dto/ - title: 概览 - - path: /devices/architecture/dto/implement - title: 实现 DTO - - path: /devices/architecture/dto/syntax - title: DTO 语法 - - path: /devices/architecture/dto/compile - title: 编译和验证 - - path: /devices/architecture/dto/multiple - title: 使用多个 DT - - path: /devices/architecture/dto/partitions - title: DTB/DTBO 分区格式 - - path: /devices/architecture/dto/optimize - title: 优化 DTO - title: 设备树叠加层 - - section: - - path: /devices/architecture/vndk/ - title: 概览 - - path: /devices/architecture/vndk/enabling - title: 启用 VNDK - - path: /devices/architecture/vndk/build-system - title: VNDK 编译系统支持 - - path: /devices/architecture/vndk/extensions - title: VNDK 扩展 - - path: /devices/architecture/vndk/deftool - title: VNDK 定义工具 - - path: /devices/architecture/vndk/linker-namespace - title: 链接器命名空间 - - path: /devices/architecture/vndk/dir-rules-sepolicy - title: 目录、规则和 sepolicy - - path: /devices/architecture/vndk/renderscript - title: Renderscript - title: 供应商 NDK - - section: - - path: /devices/architecture/vintf/ - title: 概览 - - path: /devices/architecture/vintf/objects - title: VINTF 对象数据 - - path: /devices/architecture/vintf/comp-matrices - title: 兼容性矩阵 - - path: /devices/architecture/vintf/match-rules - title: 匹配规则 - - path: /devices/architecture/vintf/resources - title: 资源 - title: 供应商接口对象 - title: 架构 - - section: - - path: /devices/audio/ + - path: /devices/audio/implement-policy + title: 策略配置 + - path: /devices/audio/implement-shared-library + title: 共享库 + - path: /devices/audio/implement-pre-processing + title: 预处理效果 + title: 实现 + - path: /devices/audio/data_formats + title: 数据格式 + - path: /devices/audio/attributes + title: 属性 + - path: /devices/audio/highres-effects + title: 高分辨率效果 + - path: /devices/audio/aaudio + title: AAudio 和 MMAP + - path: /devices/audio/warmup + title: 预热 + - section: + - path: /devices/audio/latency/latency title: 概览 - - path: /devices/audio/terminology - title: 术语 - - section: - - path: /devices/audio/implement - title: 概览 - - path: /devices/audio/implement-policy - title: 策略配置 - - path: /devices/audio/implement-shared-library - title: 共享库 - - path: /devices/audio/implement-pre-processing - title: 预处理效果 - title: 实现 - - path: /devices/audio/data_formats - title: 数据格式 - - path: /devices/audio/attributes - title: 属性 - - path: /devices/audio/aaudio - title: AAudio 和 MMAP - - path: /devices/audio/warmup - title: 预热 - - section: - - path: /devices/audio/latency/latency - title: 概览 - - path: /devices/audio/latency/contrib - title: 影响因素 - - path: /devices/audio/latency/design - title: 设计 - - path: /devices/audio/latency/measure - title: 衡量 - - path: /devices/audio/latency/testing_circuit - title: 灯光测试电路 - - path: /devices/audio/latency/loopback - title: 音频环回适配器 - - path: /devices/audio/latency/measurements - title: 测量结果 - - path: /devices/audio/latency/app - title: 应用 - title: 延迟 - - path: /devices/audio/avoiding_pi - title: 优先级倒置 - - path: /devices/audio/src - title: 采样率转换 - - path: /devices/audio/debugging - title: 调试 - - section: - - path: /devices/audio/midi - title: 概览 - - path: /devices/audio/midi_arch - title: MIDI 架构 - - path: /devices/audio/midi_test - title: MIDI 测试程序 - title: MIDI - - path: /devices/audio/usb - title: USB 数字音频 - - path: /devices/audio/tv - title: 电视音频 - title: 音频 + - path: /devices/audio/latency/contrib + title: 影响因素 + - path: /devices/audio/latency/design + title: 设计 + - path: /devices/audio/latency/measure + title: 衡量 + - path: /devices/audio/latency/testing_circuit + title: 灯光测试电路 + - path: /devices/audio/latency/loopback + title: 音频环回适配器 + - path: /devices/audio/latency/measurements + title: 测量结果 + - path: /devices/audio/latency/app + title: 应用 + title: 延迟 + - path: /devices/audio/avoiding_pi + title: 优先级倒置 + - path: /devices/audio/src + title: 采样率转换 + - path: /devices/audio/debugging + title: 调试 - section: - - path: /devices/automotive/ + - path: /devices/audio/midi title: 概览 - - path: /devices/automotive/properties - title: 车辆属性 - - path: /devices/automotive/camera-hal - title: 相机 HAL - - path: /devices/automotive/ivi_connectivity - title: IVI 连接 - title: 汽车 + - path: /devices/audio/midi_arch + title: MIDI 架构 + - path: /devices/audio/midi_test + title: MIDI 测试程序 + title: MIDI + - path: /devices/audio/usb + title: USB 数字音频 + - path: /devices/audio/tv + title: 电视音频 + name: 音频 + - contents: + - path: /devices/camera/ + title: 概览 + - path: /devices/camera/camera3 + title: Camera3 + - path: /devices/camera/camera3_requests_hal + title: HAL 子系统 + - path: /devices/camera/camera3_metadata + title: 元数据和控件 + - path: /devices/camera/camera3_3Amodes + title: 3A 模式和状态 + - path: /devices/camera/camera3_crop_reprocess + title: 输出和剪裁 + - path: /devices/camera/camera3_error_stream + title: 错误和数据流 + - path: /devices/camera/camera3_requests_methods + title: 创建请求 + - path: /devices/camera/external-usb-cameras + title: 外接 USB 摄像头 + - path: /devices/camera/multi-camera + title: 多摄像头支持 + - path: /devices/camera/motion-tracking + title: 运动跟踪 + - path: /devices/camera/session-parameters + title: 会话参数 + - path: /devices/camera/singleprod-multiconsum + title: 单一生产方，多个消费方 + - path: /devices/camera/versioning + title: 版本支持 + name: 相机 + - contents: + - path: /devices/tech/connect/ + title: 概览 - section: - path: /devices/bluetooth title: 概览 - path: /devices/bluetooth/services - title: 服务 + title: 蓝牙服务 - path: /devices/bluetooth/ble title: 蓝牙低功耗 - path: /devices/bluetooth/ble_advertising - title: BLE 广告 + title: BLE 广播 - path: /devices/bluetooth/verifying_debugging - title: 验证和调试 + title: 验证和调试蓝牙 - path: /devices/bluetooth/hci_requirements - title: HCI 要求 - title: 蓝牙 + title: 蓝牙 HCI 要求 + - path: /devices/tech/connect/felica + title: FeliCa 的 NFC 主机卡模拟 + title: 蓝牙和 NFC - section: - - path: /devices/bootloader + - path: /devices/tech/connect/block-numbers + title: 屏蔽电话号码 + - path: /devices/tech/connect/call-notification + title: 来电通知 + - path: /devices/tech/connect/emergency-affordance + title: 紧急呼叫 + - path: /devices/tech/connect/ims + title: IP 多媒体子系统 (IMS) + - path: /devices/tech/connect/rtt + title: 实时信息 (RTT) + - path: /devices/tech/connect/third-party-call-apps + title: 第三方通话应用 + title: 通话和短信 + - section: + - path: /devices/tech/config/carrier title: 概览 - - path: /devices/bootloader/partitions-images - title: 分区和映像 - - path: /devices/bootloader/flashing-updating - title: 刷写和更新 - - path: /devices/bootloader/unlock-trusty - title: 解锁和 Trusty - title: 引导加载程序 + - path: /devices/tech/config/update + title: APN 和 CarrierConfig + - path: /devices/tech/config/carrierid + title: 运营商识别号 + - path: /devices/tech/connect/data-plans + title: 流量套餐 + - section: + - path: /devices/tech/connect/esim-overview + title: 实现 eSIM + - path: /devices/tech/connect/esim-modem-requirements + title: 调制解调器要求 + - path: /devices/tech/connect/esim-euicc-api + title: eUICC API + title: eSIM + - path: /devices/tech/connect/oob-users + title: 流量用尽的用户 + - path: /devices/tech/connect/ril + title: 无线接口层 (RIL) + - path: /devices/tech/config/uicc + title: UICC + title: 运营商 - section: - - path: /devices/camera/ + - path: /devices/tech/connect/wifi-overview title: 概览 - - path: /devices/camera/camera3 - title: Camera3 - - path: /devices/camera/camera3_requests_hal - title: HAL 子系统 - - path: /devices/camera/camera3_metadata - title: 元数据和控件 - - path: /devices/camera/camera3_3Amodes - title: 3A 模式和状态 - - path: /devices/camera/camera3_crop_reprocess - title: 输出和剪裁 - - path: /devices/camera/camera3_error_stream - title: 错误和数据流 - - path: /devices/camera/camera3_requests_methods - title: 创建请求 - - path: /devices/camera/versioning - title: 版本支持 - title: 相机 - - path: /devices/drm - title: DRM + - path: /devices/tech/connect/wifi-hal + title: WLAN HAL + - path: /devices/tech/connect/wifi-infrastructure + title: Wi-Fi Infrastructure Features + - path: /devices/tech/connect/wifi-sta-ap-concurrency + title: STA/AP 并发 + - path: /devices/tech/connect/wifi-mac-randomization + title: 随机分配 MAC 地址 + - path: /devices/tech/connect/wifi-passpoint + title: Passpoint R1 + - path: /devices/tech/connect/carrier-wifi + title: 运营商 WLAN + - path: /devices/tech/connect/wifi-aware + title: WLAN 感知 + - path: /devices/tech/connect/wifi-rtt + title: WLAN 往返时间 (RTT) + - path: /devices/tech/connect/wifi-debug + title: 测试和调试 + title: WLAN + name: 连接 + - contents: + - path: /devices/graphics/ + title: 概览 - section: - - path: /devices/graphics/ + - path: /devices/graphics/architecture title: 概览 - - section: - - path: /devices/graphics/architecture - title: 概览 - - path: /devices/graphics/arch-bq-gralloc - title: BufferQueue - - path: /devices/graphics/arch-sf-hwc - title: SurfaceFlinger 和 HWC - - path: /devices/graphics/arch-sh - title: Surface 和 SurfaceHolder - - path: /devices/graphics/arch-egl-opengl - title: OpenGL ES - - path: /devices/graphics/renderer - title: OpenGLRenderer 配置 - - path: /devices/graphics/arch-vulkan - title: Vulkan - - path: /devices/graphics/arch-sv-glsv - title: SurfaceView - - path: /devices/graphics/arch-st - title: SurfaceTexture - - path: /devices/graphics/arch-tv - title: TextureView - - path: /devices/graphics/arch-gameloops - title: 游戏循环 - title: 架构 - - section: - - path: /devices/graphics/implement - title: 概览 - - path: /devices/graphics/implement-hwc - title: 硬件混合渲染器 HAL - - path: /devices/graphics/implement-vsync - title: VSYNC - - path: /devices/graphics/implement-vulkan - title: Vulkan - - path: /devices/graphics/implement-vdisplays - title: 虚拟显示屏 - title: 实现 - - section: - - path: /devices/graphics/testing - title: 概览 - - path: /devices/graphics/build-tests - title: 编译测试程序 - - path: /devices/graphics/port-tests - title: 移植测试框架 - - path: /devices/graphics/run-tests - title: 运行测试 - - path: /devices/graphics/automate-tests - title: 自动执行测试 - - path: /devices/graphics/test-groups - title: 使用特殊测试组 - - path: /devices/graphics/cts-integration - title: 与 Android CTS 集成 - title: OpenGL ES 测试 - title: 图形 + - path: /devices/graphics/arch-bq-gralloc + title: BufferQueue + - path: /devices/graphics/arch-sf-hwc + title: SurfaceFlinger 和 HWC + - path: /devices/graphics/arch-sh + title: Surface 和 SurfaceHolder + - path: /devices/graphics/arch-egl-opengl + title: OpenGL ES + - path: /devices/graphics/renderer + title: OpenGLRenderer 配置 + - path: /devices/graphics/arch-vulkan + title: Vulkan + - path: /devices/graphics/arch-sv-glsv + title: SurfaceView + - path: /devices/graphics/arch-st + title: SurfaceTexture + - path: /devices/graphics/arch-tv + title: TextureView + - path: /devices/graphics/arch-gameloops + title: 游戏循环 + title: 架构 + - section: + - path: /devices/graphics/implement + title: 概览 + - path: /devices/graphics/implement-hwc + title: 硬件混合渲染器 HAL + - path: /devices/graphics/implement-vsync + title: VSYNC + - path: /devices/graphics/implement-vulkan + title: Vulkan + - path: /devices/graphics/implement-vdisplays + title: 虚拟显示屏 + title: 实现 + - section: + - path: /devices/graphics/testing + title: 概览 + - path: /devices/graphics/build-tests + title: 编译测试程序 + - path: /devices/graphics/port-tests + title: 移植测试框架 + - path: /devices/graphics/run-tests + title: 运行测试 + - path: /devices/graphics/automate-tests + title: 自动执行测试 + - path: /devices/graphics/test-groups + title: 使用特殊测试组 + - path: /devices/graphics/cts-integration + title: 与 Android CTS 集成 + title: OpenGL ES 测试 + name: 图形 + - contents: - section: - path: /devices/input/ title: 概览 @@ -643,15 +984,31 @@ upper_tabs: title: 验证按键映射 title: 输入 - section: - - path: /devices/media/ + - path: /devices/automotive/ title: 概览 - - path: /devices/media/framework-hardening - title: 框架安全强化 - - path: /devices/media/soc - title: SoC 依赖项 - - path: /devices/media/oem - title: OEM 依赖项 - title: 媒体 + - section: + - path: /devices/automotive/audio/ + title: 概览 + - path: /devices/automotive/audio/audio-hal + title: 音频 HAL + - path: /devices/automotive/audio/audio-control + title: AudioControl HAL + - path: /devices/automotive/audio/interaction-sequences + title: 互动序列 + - path: /devices/automotive/audio/multi-zone + title: 多地区 + title: 音频 + - path: /devices/automotive/camera-hal + title: 相机 HAL + - path: /devices/automotive/ivi_connectivity + title: IVI 连接 + - path: /devices/automotive/properties + title: 车辆属性 + - path: /devices/tech/perf/flash-wear + title: 闪存磨损管理 + title: 汽车 + - path: /devices/interaction/neural-networks + title: 神经网络 - path: /devices/accessories section: - section: @@ -714,20 +1071,6 @@ upper_tabs: title: 版本弃用 title: 传感器 - section: - - path: /devices/storage/ - title: 概览 - - path: /devices/storage/traditional - title: 传统存储设备 - - path: /devices/storage/adoptable - title: 可合并的存储设备 - - path: /devices/storage/config - title: 设备配置 - - path: /devices/storage/config-example - title: 配置示例 - - path: /devices/storage/faster-stats - title: 更快获取统计信息 - title: 存储 - - section: - path: /devices/tv title: 概览 - path: /devices/tv/hdmi-cec @@ -736,357 +1079,190 @@ upper_tabs: title: 参考 TV 应用 - path: /devices/tv/customize-tv-app title: 自定义 TV 应用 - title: 电视 - name: 移植 - name: 移植 + title: TV + name: 互动 + - contents: + - path: /devices/media/ + title: 概览 + - path: /devices/media/framework-hardening + title: 框架安全强化 + - path: /devices/media/soc + title: SoC 依赖项 + - path: /devices/media/oem + title: OEM 依赖项 + - path: /devices/drm + title: DRM + name: 媒体 + - contents: + - path: /devices/storage/ + title: 概览 + - path: /devices/storage/traditional + title: 传统存储设备 + - path: /devices/storage/adoptable + title: 可合并的存储设备 + - path: /devices/storage/config + title: 设备配置 + - path: /devices/storage/config-example + title: 配置示例 + - path: /devices/storage/faster-stats + title: 更快获取统计信息 + name: 存储 + name: 开发 - lower_tabs: other: - contents: - - path: /devices/tech/ + - path: /devices/tech/dalvik title: 概览 - - section: - - path: /devices/tech/dalvik - title: 概览 - - path: /devices/tech/dalvik/improvements - title: 改进 - - path: /devices/tech/dalvik/dalvik-bytecode - title: 字节码格式 - - path: /devices/tech/dalvik/dex-format - title: Dex 格式 - - path: /devices/tech/dalvik/instruction-formats - title: 说明格式 - - path: /devices/tech/dalvik/constraints - title: 限制 - - path: /devices/tech/dalvik/configure - title: 配置 - - path: /devices/tech/dalvik/gc-debug - title: 垃圾回收 - - path: /devices/tech/dalvik/jit-compiler - title: JIT 编译 - title: ART 和 Dalvik - - section: - - path: /devices/tech/config/ - title: 概览 - - path: /devices/tech/config/ambient - title: Ambient 权能 - - section: - - path: /devices/tech/config/carrier - title: 运营商配置 - - path: /devices/tech/config/update - title: APN 和 CarrierConfig - - path: /devices/tech/config/uicc - title: UICC - title: 运营商定制 - - path: /devices/tech/config/filesystem - title: 文件 DAC 配置 - - path: /devices/tech/config/namespaces_libraries - title: 库的命名空间 - - path: /devices/tech/config/perms-whitelist - title: 特许权限白名单 - - path: /devices/tech/config/runtime_perms - title: 运行时权限 - - path: /devices/tech/config/timezone-rules - title: 时区规则 - - path: /devices/tech/config/usb-hal - title: USB HAL - - path: /devices/tech/config/voicemail - title: 可视化语音信箱 + - path: /devices/tech/dalvik/improvements + title: 改进 + - path: /devices/tech/dalvik/dalvik-bytecode + title: 字节码格式 + - path: /devices/tech/dalvik/dex-format + title: Dex 格式 + - path: /devices/tech/dalvik/instruction-formats + title: 说明格式 + - path: /devices/tech/dalvik/constraints + title: 限制 + - path: /devices/tech/dalvik/configure title: 配置 - - section: - - path: /devices/tech/connect/ - title: 概览 - - path: /devices/tech/connect/block-numbers - title: 屏蔽电话号码 - - path: /devices/tech/connect/call-notification - title: 来电通知 - - path: /devices/tech/connect/data-saver - title: 流量节省模式 - - path: /devices/tech/connect/emergency-affordance - title: 快速紧急呼救 - - path: /devices/tech/connect/felica - title: FeliCa 的主机卡模拟 - - path: /devices/tech/connect/oob-users - title: 流量用尽的用户 - - path: /devices/tech/connect/connect_tests - title: 网络连接测试 - - path: /devices/tech/connect/ril - title: 无线接口层 (RIL) - - path: /devices/tech/connect/wifi-aware - title: Wi-Fi Aware - title: 网络连接 - - section: - - path: /devices/tech/datausage/ - title: 概览 - - path: /devices/tech/datausage/iface-overview - title: 网络接口统计信息概览 - - path: /devices/tech/datausage/excluding-network-types - title: 从流量使用情况中排除特定网络类型 - - path: /devices/tech/datausage/tethering-data - title: 网络共享流量 - - path: /devices/tech/datausage/usage-cycle-resets-dates - title: 流量统计周期重置日期 - - path: /devices/tech/datausage/kernel-overview - title: 内核概览 - - path: /devices/tech/datausage/tags-explained - title: 流量使用情况标签说明 - - path: /devices/tech/datausage/kernel-changes - title: 内核变化 - title: 流量使用情况 - - section: - - path: /devices/tech/debug/ - title: 概览 - - path: /devices/tech/debug/native-crash - title: 诊断原生代码崩溃问题 - - section: - - path: /devices/tech/debug/eval_perf - title: 概览 - - path: /devices/tech/debug/systrace - title: 了解 systrace - - path: /devices/tech/debug/ftrace - title: 使用 ftrace - - path: /devices/tech/debug/jank_capacity - title: 识别与负载能力相关的卡顿 - - path: /devices/tech/debug/jank_jitter - title: 识别与系统行为相关的卡顿 - title: 评估性能 - - section: - - path: /devices/tech/debug/fuzz-sanitize - title: 概览 - - path: /devices/tech/debug/asan - title: AddressSanitizer - - path: /devices/tech/debug/sanitizers - title: LLVM 排错程序 - - path: /devices/tech/debug/kasan-kcov - title: 使用 KASAN + KCOV 编译内核 - - path: /devices/tech/debug/libfuzzer - title: 通过 libFuzzer 进行模糊测试 - title: 模糊测试和排错 - - path: /devices/tech/debug/gdb - title: 使用 GDB - - path: /devices/tech/debug/native-memory - title: 本机内存使用情况 - - path: /devices/tech/debug/rescue-party - title: Rescue Party - - path: /devices/tech/debug/storaged - title: Storaged - - path: /devices/tech/debug/strace - title: Strace - - path: /devices/tech/debug/valgrind - title: Valgrind - title: 调试 - - section: - - path: /devices/tech/admin/ - title: 概览 - - path: /devices/tech/admin/implement - title: 实现 - - path: /devices/tech/admin/multi-user - title: 多用户 - - path: /devices/tech/admin/managed-profiles - title: 受管理的资料 - - path: /devices/tech/admin/provision - title: 配置 - - path: /devices/tech/admin/multiuser-apps - title: 多用户应用 - - path: /devices/tech/admin/enterprise-telephony - title: 企业电话 - - path: /devices/tech/admin/testing-provision - title: 测试设备配置 - - path: /devices/tech/admin/testing-setup - title: 测试设备管理 - title: 设备管理 - - section: - - path: /devices/tech/display/ - title: 概览 - - path: /devices/tech/display/adaptive-icons - title: 自适应图标 - - path: /devices/tech/display/app-shortcuts - title: 应用快捷方式 - - path: /devices/tech/display/circular-icons - title: 圆形图标 - - path: /devices/tech/display/color-mgmt - title: 颜色管理 - - path: /devices/tech/display/dnd - title: 勿扰 - - path: /devices/tech/display/hdr - title: HDR 视频 - - path: /devices/tech/display/multi-window - title: 多窗口模式 - - path: /devices/tech/display/night-light - title: 夜间模式 - - path: /devices/tech/display/pip - title: 画中画 - - path: /devices/tech/display/retail-mode - title: 零售演示模式 - - path: /devices/tech/display/split-screen - title: 分屏交互 - - path: /devices/tech/display/textclassifier - title: TEXTCLASSIFIER - - path: /devices/tech/display/widgets-shortcuts - title: 微件和快捷方式 - title: 显示 - - section: - - path: /devices/tech/ota/ - title: 概览 - - path: /devices/tech/ota/tools - title: OTA 工具 - - path: /devices/tech/ota/sign_builds - title: 对要发布的版本进行签名 - - path: /devices/tech/ota/reduce_size - title: 减小 OTA 大小 - - section: - - path: /devices/tech/ota/ab/ - title: 概览 - - path: /devices/tech/ota/ab/ab_implement - title: 实现 A/B 更新 - - path: /devices/tech/ota/ab/ab_faqs - title: 常见问题解答 - title: A/B 系统更新 - - section: - - path: /devices/tech/ota/nonab/ - title: 概览 - - path: /devices/tech/ota/nonab/block - title: 基于块的 OTA - - path: /devices/tech/ota/nonab/inside_packages - title: OTA 软件包内部探秘 - - path: /devices/tech/ota/nonab/device_code - title: 设备专属代码 - title: 非 A/B 系统更新 - title: OTA 更新 - - section: - - path: /devices/tech/perf/ - title: 概览 - - path: /devices/tech/perf/boot-times - title: 启动时间 - - path: /devices/tech/perf/flash-wear - title: 闪存磨损管理 - - path: /devices/tech/perf/low-ram - title: 低内存 - - path: /devices/tech/perf/task-snapshots - title: 任务快照 - title: 性能 - - section: - - path: /devices/tech/power/ - title: 概览 - - path: /devices/tech/power/mgmt - title: 电耗管理 - - path: /devices/tech/power/performance - title: 性能管理 - - path: /devices/tech/power/component - title: 组件电耗 - - path: /devices/tech/power/device - title: 设备电耗 - - path: /devices/tech/power/values - title: 电耗值 - title: 电耗 - - section: - - path: /devices/tech/settings/ - title: 概览 - - path: /devices/tech/settings/patterns-components - title: 模式和组件 - - path: /devices/tech/settings/info-architecture - title: 信息架构 - - path: /devices/tech/settings/personalized - title: 个性化设置 - - path: /devices/tech/settings/universal-search - title: 通用搜索 - - path: /devices/tech/settings/settings-guidelines - title: 设计指南 - title: 设置菜单 - - section: - - path: /devices/tech/test_infra/tradefed/ - title: 概览 - - path: /devices/tech/test_infra/tradefed/fundamentals - title: 开始使用 - - path: /devices/tech/test_infra/tradefed/fundamentals/machine_setup - title: 机器设置 - - path: /devices/tech/test_infra/tradefed/fundamentals/devices - title: 测试设备 - - path: /devices/tech/test_infra/tradefed/fundamentals/lifecycle - title: 测试生命周期 - - path: /devices/tech/test_infra/tradefed/fundamentals/options - title: 选项处理 - - path: /devices/tech/test_infra/tradefed/full_example - title: 端到端示例 - - path: /reference/tradefed/ - title: 软件包索引 - title: 测试基础架构 - name: 调整 - name: 调整 -- lower_tabs: - other: + - path: /devices/tech/dalvik/gc-debug + title: 垃圾回收 + - path: /devices/tech/dalvik/jit-compiler + title: JIT 编译 + name: ART + - contents: + - path: /devices/tech/datausage/ + title: 概览 + - path: /devices/tech/datausage/tags-explained + title: 流量使用情况标签说明 + - path: /devices/tech/connect/data-saver + title: 流量节省程序模式 + - path: /devices/tech/datausage/ebpf-traffic-monitor + title: eBPF 流量监控 + - path: /devices/tech/datausage/excluding-network-types + title: 从流量消耗中排除特定的网络类型 + - path: /devices/tech/datausage/iface-overview + title: 网络接口统计信息概览 + - path: /devices/tech/datausage/tethering-data + title: 网络共享流量 + - path: /devices/tech/datausage/usage-cycle-resets-dates + title: 流量统计周期重置日期 + - path: /devices/tech/datausage/kernel-overview + title: 内核概览 + - path: /devices/tech/datausage/kernel-changes + title: 内核变化 + name: 数据流量 + - contents: + - path: /devices/tech/admin/ + title: 概览 + - path: /devices/tech/admin/implement + title: 实现 + - path: /devices/tech/admin/multi-user + title: 多用户 + - path: /devices/tech/admin/managed-profiles + title: 受管理的资料 + - path: /devices/tech/admin/provision + title: 配置 + - path: /devices/tech/admin/multiuser-apps + title: 多用户应用 + - path: /devices/tech/admin/enterprise-telephony + title: 企业电话 + - path: /devices/tech/admin/testing-provision + title: 测试设备配置 + - path: /devices/tech/admin/testing-setup + title: 测试设备管理 + - path: /devices/tech/admin/ota-updates + title: 企业 OTA 更新 + name: 企业 - contents: - - path: /compatibility/ - title: 简介 - - path: /compatibility/overview - title: 计划概览 - section: - - path: /compatibility/cdd/ + - path: /devices/tech/health/ title: 概览 - - path: /compatibility/android-cdd - title: 兼容性定义文档（HTML 格式） - - path: /compatibility/android-cdd.pdf - title: 兼容性定义文档（PDF 格式） - title: 兼容性定义 - - section: - - path: /compatibility/cts/ + - path: /devices/tech/health/implementation + title: 实现“运行状况” + - path: /devices/tech/health/deprecation + title: 弃用 health@1.0 + title: 运行状况 + - path: /devices/tech/perf/apk-caching + title: APK 缓存 + - path: /devices/tech/perf/boot-times + title: 启动时间 + - path: /devices/tech/perf/low-ram + title: 低内存 + - path: /devices/tech/perf/pgo + title: 配置文件引导的优化 (PGO) + - path: /devices/tech/perf/task-snapshots + title: 任务快照 + - path: /devices/tech/perf/compatibility-wal + title: 预写日志 + name: 性能 + - contents: + - path: /devices/tech/config/perms-whitelist + title: 特许权限白名单 + - path: /devices/tech/config/runtime_perms + title: 运行时权限 + - path: /devices/tech/config/timezone-rules + title: 时区规则 + - path: /devices/tech/config/ambient + title: Ambient 权能 + - path: /devices/tech/config/filesystem + title: 自主访问控制 + - path: /devices/tech/config/namespaces_libraries + title: 库命名空间 + - path: /devices/tech/config/usb-hal + title: USB HAL + - path: /devices/tech/config/voicemail + title: 可视化语音信箱 + name: 权限 + - contents: + - path: /devices/tech/power/ + title: 概览 + - path: /devices/tech/power/mgmt + title: 电源管理 + - path: /devices/tech/power/app_mgmt + title: 应用管理 + - path: /devices/tech/power/platform_mgmt + title: 平台管理 + - path: /devices/tech/power/performance + title: 性能管理 + - path: /devices/tech/power/batteryless + title: 无电池设备 + - path: /devices/tech/power/component + title: 组件电耗 + - path: /devices/tech/power/device + title: 设备电耗 + - path: /devices/tech/power/values + title: 电耗值 + name: 电耗 + - contents: + - path: /devices/tech/ota/ + title: 概览 + - path: /devices/tech/ota/tools + title: OTA 工具 + - path: /devices/tech/ota/sign_builds + title: 对要发布的版本进行签名 + - path: /devices/tech/ota/reduce_size + title: 减小 OTA 大小 + - section: + - path: /devices/tech/ota/ab/ title: 概览 - - path: /compatibility/cts/setup - title: 设置 CTS - - path: /compatibility/cts/run - title: 运行 CTS - - section: - - path: /compatibility/cts/verifier - title: 概览 - - path: /compatibility/cts/audio-framework - title: 音频框架 - - path: /compatibility/cts/near-ultrasound - title: 近超声测试 - - path: /compatibility/cts/rotation-vector - title: 旋转矢量交叉检验 - - path: /compatibility/cts/usb-audio - title: USB 音频 CTS 测试 - title: 运行 CTS 验证程序 - - section: - - path: /compatibility/cts/camera-hal - title: 相机 HAL 测试 - - path: /compatibility/cts/camera-its-box - title: 相机盒装 ITS - - path: /compatibility/cts/camera-its-box-assembly - title: 组装相机盒装 ITS - title: 相机测试 - - path: /compatibility/cts/interpret - title: 解读结果 - - path: /compatibility/cts/development - title: CTS 开发 - - path: /compatibility/cts/downloads - title: 下载 - title: 兼容性测试套件 - - path: /compatibility/contact-us - title: 与我们联系 + - path: /devices/tech/ota/ab/ab_implement + title: 实现 A/B 更新 + - path: /devices/tech/ota/ab/ab_faqs + title: 常见问题解答 + title: A/B 系统更新 - section: - - path: /compatibility/vts/ + - path: /devices/tech/ota/nonab/ title: 概览 - - path: /compatibility/vts/systems - title: 使用 VTS 进行系统测试 - - section: - - path: /compatibility/vts/shell-commands - title: 设备 shell 命令 - - path: /compatibility/vts/test-templates - title: 测试模板 - - path: /compatibility/vts/multi-device-testing - title: 多设备测试 - title: 测试框架 - - path: /compatibility/vts/setup - title: VTS 信息中心设置 - - path: /compatibility/vts/database - title: VTS 信息中心数据库 - - path: /compatibility/vts/ui - title: VTS 信息中心界面 - - path: /compatibility/vts/performance - title: 性能测试 - title: 供应商测试套件 (VTS) - name: 兼容性 - name: 兼容性 + - path: /devices/tech/ota/nonab/block + title: 基于块的 OTA + - path: /devices/tech/ota/nonab/inside_packages + title: OTA 软件包内部探秘 + - path: /devices/tech/ota/nonab/device_code + title: 设备专属代码 + title: 非 A/B 系统更新 + name: 更新 + name: 配置 - lower_tabs: other: - contents: @@ -1127,60 +1303,118 @@ upper_tabs: title: IVrComposerClient @1.0 title: android.frameworks.vr.composer - section: + - path: /reference/hidl/android/hardware/audio/4.0/IDevice + title: IDevice @4.0 - path: /reference/hidl/android/hardware/audio/2.0/IDevice title: IDevice @2.0 + - path: /reference/hidl/android/hardware/audio/4.0/IDevicesFactory + title: IDevicesFactory @4.0 - path: /reference/hidl/android/hardware/audio/2.0/IDevicesFactory title: IDevicesFactory @2.0 + - path: /reference/hidl/android/hardware/audio/4.0/IPrimaryDevice + title: IPrimaryDevice @4.0 - path: /reference/hidl/android/hardware/audio/2.0/IPrimaryDevice title: IPrimaryDevice @2.0 + - path: /reference/hidl/android/hardware/audio/4.0/IStream + title: IStream @4.0 - path: /reference/hidl/android/hardware/audio/2.0/IStream title: IStream @2.0 + - path: /reference/hidl/android/hardware/audio/4.0/IStreamIn + title: IStreamIn @4.0 - path: /reference/hidl/android/hardware/audio/2.0/IStreamIn title: IStreamIn @2.0 + - path: /reference/hidl/android/hardware/audio/4.0/IStreamOut + title: IStreamOut @4.0 - path: /reference/hidl/android/hardware/audio/2.0/IStreamOut title: IStreamOut @2.0 + - path: /reference/hidl/android/hardware/audio/4.0/IStreamOutCallback + title: IStreamOutCallback @4.0 - path: /reference/hidl/android/hardware/audio/2.0/IStreamOutCallback title: IStreamOutCallback @2.0 + - path: /reference/hidl/android/hardware/audio/4.0/types + title: types @4.0 - path: /reference/hidl/android/hardware/audio/2.0/types title: types @2.0 title: android.hardware.audio - section: + - path: /reference/hidl/android/hardware/audio/common/4.0/types + title: types @4.0 - path: /reference/hidl/android/hardware/audio/common/2.0/types title: types @2.0 title: android.hardware.audio.common - section: + - path: /reference/hidl/android/hardware/audio/effect/4.0/IAcousticEchoCancelerEffect + title: IAcousticEchoCancelerEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IAcousticEchoCancelerEffect title: IAcousticEchoCancelerEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IAutomaticGainControlEffect + title: IAutomaticGainControlEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IAutomaticGainControlEffect title: IAutomaticGainControlEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IBassBoostEffect + title: IBassBoostEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IBassBoostEffect title: IBassBoostEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IDownmixEffect + title: IDownmixEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IDownmixEffect title: IDownmixEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IEffect + title: IEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IEffect title: IEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IEffectBufferProviderCallback + title: IEffectBufferProviderCallback @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IEffectBufferProviderCallback title: IEffectBufferProviderCallback @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IEffectsFactory + title: IEffectsFactory @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IEffectsFactory title: IEffectsFactory @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IEnvironmentalReverbEffect + title: IEnvironmentalReverbEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IEnvironmentalReverbEffect title: IEnvironmentalReverbEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IEqualizerEffect + title: IEqualizerEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IEqualizerEffect title: IEqualizerEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/ILoudnessEnhancerEffect + title: ILoudnessEnhancerEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/ILoudnessEnhancerEffect title: ILoudnessEnhancerEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/INoiseSuppressionEffect + title: INoiseSuppressionEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/INoiseSuppressionEffect title: INoiseSuppressionEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IPresetReverbEffect + title: IPresetReverbEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IPresetReverbEffect title: IPresetReverbEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IVirtualizerEffect + title: IVirtualizerEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IVirtualizerEffect title: IVirtualizerEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/IVisualizerEffect + title: IVisualizerEffect @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/IVisualizerEffect title: IVisualizerEffect @2.0 + - path: /reference/hidl/android/hardware/audio/effect/4.0/types + title: types @4.0 - path: /reference/hidl/android/hardware/audio/effect/2.0/types title: types @2.0 title: android.hardware.audio.effect - section: + - path: /reference/hidl/android/hardware/authsecret/1.0/IAuthSecret + title: IAuthSecret @1.0 + title: android.hardware.authsecret + - section: + - path: /reference/hidl/android/hardware/automotive/audiocontrol/1.0/IAudioControl + title: IAudioControl @1.0 + - path: /reference/hidl/android/hardware/automotive/audiocontrol/1.0/types + title: types @1.0 + title: android.hardware.automotive.audiocontrol + - section: - path: /reference/hidl/android/hardware/automotive/evs/1.0/IEvsCamera title: IEvsCamera @1.0 - path: /reference/hidl/android/hardware/automotive/evs/1.0/IEvsCameraStream @@ -1217,12 +1451,24 @@ upper_tabs: title: types @1.0 title: android.hardware.bluetooth - section: + - path: /reference/hidl/android/hardware/bluetooth/a2dp/1.0/IBluetoothAudioHost + title: IBluetoothAudioHost @1.0 + - path: /reference/hidl/android/hardware/bluetooth/a2dp/1.0/IBluetoothAudioOffload + title: IBluetoothAudioOffload @1.0 + - path: /reference/hidl/android/hardware/bluetooth/a2dp/1.0/types + title: types @1.0 + title: android.hardware.bluetooth.a2dp + - section: - path: /reference/hidl/android/hardware/boot/1.0/IBootControl title: IBootControl @1.0 - path: /reference/hidl/android/hardware/boot/1.0/types title: types @1.0 title: android.hardware.boot - section: + - path: /reference/hidl/android/hardware/broadcastradio/2.0/IAnnouncementListener + title: IAnnouncementListener @2.0 + - path: /reference/hidl/android/hardware/broadcastradio/2.0/IBroadcastRadio + title: IBroadcastRadio @2.0 - path: /reference/hidl/android/hardware/broadcastradio/1.1/IBroadcastRadio title: IBroadcastRadio @1.1 - path: /reference/hidl/android/hardware/broadcastradio/1.0/IBroadcastRadio @@ -1231,14 +1477,22 @@ upper_tabs: title: IBroadcastRadioFactory @1.1 - path: /reference/hidl/android/hardware/broadcastradio/1.0/IBroadcastRadioFactory title: IBroadcastRadioFactory @1.0 + - path: /reference/hidl/android/hardware/broadcastradio/2.0/ICloseHandle + title: ICloseHandle @2.0 - path: /reference/hidl/android/hardware/broadcastradio/1.1/ITuner title: ITuner @1.1 - path: /reference/hidl/android/hardware/broadcastradio/1.0/ITuner title: ITuner @1.0 + - path: /reference/hidl/android/hardware/broadcastradio/2.0/ITunerCallback + title: ITunerCallback @2.0 - path: /reference/hidl/android/hardware/broadcastradio/1.1/ITunerCallback title: ITunerCallback @1.1 - path: /reference/hidl/android/hardware/broadcastradio/1.0/ITunerCallback title: ITunerCallback @1.0 + - path: /reference/hidl/android/hardware/broadcastradio/2.0/ITunerSession + title: ITunerSession @2.0 + - path: /reference/hidl/android/hardware/broadcastradio/2.0/types + title: types @2.0 - path: /reference/hidl/android/hardware/broadcastradio/1.1/types title: types @1.1 - path: /reference/hidl/android/hardware/broadcastradio/1.0/types @@ -1253,16 +1507,22 @@ upper_tabs: title: ICameraDevice @3.2 - path: /reference/hidl/android/hardware/camera/device/1.0/ICameraDevice title: ICameraDevice @1.0 + - path: /reference/hidl/android/hardware/camera/device/3.4/ICameraDeviceCallback + title: ICameraDeviceCallback @3.4 - path: /reference/hidl/android/hardware/camera/device/3.2/ICameraDeviceCallback title: ICameraDeviceCallback @3.2 - path: /reference/hidl/android/hardware/camera/device/1.0/ICameraDeviceCallback title: ICameraDeviceCallback @1.0 - path: /reference/hidl/android/hardware/camera/device/1.0/ICameraDevicePreviewCallback title: ICameraDevicePreviewCallback @1.0 + - path: /reference/hidl/android/hardware/camera/device/3.4/ICameraDeviceSession + title: ICameraDeviceSession @3.4 - path: /reference/hidl/android/hardware/camera/device/3.3/ICameraDeviceSession title: ICameraDeviceSession @3.3 - path: /reference/hidl/android/hardware/camera/device/3.2/ICameraDeviceSession title: ICameraDeviceSession @3.2 + - path: /reference/hidl/android/hardware/camera/device/3.4/types + title: types @3.4 - path: /reference/hidl/android/hardware/camera/device/3.3/types title: types @3.3 - path: /reference/hidl/android/hardware/camera/device/3.2/types @@ -1271,6 +1531,8 @@ upper_tabs: title: types @1.0 title: android.hardware.camera.device - section: + - path: /reference/hidl/android/hardware/camera/metadata/3.3/types + title: types @3.3 - path: /reference/hidl/android/hardware/camera/metadata/3.2/types title: types @3.2 title: android.hardware.camera.metadata @@ -1299,12 +1561,24 @@ upper_tabs: title: types @1.0 title: android.hardware.cas.native - section: + - path: /reference/hidl/android/hardware/configstore/1.1/ISurfaceFlingerConfigs + title: ISurfaceFlingerConfigs @1.1 - path: /reference/hidl/android/hardware/configstore/1.0/ISurfaceFlingerConfigs title: ISurfaceFlingerConfigs @1.0 + - path: /reference/hidl/android/hardware/configstore/1.1/types + title: types @1.1 - path: /reference/hidl/android/hardware/configstore/1.0/types title: types @1.0 title: android.hardware.configstore - section: + - path: /reference/hidl/android/hardware/confirmationui/1.0/IConfirmationResultCallback + title: IConfirmationResultCallback @1.0 + - path: /reference/hidl/android/hardware/confirmationui/1.0/IConfirmationUI + title: IConfirmationUI @1.0 + - path: /reference/hidl/android/hardware/confirmationui/1.0/types + title: types @1.0 + title: android.hardware.confirmationui + - section: - path: /reference/hidl/android/hardware/contexthub/1.0/IContexthub title: IContexthub @1.0 - path: /reference/hidl/android/hardware/contexthub/1.0/IContexthubCallback @@ -1313,16 +1587,24 @@ upper_tabs: title: types @1.0 title: android.hardware.contexthub - section: + - path: /reference/hidl/android/hardware/drm/1.1/ICryptoFactory + title: ICryptoFactory @1.1 - path: /reference/hidl/android/hardware/drm/1.0/ICryptoFactory title: ICryptoFactory @1.0 - path: /reference/hidl/android/hardware/drm/1.0/ICryptoPlugin title: ICryptoPlugin @1.0 + - path: /reference/hidl/android/hardware/drm/1.1/IDrmFactory + title: IDrmFactory @1.1 - path: /reference/hidl/android/hardware/drm/1.0/IDrmFactory title: IDrmFactory @1.0 + - path: /reference/hidl/android/hardware/drm/1.1/IDrmPlugin + title: IDrmPlugin @1.1 - path: /reference/hidl/android/hardware/drm/1.0/IDrmPlugin title: IDrmPlugin @1.0 - path: /reference/hidl/android/hardware/drm/1.0/IDrmPluginListener title: IDrmPluginListener @1.0 + - path: /reference/hidl/android/hardware/drm/1.1/types + title: types @1.1 - path: /reference/hidl/android/hardware/drm/1.0/types title: types @1.0 title: android.hardware.drm @@ -1345,14 +1627,20 @@ upper_tabs: title: IAGnssRil @1.0 - path: /reference/hidl/android/hardware/gnss/1.0/IAGnssRilCallback title: IAGnssRilCallback @1.0 + - path: /reference/hidl/android/hardware/gnss/1.1/IGnss + title: IGnss @1.1 - path: /reference/hidl/android/hardware/gnss/1.0/IGnss title: IGnss @1.0 - path: /reference/hidl/android/hardware/gnss/1.0/IGnssBatching title: IGnssBatching @1.0 - path: /reference/hidl/android/hardware/gnss/1.0/IGnssBatchingCallback title: IGnssBatchingCallback @1.0 + - path: /reference/hidl/android/hardware/gnss/1.1/IGnssCallback + title: IGnssCallback @1.1 - path: /reference/hidl/android/hardware/gnss/1.0/IGnssCallback title: IGnssCallback @1.0 + - path: /reference/hidl/android/hardware/gnss/1.1/IGnssConfiguration + title: IGnssConfiguration @1.1 - path: /reference/hidl/android/hardware/gnss/1.0/IGnssConfiguration title: IGnssConfiguration @1.0 - path: /reference/hidl/android/hardware/gnss/1.0/IGnssDebug @@ -1361,8 +1649,12 @@ upper_tabs: title: IGnssGeofenceCallback @1.0 - path: /reference/hidl/android/hardware/gnss/1.0/IGnssGeofencing title: IGnssGeofencing @1.0 + - path: /reference/hidl/android/hardware/gnss/1.1/IGnssMeasurement + title: IGnssMeasurement @1.1 - path: /reference/hidl/android/hardware/gnss/1.0/IGnssMeasurement title: IGnssMeasurement @1.0 + - path: /reference/hidl/android/hardware/gnss/1.1/IGnssMeasurementCallback + title: IGnssMeasurementCallback @1.1 - path: /reference/hidl/android/hardware/gnss/1.0/IGnssMeasurementCallback title: IGnssMeasurementCallback @1.0 - path: /reference/hidl/android/hardware/gnss/1.0/IGnssNavigationMessage @@ -1391,20 +1683,28 @@ upper_tabs: title: IProducerListener @1.0 title: android.hardware.graphics.bufferqueue - section: + - path: /reference/hidl/android/hardware/graphics/common/1.1/types + title: types @1.1 - path: /reference/hidl/android/hardware/graphics/common/1.0/types title: types @1.0 title: android.hardware.graphics.common - section: + - path: /reference/hidl/android/hardware/graphics/composer/2.2/IComposer + title: IComposer @2.2 - path: /reference/hidl/android/hardware/graphics/composer/2.1/IComposer title: IComposer @2.1 - path: /reference/hidl/android/hardware/graphics/composer/2.1/IComposerCallback title: IComposerCallback @2.1 + - path: /reference/hidl/android/hardware/graphics/composer/2.2/IComposerClient + title: IComposerClient @2.2 - path: /reference/hidl/android/hardware/graphics/composer/2.1/IComposerClient title: IComposerClient @2.1 - path: /reference/hidl/android/hardware/graphics/composer/2.1/types title: types @2.1 title: android.hardware.graphics.composer - section: + - path: /reference/hidl/android/hardware/graphics/mapper/2.1/IMapper + title: IMapper @2.1 - path: /reference/hidl/android/hardware/graphics/mapper/2.0/IMapper title: IMapper @2.0 - path: /reference/hidl/android/hardware/graphics/mapper/2.0/types @@ -1429,8 +1729,12 @@ upper_tabs: title: types @1.0 title: android.hardware.ir - section: + - path: /reference/hidl/android/hardware/keymaster/4.0/IKeymasterDevice + title: IKeymasterDevice @4.0 - path: /reference/hidl/android/hardware/keymaster/3.0/IKeymasterDevice title: IKeymasterDevice @3.0 + - path: /reference/hidl/android/hardware/keymaster/4.0/types + title: types @4.0 - path: /reference/hidl/android/hardware/keymaster/3.0/types title: types @3.0 title: android.hardware.keymaster @@ -1445,6 +1749,16 @@ upper_tabs: title: types @1.0 title: android.hardware.media - section: + - path: /reference/hidl/android/hardware/media/bufferpool/1.0/IAccessor + title: IAccessor @1.0 + - path: /reference/hidl/android/hardware/media/bufferpool/1.0/IClientManager + title: IClientManager @1.0 + - path: /reference/hidl/android/hardware/media/bufferpool/1.0/IConnection + title: IConnection @1.0 + - path: /reference/hidl/android/hardware/media/bufferpool/1.0/types + title: types @1.0 + title: android.hardware.media.bufferpool + - section: - path: /reference/hidl/android/hardware/media/omx/1.0/IGraphicBufferSource title: IGraphicBufferSource @1.0 - path: /reference/hidl/android/hardware/media/omx/1.0/IOmx @@ -1467,6 +1781,8 @@ upper_tabs: title: types @1.0 title: android.hardware.memtrack - section: + - path: /reference/hidl/android/hardware/neuralnetworks/1.1/IDevice + title: IDevice @1.1 - path: /reference/hidl/android/hardware/neuralnetworks/1.0/IDevice title: IDevice @1.0 - path: /reference/hidl/android/hardware/neuralnetworks/1.0/IExecutionCallback @@ -1475,14 +1791,22 @@ upper_tabs: title: IPreparedModel @1.0 - path: /reference/hidl/android/hardware/neuralnetworks/1.0/IPreparedModelCallback title: IPreparedModelCallback @1.0 + - path: /reference/hidl/android/hardware/neuralnetworks/1.1/types + title: types @1.1 - path: /reference/hidl/android/hardware/neuralnetworks/1.0/types title: types @1.0 title: android.hardware.neuralnetworks - section: + - path: /reference/hidl/android/hardware/nfc/1.1/INfc + title: INfc @1.1 - path: /reference/hidl/android/hardware/nfc/1.0/INfc title: INfc @1.0 + - path: /reference/hidl/android/hardware/nfc/1.1/INfcClientCallback + title: INfcClientCallback @1.1 - path: /reference/hidl/android/hardware/nfc/1.0/INfcClientCallback title: INfcClientCallback @1.0 + - path: /reference/hidl/android/hardware/nfc/1.1/types + title: types @1.1 - path: /reference/hidl/android/hardware/nfc/1.0/types title: types @1.0 title: android.hardware.nfc @@ -1493,10 +1817,18 @@ upper_tabs: title: types @1.0 title: android.hardware.oemlock - section: + - path: /reference/hidl/android/hardware/power/1.3/IPower + title: IPower @1.3 + - path: /reference/hidl/android/hardware/power/1.2/IPower + title: IPower @1.2 - path: /reference/hidl/android/hardware/power/1.1/IPower title: IPower @1.1 - path: /reference/hidl/android/hardware/power/1.0/IPower title: IPower @1.0 + - path: /reference/hidl/android/hardware/power/1.3/types + title: types @1.3 + - path: /reference/hidl/android/hardware/power/1.2/types + title: types @1.2 - path: /reference/hidl/android/hardware/power/1.1/types title: types @1.1 - path: /reference/hidl/android/hardware/power/1.0/types @@ -1537,6 +1869,16 @@ upper_tabs: title: types @1.0 title: android.hardware.radio - section: + - path: /reference/hidl/android/hardware/radio/config/1.0/IRadioConfig + title: IRadioConfig @1.0 + - path: /reference/hidl/android/hardware/radio/config/1.0/IRadioConfigIndication + title: IRadioConfigIndication @1.0 + - path: /reference/hidl/android/hardware/radio/config/1.0/IRadioConfigResponse + title: IRadioConfigResponse @1.0 + - path: /reference/hidl/android/hardware/radio/config/1.0/types + title: types @1.0 + title: android.hardware.radio.config + - section: - path: /reference/hidl/android/hardware/radio/deprecated/1.0/IOemHook title: IOemHook @1.0 - path: /reference/hidl/android/hardware/radio/deprecated/1.0/IOemHookIndication @@ -1553,6 +1895,14 @@ upper_tabs: title: types @1.0 title: android.hardware.renderscript - section: + - path: /reference/hidl/android/hardware/secure_element/1.0/ISecureElement + title: ISecureElement @1.0 + - path: /reference/hidl/android/hardware/secure_element/1.0/ISecureElementHalCallback + title: ISecureElementHalCallback @1.0 + - path: /reference/hidl/android/hardware/secure_element/1.0/types + title: types @1.0 + title: android.hardware.secure_element + - section: - path: /reference/hidl/android/hardware/sensors/1.0/ISensors title: ISensors @1.0 - path: /reference/hidl/android/hardware/sensors/1.0/types @@ -1619,10 +1969,22 @@ upper_tabs: title: types @1.0 title: android.hardware.usb - section: + - path: /reference/hidl/android/hardware/usb/gadget/1.0/IUsbGadget + title: IUsbGadget @1.0 + - path: /reference/hidl/android/hardware/usb/gadget/1.0/IUsbGadgetCallback + title: IUsbGadgetCallback @1.0 + - path: /reference/hidl/android/hardware/usb/gadget/1.0/types + title: types @1.0 + title: android.hardware.usb.gadget + - section: + - path: /reference/hidl/android/hardware/vibrator/1.2/IVibrator + title: IVibrator @1.2 - path: /reference/hidl/android/hardware/vibrator/1.1/IVibrator title: IVibrator @1.1 - path: /reference/hidl/android/hardware/vibrator/1.0/IVibrator title: IVibrator @1.0 + - path: /reference/hidl/android/hardware/vibrator/1.2/types + title: types @1.2 - path: /reference/hidl/android/hardware/vibrator/1.1/types title: types @1.1 - path: /reference/hidl/android/hardware/vibrator/1.0/types @@ -1639,24 +2001,34 @@ upper_tabs: title: types @1.0 title: android.hardware.weaver - section: + - path: /reference/hidl/android/hardware/wifi/1.2/IWifi + title: IWifi @1.2 - path: /reference/hidl/android/hardware/wifi/1.1/IWifi title: IWifi @1.1 - path: /reference/hidl/android/hardware/wifi/1.0/IWifi title: IWifi @1.0 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiApIface title: IWifiApIface @1.0 + - path: /reference/hidl/android/hardware/wifi/1.2/IWifiChip + title: IWifiChip @1.2 - path: /reference/hidl/android/hardware/wifi/1.1/IWifiChip title: IWifiChip @1.1 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiChip title: IWifiChip @1.0 + - path: /reference/hidl/android/hardware/wifi/1.2/IWifiChipEventCallback + title: IWifiChipEventCallback @1.2 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiChipEventCallback title: IWifiChipEventCallback @1.0 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiEventCallback title: IWifiEventCallback @1.0 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiIface title: IWifiIface @1.0 + - path: /reference/hidl/android/hardware/wifi/1.2/IWifiNanIface + title: IWifiNanIface @1.2 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiNanIface title: IWifiNanIface @1.0 + - path: /reference/hidl/android/hardware/wifi/1.2/IWifiNanIfaceEventCallback + title: IWifiNanIfaceEventCallback @1.2 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiNanIfaceEventCallback title: IWifiNanIfaceEventCallback @1.0 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiP2pIface @@ -1665,14 +2037,24 @@ upper_tabs: title: IWifiRttController @1.0 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiRttControllerEventCallback title: IWifiRttControllerEventCallback @1.0 + - path: /reference/hidl/android/hardware/wifi/1.2/IWifiStaIface + title: IWifiStaIface @1.2 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiStaIface title: IWifiStaIface @1.0 - path: /reference/hidl/android/hardware/wifi/1.0/IWifiStaIfaceEventCallback title: IWifiStaIfaceEventCallback @1.0 + - path: /reference/hidl/android/hardware/wifi/1.2/types + title: types @1.2 - path: /reference/hidl/android/hardware/wifi/1.0/types title: types @1.0 title: android.hardware.wifi - section: + - path: /reference/hidl/android/hardware/wifi/hostapd/1.0/IHostapd + title: IHostapd @1.0 + - path: /reference/hidl/android/hardware/wifi/hostapd/1.0/types + title: types @1.0 + title: android.hardware.wifi.hostapd + - section: - path: /reference/hidl/android/hardware/wifi/offload/1.0/IOffload title: IOffload @1.0 - path: /reference/hidl/android/hardware/wifi/offload/1.0/IOffloadCallback @@ -1681,6 +2063,8 @@ upper_tabs: title: types @1.0 title: android.hardware.wifi.offload - section: + - path: /reference/hidl/android/hardware/wifi/supplicant/1.1/ISupplicant + title: ISupplicant @1.1 - path: /reference/hidl/android/hardware/wifi/supplicant/1.0/ISupplicant title: ISupplicant @1.0 - path: /reference/hidl/android/hardware/wifi/supplicant/1.0/ISupplicantCallback @@ -1697,10 +2081,16 @@ upper_tabs: title: ISupplicantP2pNetwork @1.0 - path: /reference/hidl/android/hardware/wifi/supplicant/1.0/ISupplicantP2pNetworkCallback title: ISupplicantP2pNetworkCallback @1.0 + - path: /reference/hidl/android/hardware/wifi/supplicant/1.1/ISupplicantStaIface + title: ISupplicantStaIface @1.1 - path: /reference/hidl/android/hardware/wifi/supplicant/1.0/ISupplicantStaIface title: ISupplicantStaIface @1.0 + - path: /reference/hidl/android/hardware/wifi/supplicant/1.1/ISupplicantStaIfaceCallback + title: ISupplicantStaIfaceCallback @1.1 - path: /reference/hidl/android/hardware/wifi/supplicant/1.0/ISupplicantStaIfaceCallback title: ISupplicantStaIfaceCallback @1.0 + - path: /reference/hidl/android/hardware/wifi/supplicant/1.1/ISupplicantStaNetwork + title: ISupplicantStaNetwork @1.1 - path: /reference/hidl/android/hardware/wifi/supplicant/1.0/ISupplicantStaNetwork title: ISupplicantStaNetwork @1.0 - path: /reference/hidl/android/hardware/wifi/supplicant/1.0/ISupplicantStaNetworkCallback @@ -1745,6 +2135,8 @@ upper_tabs: title: ITokenManager @1.0 title: android.hidl.token - section: + - path: /reference/hidl/android/system/net/netd/1.1/INetd + title: INetd @1.1 - path: /reference/hidl/android/system/net/netd/1.0/INetd title: INetd @1.0 title: android.system.net.netd @@ -1782,24 +2174,28 @@ upper_tabs: title: com.android.tradefed.command.remote - path: /reference/tradefed/com/android/tradefed/config/package-summary title: com.android.tradefed.config + - path: /reference/tradefed/com/android/tradefed/config/gcs/package-summary + title: com.android.tradefed.config.gcs - path: /reference/tradefed/com/android/tradefed/device/package-summary title: com.android.tradefed.device - path: /reference/tradefed/com/android/tradefed/device/metric/package-summary title: com.android.tradefed.device.metric + - path: /reference/tradefed/com/android/tradefed/guice/package-summary + title: com.android.tradefed.guice - path: /reference/tradefed/com/android/tradefed/host/package-summary title: com.android.tradefed.host - path: /reference/tradefed/com/android/tradefed/invoker/package-summary title: com.android.tradefed.invoker + - path: /reference/tradefed/com/android/tradefed/invoker/sandbox/package-summary + title: com.android.tradefed.invoker.sandbox - path: /reference/tradefed/com/android/tradefed/invoker/shard/package-summary title: com.android.tradefed.invoker.shard - path: /reference/tradefed/com/android/tradefed/log/package-summary title: com.android.tradefed.log - - path: /reference/tradefed/com/android/tradefed/profiler/package-summary - title: com.android.tradefed.profiler - - path: /reference/tradefed/com/android/tradefed/profiler/recorder/package-summary - title: com.android.tradefed.profiler.recorder - path: /reference/tradefed/com/android/tradefed/result/package-summary title: com.android.tradefed.result + - path: /reference/tradefed/com/android/tradefed/result/ddmlib/package-summary + title: com.android.tradefed.result.ddmlib - path: /reference/tradefed/com/android/tradefed/result/suite/package-summary title: com.android.tradefed.result.suite - path: /reference/tradefed/com/android/tradefed/sandbox/package-summary @@ -1816,8 +2212,14 @@ upper_tabs: title: com.android.tradefed.targetprep.suite - path: /reference/tradefed/com/android/tradefed/testtype/package-summary title: com.android.tradefed.testtype + - path: /reference/tradefed/com/android/tradefed/testtype/host/package-summary + title: com.android.tradefed.testtype.host - path: /reference/tradefed/com/android/tradefed/testtype/junit4/package-summary title: com.android.tradefed.testtype.junit4 + - path: /reference/tradefed/com/android/tradefed/testtype/junit4/builder/package-summary + title: com.android.tradefed.testtype.junit4.builder + - path: /reference/tradefed/com/android/tradefed/testtype/metricregression/package-summary + title: com.android.tradefed.testtype.metricregression - path: /reference/tradefed/com/android/tradefed/testtype/python/package-summary title: com.android.tradefed.testtype.python - path: /reference/tradefed/com/android/tradefed/testtype/suite/package-summary @@ -1836,6 +2238,8 @@ upper_tabs: title: com.android.tradefed.util.keystore - path: /reference/tradefed/com/android/tradefed/util/net/package-summary title: com.android.tradefed.util.net + - path: /reference/tradefed/com/android/tradefed/util/proto/package-summary + title: com.android.tradefed.util.proto - path: /reference/tradefed/com/android/tradefed/util/sl4a/package-summary title: com.android.tradefed.util.sl4a - path: /reference/tradefed/com/android/tradefed/util/xml/package-summary diff --git a/zh-cn/devices/architecture/dto/optimize.html b/zh-cn/devices/architecture/dto/optimize.html index 399eb9be..a7ad7550 100644 --- a/zh-cn/devices/architecture/dto/optimize.html +++ b/zh-cn/devices/architecture/dto/optimize.html @@ -70,7 +70,7 @@ </tbody></table> <h2 id="libufdt">libufdt</h2> -<p>虽然最新的 <code><a href="https://github.com/dgibson/dtc/tree/master/libfdt" class="external">libfdt</a></code> 支持 DTO，但是我们建议您使用 <code>libufdt</code> 来实现 DTP（源文件位于 AOSP 中的 <code><a href="https://android.googlesource.com/platform/system/libufdt/+/refs/heads/master" class="external">platform/system/libufdt</a></code> 下）。<code>libufdt</code> 会从扁平化设备树 (FDT) 编译真实的树结构（非扁平化设备树，简称为“ufdt”<em></em>），从而改善两个 <code>.dtb</code> 文件（从 O(N2) 到 O(N)，其中 N 是树中的节点数）的合并效果。</p> +<p>虽然最新的 <code><a href="https://github.com/dgibson/dtc/tree/master/libfdt" class="external">libfdt</a></code> 支持 DTO，但是我们建议您使用 <code>libufdt</code> 来实现 DTP（源代码位于 AOSP 中的 <code><a href="https://android.googlesource.com/platform/system/libufdt/+/refs/heads/master" class="external">platform/system/libufdt</a></code> 下）。<code>libufdt</code> 会从扁平化设备树 (FDT) 编译真实的树结构（非扁平化设备树，简称“ufdt”<em></em>），从而改善两个 <code>.dtb</code> 文件（从 O(N2) 到 O(N)，其中 N 是树中的节点数）的合并效果。</p> <h3 id="performance">性能测试</h3> <p>在 Google 的内部测试中，进行编译后，在 2405 个 <code>.dtb</code> 和 283 个 <code>.dtbo</code> DT 节点上使用 <code>libufdt</code> 生成了 70618 字节和 8566 字节的文件。与从 FreeBSD 移植的 <a href="http://fxr.watson.org/fxr/source/boot/fdt/" class="external">DTO 实现</a>（运行时为 124 毫秒）相比，<code>libufdt</code> DTO 运行时为 10 毫秒。</p> diff --git a/zh-cn/devices/architecture/hidl-java/index.html b/zh-cn/devices/architecture/hidl-java/index.html index 2d8820d5..20f1e1cb 100644 --- a/zh-cn/devices/architecture/hidl-java/index.html +++ b/zh-cn/devices/architecture/hidl-java/index.html @@ -54,8 +54,9 @@ shared_libs: [ <pre class="prettyprint"> import android.hardware.foo.V1_0.IFoo; ... -IFoo server = IFoo.getService(); // throws exception if not available -IFoo anotherServer = IFoo.getService("second_impl"); +// retry to wait until the service starts up if it is in the manifest +IFoo server = IFoo.getService(true /* retry */); // throws NoSuchElementException if not available +IFoo anotherServer = IFoo.getService("second_impl", true /* retry */); server.doSomething(…); </pre> </li> @@ -64,15 +65,17 @@ server.doSomething(…); <h2 id="service">提供服务</h2> <p>Java 中的框架代码可能需要提供接口才能接收来自 HAL 的异步回调。</p> -<p class="warning"><strong>警告</strong>：请勿用 Java 实现驱动程序 (HAL)。我们强烈建议您用 C ++ 实现驱动程序。</p> +<p class="warning"><strong>警告</strong>：请勿用 Java 实现驱动程序 (HAL)。我们强烈建议您用 C++ 实现驱动程序。</p> -<p>对于软件包 <code>android.hardware.foo</code> 版本 1.0 中的接口 <code>IFooCallback</code>，您可以按照以下步骤用 Java 实现接口。</p> +<p class="warning"><strong>警告</strong>：Java 驱动程序必须与其客户端处于不同的进程中（不支持同一进程通信）。</p> + +<p>对于 1.0 版软件包 <code>android.hardware.foo</code> 中的接口 <code>IFooCallback</code>，您可以按照以下步骤用 Java 实现接口。</p> <ol> <li>用 HIDL 定义您的接口。</li> <li>打开 <code>/tmp/android/hardware/foo/IFooCallback.java</code> 作为参考。</li> <li>为您的 Java 实现创建一个新模块。</li> -<li>检查抽象类 <code>android.hardware.foo.V1_0.IFooCallback.Stub</code>，然后编写一个新类以将其扩展，并实现抽象方法。</li> +<li>检查抽象类 <code>android.hardware.foo.V1_0.IFooCallback.Stub</code>，然后编写一个新类以对其进行扩展，并实现抽象方法。</li> </ol> <h3 id="autogen">查看自动生成的文件</h3> @@ -103,7 +106,7 @@ class FooCallback extends IFooCallback.Stub { .... // Get the service you will be receiving callbacks from. // This also starts the threadpool for your callback service. -IFoo server = IFoo.getService(); // throws exception if not available +IFoo server = IFoo.getService(true /* retry */); // throws NoSuchElementException if not available .... // This must be a persistent instance variable, not local, // to avoid premature garbage collection. @@ -129,7 +132,7 @@ interface IBetterFoo extends IFoo { <p>感知到扩展接口的调用代码可以使用 <code>castFrom()</code> Java 方法将基本接口安全地转换为扩展接口：</p> <pre class="prettyprint"> -IFoo baseService = Foo.getService(); +IFoo baseService = IFoo.getService(true /* retry */); // throws NoSuchElementException if not available IBetterFoo extendedService = IBetterFoo.castFrom(baseService); if (extendedService != null) { // The service implements the extended interface. diff --git a/zh-cn/devices/architecture/hidl/hashing.html b/zh-cn/devices/architecture/hidl/hashing.html index 1663c87a..045aefd5 100644 --- a/zh-cn/devices/architecture/hidl/hashing.html +++ b/zh-cn/devices/architecture/hidl/hashing.html @@ -45,7 +45,7 @@ c84da9f5...f8ea2648 vendor.awesome.foo@1.0::types 822998d7...74d63b8c vendor.awesome.foo@1.0::IFoo </pre> -<p class="note"><strong>注意</strong>：为了便于跟踪各个哈希的来源，Google 将 HIDL <code>current.txt</code> 文件分为不同的部分：第一部分列出在 Android O 中发布的接口文件，第二部分列出在 Android O MR1 中发布的接口文件。<em></em><em></em>我们强烈建议在您的 <code>current.txt</code> 文件中使用类似布局。</p> +<p class="note"><strong>注意</strong>：为了便于跟踪各个哈希的来源，Google 将 HIDL <code>current.txt</code> 文件分为不同的部分：第一部分列出在 Android O 中发布的接口文件中，第二部分列出在 Android O MR1 中发布的接口文件中。<em></em><em></em>我们强烈建议在您的 <code>current.txt</code> 文件中使用类似布局。</p> <h2 id="hidl-gen">使用 hidl-gen 添加哈希</h2> <p>您可以手动将哈希添加到 <code>current.txt</code> 文件中，也可以使用 <code>hidl-gen</code> 添加。以下代码段提供了可与 <code>hidl-gen</code> 搭配使用来管理 <code>current.txt</code> 文件的命令示例（哈希已缩短）：</p> @@ -73,7 +73,7 @@ f2fe5442...72655de6 vendor.awesome.nfc@1.0::INfcClientCallback <li>如果接口与哈希匹配，则编译会继续进行。</li> <li>如果接口与哈希不匹配，则编译会暂停，因为这意味着之前发布的接口会被更改。 <ul> -<li>要在更改的同时不影响 ABI（请参阅 <a href="#abi-stability">ABI 稳定性</a>），请务必先修改 <code>current.txt</code> 文件，然后编译才能继续进行。</li> +<li>要在更改的同时不影响 ABI（请参阅 <a href="#abi-stability">ABI 稳定性</a>），请务必先修改 <code>current.txt</code> 文件，然后编译才能继续进行。 </li> <li>所有其他更改都应在接口的 minor 或 major 版本升级中进行。</li> </ul></li></ul></li></ul> diff --git a/zh-cn/devices/architecture/hidl/services.html b/zh-cn/devices/architecture/hidl/services.html index b12d24ab..6bca2beb 100644 --- a/zh-cn/devices/architecture/hidl/services.html +++ b/zh-cn/devices/architecture/hidl/services.html @@ -38,10 +38,10 @@ status_t anotherStatus = anotherFoo->registerAsService("another_foo_service") <pre class="prettyprint"> // C++ sp<V1_1::IFooService> service = V1_1::IFooService::getService(); -sp<V1_1::IFooService> alternateService = 1_1::IFooService::getService("another_foo_service"); +sp<V1_1::IFooService> alternateService = V1_1::IFooService::getService("another_foo_service"); // Java V1_1.IFooService; service = V1_1.IFooService.getService(true /* retry */); -V1_1.IFooService; alternateService = 1_1.IFooService.getService("another", true /* retry */); +V1_1.IFooService; alternateService = V1_1.IFooService.getService("another", true /* retry */); </pre> <p>每个版本的 HIDL 接口都会被视为单独的接口。因此，<code>IFooService</code> 版本 1.1 和 <code>IFooService</code> 版本 2.2 都可以注册为“foo_service”，并且两个接口上的 <code>getService("foo_service")</code> 都可获取该接口的已注册服务。因此，在大多数情况下，注册或发现服务均无需提供名称参数（也就是说名称为“默认”）。</p> diff --git a/zh-cn/devices/architecture/hidl/types.html b/zh-cn/devices/architecture/hidl/types.html index 696c88bb..ad35837f 100644 --- a/zh-cn/devices/architecture/hidl/types.html +++ b/zh-cn/devices/architecture/hidl/types.html @@ -48,7 +48,7 @@ Point[3] triangle; // sized array </ul> <h2 id="represent">数据表示法</h2> -<p>采用 <a href="http://en.cppreference.com/w/cpp/language/data_members#Standard_layout">标准布局</a>（plain-old-data 类型相关要求的子集）的 <code>struct</code> 或 <code>union</code> 在生成的 C++ 代码中具有一致的内存布局，这是依靠 <code>struct</code> 和 <code>union</code> 成员上的显式对齐属性实现的。</p> +<p>采用<a href="http://en.cppreference.com/w/cpp/language/data_members#Standard_layout">标准布局</a>（plain-old-data 类型相关要求的子集）的 <code>struct</code> 或 <code>union</code> 在生成的 C++ 代码中具有一致的内存布局，这是依靠 <code>struct</code> 和 <code>union</code> 成员上的显式对齐属性实现的。</p> <p>基本的 HIDL 类型以及 <code>enum</code> 和 <code>bitfield</code> 类型（一律从基本类型派生而来）会映射到标准 C++ 类型，例如 <a href="http://en.cppreference.com/w/cpp/types/integer">cstdint</a> 中的 <code>std::uint32_t</code>。</p> @@ -171,10 +171,10 @@ typedef struct native_handle <p>当您调用传递（或返回）<code>hidl_handle</code> 对象（复合类型的顶级或一部分）的 HIDL 接口方法时，其中包含的文件描述符的所有权如下所述：</p> <ul> -<li>将 <code>hidl_handle</code> 对象作为参数传递的<strong>调用程序</strong>会保留对其封装的 <code>native_handle_t</code> 中包含的文件描述符的所有权；该调用程序必须在对这些文件描述符的相关操作完成后将其关闭。</li> -<li>返回 <code>hidl_handle</code> 对象（通过将其传递到 <code>_cb</code> 函数）的<strong>进程</strong>会保留对相应对象封装的 <code>native_handle_t</code> 中包含的文件描述符的所有权；该进程必须在对这些文件描述符的相关操作完成后将其关闭。 +<li>将 <code>hidl_handle</code> 对象作为参数传递的<strong>调用程序</strong>会保留对其封装的 <code>native_handle_t</code> 中包含的文件描述符的所有权；在对这些文件描述符完成操作后，该调用程序必须将其关闭。</li> +<li>返回 <code>hidl_handle</code> 对象（通过将其传递到 <code>_cb</code> 函数）的<strong>进程</strong>会保留对相应对象封装的 <code>native_handle_t</code> 中包含的文件描述符的所有权；在对这些文件描述符完成操作后，该进程必须将其关闭。 </li> -<li>接收 <code>hidl_handle</code> 的 <strong>transport</strong> 拥有对相应对象封装的 <code>native_handle_t</code> 中的文件描述符的所有权；接收器可在事务回调期间按原样使用这些文件描述符，但如果您想在回调完成后继续使用这些文件描述符，则必须克隆相应的原生句柄。事务完成时，transport 将自动对文件描述符执行 <code>close()</code> 操作。</li> +<li>接收 <code>hidl_handle</code> 的 <strong>transport</strong> 拥有对相应对象封装的 <code>native_handle_t</code> 中的文件描述符的所有权；接收器可在事务回调期间按原样使用这些文件描述符，但如果想在回调完成后继续使用这些文件描述符，则必须克隆原生句柄。事务完成时，transport 将自动对文件描述符执行 <code>close()</code> 操作。</li> </ul> <p>HIDL 不支持在 Java 中使用句柄（因为 Java 根本不支持句柄）。</p> diff --git a/zh-cn/devices/architecture/kernel/modular-kernels.html b/zh-cn/devices/architecture/kernel/modular-kernels.html index a43c2dff..9cad64e7 100644 --- a/zh-cn/devices/architecture/kernel/modular-kernels.html +++ b/zh-cn/devices/architecture/kernel/modular-kernels.html @@ -196,7 +196,8 @@ on early-init <ol> <li>设备节点路径必须在 <code>fstab</code> 和设备树条目中使用其 by-name 符号链接。<em></em>例如，确保对分区进行命名且设备节点为 <code>/dev/block/…./by-name/{system,vendor,odm}</code>，而不是使用 <code>/dev/block/mmcblk0pX</code> 指定分区。 </li> -<li>在产品的设备配置中（即 <code>device/<em>oem</em>/<em>project</em>/device.mk</code> 中）为 <code>PRODUCT_{SYSTEM,VENDOR}_VERITY_PARTITION</code> 和 <code>CUSTOM_IMAGE_VERITY_BLOCK_DEVICE</code> 指定的路径必须与 <code>fstab</code>/设备树条目中指定 by-name 的相应块设备节点相匹配。<em></em>例如：<pre class="prettyprint"> +<li>在产品的设备配置中（即 <code>device/<em>oem</em>/<em>project</em>/device.mk</code> 中）为 <code>PRODUCT_{SYSTEM,VENDOR}_VERITY_PARTITION</code> 和 <code>CUSTOM_IMAGE_VERITY_BLOCK_DEVICE</code> 指定的路径必须与 <code>fstab</code>/设备树条目中指定 by-name 的相应块设备节点相匹配。<em></em>例如： +<pre class="prettyprint"> PRODUCT_SYSTEM_VERITY_PARTITION := /dev/block/…./by-name/system PRODUCT_VENDOR_VERITY_PARTITION := /dev/block/…./by-name/vendor CUSTOM_IMAGE_VERITY_BLOCK_DEVICE := /dev/block/…./by-name/odm diff --git a/zh-cn/devices/automotive/camera-hal.html b/zh-cn/devices/automotive/camera-hal.html index 62e2f3c8..d8f6d91f 100644 --- a/zh-cn/devices/automotive/camera-hal.html +++ b/zh-cn/devices/automotive/camera-hal.html @@ -200,7 +200,7 @@ deliverFrame(BufferDesc buffer); <p>尽管专用缓冲区格式在技术上是可行的，但兼容性测试要求缓冲区采用以下四种受支持的格式之一：NV21 (YCrCb 4:2:0 Semi-Planar)、YV12 (YCrCb 4:2:0 Planar)、YUYV (YCrCb 4:2:2 Interleaved)、RGBA（32 位 R:G:B:x）。所选格式必须是平台的 GLES 实现上的有效 GL 纹理源。</p> -<p>应用<strong>不</strong>得依赖 <code>bufferId</code> 字段与 <code>BufferDesc</code> 结构中的 <code>memHandle</code> 之间的对应关系。一般来说，<code>bufferId</code> 值对于 HAL 驱动程序实现是私有的，该实现可以在适当的情况下使用（和重新使用）这些值。</p> +<p>应用<strong>不</strong>得依赖 <code>bufferId</code> 字段与 <code>BufferDesc</code> 结构中的 <code>memHandle</code> 之间的任何对应关系。一般来说，<code>bufferId</code> 值对于 HAL 驱动程序实现是私有的，该实现可以在适当的情况下使用（和重新使用）这些值。</p> <h3 id="ievsdisplay">IEvsDisplay</h3> diff --git a/zh-cn/devices/bootloader/partitions-images.html b/zh-cn/devices/bootloader/partitions-images.html index b94f6dc4..5592d756 100644 --- a/zh-cn/devices/bootloader/partitions-images.html +++ b/zh-cn/devices/bootloader/partitions-images.html @@ -26,17 +26,17 @@ Android 设备包含若干个分区，这些分区在启动过程中发挥不同 </p> <ul> <li><strong>boot</strong>：<code>boot</code> 分区包含通过 <code>mkbootimg</code> 组合在一起的内核映像和 RAM 磁盘。为了直接刷写内核而不刷写新的 boot 分区，可以使用虚拟分区：<ul> - <li><strong>kernel</strong>：<code>kernel</code> 虚拟分区通过将新映像写入旧磁盘来仅覆盖内核（zImage、zImage-dtb 和 Image.gz-dtb）。为此，它会确定 eMMC 中现有内核映像的起始位置并将新内核映像复制到该位置。请记住，新内核映像可能会大于现有内核映像。引导加载程序可以通过移动其后的任何数据来腾出空间或放弃出错的操作。如果提供的开发内核不兼容，则可能需要使用相关的内核模块更新 dtb 分区（如果存在）、vendor 分区或 system 分区。 - </li><li><strong>ramdisk</strong>：<code>ramdisk</code> 虚拟分区通过将新映像写入旧磁盘来仅覆盖 RAM 磁盘。为此，它会确定 eMMC 中现有 <code>ramdisk.img</code> 的起始位置并将新 RAM 磁盘映像复制到该位置。请记住，新 RAM 磁盘映像可能会大于现有 RAM 磁盘映像。引导加载程序可以通过移动其后的任何数据来腾出空间或放弃出错的操作。</li></ul> + <li><strong>kernel</strong>：<code>kernel</code> 虚拟分区会通过将新映像写入旧磁盘来仅覆盖内核（zImage、zImage-dtb 和 Image.gz-dtb）。为此，它会确定 eMMC 中现有内核映像的起始位置并将新内核映像复制到该位置。请记住，新内核映像可能会大于现有内核映像。引导加载程序可以通过移动其后的任何数据来腾出空间或放弃出错的操作。如果提供的开发内核不兼容，则可能需要使用相关的内核模块更新 dtb 分区（如果存在）、vendor 分区或 system 分区。 + </li><li><strong>ramdisk</strong>：<code>ramdisk</code> 虚拟分区会通过将新映像写入旧磁盘来仅覆盖 RAM 磁盘。为此，它会确定 eMMC 中现有 <code>ramdisk.img</code> 的起始位置并将新 RAM 磁盘映像复制到该位置。请记住，新 RAM 磁盘映像可能会大于现有 RAM 磁盘映像。引导加载程序可以通过移动其后的任何数据来腾出空间或放弃出错的操作。</li></ul> </li><li><strong>system</strong>：<code>system</code> 分区主要包含 Android 框架。 -</li><li><strong>system</strong>：<code>recovery</code> 分区存储在 OTA 过程中启动的恢复映像。如果设备支持 <a href="/devices/tech/ota/ab/">A/B 更新</a>，则恢复映像可以是启动映像中包含的 RAM 磁盘，而不是单独的映像。 -</li><li><strong>cache</strong>：<code>cache</code> 分区存储临时数据，如果设备使用 A/B 更新，则该分区是可选的。cache 分区不需要可从引导加载程序写入，而只需要可清空。大小取决于设备类型和 userdata 分区的可用空间。目前，50MB 至 100MB 应该没问题。 +</li><li><strong>recovery</strong>：<code>recovery</code> 分区会存储在 OTA 过程中启动的恢复映像。如果设备支持 <a href="/devices/tech/ota/ab/">A/B 更新</a>，则恢复映像可以是启动映像中包含的 RAM 磁盘，而不是单独的映像。 +</li><li><strong>cache</strong>：<code>cache</code> 分区会存储临时数据，如果设备使用 A/B 更新，则该分区是可选的。cache 分区不需要可从引导加载程序写入，而只需要可清空。大小取决于设备类型和 userdata 分区的可用空间。目前，50MB 至 100MB 应该没问题。 </li><li><strong>misc</strong>：<code>misc</code> 分区由恢复映像使用，大小为 4KB 或更大。 </li><li><strong>userdata</strong>：<code>userdata</code> 分区包含用户安装的应用和数据，包括自定义数据。 </li><li><strong>metadata</strong>：当设备已加密且存储空间为 16MB 或更大时，便会使用 <code>metadata</code> 分区。 </li><li><strong>vendor</strong>：<code>vendor</code> 分区包含所有不可分发给 Android 开源项目 (AOSP) 的二进制文件。如果没有专有信息，则可以省略此分区。 </li><li><strong>radio</strong>：<code>radio</code> 分区包含无线装置映像。只有包含无线装置且在专用分区中包含特定于无线装置的软件的设备需要此分区。 -</li><li><strong>tos</strong>：<code>tos</code> 分区存储 Trusty 操作系统的二进制映像，仅在设备包含 Trusty 时使用。</li> +</li><li><strong>tos</strong>：<code>tos</code> 分区会存储 Trusty 操作系统的二进制映像，且仅在设备包含 Trusty 时使用。</li> </ul> <h2 id="flow">流程</h2> <p> @@ -69,7 +69,7 @@ RAM 磁盘应包含适合作为 rootfs 装载的根文件系统。RAM 磁盘映 启动映像应包含通过未经修改的 <code>mkbootimg</code> 组合在一起的内核和 RAM 磁盘。 </p> <p> -<code>mkbootimg</code> 实现位于：<code><a href="https://android.googlesource.com/platform/system/core/+/master/mkbootimg">system/core/mkbootimg</a></code> +您可以在以下位置找到 <code>mkbootimg</code>：<code><a href="https://android.googlesource.com/platform/system/core/+/master/mkbootimg">system/core/mkbootimg</a></code> </p> <p> 引导加载程序会读取由 mkbootimg 生成的 <code><a href="https://android.googlesource.com/platform/system/core/+/master/mkbootimg/bootimg.h">bootimg.h</a></code> 标头文件，并更新内核标头以使其包含正在被刷写的 RAM 磁盘的正确位置和大小、内核基址、命令行参数等。然后，引导加载程序会将启动映像中指定的命令行附加到引导加载程序生成的命令行的末尾。 diff --git a/zh-cn/devices/bootloader/unlock-trusty.html b/zh-cn/devices/bootloader/unlock-trusty.html index 64d955dd..6eefdfc2 100644 --- a/zh-cn/devices/bootloader/unlock-trusty.html +++ b/zh-cn/devices/bootloader/unlock-trusty.html @@ -27,7 +27,7 @@ flashing unlock</code> 设置此解锁模式，设置后，此模式在系统重新启动后应保留。 </p> <p> -除非 <code> fastboot flashing get_unlock_ability </code> 为“1”，否则设备应拒绝 <code>fastboot flashing unlock</code> 命令。如果 <code>get_unlock_ability</code> 为“0”，则用户需要启动到主屏幕，依次转到<em></em>“设置”>“系统”> <a href="https://developer.android.com/studio/debug/dev-options.html">开发者选项</a>菜单并启用 <strong>OEM 解锁</strong>选项，以将 <code>unlock_ability</code> 设置为“1”。该标记在重新启动后以及恢复出厂设置后应保持不变。 +除非<code> fastboot flashing get_unlock_ability </code>为“1”，否则设备应拒绝 <code>fastboot flashing unlock</code> 命令。如果 <code>get_unlock_ability</code> 为“0”，则用户需要启动进入主屏幕，依次转到<em></em>“设置”>“系统”> <a href="https://developer.android.com/studio/debug/dev-options.html">开发者选项</a>菜单并启用 <strong>OEM 解锁</strong>选项，将 <code>unlock_ability</code> 设置为“1”。该标记在重新启动后以及恢复出厂设置后应保持不变。 </p> <p> 发送 <code>fastboot flashing unlock</code> 命令后，设备应提示用户，警告他们可能会遇到非官方映像的问题。确认后，应恢复出厂设置，以防止未经授权的数据访问。即使引导加载程序无法正确重新格式化设备，也应将设备恢复出厂设置。只有在恢复出厂设置后，才能设置持久性标记，以便重新刷写设备。 @@ -52,7 +52,7 @@ unlock</code> 过程中被重置。此措施可防止出现读取上次启动的 1</code>），则引导加载程序应通过将内核命令行变量 <code>androidboot.flash.locked</code>（或 <code>/firmware/android/flash.locked</code> DT 属性）设置为“1”（如果已锁定）或“0”（如果已解锁）来指示锁定状态。 </p> <p> -<strong>注意</strong>：对于支持 <a href="/security/verifiedboot/dm-verity">dm-verity</a> 的设备，您可以改用 <code>ro.boot.verifiedbootstate</code> 来设置 <code>ro.boot.flash.locked</code> 的值，如果验证启动状态显示为橙色，则值为“0”，即已解锁。 +<strong>注意</strong>：对于支持 <a href="/security/verifiedboot/dm-verity">dm-verity</a> 的设备，您可以改用 <code>ro.boot.verifiedbootstate</code> 来设置 <code>ro.boot.flash.locked</code> 的值（如果验证启动状态显示为橙色，则值为“0”，即已解锁）。 </p> <h3 id="flashing-lock-unlock_critical">刷写锁定/解锁关键部分</h3> <p> diff --git a/zh-cn/devices/camera/index.html b/zh-cn/devices/camera/index.html index 0c8130ff..6037fdcd 100644 --- a/zh-cn/devices/camera/index.html +++ b/zh-cn/devices/camera/index.html @@ -38,7 +38,7 @@ <dt>AIDL</dt> <dd>与 CameraService 关联的 Binder 接口可在 <a href="https://android.googlesource.com/platform/frameworks/av/+/master/camera/aidl/android/hardware/ICameraService.aidl">frameworks/av/camera/aidl/android/hardware</a> 中找到。生成的代码会调用较低级别的原生代码以获取对实体相机的访问权限，并返回用于在框架级别创建 <a href="https://developer.android.com/reference/android/hardware/camera2/CameraDevice">CameraDevice</a> 并最终创建 <a href="https://developer.android.com/reference/android/hardware/camera2/CameraCaptureSession.html">CameraCaptureSession</a> 对象的数据。</dd> <dt>原生框架</dt><dt> - </dt><dd>此框架位于 <code>frameworks/av/</code> 中，并提供相当于 <a href="https://developer.android.com/reference/android/hardware/camera2/CameraDevice">CameraDevice</a> 和 <a href="https://developer.android.com/reference/android/hardware/camera2/CameraCaptureSession">CameraCaptureSession</a> 类的原生内容。另请参阅 <a href="https://developer.android.com/ndk/reference/group/camera">NDK camera2 参考</a>。</dd> + </dt><dd>此框架位于 <code>frameworks/av/</code> 中，并提供相当于 <a href="https://developer.android.com/reference/android/hardware/camera2/CameraDevice">CameraDevice</a> 和 <a href="https://developer.android.com/reference/android/hardware/camera2/CameraCaptureSession">CameraCaptureSession</a> 类的原生类。另请参阅 <a href="https://developer.android.com/ndk/reference/group/camera">NDK camera2 参考</a>。</dd> <dt>Binder IPC 接口</dt> <dd>IPC binder 接口用于实现跨越进程边界的通信。调用相机服务的 <code>frameworks/av/camera/camera/aidl/android/hardware</code> 目录中有若干个相机 binder 类。 <a href="https://android.googlesource.com/platform/frameworks/av/+/master/camera/aidl/android/hardware/ICameraService.aidl">ICameraService</a> 是相机服务的接口；<a href="https://android.googlesource.com/platform/frameworks/av/+/master/camera/aidl/android/hardware/camera2/ICameraDeviceUser.aidl">ICameraDeviceUser</a> 是已打开的特定相机设备的接口；<a href="https://android.googlesource.com/platform/frameworks/av/+/master/camera/aidl/android/hardware/ICameraServiceListener.aidl">ICameraServiceListener</a> 和 <a href="https://android.googlesource.com/platform/frameworks/av/+/master/camera/aidl/android/hardware/camera2/ICameraDeviceCallbacks.aidl">ICameraDeviceCallbacks</a> 分别是对应用框架的 CameraService 和 CameraDevice 回调。</dd> @@ -73,7 +73,7 @@ <dl> <dt>应用框架</dt> - <dd>应用代码位于应用框架级别，它利用 <a href="http://developer.android.com/reference/android/hardware/Camera.html">android.hardware.Camera</a> API 与相机硬件进行互动。在内部，此代码会调用相应的 JNI 粘合类，以访问与该相机互动的原生代码。</dd> + <dd>应用代码位于应用框架级别，它利用 <a href="http://developer.android.com/reference/android/hardware/Camera.html">android.hardware.Camera</a> API 与相机硬件进行交互。在内部，此代码会调用相应的 JNI 粘合类，以访问与该相机互动的原生代码。</dd> <dt>JNI</dt> <dd>与 <a href="http://developer.android.com/reference/android/hardware/Camera.html">android.hardware.Camera</a> 关联的 JNI 代码位于 <code>frameworks/base/core/jni/android_hardware_Camera.cpp</code> 中。此代码会调用较低级别的原生代码以获取对实体相机的访问权限，并返回用于在框架级别创建 <a href="http://developer.android.com/reference/android/hardware/Camera.html">android.hardware.Camera</a> 对象的数据。</dd> <dt>原生框架</dt><dt> diff --git a/zh-cn/devices/camera/versioning.html b/zh-cn/devices/camera/versioning.html index f28b4dba..12783cd8 100644 --- a/zh-cn/devices/camera/versioning.html +++ b/zh-cn/devices/camera/versioning.html @@ -284,7 +284,7 @@ Android 8.0 版本引入了 Treble。引入 Treble 后，供应商相机 HAL 实 <p>初始版本的扩展功能 HAL (Android 4.2) [camera2.h]：</p> <ul> -<li>足够用于实现既有的 <code>android.hardware.Camera</code> API。</li> +<li>足够用于实现现有的 <code>android.hardware.Camera</code> API。</li> <li>允许用于相机服务层中的 ZSL 队列。</li> <li>未针对任何新功能（如手动捕获控制、Bayer RAW 捕获，RAW 数据的重新处理等）进行测试。</li> </ul> diff --git a/zh-cn/devices/graphics/build-tests.html b/zh-cn/devices/graphics/build-tests.html index fbbeb7e9..70cfd97a 100644 --- a/zh-cn/devices/graphics/build-tests.html +++ b/zh-cn/devices/graphics/build-tests.html @@ -60,7 +60,7 @@ <p>针对新目标的 deqp 编译系统使用目标编译文件进行配置。目标编译文件可定义该平台支持哪些功能以及需要哪些库或其他包含路径。目标文件名遵循 <code>targets/<var>NAME</var>/<var>NAME</var>.cmake</code> 格式，且选择目标时会用到 <code>DEQP_TARGET</code> 编译参数。</p> -<p>目标文件中的文件路径是相对于基本 <code>deqp</code> 目录（而非 <code>targets/<var>NAME</var></code> 目录）的。目标编译文件可以设置以下标准变量。</p> +<p>目标文件中的文件路径是相对于基本 <code>deqp</code> 目录（而非 <code>targets/<var>NAME</var></code> 目录）的路径。目标编译文件可以设置以下标准变量。</p> <table> <tbody><tr> @@ -138,7 +138,7 @@ DEQP_PLATFORM_COPY_LIBRARIES</code></td> TCUTIL_PLATFORM_SRCS</code></td> <td><p>平台端口来源列表。默认来源取决于功能和操作系统。</p> -<p><strong>注意</strong>：路径是相对于 <code>framework/platform</code> 的</p> +<p><strong>注意</strong>：路径是相对于 <code>framework/platform</code> 的路径</p> </td> </tr> </tbody></table> diff --git a/zh-cn/devices/sensors/batching.html b/zh-cn/devices/sensors/batching.html index 52efd81c..b5a3a6c5 100644 --- a/zh-cn/devices/sensors/batching.html +++ b/zh-cn/devices/sensors/batching.html @@ -68,7 +68,7 @@ 在挂起模式下，<code>max_report_latency</code> 对非唤醒 FIFO 没有影响。</p> <p>当唤醒 FIFO 存满时，或者当其中一个唤醒传感器的 <code>max_report_latency</code> 已过时，硬件必须唤醒 SoC 并报告数据。</p> <p>在这两种情况下（唤醒和非唤醒），只要 SoC 退出挂起模式，即使一些传感器的 <code>max_report_latency</code> 未过，也会产生一个包含所有 FIFO 内容的批处理。这样可最大限度地降低 SoC 再次挂起而必须重新将其唤醒的风险。这进而可以最大限度地降低功耗。</p> -<p>*不允许驱动程序持有唤醒锁定的一个明显例外情况是，在 <code>max_report_latency</code> 小于 1 秒的情况下启用使用<a href="report-modes.html#continuous">连续报告模式</a>的唤醒传感器。在此情况下，驱动程序可以持有唤醒锁，这是因为 SoC 在进入挂起模式前会被唤醒事件唤醒，因此没有机会进入挂起模式。</p> +<p>*不允许驱动程序持有唤醒锁定的一个明显例外情况是，在 <code>max_report_latency</code> 小于 1 秒的情况下启用带<a href="report-modes.html#continuous">连续报告模式</a>的唤醒传感器。在此情况下，驱动程序可以持有唤醒锁，这是因为 SoC 在进入挂起模式前会被唤醒事件唤醒，因此没有机会进入挂起模式。</p> <h2 id="precautions_to_take_when_batching_wake-up_sensors">批处理唤醒传感器时的注意事项</h2> <p>根据设备不同，SoC 可能需要几毫秒才能完全退出挂起模式并开始刷新 FIFO。因此必须在 FIFO 中分配足够的头空间，才能让设备完全退出挂起状态，而不造成唤醒 FIFO 溢出。不得丢失任何事件，并且必须遵照 <code>max_report_latency</code>。</p> <h2 id="precautions_to_take_when_batching_non-wake-up_on-change_sensors">批处理采用 On-change 触发方式的非唤醒传感器时的注意事项</h2> diff --git a/zh-cn/devices/sensors/hal-interface.html b/zh-cn/devices/sensors/hal-interface.html index cfa6147f..071cf321 100644 --- a/zh-cn/devices/sensors/hal-interface.html +++ b/zh-cn/devices/sensors/hal-interface.html @@ -84,8 +84,8 @@ int (*batch)( <p>要详细了解 <code>sampling_period_ns</code> 在不同模式下造成的影响，请参阅<a href="report-modes.html">报告模式</a>。</p> <p>对于连续和变化传感器：</p> <ul> - <li>如果 <code>sampling_period_ns</code> 小于 <code>sensor_t.minDelay</code>，则 HAL 实现必须静默将其限制到 <code>max(sensor_t.minDelay, 1ms)</code>。Android 不支持以高于 1000Hz 的频率生成事件。</li> - <li>如果 <code>sampling_period_ns</code> 大于 <code>sensor_t.maxDelay</code>，则 HAL 实现必须静默将其截断为 <code>sensor_t.maxDelay</code>。</li> + <li>如果 <code>sampling_period_ns</code> 小于 <code>sensor_t.minDelay</code>，则 HAL 实现必须静默地将其限制到 <code>max(sensor_t.minDelay, 1ms)</code>。Android 不支持以高于 1000Hz 的频率生成事件。</li> + <li>如果 <code>sampling_period_ns</code> 大于 <code>sensor_t.maxDelay</code>，则 HAL 实现必须静默地将其截断为 <code>sensor_t.maxDelay</code>。</li> </ul> <p>物理传感器的运行速率和时钟精度有时会受到限制。因此，实际采样率与请求的频率可以不同，只要它满足下表中的要求即可。</p> <table> @@ -115,7 +115,7 @@ int (*batch)( <p>当 <code>max_report_latency_ns>0</code> 时，在检测到传感器事件后无需立即报告。只要所有事件的延迟均不超过 max_report_latency_ns 纳秒，就可以暂时存储在硬件 FIFO 中并批量报告。也就是说，一次性记录并返回上一批之后的所有事件。这样一来，发送到 SoC 的中断数量会减少，并且在传感器捕获数据并进行批量处理时，SoC 可以切换到低电耗模式（闲置）。</p> <p>每个事件都具有相关联的时间戳。事件的报告时间有所延迟并不影响事件时间戳。时间戳必须准确且对应于事件实际发生的时间，而不是对应于事件的报告时间。</p> <p>允许传感器事件暂时存储在硬件 FIFO 中不会修改 <code>poll</code> 的行为：来自于不同传感器的事件可交错，并且和往常一样，来自于同一传感器的所有事件按时间排序。</p> -<p>要详细了解传感器批量处理（包括暂停模式和非暂停模式中的行为），请参阅<a href="batching.html">批量处理</a>。</p> +<p>要详细了解传感器批量处理（包括暂停模式和非暂停模式下的行为），请参阅<a href="batching.html">批量处理</a>。</p> <h2 id="setdelay_sensor_sampling_period">setDelay(sensor, sampling period)</h2> <pre class="prettyprint"> int (*setDelay)( @@ -123,16 +123,16 @@ int (*setDelay)( int sensor_handle, int64_t sampling_period_ns); </pre> -<p>在 1.0 版本之后的 HAL 中，该函数已被弃用，并且无法再调用。改为调用 <code>batch</code> 函数来设置 <code>sampling_period_ns</code> 参数。</p> -<p>在 1.0 版本的 HAL 中，使用 setDelay（而非 batch）来设置 <a href="#sampling_period_ns">sampling_period_ns</a>。</p> +<p>在 1.0 版之后的 HAL 中，该函数已被弃用，并且无法再调用。我们将调用 <code>batch</code> 函数来设置 <code>sampling_period_ns</code> 参数。</p> +<p>在 1.0 版 HAL 中，使用 setDelay（而非 batch）来设置 <a href="#sampling_period_ns">sampling_period_ns</a>。</p> <h2 id="flush_sensor">flush(sensor)</h2> <pre class="prettyprint">int (*flush)(struct sensors_poll_device_1* dev, int sensor_handle);</pre> <p>将<a href="#metadata_flush_complete_events">刷写完成事件</a>添加到指定传感器的硬件 FIFO 的末尾并刷写 FIFO。这些事件会照常提交（即好像最大报告延迟已过期一样）并从 FIFO 中移除。</p> -<p>刷写异步发生（即该函数必须立即返回）。如果实现将一个 FIFO 用于多个传感器，则刷写该 FIFO，并且仅为指定传感器添加刷写完成事件。</p> +<p>刷写会异步执行（即该函数必须立即返回）。如果实现将一个 FIFO 用于多个传感器，则刷写该 FIFO，并且仅为指定传感器添加刷写完成事件。</p> <p>如果指定传感器没有 FIFO（无法缓冲），或者如果 FIFO 在调用时为空，则 <code>flush</code> 仍必须操作成功并为该传感器发送刷写完成事件。这适用于除单次传感器以外的所有传感器。</p> <p>当调用 <code>flush</code> 时，即使该传感器的 FIFO 中已经存在刷写事件，也必须另外创建一个刷写事件并将其添加到 FIFO 的末尾，并且必须刷写 FIFO。<code>flush</code> 调用的次数必须等于创建的刷写完成事件数。</p> -<p><code>flush</code> 不适用于<a href="report-modes.html#one-shot">单次</a>传感器。如果 <code>sensor_handle</code> 引用的是单次传感器，则 <code>flush</code> 必须返回 <code>-EINVAL</code>，并且不生成任何刷写完成元数据事件。</p> -<p>如果操作成功，该函数返回 0；如果指定的传感器是单次传感器或未启用，则返回 <code>-EINVAL</code>；其他情况，返回表示错误的负数。</p> +<p><code>flush</code> 不适用于<a href="report-modes.html#one-shot">单次</a>传感器。如果 <code>sensor_handle</code> 指的是单次传感器，则 <code>flush</code> 必须返回 <code>-EINVAL</code>，并且不生成任何刷写完成元数据事件。</p> +<p>如果操作成功，该函数返回 0；如果指定的传感器是单次传感器或未启用，则返回 <code>-EINVAL</code>；其他情况返回表示错误的负数。</p> <h2 id="poll">poll()</h2> <pre class="prettyprint">int (*poll)(struct sensors_poll_device_t *dev, sensors_event_t* data, int count);</pre> @@ -164,7 +164,7 @@ int (*setDelay)( <p><strong>power</strong>：启用传感器的功耗成本，以毫安为单位。该字段值几乎始终大于底层传感器的相关数据表中报告的功耗。要了解详情，请参阅<a href="sensor-types.html#base_sensors_=_not_equal_to_physical_sensors">基础传感器不等于物理传感器</a>这篇文章；要详细了解如何测量传感器的功耗，请参阅<a href="power-use.html#power_measurement_process">功率测量过程</a>。如果传感器的功耗取决于设备是否正在移动，则 <code>power</code> 字段中报告的值是移动时的功耗。</p> <p><strong>minDelay</strong>：对于连续传感器，指对应于传感器支持的最快速率的采样周期（以微秒为单位）。要详细了解该值是如何使用的，请参阅 <a href="#sampling_period_ns">sampling_period_ns</a>。请注意，<code>minDelay</code> 以微秒为单位，而 <code>sampling_period_ns</code> 以纳秒为单位。对于变化和特殊报告模式传感器，除非另行指定，否则 <code>minDelay</code> 必须为 0。对于单次传感器，该值必须为 -1。</p> <p><strong>maxDelay</strong>：对于连续和变化模式传感器，指对应于传感器支持的最慢速率的采样周期（以微秒为单位）。要详细了解该值是如何使用的，请参阅 <a href="#sampling_period_ns">sampling_period_ns</a>。请注意，<code>maxDelay</code> 以微秒为单位，而 <code>sampling_period_ns</code> 以纳秒为单位。对于特殊和单次传感器，<code>maxDelay</code> 必须为 0。</p> -<p><strong>fifoReservedEventCount</strong>：硬件 FIFO 中为该传感器保留的事件数。如果该传感器具有专属的 FIFO，则 <code>fifoReservedEventCount</code> 是该专属 FIFO 的大小。如果该传感器与其他传感器共用 FIFO，则 <code>fifoReservedEventCount</code> 是为该传感器保留的 FIFO 部分的大小。对于大多数共享 FIFO 的系统以及没有硬件 FIFO 的系统，该值为 0。</p> +<p><strong>fifoReservedEventCount</strong>：在硬件 FIFO 中为该传感器保留的事件数。如果该传感器具有专属的 FIFO，则 <code>fifoReservedEventCount</code> 是该专属 FIFO 的大小。如果该传感器与其他传感器共用 FIFO，则 <code>fifoReservedEventCount</code> 是为该传感器保留的 FIFO 部分的大小。对于大多数共享 FIFO 的系统以及没有硬件 FIFO 的系统，该值为 0。</p> <p><strong>fifoMaxEventCount</strong>：FIFO 中可为该传感器存储的最大事件数。该值总是大于或等于 <code>fifoReservedEventCount</code>。该值用于估计在假设不激活任何其他传感器的情况下，以特定速率注册到传感器时 FIFO 多快会被填满。对于没有硬件 FIFO 的系统，<code>fifoMaxEventCount</code> 为 0。要了解详情，请参阅<a href="batching.html">批量处理</a>。</p> <p>对于官方传感器类型的传感器，一些字段会被框架覆盖。例如，强制要求<a href="sensor-types.html#accelerometer">加速度计</a>传感器使用连续报告模式，并强制要求<a href="sensor-types.html#heart_rate">心率</a>监测器受 <code>SENSOR_PERMISSION_BODY_SENSORS</code> 权限的保护。</p> <h2 id="sensors_event_t">sensors_event_t</h2> diff --git a/zh-cn/devices/storage/index.html b/zh-cn/devices/storage/index.html index c3540ecf..9fda6f65 100644 --- a/zh-cn/devices/storage/index.html +++ b/zh-cn/devices/storage/index.html @@ -1,5 +1,5 @@ <html devsite><head> - <title>存储设备</title> + <title>存储</title> <meta name="project_path" value="/_project.yaml"/> <meta name="book_path" value="/_book.yaml"/> </head> diff --git a/zh-cn/devices/tech/admin/provision.html b/zh-cn/devices/tech/admin/provision.html index 69808f05..c8bc21e9 100644 --- a/zh-cn/devices/tech/admin/provision.html +++ b/zh-cn/devices/tech/admin/provision.html @@ -22,8 +22,7 @@ <p>本页面介绍了使用 NFC 或通过云服务向企业用户部署设备的过程（要查看完整的要求列表，请参阅<a href="/devices/tech/admin/implement.html">实现设备管理</a>）。</p> -<p>首先，请下载 <a href="https://github.com/googlesamples/android-NfcProvisioning">NfcProvisioning APK</a> 和 <a href="https://github.com/googlesamples/android-DeviceOwner">Android-DeviceOwner APK</a>。 -</p> +<p>首先，请下载 <a href="https://github.com/googlesamples/android-NfcProvisioning">NfcProvisioning APK</a> 和 <a href="https://github.com/googlesamples/android-DeviceOwner">Android-DeviceOwner APK</a>。</p> <p class="caution"><strong>注意</strong>：如果配置已经开始，则必须先将受影响的设备恢复出厂设置。</p> diff --git a/zh-cn/devices/tech/dalvik/configure.html b/zh-cn/devices/tech/dalvik/configure.html index 929d9920..7fd9d357 100644 --- a/zh-cn/devices/tech/dalvik/configure.html +++ b/zh-cn/devices/tech/dalvik/configure.html @@ -149,7 +149,7 @@ PRODUCT_COPY_FILES += <filename>:system/etc/preloaded-classes </pre> -<p class="note"><strong>注意</strong>：如果有任何从 <code>build/target/product/base.mk</code> 提取默认值的产品配置 Makefile，则此行必须放置在沿用此类 Makefile 的行之前。</p> +<p class="note"><strong>注意</strong>：如果有任何从 <code>build/target/product/base.mk</code> 提取默认值的产品配置 Makefile，则此行必须放置在沿用任何这类 Makefile 的行之前。</p> <li>映像类列表</li> @@ -179,7 +179,7 @@ PRODUCT_DEX_PREOPT_BOOT_FLAGS PRODUCT_COPY_FILES += <filename>:system/etc/compiled-classes </pre> -<p class="note"><strong>注意</strong>：如果有任何从 <code>build/target/product/base.mk</code> 提取默认值的产品配置 Makefile，则此行必须放置在沿用此类 Makefile 的行之前。</p> +<p class="note"><strong>注意</strong>：如果有任何从 <code>build/target/product/base.mk</code> 提取默认值的产品配置 Makefile，则此行必须放置在沿用任何这类 Makefile 的行之前。</p> </ul> <h3 id="runtime_configuration">运行时配置</h3> diff --git a/zh-cn/devices/tech/dalvik/gc-debug.html b/zh-cn/devices/tech/dalvik/gc-debug.html index f4fc2225..c0369d60 100644 --- a/zh-cn/devices/tech/dalvik/gc-debug.html +++ b/zh-cn/devices/tech/dalvik/gc-debug.html @@ -20,7 +20,7 @@ limitations under the License. --> -<p>本文档介绍如何调试 Android 运行时 (ART) 垃圾回收 (GC) 的正确性和性能问题。本文档解释了如何使用 GC 验证选项、确定 GC 验证失败的解决方案，以及测量并解决 GC 性能问题。</p> +<p>本文档介绍如何调试 Android 运行时 (ART) 垃圾回收 (GC) 的正确性和性能问题，并解释了如何使用 GC 验证选项、确定 GC 验证失败的解决方案，以及测量并解决 GC 性能问题。</p> <p>有关处理 ART 的说明，请参阅 <a href="index.html">ART 和 Dalvik</a>、<a href="dex-format.html">Dalvik 可执行格式</a>以及此 <a href="index.html">ART 和 Dalvik</a> 部分的其他页面。有关验证应用行为的其他帮助信息，请参阅<a href="http://developer.android.com/guide/practices/verifying-apps-art.html">在 Android 运行时 (ART) 上验证应用行为</a>。</p> @@ -208,7 +208,7 @@ adb shell setprop dalvik.vm.checkjni true adb shell setprop dalvik.vm.jniopts forcecopy </pre> -<p>CheckJNI 应捕获错误的一个示例是超出从 <code>GetPrimitiveArrayCritical</code> 获取的数组末端的写入。该操作很可能会破坏 Java 堆。如果写入位于 CheckJNI 红色区域内，则在调用相应 <code>ReleasePrimitiveArrayCritical</code> 时，CheckJNI 将会捕获该问题。否则，写入将最终损坏 Java 堆中的一些随机对象，并可能会导致之后出现 GC 崩溃。<ptr></ptr>如果崩溃的内存是引用字段，则 GC 可能会捕获错误并输出“Tried to mark <em></em>not contained by any spaces”这一错误消息。</p> +<p>CheckJNI 应捕获错误的一个示例是超出从 <code>GetPrimitiveArrayCritical</code> 获取的数组末端的写入。该操作很可能会破坏 Java 堆。如果写入位于 CheckJNI 红色区域内，则在调用相应 <code>ReleasePrimitiveArrayCritical</code> 时，CheckJNI 将会捕获该问题。否则，写入将最终损坏 Java 堆中的一些随机对象，并可能会导致之后出现 GC 崩溃。<em></em>如果崩溃的内存是引用字段，则 GC 可能会捕获错误并输出“Tried to mark <ptr></ptr>not contained by any spaces”这一错误消息。</p> <p>当 GC 尝试标记无法找到空间的对象时，就会发生此错误。在此检查失败后，GC 会遍历根，并尝试查看无效对象是否为根。结果共有两个选项：对象为根或非根。</p> diff --git a/zh-cn/devices/tech/debug/gdb.html b/zh-cn/devices/tech/debug/gdb.html index 4062fcd4..7f17247a 100644 --- a/zh-cn/devices/tech/debug/gdb.html +++ b/zh-cn/devices/tech/debug/gdb.html @@ -52,7 +52,7 @@ Listening on port 5039 gdbclient <var>APP_PID</var> </pre> -<p>最后，在 <strong>gdb</strong> 提示处输入 <code>gdb</code>。</p> +<p>最后，在 <code>gdb</code> 提示处输入 <strong>continue</strong>。</p> <p class="note"><strong>注意</strong>：如果您指定了错误的 <code>gdbserver</code>，将会收到没任何帮助的错误消息（例如“<code>Reply contains invalid hex digit 59</code>”）。</p> diff --git a/zh-cn/devices/tech/debug/sanitizers.html b/zh-cn/devices/tech/debug/sanitizers.html index dfd25ddc..8285f5b5 100644 --- a/zh-cn/devices/tech/debug/sanitizers.html +++ b/zh-cn/devices/tech/debug/sanitizers.html @@ -37,7 +37,7 @@ Android 编译版本最好在启用排错程序（如 AddressSanitizer 和 Undef <li>释放后再使用</li> </ul> <p> -Android 允许在完整编译级别和在<a href="/devices/tech/debug/asan#addresssanitizer_in_the_apps">应用级别</a>通过 asanwrapper 进行 <a href="/devices/tech/debug/asan">ASan instrumentation</a>。 +Android 允许在完整编译级别和在<a href="/devices/tech/debug/asan#addresssanitizer_in_the_apps">应用级别</a>通过 asanwrapper 进行 <a href="/devices/tech/debug/asan">ASan 插桩</a>。 </p> <p> AddressSanitizer 对所有与内存相关的函数调用（包括 alloca、malloc 和 free）进行插桩，并使用被读取或写入时会触发 ASan 回调的内存填充所有变量和已分配的内存区域。 diff --git a/zh-cn/devices/tech/ota/sign_builds.html b/zh-cn/devices/tech/ota/sign_builds.html index aa77396d..f338e994 100644 --- a/zh-cn/devices/tech/ota/sign_builds.html +++ b/zh-cn/devices/tech/ota/sign_builds.html @@ -120,7 +120,7 @@ LOCAL_CERTIFICATE := device/yoyodyne/security/special <h2 id="advanced-signing-options">高级签名选项</h2> <p>当您运行 <code>sign_target_files_apks</code> 脚本时，必须在命令行中指定在编译版本中使用的每个密钥的替换密钥。<code>-k <i>src_key</i>=<i> -dest_key</i></code> 标记每次只能指定一个替换密钥。<code>-d <i>dir</i></code> 标记可让您指定一个包含四个密钥（可替换 <code>build/target/product/security</code> 中的所有相应密钥）的目录；这相当于使用四次 <code>-k</code> 来指定相应的映射：</p> +dest_key</i></code> 标记每次只能指定一个替换密钥。<code>-d <i>dir</i></code> 标记可让您指定一个包含四个密钥（以替换 <code>build/target/product/security</code> 中的所有相应密钥）的目录；这相当于使用四次 <code>-k</code> 来指定相应的映射：</p> <pre class="devsite-click-to-copy"> build/target/product/security/testkey = dir/releasekey @@ -129,7 +129,7 @@ build/target/product/security/shared = dir/shared build/target/product/security/media = dir/media </pre> -<p>对于假定的 tardis 产品，您需要五个受密码保护的密钥：四个用于替换 <code>build/target/product/security</code> 中的四个密钥，其余一个则用于替换 SpecialApp 所需的另外一个 <code>keydevice/yoyodyne/security/special</code>（请参见上面的示例）。如果密钥位于以下文件中：</p> +<p>对于假定的 tardis 产品，您需要五个受密码保护的密钥：四个用于替换 <code>build/target/product/security</code> 中的四个密钥，其余一个用于替换 SpecialApp 所需的另外一个 <code>keydevice/yoyodyne/security/special</code>（请参见上面的示例）。如果密钥位于以下文件中：</p> <pre class="devsite-click-to-copy"> vendor/yoyodyne/security/tardis/releasekey.x509.pem diff --git a/zh-cn/devices/tv/index.html b/zh-cn/devices/tv/index.html index 42234d92..1aa79fa1 100644 --- a/zh-cn/devices/tv/index.html +++ b/zh-cn/devices/tv/index.html @@ -176,7 +176,7 @@ <figcaption><strong>图 6.</strong> Android TV KeyEvent</figcaption> </figure> -<p>上图显示了遥控器上的按钮事件如何传递到特定的 TV Input，从而实现画中画 (PIP) 显示。这些按下按钮的操作由设备制造商提供的硬件驱动程序进行解析，从而将硬件扫描码转换为 Android 键码，并将它们作为 <a href="http://developer.android.com/reference/android/view/KeyEvent.html">KeyEvents</a> 传递到标准的<a href="/devices/input/overview.html">输入管道</a> <code>InputReader</code> 和 <code>InputDispatcher</code> 函数。 +<p>上图显示了遥控器上的按钮事件如何传递到特定的 TV Input，从而实现画中画 (PIP) 显示。这些按下按钮的操作由设备制造商提供的硬件驱动程序进行解析，从而将硬件扫描码转换为 Android 键码，并将它们作为 <a href="http://developer.android.com/reference/android/view/KeyEvent.html">KeyEvents</a> 传递到标准的 Android <a href="/devices/input/overview.html">输入管道</a> <code>InputReader</code> 和 <code>InputDispatcher</code> 函数。 当 TV 应用获得焦点时，它们就会在 TV 应用上触发事件。</p> <p>只有系统 TV Input 才有资格接收 <code>InputEvents</code>（前提是这些系统 TV Input 具有 <code>RECEIVE_INPUT_EVENT</code> 系统权限）。 diff --git a/zh-cn/security/advisory/index.html b/zh-cn/security/advisory/index.html index 337030c3..444e8a53 100644 --- a/zh-cn/security/advisory/index.html +++ b/zh-cn/security/advisory/index.html @@ -35,7 +35,7 @@ <tr> <td><a href="2016-03-18.html">2016-03-18</a></td> <td> - <a href="/security/advisory/2016-03-18.html">English</a> / <a href="/security/advisory/2016-03-18.html?hl=ja">日本語</a> / <a href="/security/advisory/2016-03-18.html?hl=ko">한국어</a> / <a href="/security/advisory/2016-03-18.html?hl=ru">ру́сский</a> / <a href="/security/advisory/2016-03-18.html?hl=zh-cn">中文 (中国)</a> / <a href="/security/advisory/2016-03-18.html?hl=zh-tw">中文 (台灣)</a> + <a href="/security/advisory/2016-03-18.html">English</a> / <a href="/security/advisory/2016-03-18.html?hl=ja">日本語</a> / <a href="/security/advisory/2016-03-18.html?hl=ko">한국어</a> / <a href="/security/advisory/2016-03-18.html?hl=ru">ру́сский</a> / <a href="/security/advisory/2016-03-18.html?hl=zh-cn">中文 (中国)</a> / <a href="/security/advisory/2016-03-18.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2016 年 3 月 18 日</td> </tr> diff --git a/zh-cn/security/enhancements/enhancements42.html b/zh-cn/security/enhancements/enhancements42.html index 3710e85e..9c6383b8 100644 --- a/zh-cn/security/enhancements/enhancements42.html +++ b/zh-cn/security/enhancements/enhancements42.html @@ -33,9 +33,9 @@ Android 提供了一个多层安全模型，<a href="/security/index.html">Andro <li><strong>改进后的 Android 权限显示方式</strong> - 权限划分到了多个对用户来说更清晰明了的组中。在审核权限时，用户可以点击权限来查看关于相应权限的更多详细信息。</li> -<li><strong>installd 加固</strong> - <code>installd</code> 守护进程不会以 Root 用户身份运行，从而可减小 Root 提权攻击的潜在攻击面。</li> +<li><strong>installd 安全强化</strong> - <code>installd</code> 守护进程不会以 Root 用户身份运行，从而可减小 Root 提权攻击的潜在攻击面。</li> -<li><strong>init 脚本加固</strong> - init 脚本现在应用 <code>O_NOFOLLOW</code> 语义来防范与符号链接相关的攻击。</li> +<li><strong>init 脚本安全强化</strong> - init 脚本现在应用 <code>O_NOFOLLOW</code> 语义来防范与符号链接相关的攻击。</li> <li><strong>FORTIFY_SOURCE</strong> - Android 现在实现了 <code>FORTIFY_SOURCE</code>，以供系统库和应用用于防范内存损坏。</li> diff --git a/zh-cn/security/selinux/validate.html b/zh-cn/security/selinux/validate.html index 408fc080..8657aa1a 100644 --- a/zh-cn/security/selinux/validate.html +++ b/zh-cn/security/selinux/validate.html @@ -22,13 +22,13 @@ <p>Android 强烈建议 OEM 全面测试其 SELinux 实现。制造商在实现 SELinux 时，应先在一组测试设备上实施新政策。</p> -<p>实施新政策后，可通过执行 getenforce 命令来确认 SELinux 在设备上的运行模式是否正确</p> +<p>实施新政策后，您可以通过执行 <code>getenforce</code> 命令来确认 SELinux 在设备上的运行模式是否正确。</p> -<p>该命令将会显示全局 SELinux 模式：强制或宽容。请注意，该命令只会显示全局 SELinux 模式。要确定每个域的 SELinux 模式，您必须查看相应的文件，或运行带有适当 (-p) 标记的最新版 <code>sepolicy-analyze</code>（位于 /platform/system/sepolicy/tools/ 中）。</p> +<p>该命令会显示全局 SELinux 模式：强制或宽容。要确定每个域的 SELinux 模式，您必须查看相应的文件，或运行带有适当 (<code>-p</code>) 标记的最新版 <code>sepolicy-analyze</code>（位于 <a href="https://android.googlesource.com/platform/system/sepolicy/+/master/tools/" class="external"><code>/platform/system/sepolicy/tools/</code></a> 中）。</p> <h2 id="reading_denials">读取拒绝事件</h2> -<p>接下来是检查是否存在错误。错误会以事件日志的形式传给 dmesg 和 <code>logcat</code>，并可在设备上从本地查看。制造商应先检查这些设备上传给 dmesg 的 SELinux 输出并优化设置，然后再在宽容模式下公开发布，最后切换到强制模式。SELinux 日志消息中包含“avc:”字样，因此可使用 <code>grep</code> 轻松找到。您可以使用 <code>cat /proc/kmsg</code> 来获取当前的拒绝事件日志，也可以使用 <code>cat /sys/fs/pstore/console-ramoops</code> 来获取上次启动时的拒绝事件日志。</p> +<p>检查是否有错误，错误会以事件日志的形式传给 <code>dmesg</code> 和 <code>logcat</code>，并可在设备上从本地查看。制造商应先检查这些设备上传给 <code>dmesg</code> 的 SELinux 输出并优化设置，然后再在宽容模式下公开发布，最后切换到强制模式。SELinux 日志消息中包含“<code>avc:</code>”字样，因此可使用 <code>grep</code> 轻松找到。您可以通过运行 <code>cat /proc/kmsg</code> 来获取当前的拒绝事件日志，也可以通过运行 <code>cat /sys/fs/pstore/console-ramoops</code> 来获取上次启动时的拒绝事件日志。</p> <p>根据这些输出内容，制造商可以轻松发现系统用户或组件违反 SELinux 政策的行为。然后，制造商便可更改相应软件和/或 SELinux 政策，以防范此类恶意行为。</p> @@ -48,7 +48,7 @@ scontext=u:r:shell:s0 tcontext=u:r:netd:s0 tclass=unix_stream_socket </li><li>顶部的 <code>comm="ping"</code> 可帮助您了解拒绝事件发生时正在运行的程序。在此示例中，给出的信息非常清晰明了。 </li></ul> -<p>下面是另一个示例：</p> +<p>我们再看看另一个示例：</p> <pre class="devsite-terminal devsite-click-to-copy">adb shell su root dmesg | grep 'avc: '</pre> <p>输出：</p> <pre> @@ -60,8 +60,8 @@ tcontext=u:object_r:kmem_device:s0 tclass=chr_file <p>以下是此拒绝事件的关键元素：</p> <ul> - <li><em></em>操作 - 试图进行的操作列在花括号中：<code>read write</code> 或 <code>setenforce</code>。 - </li><li><em></em>操作方 - <code>scontext</code>（来源环境）条目表示操作方；在此例中为<code> rmt_storage</code> 守护进程。 + <li><em></em>操作 - 试图进行的操作会使用括号突出显示：<code>read write</code> 或 <code>setenforce</code>。 + </li><li><em></em>操作方 - <code>scontext</code>（来源环境）条目表示操作方；在此例中为 <code> rmt_storage</code> 守护进程。 </li><li><em></em>对象 - <code>tcontext</code>（目标环境）条目表示是对哪个对象执行操作；在此例中为 kmem。 </li><li><em></em>结果 - <code>tclass</code>（目标类别）条目表示操作对象的类型；在此例中为 <code>chr_file</code>（字符设备）。 </li></ul> diff --git a/zh-cn/setup/build/jack.html b/zh-cn/setup/build/jack.html index 50bfb63a..5871e50b 100644 --- a/zh-cn/setup/build/jack.html +++ b/zh-cn/setup/build/jack.html @@ -20,7 +20,9 @@ limitations under the License. --> -<aside class="warning"><strong>警告</strong>：在 <a href="https://android-developers.googleblog.com/2017/03/future-of-java-8-language-feature.html" class="external">2017 年 3 月 14 日公告</a>发布之后，Jack 工具链已被弃用。Jack 是 Android 6.0–8.1 的默认 Android 编译工具链。</aside> +<aside class="warning"> + <strong>警告</strong>：在 <a href="https://android-developers.googleblog.com/2017/03/future-of-java-8-language-feature.html" class="external">2017 年 3 月 14 日公告</a>发布之后，Jack 工具链已被弃用。Jack 是 Android 6.0 - 8.1 的默认 Android 编译工具链。 +</aside> <p>Jack 是一种 Android 工具链，用于将 Java 源代码编译成 Android dex 字节码。要使用 Jack，您只需使用标准的 Makefile 命令来编译源代码树或您的项目即可，无需进行任何其他操作。Android 8.1 是使用 Jack 的最后一个版本。</p> @@ -28,21 +30,21 @@ <p>Jack 的工作原理如下：</p> <img src="../images/jack_overview.png" alt="Jack 概览"/> -<figcaption><strong>图 1.</strong> Jack 概览。</figcaption> +<figcaption><strong>图 1</strong> Jack 概览</figcaption> <h3 id="jack_library">Jack 库格式</h3> <p>Jack 具有自己的 .jack 文件格式，其中包含相应库的预编译 dex 代码，可实现更快速的编译（dex 预处理）。</p> <img src="../images/jack_library.png" alt="Jack 库文件内容"/> -<figcaption><strong>图 2.</strong> Jack 库文件内容。</figcaption> +<figcaption><strong>图 2.</strong> Jack 库文件内容</figcaption> <h3 id="jill">Jill</h3> <p>Jill 工具可将现有的 .jar 库转换为新的库格式，如下图所示。</p> <img src="../images/jack_jill.png" alt="使用 Jill 导入 .jar 库"/> -<figcaption><strong>图 3.</strong> 导入现有 .jar 库的工作流程。</figcaption> +<figcaption><strong>图 3.</strong> 导入现有 .jar 库的工作流程</figcaption> <h2 id="using_jack">Jack 编译服务器</h2> @@ -85,37 +87,16 @@ </tr> <tr> <td>编译因“Cannot launch background server”（无法启动后台服务器）而失败</td> -<td>最可能的原因是您计算机上的 TCP 端口都被占用了。您可以通过修改 <code>$HOME/.jack</code>（<code>SERVER_PORT_SERVICE</code> 和 <code>SERVER_PORT_ADMIN</code> 变量）来更改端口。 - -<br /><br />如果上述方法无法解决问题，请报告该错误（务必附上您的编译日志和 <a href="#jack_log">Jack 服务器日志</a>）。要解决这种问题，请通过修改 <code>$HOME/.jack</code> 并将 <code>SERVER</code> 更改为 false 来停用 Jack 编译服务器。遗憾的是，这将大大降低编译速度，并可能会迫使您使用加载控制（<code>make</code> 的选项 <code>-l</code> ）启动 <code>make -j</code>。 -</td> +<td>最可能的原因是您计算机上的 TCP 端口都被占用了。您可以通过修改 <code>$HOME/.jack</code>（<code>SERVER_PORT_SERVICE</code> 和 <code>SERVER_PORT_ADMIN</code> 变量）来更改端口。要解决这种问题，请通过修改 <code>$HOME/.jack</code> 并将 <code>SERVER</code> 更改为 false 来停用 Jack 编译服务器。遗憾的是，这将大大降低编译速度，并可能会迫使您使用加载控制（<code>make</code> 的选项 <code>-l</code> ）启动 <code>make -j</code>。</td> </tr> <tr> <td>编译卡住了，没有任何进展</td> -<td>报告并提供以下信息（如果可能）： -<br /> -<ul> -<li>卡住时所在的命令行。</li> -<li>此命令行的输出。</li> -<li>执行 <code>jack-admin server-stat</code> 获得的结果。</li> -<li><code>$HOME/.jack</code> 文件。</li> -<li><a href="#jack_log">Jack 服务器日志</a>（已转储服务器状态）的内容。要获取服务器日志，请执行以下操作： - <ul> - <li>通过运行 <code>jack-admin list-server</code> 查找 Jack 后台服务器进程。</li> - <li>向该服务器发送 <code>kill -3</code> 命令，将其状态转储到日志文件中。</li> - </ul> -</li> -<li>执行 <code>ls -lR $TMPDIR/jack-$USER</code> 获得的结果。</li> -<li>运行 <code>ps j -U $USER</code> 获得的结果。</li> -</ul> - -要解决这种问题，请使用 <code>jack-admin kill-server</code> 停止 Jack 后台服务器，然后移除临时目录（<code>/tmp</code> 或 <code>$TMPDIR</code>）的 <code>jack-$USER</code> 中包含的临时目录。 -</td> +<td>要解决这种问题，请使用 <code>jack-admin kill-server</code>) 停止 Jack 后台服务器，然后移除临时目录（<code>/tmp</code> 或 <code>$TMPDIR</code>）的 <code>jack-$USER</code> 中包含的临时目录。</td> </tr> </tbody></table> <h3 id="jack_log">查找 Jack 日志</h3> -如果您曾针对 dist 目标运行 <code>make</code> 命令，则 Jack 日志位于 <code>$ANDROID_BUILD_TOP/out/dist/logs/jack-server.log</code> 中。如果没有，则您可以通过运行 <code>jack-admin server-log</code> 找到该日志。对于可重现的 Jack 错误，您可以通过设置以下变量来获取更详细的日志：<p></p> +<p>如果您曾针对 dist 目标运行 <code>make</code> 命令，则 Jack 日志位于 <code>$ANDROID_BUILD_TOP/out/dist/logs/jack-server.log</code> 中。如果没有，则您可以通过运行 <code>jack-admin server-log</code> 找到该日志。对于可重现的 Jack 错误，您可以通过设置以下变量来获取更详细的日志：</p> <pre class="devsite-terminal devsite-click-to-copy"> export ANDROID_JACK_EXTRA_ARGS="--verbose debug --sanity-checks on -D sched.runner=single-threaded" @@ -144,7 +125,7 @@ unset ANDROID_JACK_EXTRA_ARGS <p>在生成 Jack 库文件时，系统会生成该库的 <code>.dex</code> 文件并将其作为 dex 预处理文件存储在 <code>.jack</code> 库文件中。在进行编译时，Jack 会重复使用每个库中的 dex 预处理文件。所有库均会经过 dex 预处理：</p> <img src="../images/jack_predex.png" alt="包含 dex 预处理文件的 Jack 库"/> -<figcaption><strong>图 4.</strong> 包含 dex 预处理文件的 Jack 库。</figcaption> +<figcaption><strong>图 4.</strong> 包含 dex 预处理文件的 Jack 库</figcaption> <p>如果在编译过程中使用了压缩、混淆或重新打包功能，则 Jack 不会重复使用库的 dex 预处理文件。</p> diff --git a/zh-cn/setup/community.html b/zh-cn/setup/community.html index b72eb318..94a5487c 100644 --- a/zh-cn/setup/community.html +++ b/zh-cn/setup/community.html @@ -155,9 +155,16 @@ <li>通过电子邮件订阅：<a href="mailto:android-ota+subscribe@googlegroups.com">android-ota</a></li> </ul> </li> +<li> +<p><em></em>android-compatibility：如果您有关于 Android 兼容性的技术问题，但本网站未提供解答，则您可以向此名单上的同行寻求帮助。</p> +<ul> +<li>通过 Google 网上论坛订阅：<a href="https://groups.google.com/forum/?fromgroups#!forum/android-compatibility">android-compatibility</a></li> +<li>通过电子邮件订阅：<a href="mailto:android-compatibility+subscribe@googlegroups.com">android-compatibility</a></li> +</ul> +</li> </ul> -<h3 id="audience">受众群体</h3> +<h3 id="audience">目标群体</h3> <p>这些论坛适合使用 Android 平台的开发者。我们欢迎每个人加入论坛，但前提是要遵守下述社区政策。我们的用户会互相帮助，包括“开放手机联盟”(Open Handset Alliance) 成员在内的很多专家也会在这些论坛中发帖。</p> <p>只要主题在某种程度上与 Android 相关，我们都不会加以限制。不过，由于这些论坛非常繁忙，因此在发帖提问之前请先在归档内容中搜索一下，您也许会发现自己的问题已经有人解答过了。</p> @@ -238,4 +245,9 @@ </li> </ul> +<h2 id="for-business-inquiries">关于 Google 移动服务许可方面的问题</h2> +<p>请通过 <a href="https://www.android.com/gms/contact/">GMS 联系</a>表单咨询有关 <a href="https://www.android.com/gms/">Google 移动服务</a>许可方面的问题。其他非 GMS 合作伙伴关系问询可发送至 <a href="mailto:android-partnerships@google.com">android-partnerships@google.com</a>。</p> + +<p>我们会阅读收到的每封邮件，但无法一一进行回复。如果我们能够提供帮助，一定会与您联系！</p> + </body></html>
\ No newline at end of file diff --git a/zh-cn/setup/develop/64-bit-builds.html b/zh-cn/setup/develop/64-bit-builds.html index 93e2325e..2c6e904d 100644 --- a/zh-cn/setup/develop/64-bit-builds.html +++ b/zh-cn/setup/develop/64-bit-builds.html @@ -28,7 +28,7 @@ <p>对于可执行文件和应用，编译系统默认仅编译 64 位版本，但您可以使用一个全局 <code>BoardConfig.mk</code> 变量或针对特定模块的变量来替换此设置。</p> -<p class="caution"><strong>注意</strong>：如果某个应用提供了一个可供其他应用（可以是 32 位，也可以是 64 位）使用的 API，那么在该应用的清单中，<code>android:multiarch</code> 属性的值必须设为 <code>true</code> 以避免可能出现的错误。</p> +<p class="caution"><strong>注意</strong>：如果某个应用提供了一个可供其他应用（32 位或 64 位）使用的 API，那么在该应用的清单中，<code>android:multiarch</code> 属性的值必须设为 <code>true</code> 以避免可能出现的错误。</p> <h2 id="product_configuration">产品配置</h2> diff --git a/zh-tw/security/bulletin/2018-02-01.html b/zh-tw/security/bulletin/2018-02-01.html index 19c787aa..e74dfb5e 100644 --- a/zh-tw/security/bulletin/2018-02-01.html +++ b/zh-tw/security/bulletin/2018-02-01.html @@ -21,7 +21,8 @@ --> <p><em>發佈日期：2018 年 2 月 5 日 | 更新日期：2018 年 4 月 2 日</em></p> -<p>Android 安全性公告羅列了會對 Android 裝置造成影響的安全性漏洞，並說明各項相關細節。2018-02-05 之後的安全性修補程式等級已解決了這些問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 +<p> +Android 安全性公告列舉對 Android 裝置造成影響的安全性漏洞，並說明各項相關細節。2018-02-05 之後的安全性修補程式等級已解決了這些問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 </p> <p> Android 的合作夥伴至少會提前一個月收到公告中所有問題的相關通知。這些問題的原始碼修補程式已發佈到 Android 開放原始碼計劃 (AOSP) 存放區中，且公告中亦提供相關連結。此外，本公告也提供 Android 開放原始碼計劃以外的修補程式連結。</p> @@ -173,14 +174,14 @@ Android 的合作夥伴至少會提前一個月收到公告中所有問題的相 <td>A-64610940<a href="#asterisk">*</a></td> <td>ID</td> <td>高</td> - <td>開機載入器</td> + <td>系統啟動載入程式</td> </tr> <tr> <td>CVE-2017-13247</td> <td>A-71486645<a href="#asterisk">*</a></td> <td>EoP</td> <td>中</td> - <td>開機載入器</td> + <td>系統啟動載入程式</td> </tr> </tbody></table> @@ -369,7 +370,8 @@ QC-CR#2114187</a></td> </tbody></table> <h3 id="qualcomm-closed-source-components">Qualcomm 封閉原始碼元件</h3> -<p>以下列出會影響 Qualcomm 元件的安全性漏洞，詳情請參考適用的 Qualcomm AMSS 安全性公告或安全性警示。這些問題的嚴重程度是由 Qualcomm 直接評定。</p> +<p> +以下列出會影響 Qualcomm 元件的安全性漏洞，詳情請參考適用的 Qualcomm AMSS 安全性公告或安全性警示。這些問題的嚴重程度是由 Qualcomm 直接評定。</p> <table> <colgroup><col width="17%" /> diff --git a/zh-tw/security/bulletin/2018-03-01.html b/zh-tw/security/bulletin/2018-03-01.html index 8437d8ae..d0112610 100644 --- a/zh-tw/security/bulletin/2018-03-01.html +++ b/zh-tw/security/bulletin/2018-03-01.html @@ -456,7 +456,8 @@ QC-CR#2101439</a></td> </tbody></table> <h3 id="qualcomm-closed-source-components">Qualcomm 封閉原始碼元件</h3> -<p>以下列出會影響 Qualcomm 元件的安全性漏洞，詳情請參考適用的 Qualcomm AMSS 安全性公告或安全性警示。這些問題的嚴重程度是由 Qualcomm 直接評定。</p> +<p> +以下列出會影響 Qualcomm 元件的安全性漏洞，詳情請參考適用的 Qualcomm AMSS 安全性公告或安全性警示。這些問題的嚴重程度是由 Qualcomm 直接評定。</p> <table> <colgroup><col width="17%" /> diff --git a/zh-tw/security/bulletin/2018-04-01.html b/zh-tw/security/bulletin/2018-04-01.html index 06e57b01..7dc87623 100644 --- a/zh-tw/security/bulletin/2018-04-01.html +++ b/zh-tw/security/bulletin/2018-04-01.html @@ -29,7 +29,8 @@ Android 的合作夥伴至少會提前一個月收到公告中所有問題的相 <p> 在這些問題中，最嚴重的就是媒體架構中嚴重程度「最高」的安全性漏洞。遠端攻擊者可利用這類漏洞，在獲得授權的程序環境內透過特製檔案執行任何程式碼。<a href="/security/overview/updates-resources.html#severity">嚴重程度評定標準</a>是假設平台與服務的因應防護措施基於開發作業的需求而被關閉，或是遭到有心人士破解，然後推算當有人惡意運用漏洞時，使用者的裝置會受到多大的影響，據此評定漏洞的嚴重程度。 </p> -<p>針對這些新發現的漏洞，我們目前尚未收到任何客戶回報相關的漏洞濫用案例。如果想進一步瞭解 <a href="/security/enhancements/index.html">Android 安全性平台防護措施</a>和 Google Play 安全防護機制如何加強 Android 平台的安全性，請參閱 <a href="#mitigations">Android 和 Google Play 安全防護機制所提供的因應措施</a>。 +<p> +針對這些新發現的漏洞，我們目前尚未收到任何客戶回報相關的漏洞濫用案例。如果想進一步瞭解 <a href="/security/enhancements/index.html">Android 安全性平台防護措施</a>和 Google Play 安全防護機制如何加強 Android 平台的安全性，請參閱 <a href="#mitigations">Android 和 Google Play 安全防護機制所提供的因應措施</a>。 </p> <p class="note"> <strong>注意：</strong>在 <a href="/security/bulletin/pixel/2018-04-01.html">2018 年 4 月 Pixel/Nexus 安全性公告</a>中，我們提供了 Google 裝置適用的最新無線下載更新 (OTA) 和韌體映像檔的相關資訊。 @@ -76,7 +77,7 @@ Android 的合作夥伴至少會提前一個月收到公告中所有問題的相 </tbody></table> <h3 id="framework">架構</h3> -<p>Android 開放原始碼計劃 Mail 中的資訊外洩漏洞可能會讓本機惡意應用程式規避作業系統為了將應用程式資料與其他應用程式隔離而採取的防護措施。</p> +<p>本節中最嚴重的漏洞可能會讓本機惡意應用程式規避作業系統為了將應用程式資料與其他應用程式隔離而採取的防護措施。</p> <table> <colgroup><col width="17%" /> @@ -671,7 +672,7 @@ QC-CR#2129237</a></td> </tbody></table> <h3 id="qualcomm-closed-source-components-2014-2016-cumulative-update">Qualcomm 封閉原始碼元件在 2014 至 2016 年之間的累積更新</h3> -<p>以下列出會影響 Qualcomm 元件的安全性漏洞。Qualcomm 在 2014 到 2016 年之間透過 Qualcomm AMSS 安全性公告或安全性警示向合作夥伴提供相關資訊。我們在這個 Android 安全性公告中列出這些漏洞，方便使用者確認與漏洞相對應的安全性修補程式等級 (我們已透過先前的更新為許多 Android 裝置解決了這些問題)。這些問題的嚴重程度評定標準是由 Qualcomm 直接評定。</p> +<p>以下列出會影響 Qualcomm 元件的安全性漏洞。Qualcomm 在 2014 到 2016 年之間透過 Qualcomm AMSS 安全性公告或安全性警示向合作夥伴提供相關資訊。我們在這個 Android 安全性公告中列出這些漏洞，方便使用者確認與漏洞相對應的安全性修補程式等級 (我們已透過先前的更新為許多 Android 裝置解決了這些問題)。這些問題的嚴重程度是由 Qualcomm 直接評定。</p> <table> <colgroup><col width="17%" /> @@ -2472,13 +2473,13 @@ QC-CR#2129237</a></td> <strong>3.「類型」<em></em>欄中的項目代表什麼意義？</strong> </p> <p> -資安漏洞詳情表格中「類型」<em></em>欄內的項目代表的是安全性漏洞的類別。 +在資安漏洞詳情表格中，「類型」<em></em>欄中的項目代表的是安全性漏洞的類別。 </p> <table> <colgroup><col width="25%" /> <col width="75%" /> </colgroup><tbody><tr> - <th>縮寫詞</th> + <th>縮寫</th> <th>定義</th> </tr> <tr> diff --git a/zh-tw/security/bulletin/2018-05-01.html b/zh-tw/security/bulletin/2018-05-01.html index 8aa41e88..68be324a 100644 --- a/zh-tw/security/bulletin/2018-05-01.html +++ b/zh-tw/security/bulletin/2018-05-01.html @@ -181,7 +181,7 @@ Android 的合作夥伴在至少一個月之前已收到公告中所有問題的 <h3 id="kernel-components">核心元件</h3> <p> -Android 開放原始碼計劃 Mail 中的資訊外洩漏洞可能會讓本機惡意應用程式規避作業系統為了將應用程式資料與其他應用程式隔離而採取的防護措施。</p> +本節中最嚴重的漏洞可能會讓本機惡意應用程式規避作業系統為了將應用程式資料與其他應用程式隔離而採取的防護措施。</p> <table> <colgroup><col width="17%" /> diff --git a/zh-tw/security/bulletin/2018-06-01.html b/zh-tw/security/bulletin/2018-06-01.html index 250cb5c1..3a48cfd7 100644 --- a/zh-tw/security/bulletin/2018-06-01.html +++ b/zh-tw/security/bulletin/2018-06-01.html @@ -19,16 +19,16 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>發佈日期：2018 年 6 月 4 日 | 更新日期：2018 年 6 月 6 日更新</em></p> +<p><em>發佈日期：2018 年 6 月 4 日 | 更新日期：2018 年 7 月 24 日</em></p> <p> -Android 安全性公告列舉會對 Android 裝置造成影響的安全性漏洞，並說明各項相關細節。2018-06-05 之後的安全性修補程式等級已解決了這些問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 +Android 安全性公告列舉對 Android 裝置造成影響的安全性漏洞，並說明各項相關細節。2018-06-05 之後的安全性修補程式等級已解決了這些問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 </p> <p> Android 的合作夥伴至少會提前一個月收到公告中所有問題的相關通知。這些問題的原始碼修補程式已發佈到 Android 開放原始碼計劃 (AOSP) 存放區中，且公告中亦提供相關連結。此外，本公告也提供 Android 開放原始碼計劃以外的修補程式連結。 </p> <p> -在這些問題中，最嚴重的就是媒體架構中「最高」等級的安全性漏洞。遠端攻擊者可利用這類漏洞，在獲得授權的程序環境內透過特製檔案執行任何程式碼。<a href="/security/overview/updates-resources.html#severity">嚴重程度評定標準</a>是假設平台與服務的因應防護措施基於開發作業的需求而被關閉，或是遭到有心人士破解，然後推算當有人惡意運用漏洞時，使用者的裝置會受到多大的影響，據此評定漏洞的嚴重程度。 +在這些問題中，最嚴重的就是媒體架構中嚴重程度「最高」的安全性漏洞。遠端攻擊者可利用這類漏洞，在獲得授權的程序環境內透過特製檔案執行任何程式碼。<a href="/security/overview/updates-resources.html#severity">嚴重程度評定標準</a>是假設平台與服務的因應防護措施基於開發作業的需求而被關閉，或是遭到有心人士破解，然後推算當有人惡意運用漏洞時，使用者的裝置會受到多大的影響，據此評定漏洞的嚴重程度。 </p> <p> 針對這些新發現的漏洞，我們目前尚未收到任何客戶回報相關的漏洞濫用案例。如果想進一步瞭解 <a href="/security/enhancements/index.html">Android 安全性平台防護措施</a>和 Google Play 安全防護機制如何加強 Android 平台的安全性，請參閱 <a href="#mitigations">Android 和 Google Play 安全防護機制所提供的因應措施</a>。 @@ -253,6 +253,36 @@ Android 的合作夥伴至少會提前一個月收到公告中所有問題的相 <p> 下列各節針對 2018-06-05 安全性修補程式等級適用的各項安全性漏洞提供了詳細資訊，我們依照資安問題本身所影響的元件將各項漏洞分門別類，另外也附上了一些詳細資料，例如 CVE、相關參考資料、<a href="#type">漏洞類型</a>、<a href="/security/overview/updates-resources.html#severity">嚴重程度</a>、元件 (在適用情況下)，和更新的 Android 開放原始碼計劃版本 (在適用情況下)。假如相關錯誤有公開變更，該錯誤 ID 會連結到相對應的變更 (例如 Android 開放原始碼計劃變更清單)。如果單一錯誤有多項相關變更，您可以透過該錯誤 ID 後面的編號連結開啟額外的參考資料。</p> + +<h3 id="broadcom-components">Broadcom 元件</h3> + +<p> +本節中最嚴重的漏洞可能會讓遠端攻擊者存取一般只開放給獲得授權的本機安裝應用程式的資料。 +</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-73665456<a href="#asterisk">*</a><br /> +B-CS4906525</td> + <td>ID</td> + <td>高</td> + <td>藍牙</td> + </tr> +</tbody></table> + <h3 id="kernel-components">核心元件</h3> <p> @@ -568,7 +598,15 @@ QC-CR#2151241</a></td> <td>高</td> <td>WLAN</td> </tr> - <tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-73665204<a href="#asterisk">*</a><br /> + QC-CR#2187697</td> + <td>ID</td> + <td>高</td> + <td>藍牙</td> + </tr> + <tr> <td>CVE-2017-18159</td> <td>A-68992405<br /> <a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=633fa4ffb38bbfb0fad79204e19b9f59d42d7680">QC-CR#2105697</a> @@ -700,6 +738,34 @@ QC-CR#2161310</a></td> </tr> </tbody></table> +<h3 id="system-components">系統</h3> + +<p> +本節中最嚴重的漏洞可能會讓遠端攻擊者存取一般只開放給獲得授權的本機安裝應用程式的資料。 +</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>更新的 Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/fa3d7e1f784d3bdbf8f9d8b572a60696289211b1">A-72377774</a></td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + <h2 id="common-questions-and-answers">常見問題與解答</h2> <p>如果您在閱讀這篇公告後有任何疑問，可參考本節的常見問答。</p> <p><strong>1. 如何判斷我目前的裝置軟體版本是否已修正這些問題？</strong></p> @@ -824,6 +890,11 @@ QC-CR#2161310</a></td> <td>2018 年 6 月 6 日</td> <td>修訂公告內容 (加入 Android 開放原始碼計劃連結)。</td> </tr> + <tr> + <td>1.2</td> + <td>2018 年 7 月 24 日</td> + <td>修訂公告內容 (根據協調揭露原則加入 CVE-2018-5383 的參考資料)。</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/zh-tw/security/bulletin/2018-07-01.html b/zh-tw/security/bulletin/2018-07-01.html index 3e8db9f4..3f89b345 100644 --- a/zh-tw/security/bulletin/2018-07-01.html +++ b/zh-tw/security/bulletin/2018-07-01.html @@ -19,16 +19,16 @@ See the License for the specific language governing permissions and limitations under the License. --> -<p><em>發佈日期：2018 年 7 月 2 日</em></p> +<p><em>發佈日期：2018 年 7 月 2 日 | 更新日期：2018 年 7 月 3 日</em></p> <p> -Android 安全性公告列舉會對 Android 裝置造成影響的安全性漏洞，並說明各項相關細節。2018-07-05 之後的安全性修補程式等級已解決了這些問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 +Android 安全性公告列舉對 Android 裝置造成影響的安全性漏洞，並說明各項相關細節。2018-07-05 之後的安全性修補程式等級已解決了這些問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 </p> <p> -Android 的合作夥伴在至少一個月之前已收到公告中所有問題的相關通知。這些問題的原始碼修補程式將於接下來 48 小時內發佈到 Android 開放原始碼計劃 (AOSP) 存放區，等到相關 Android 開放原始碼計劃連結建立完成後，我們就會修訂這則公告。 +Android 的合作夥伴至少會提前一個月收到公告中所有問題的相關通知。這些問題的原始碼修補程式已發佈到 Android 開放原始碼計劃 (AOSP) 存放區中，且公告中亦提供相關連結。此外，本公告也提供 Android 開放原始碼計劃以外的修補程式連結。 </p> <p> -在這些問題中，最嚴重的就是媒體架構中「最高」等級的安全性漏洞。遠端攻擊者可利用這類漏洞，在獲得授權的程序環境內透過特製檔案執行任何程式碼。<a href="/security/overview/updates-resources.html#severity">嚴重程度評定標準</a>是假設平台與服務的因應防護措施基於開發作業的需求而被關閉，或是遭到有心人士破解，然後推算當有人惡意運用漏洞時，使用者的裝置會受到多大的影響，據此評定漏洞的嚴重程度。 +在這些問題中，最嚴重的就是媒體架構中嚴重程度「最高」的安全性漏洞。遠端攻擊者可利用這類漏洞，在獲得授權的程序環境內透過特製檔案執行任何程式碼。<a href="/security/overview/updates-resources.html#severity">嚴重程度評定標準</a>是假設平台與服務的因應防護措施基於開發作業的需求而被關閉，或是遭到有心人士破解，然後推算當有人惡意運用漏洞時，使用者的裝置會受到多大的影響，據此評定漏洞的嚴重程度。 </p> <p> 針對這些新發現的漏洞，我們目前尚未收到任何客戶回報相關的漏洞濫用案例。如果想進一步瞭解 <a href="/security/enhancements/index.html">Android 安全性平台防護措施</a>和 Google Play 安全防護機制如何加強 Android 平台的安全性，請參閱 <a href="#mitigations">Android 和 Google Play 安全防護機制所提供的因應措施</a>。 @@ -67,14 +67,14 @@ Android 的合作夥伴在至少一個月之前已收到公告中所有問題的 </tr> <tr> <td>CVE-2018-9433</td> - <td>A-38196219</td> + <td>A-38196219<a href="#asterisk">*</a></td> <td>RCE</td> <td>最高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2</td> </tr> <tr> <td>CVE-2018-9410</td> - <td>A-77822336</td> + <td><a href="https://android.googlesource.com/platform/frameworks/minikin/+/62e88b9f3ac35e1e69d79c7a43c6f9ddcd5980a3">A-77822336</a></td> <td>ID</td> <td>高</td> <td>8.0、8.1</td> @@ -99,35 +99,35 @@ Android 的合作夥伴在至少一個月之前已收到公告中所有問題的 </tr> <tr> <td>CVE-2018-9411</td> - <td>A-79376389</td> + <td><a href="https://android.googlesource.com/platform/system/libhidl/+/e1302cfda34be9dd0a4aeae6bfa9561b44536758">A-79376389</a></td> <td>RCE</td> <td>最高</td> <td>8.0、8.1</td> </tr> <tr> <td>CVE-2018-9424</td> - <td>A-76221123</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/d3860e51b83296ae1d2921d8109210283573862a">A-76221123</a></td> <td>EoP</td> <td>高</td> <td>8.0、8.1</td> </tr> <tr> <td>CVE-2018-9428</td> - <td>A-74122779</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/46bd7c682db5bbc048b177c52448a7999e5740ce">A-74122779</a></td> <td>EoP</td> <td>高</td> <td>8.1</td> </tr> <tr> <td>CVE-2018-9412</td> - <td>A-78029004</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/fa12c0fcdc6607b746177ccad4f7099098b4849a">A-78029004</a></td> <td>DoS</td> <td>高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9421</td> - <td>A-77237570</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/ff2171f2460e3a6d3443ab957732b8b7d4831d40">A-77237570</a></td> <td>ID</td> <td>高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> @@ -152,28 +152,28 @@ Android 的合作夥伴在至少一個月之前已收到公告中所有問題的 </tr> <tr> <td>CVE-2018-9365</td> - <td>A-74121126</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/ae94a4c333417a1829030c4d87a58ab7f1401308">A-74121126</a></td> <td>RCE</td> <td>最高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9432</td> - <td>A-73173182</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/a6fe2cd18c77c68219fe7159c051bc4e0003fc40">A-73173182</a></td> <td>EoP</td> <td>高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9420</td> - <td>A-77238656</td> + <td><a href="https://android.googlesource.com/platform/system/media/+/12df4b05fd918d836636e21f783df7ad9d5e17a3">A-77238656</a></td> <td>ID</td> <td>高</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9419</td> - <td>A-74121659</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/f1c2c86080bcd7b3142ff821441696fc99c2bc9a">A-74121659</a></td> <td>ID</td> <td>高</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> @@ -259,14 +259,6 @@ Android 的合作夥伴在至少一個月之前已收到公告中所有問題的 <td>WLAN</td> </tr> <tr> - <td>CVE-2018-5855</td> - <td>A-77527719<br /> - <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qca-wifi-host-cmn/commit/?id=61f4a467177afc23bdc1944ec61e52bed156c104">QC-CR#2181685</a></td> - <td>ID</td> - <td>高</td> - <td>WLAN</td> - </tr> - <tr> <td>CVE-2017-13077、CVE-2017-13078</td> <td>A-78285557<br /> <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=5c671a69c57ce4fd84f0eaf082b336a49d0cf5dd">QC-CR#2133114</a></td> @@ -416,13 +408,6 @@ Android 的合作夥伴在至少一個月之前已收到公告中所有問題的 <td>封閉原始碼元件</td> </tr> <tr> - <td>CVE-2018-11258</td> - <td>A-72951054<a href="#asterisk">*</a></td> - <td>無</td> - <td>高</td> - <td>封閉原始碼元件</td> - </tr> - <tr> <td>CVE-2018-11257</td> <td>A-74235874<a href="#asterisk">*</a></td> <td>無</td> @@ -592,6 +577,16 @@ Android 的合作夥伴在至少一個月之前已收到公告中所有問題的 <td>2018 年 7 月 2 日</td> <td>發佈公告。</td> </tr> + <tr> + <td>1.1</td> + <td>2018 年 7 月 3 日</td> + <td>修訂公告內容 (加入 Android 開放原始碼計劃連結)。</td> + </tr> + <tr> + <td>1.2</td> + <td>2018 年 7 月 11 日</td> + <td>已將 CVE-2018-5855 和 CVE-2018-11258 從 2018-07-05 SPL 中移除。</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/zh-tw/security/bulletin/2018-08-01.html b/zh-tw/security/bulletin/2018-08-01.html new file mode 100644 index 00000000..fa5f0c18 --- /dev/null +++ b/zh-tw/security/bulletin/2018-08-01.html @@ -0,0 +1,634 @@ +<html devsite><head> + <title>Android 安全性公告 - 2018 年 8 月</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> +<p><em>發佈日期：2018 年 8 月 6 日</em></p> + +<p> +Android 安全性公告列舉對 Android 裝置造成影響的安全性漏洞，並說明各項相關細節。2018-08-05 之後的安全性修補程式等級已解決了這些問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705" class="external">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 +</p> +<p> +Android 的合作夥伴至少會提前一個月收到公告中所有問題的相關通知。這些問題的原始碼修補程式已發佈到 Android 開放原始碼計劃 (AOSP) 存放區中，且公告中亦提供相關連結。此外，本公告也提供 Android 開放原始碼計劃以外的修補程式連結。</p> +<p> +在這些問題中，最嚴重的漏洞就是遠端攻擊者可利用特製檔案，在獲得授權的程序環境內執行任何程式碼。<a href="/security/overview/updates-resources.html#severity">嚴重程度評定標準</a>是假設平台與服務的因應防護措施基於開發作業的需求而被關閉，或是遭到有心人士破解，然後推算當有人惡意運用漏洞時，使用者的裝置會受到多大的影響，據此評定漏洞的嚴重程度。 +</p> +<p> +針對這些新發現的漏洞，我們目前尚未收到任何客戶回報相關的漏洞濫用案例。如果想進一步瞭解 <a href="/security/enhancements/index.html">Android 安全性平台防護措施</a>和 Google Play 安全防護機制如何加強 Android 平台的安全性，請參閱 <a href="#mitigations">Android 和 Google Play 安全防護機制所提供的因應措施</a>。 +</p> +<p class="note"> +<strong>注意：</strong>在 <a href="/security/bulletin/pixel/2018-08-01.html">2018 年 8 月 Pixel/Nexus 安全性公告</a>中，我們提供了 Google 裝置適用的最新無線下載更新 (OTA) 和韌體映像檔的相關資訊。 +</p> + +<h2 id="mitigations">Android 和 Google 服務問題因應措施</h2> +<p> +本節概述 <a href="/security/enhancements/index.html">Android 安全性平台</a>和 <a href="https://www.android.com/play-protect">Google Play 安全防護</a>等服務防護方案所提供的因應措施。這些措施可有效防範有心人士在 Android 系統上惡意運用安全性漏洞來達到特定目的。 +</p> +<ul> +<li>Android 平台持續推出新的版本來強化安全性，因此有心人士越來越難在 Android 系統上找出漏洞加以利用。我們建議所有使用者盡可能更新至最新版的 Android。</li> +<li>Android 安全性小組透過 <a href="https://www.android.com/play-protect" class="external">Google Play 安全防護</a>主動監控濫用情形；使用這些功能的目的是在發現<a href="/security/reports/Google_Android_Security_PHA_classifications.pdf">可能有害的應用程式</a>時警告使用者。在預設情況下，搭載 <a href="http://www.android.com/gms" class="external">Google 行動服務</a>的裝置會自動啟用 Google Play 安全防護機制。對於需要從 Google Play 以外的來源安裝應用程式的使用者來說，這項防護措施格外重要。</li> +</ul> +<h2 id="2018-08-01-details">2018-08-01 安全性修補程式等級 - 資安漏洞詳情</h2> +<p> +下列各節針對 2018-08-01 安全性修補程式等級適用的各項安全性漏洞提供了詳細資訊，我們依照資安問題本身所影響的元件將各項漏洞分門別類，另外也附上了問題說明和一份 CVE 資訊表，其中包括了相關參考資料、<a href="#type">漏洞類型</a>、<a href="/security/overview/updates-resources.html#severity">嚴重程度</a>，以及更新的 Android 開放原始碼計劃版本 (在適用情況下)。假如相關錯誤有公開變更，該錯誤 ID 會連結到相對應的變更 (例如 Android 開放原始碼計劃變更清單)。如果單一錯誤有多項相關變更，您可以透過該錯誤 ID 後面的編號連結開啟額外的參考資料。</p> + +<h3 id="framework">架構</h3> +<p>本節中最嚴重的漏洞可能會讓本機惡意應用程式規避使用者互動要求，以取得其他權限。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>更新的 Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2018-9445</td> + <td> + <a href="https://android.googlesource.com/platform/external/e2fsprogs/+/9a2d95e4ed9ec5ab76998654b1c2fba9cc139e50">A-80436257</a> + [<a href="https://android.googlesource.com/platform/system/vold/+/940a1ff70cfc5f2e4de83da9ad84cd9734faadf6">2</a>] + </td> + <td>EoP</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9438</td> + <td> +<a href="https://android.googlesource.com/platform/packages/providers/DownloadProvider/+/b552ebf70913cc79085bcc4212235ea45e036d3b">A-78644887</a> +[<a href="https://android.googlesource.com/platform/frameworks/base/+/e3854655e75d97552140d77cca5d20c121a17ef9">2</a>] +[<a href="https://android.googlesource.com/platform/frameworks/opt/telephony/+/d1ce32b059bed774b41f11413c1d83a1bc412964">3</a>] +[<a href="https://android.googlesource.com/platform/frameworks/base/+/97e1cd61d3040dd366ac9e25cdb6f134c7490846">4</a>] +</td> + <td>DoS</td> + <td>高</td> + <td>8.1</td> + </tr> + <tr> + <td>CVE-2018-9458</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/c4f66f4f607654611b2227827123e016c57a5729">A-71786287</a> +</td> + <td>EoP</td> + <td>高</td> + <td>8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9451</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/a409aa1214d6483efe129a4966f09aa4fdc097ad">A-79488511</a> +[<a href="https://android.googlesource.com/platform/frameworks/base/+/1de25074adb5d9ed572d6a85e77d3df5ac3a7e9e">2</a>] +</td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="media-framework">媒體架構</h3> +<p>本節中最嚴重的漏洞可能會讓遠端攻擊者得以利用特製檔案在獲得授權的程序環境內執行任何程式碼。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>更新的 Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2018-9427</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/av/+/08d392085c095e227c029f64644bc08ef5a544de">A-77486542</a> +[<a href="https://android.googlesource.com/platform/frameworks/av/+/c9909e5a980f941a5b72477755e09fb4dc57c478">2</a>] +</td> + <td>RCE</td> + <td>最高</td> + <td>8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9444</td> + <td>A-63521984<a href="#asterisk">*</a></td> + <td>DoS</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2</td> + </tr> + <tr> + <td>CVE-2018-9437</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/av/+/017ff33fd419c50734f775d5054e2cbea719700b">A-78656554</a> + </td> + <td>DoS</td> + <td>高</td> + <td>6.0、6.0.1</td> + </tr> +</tbody></table> + +<h3 id="system">系統</h3> +<p>本節中最嚴重的漏洞可能會讓遠端攻擊者得以利用特製檔案在獲得授權的程序環境內執行任何程式碼。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>更新的 Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2018-9446</td> + <td> + <a href="https://android.googlesource.com/platform/system/bt/+/49acada519d088d8edf37e48640c76ea5c70e010">A-80145946</a> + </td> + <td>RCE</td> + <td>最高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9450</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/bc259b4926a6f9b33b9ee2c917cd83a55f360cbf">A-79541338</a> + </td> + <td>RCE</td> + <td>最高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9459</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/UnifiedEmail/+/76c5261a03c8402e893999196651afc5791ca0fd">A-66230183</a> + </td> + <td>EoP</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9455</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/d56c7ec9e2ecfa8a8ceeb82f37187e5ea21f2101">A-78136677</a> + </td> + <td>DoS</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9436</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/289a49814aef7f0f0bb98aac8246080abdfeac01">A-79164722</a> + </td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9454</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/289a49814aef7f0f0bb98aac8246080abdfeac01">A-78286118</a> + </td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9448</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/13294c70a66347c9e5d05b9f92f8ceb6fe38d7f6">A-79944113</a> +[<a href="https://android.googlesource.com/platform/system/bt/+/f1f1c3e00f8d1baad0215b057e6d894517eeaddb">2</a>] + </td> + <td>ID</td> + <td>高</td> + <td>8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9453</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/cb6a56b1d8cdab7c495ea8f53dcbdb3cfc9477d2">A-78288378</a> + </td> + <td>ID</td> + <td>高</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h2 id="2018-08-05-details">2018-08-05 安全性修補程式等級 - 資安漏洞詳情</h2> +<p> +下列各節針對 2018-08-05 安全性修補程式等級適用的各項安全性漏洞提供了詳細資訊，我們依照資安問題本身所影響的元件將各項漏洞分門別類，另外也附上了一些詳細資料，例如 CVE、相關參考資料、<a href="#type">漏洞類型</a>、<a href="/security/overview/updates-resources.html#severity">嚴重程度</a>、元件 (在適用情況下)，和更新的 Android 開放原始碼計劃版本 (在適用情況下)。假如相關錯誤有公開變更，該錯誤 ID 會連結到相對應的變更 (例如 Android 開放原始碼計劃變更清單)。如果單一錯誤有多項相關變更，您可以透過該錯誤 ID 後面的編號連結開啟額外的參考資料。</p> + +<h3 id="kernel-components">核心元件</h3> +<p>本節中最嚴重的漏洞可能會讓本機惡意應用程式在獲得授權的程序環境內執行任何程式碼。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2017-18249</td> + <td>A-78283212<br /> + <a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30a61ddf8117c26ac5b295e1233eaa9629a94ca3"> +上游程式庫核心</a></td> + <td>EoP</td> + <td>高</td> + <td>F2FS</td> + </tr> + <tr> + <td>CVE-2018-9465</td> + <td>A-69164715<br /> + <a href="https://patchwork.kernel.org/patch/10058587/">上游程式庫核心</a></td> + <td>EoP</td> + <td>高</td> + <td>繫結機制</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Qualcomm 元件</h3> +<p>本節中最嚴重的漏洞就是攻擊者可在不具備任何額外執行權限的情況下，造成遠端資訊外洩的問題。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2018-5383</td> + <td>A-79421580<a href="#asterisk">*</a><br /> + QC-CR#2209635</td> + <td>ID</td> + <td>高</td> + <td>藍牙</td> + </tr> + <tr> + <td>CVE-2017-13077</td> + <td>A-78284758<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=edb507885fc47cf3cdf061bfba1dc77451a6a332"> +QC-CR#2133033</a></td> + <td>ID</td> + <td>高</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-18281</td> + <td>A-78242172<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=69f0a80b8cc1333647397d7bc4f267bd3fe22be9"> +QC-CR#856388</a></td> + <td>ID</td> + <td>高</td> + <td>影片</td> + </tr> + <tr> + <td>CVE-2018-11260</td> + <td>A-72997254<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=9fd239116d9cb19a18b3892b8a1f428636ca1453"> +QC-CR#2204872</a></td> + <td>EoP</td> + <td>高</td> + <td>WLAN</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-closed-source-components">Qualcomm 封閉原始碼元件</h3> +<p> +以下列出會影響 Qualcomm 元件的安全性漏洞，詳情請參考適用的 Qualcomm AMSS 安全性公告或安全性警示。這些問題的嚴重程度是由 Qualcomm 直接評定。</p> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2017-18296</td> + <td>A-78240731<a href="#asterisk">*</a></td> + <td>無</td> + <td>最高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18305</td> + <td>A-78239838<a href="#asterisk">*</a></td> + <td>無</td> + <td>最高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18310</td> + <td>A-62211308<a href="#asterisk">*</a></td> + <td>無</td> + <td>最高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18295</td> + <td>A-78240386<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18283</td> + <td>A-78240411<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18294</td> + <td>A-78240247<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18293</td> + <td>A-78240316<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18292</td> + <td>A-78241027<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18298</td> + <td>A-78239976<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18299</td> + <td>A-78240418<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18304</td> + <td>A-78239975<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18303</td> + <td>A-78240396<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18301</td> + <td>A-78238455<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18302</td> + <td>A-78239233<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18300</td> + <td>A-78239508<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18297</td> + <td>A-78240275<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18280</td> + <td>A-78285512<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18282</td> + <td>A-78241591<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18309</td> + <td>A-73539064<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2017-18308</td> + <td>A-73539310<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2018-11305</td> + <td>A-72951032<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> + <tr> + <td>CVE-2018-11258</td> + <td>A-72951054<a href="#asterisk">*</a></td> + <td>無</td> + <td>高</td> + <td>封閉原始碼元件</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">常見問題與解答</h2> +<p>如果您在閱讀這篇公告後有任何疑問，可參考本節的常見問答。</p> +<p><strong>1. 如何判斷我目前的裝置軟體版本是否已修正這些問題？</strong></p> +<p>請參閱<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。</p> +<ul> +<li>2018-08-01 之後的安全性修補程式等級已解決了所有與 2018-08-01 安全性修補程式等級相關的問題。</li> +<li>2018-08-05 之後的安全性修補程式等級完全解決了與 2018-08-05 安全性修補程式等級及所有先前修補程式等級相關的問題。</li> +</ul> +<p>提供這些更新的裝置製造商應將修補程式字串等級設定為：</p> +<ul> + <li>[ro.build.version.security_patch]:[2018-08-01]</li> + <li>[ro.build.version.security_patch]:[2018-08-05]</li> +</ul> +<p><strong>2. 為什麼這篇公告有兩種安全性修補程式等級？</strong></p> +<p> +本公告有兩種安全性修補程式等級，讓 Android 合作夥伴能夠靈活運用，以快速修正某些發生在所有 Android 裝置上的類似漏洞。我們建議 Android 合作夥伴修正本公告所列的所有問題，並使用最新的安全性修補程式等級。 +</p> +<ul> +<li>安全性修補程式等級為 2018-08-01 的裝置必須納入所有與該安全性修補程式等級相關的問題，以及在之前安全性公告中回報的所有問題適用的修正程式。</li> +<li>如果裝置的安全性修補程式等級在 2018-08-05 之後，就必須加入本安全性公告 (以及之前公告) 中的所有適用修補程式。</li> +</ul> +<p> +我們建議合作夥伴將所有問題適用的修補程式都彙整在單一更新中。 +</p> +<p id="type"> +<strong>3.「類型」<em></em>欄中的項目代表什麼意義？</strong> +</p> +<p> +在資安漏洞詳情表格中，「類型」<em></em>欄中的項目代表的是安全性漏洞的類別。 +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>縮寫</th> + <th>定義</th> + </tr> + <tr> + <td>RCE</td> + <td>遠端程式碼執行</td> + </tr> + <tr> + <td>EoP</td> + <td>權限升級</td> + </tr> + <tr> + <td>ID</td> + <td>資訊外洩</td> + </tr> + <tr> + <td>DoS</td> + <td>阻斷服務</td> + </tr> + <tr> + <td>無</td> + <td>未分類</td> + </tr> +</tbody></table> +<p> +<strong>4.「參考資料」<em></em>欄底下列出的識別碼代表什麼意義？</strong> +</p> +<p> +資安漏洞詳情表格中「參考資料」<em></em>欄底下的項目可能會包含一個前置字串，用以表示該參考資料值所屬的機構或公司。 +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>前置字串</th> + <th>參考資料</th> + </tr> + <tr> + <td>A-</td> + <td>Android 錯誤 ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm 參考編號</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek 參考編號</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA 參考編號</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom 參考編號</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>5.「參考資料」<em></em>欄中 Android 錯誤 ID 旁邊的星號 (*) 代表什麼意義？</strong> +</p> +<p> +在「參考資料」<em></em>欄中 Android 錯誤 ID 旁邊標上星號 (*) 代表該問題並未公開，相關的更新通常是直接整合在最新的 Pixel/Nexus 裝置專用驅動程式的安裝檔中。您可以前往 <a href="https://developers.google.com/android/drivers" class="external">Google Developers 網站</a>下載這些驅動程式。 +</p> +<p> +<strong>6. 為什麼安全性漏洞會分別刊載在這份安全性公告和裝置/合作夥伴安全性公告 (例如 Pixel/Nexus 公告)？</strong> +</p> +<p> +為了宣告 Android 裝置最新的安全性修補程式等級，我們必須先在這份安全性公告中刊載相關的安全性漏洞。裝置/合作夥伴安全性公告所刊載的其他安全性漏洞則未強制規定宣告安全性修補程式等級。我們鼓勵 Android 裝置和晶片組製造商將旗下裝置的其他修正刊載在自己的安全性網站上，例如 <a href="https://security.samsungmobile.com/securityUpdate.smsb" class="external">Samsung</a>、<a href="https://lgsecurity.lge.com/security_updates.html" class="external">LGE</a> 或是 <a href="/security/bulletin/pixel/" class="external">Pixel/Nexus</a> 安全性公告。 +</p> + +<h2 id="versions">版本</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>版本</th> + <th>日期</th> + <th>附註</th> + </tr> + <tr> + <td>1.0</td> + <td>2018 年 8 月 6 日</td> + <td>發佈公告。</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/zh-tw/security/bulletin/2018.html b/zh-tw/security/bulletin/2018.html index 4a074425..251d0216 100644 --- a/zh-tw/security/bulletin/2018.html +++ b/zh-tw/security/bulletin/2018.html @@ -34,6 +34,37 @@ <th>安全性修補程式等級</th> </tr> <tr> + <td><a href="/security/bulletin/2018-08-01.html">2018 年 8 月</a></td> + <td>即將推出 + <!-- + <a href="/security/bulletin/2018-08-01.html">English</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018 年 8 月 6 日</td> + <td>2018-08-01<br /> + 2018-08-05</td> + </tr> + + <tr> + <td><a href="/security/bulletin/2018-07-01.html">2018 年 7 月</a></td> + <td> + <a href="/security/bulletin/2018-07-01.html">English</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2018 年 7 月 2 日</td> + <td>2018-07-01<br /> + 2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/2018-06-01.html">2018 年 6 月</a></td> <td> <a href="/security/bulletin/2018-06-01.html">English</a> / diff --git a/zh-tw/security/bulletin/index.html b/zh-tw/security/bulletin/index.html index c5433216..757fe3f7 100644 --- a/zh-tw/security/bulletin/index.html +++ b/zh-tw/security/bulletin/index.html @@ -56,6 +56,36 @@ <th>安全性修補程式等級</th> </tr> <tr> + <td><a href="/security/bulletin/2018-08-01.html">2018 年 8 月</a></td> + <td>即將推出 + <!-- + <a href="/security/bulletin/2018-08-01.html">English</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018 年 8 月 6 日</td> + <td>2018-08-01<br /> + 2018-08-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/2018-07-01.html">2018 年 7 月</a></td> + <td> + <a href="/security/bulletin/2018-07-01.html">English</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2018 年 7 月 2 日</td> + <td>2018-07-01<br /> + 2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/2018-06-01.html">2018 年 6 月</a></td> <td> <a href="/security/bulletin/2018-06-01.html">English</a> / @@ -68,7 +98,8 @@ <td>2018 年 6 月 4 日</td> <td>2018-06-01<br /> 2018-06-05</td> - </tr><tr> + </tr> + <tr> <td><a href="/security/bulletin/2018-05-01.html">2018 年 5 月</a></td> <td> <a href="/security/bulletin/2018-05-01.html">English</a> / diff --git a/zh-tw/security/bulletin/pixel/2018-01-01.html b/zh-tw/security/bulletin/pixel/2018-01-01.html index d72c63e3..01fd9d2a 100644 --- a/zh-tw/security/bulletin/pixel/2018-01-01.html +++ b/zh-tw/security/bulletin/pixel/2018-01-01.html @@ -22,7 +22,7 @@ <p><em>發佈日期：2018 年 1 月 2 日 | 更新日期：2018 年 1 月 29 日</em></p> <p> -Pixel/Nexus 安全性公告羅列了會對<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">支援的 Google Pixel 和 Nexus 裝置</a> (Google 裝置) 造成影響的安全性漏洞和功能改善項目，並說明各項相關細節。2018-01-05 之後的安全性修補程式等級也已針對 Google 裝置解決了 <a href="/security/bulletin/2018-01-01">2018 年 1 月 Android 安全性公告</a>列出的所有問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 +Pixel/Nexus 安全性公告列舉對<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">支援的 Google Pixel 和 Nexus 裝置</a> (Google 裝置) 造成影響的安全性漏洞和功能改善項目，並說明各項相關細節。2018-01-05 之後的安全性修補程式等級也已針對 Google 裝置解決了 <a href="/security/bulletin/2018-01-01">2018 年 1 月 Android 安全性公告</a>列出的所有問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 </p> <p> 所有支援的 Google 裝置都會收到 2018-01-05 修補程式等級更新。我們建議所有客戶接受這些裝置更新。 @@ -31,7 +31,7 @@ Pixel/Nexus 安全性公告羅列了會對<a href="https://support.google.com/pi <strong>注意：</strong>您可以前往 <a href="https://developers.google.com/android/nexus/images">Google Developers 網站</a>取得 Google 裝置韌體映像檔。 </p> <h2 id="announcements">公告事項</h2> -<p>我們除了修補 <a href="/security/bulletin/2018-01-01">2018 年 1 月 Android 安全性公告</a>中所列出的安全性漏洞，也針對下文列出的 Pixel 和 Nexus 裝置的安全性漏洞提供修補程式。我們的合作夥伴在至少一個月之前已收到所述問題的相關通知，方便他們將相關內容納入其裝置更新中。 +<p>我們除了修補 <a href="/security/bulletin/2018-01-01">2018 年 1 月 Android 安全性公告</a>中所列出的安全性漏洞，也針對下文列出的 Pixel 和 Nexus 裝置的安全性漏洞提供修補程式。我們的合作夥伴至少會提前一個月收到這些問題的相關通知，方便他們將相關內容納入其裝置更新中。 </p> <h2 id="security-patches">安全性修補程式</h2> <p> @@ -533,7 +533,7 @@ QC-CR#2070583</a></td> QC-CR#2026193</a></td> <td>EoP</td> <td>中</td> - <td>開機載入器</td> + <td>系統啟動載入程式</td> </tr> <tr> <td>CVE-2017-9689</td> @@ -577,7 +577,7 @@ QC-CR#2061498</a></td> QC-CR#2068506</a></td> <td>ID</td> <td>中</td> - <td>開機載入器</td> + <td>系統啟動載入程式</td> </tr> <tr> <td>CVE-2017-15850</td> @@ -603,7 +603,7 @@ QC-CR#2033195</a></td> QC-CR#2078342</a></td> <td>ID</td> <td>中</td> - <td>開機載入器</td> + <td>系統啟動載入程式</td> </tr> <tr> <td>CVE-2017-14870</td> @@ -612,7 +612,7 @@ QC-CR#2078342</a></td> QC-CR#2061506</a></td> <td>ID</td> <td>中</td> - <td>開機載入器</td> + <td>系統啟動載入程式</td> </tr> <tr> <td>CVE-2017-11079</td> @@ -621,7 +621,7 @@ QC-CR#2061506</a></td> QC-CR#2078342</a></td> <td>ID</td> <td>中</td> - <td>開機載入器</td> + <td>系統啟動載入程式</td> </tr> </tbody></table> @@ -659,7 +659,7 @@ QC-CR#2078342</a></td> 2018-01-05 之後的安全性修補程式等級已解決了所有與 2018-01-05 安全性修補程式等級及所有先前修補程式等級相關的問題。請參閱 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel 與 Nexus 更新時間表</a>中的操作說明，瞭解如何查看裝置的安全性修補程式等級。 </p> <p id="type"> -<strong>2. 「類型」<em></em>欄中的項目代表什麼意義？</strong> +<strong>2.「類型」<em></em>欄中的項目代表什麼意義？</strong> </p> <p> 在資安漏洞詳情表格中，「類型」<em></em>欄中的項目代表的是安全性漏洞的類別。 diff --git a/zh-tw/security/bulletin/pixel/2018-04-01.html b/zh-tw/security/bulletin/pixel/2018-04-01.html index bcffb8c1..a3ef5848 100644 --- a/zh-tw/security/bulletin/pixel/2018-04-01.html +++ b/zh-tw/security/bulletin/pixel/2018-04-01.html @@ -32,7 +32,7 @@ Pixel/Nexus 安全性公告列舉對<a href="https://support.google.com/pixelpho </p> <h2 id="announcements">公告事項</h2> -<p>我們除了修補 <a href="/security/bulletin/2018-04-01">2018 年 4 月 Android 安全性公告</a>中所列出的安全性漏洞，也針對下文列出的 Google 裝置的安全性漏洞提供修補程式。我們的合作夥伴在至少一個月之前已收到所述問題的相關通知，方便他們將相關內容納入其裝置更新中。</p> +<p>我們除了修補 <a href="/security/bulletin/2018-04-01">2018 年 4 月 Android 安全性公告</a>中所列出的安全性漏洞外，也針對下文列出的 Google 裝置的安全性漏洞提供修補程式。我們的合作夥伴至少會提前一個月收到這些問題的相關通知，方便他們將相關內容納入其裝置更新中。</p> <h2 id="security-patches">安全性修補程式</h2> <p> @@ -570,7 +570,7 @@ QC-CR#2098332</a></td> </tr> <tr> <td>A-65509134</td> - <td>連線</td> + <td>網路連線</td> <td>在特定網路上啟用 IMS911</td> <td>Pixel 2、Pixel 2 XL、Pixel、Pixel XL</td> </tr> @@ -618,13 +618,13 @@ QC-CR#2098332</a></td> </tr> <tr> <td>A-67774904</td> - <td>連線</td> + <td>網路連線</td> <td>改善透過 Wi-Fi 連線進行多方通話時的效能</td> <td>Pixel、Pixel XL</td> </tr> <tr> <td>A-67777512</td> - <td>連線</td> + <td>網路連線</td> <td>改善澳洲部分地區的 T-Mobile 使用者的數據連線品質</td> <td>Pixel、Pixel XL</td> </tr> @@ -647,8 +647,7 @@ QC-CR#2098332</a></td> <tr> <td>A-68217064</td> <td>效能</td> - <td>改善在訊號強度低的地區轉換至 Wi-Fi 通話時的效能 -</td> + <td>改善在訊號強度低的地區轉換至 Wi-Fi 通話時的效能</td> <td>Pixel 2、Pixel 2 XL</td> </tr> <tr> @@ -659,13 +658,13 @@ QC-CR#2098332</a></td> </tr> <tr> <td>A-68671462</td> - <td>連線</td> + <td>網路連線</td> <td>改善部分電信業者的 VoLTE 效能</td> <td>Nexus 5X、Pixel、Pixel XL、Pixel 2、Pixel 2 XL</td> </tr> <tr> <td>A-68841424</td> - <td>連線</td> + <td>網路連線</td> <td>調整 APN 更新行為</td> <td>全部</td> </tr> @@ -691,7 +690,7 @@ QC-CR#2098332</a></td> </tr> <tr> <td>A-68959671</td> - <td>連線</td> + <td>網路連線</td> <td>更新 Pixel 手機的 Verizon 服務 APK</td> <td>Pixel、Pixel XL、Pixel 2、Pixel 2 XL</td> </tr> @@ -709,7 +708,7 @@ QC-CR#2098332</a></td> A-69574837<br /> A-68474108<br /> A-70406781</td> - <td>連線、效能</td> + <td>網路連線、效能</td> <td>提升使用特定電信業者網路的連線品質和效能</td> <td>Pixel、Pixel XL、Pixel 2、Pixel 2 XL</td> </tr> @@ -721,13 +720,13 @@ QC-CR#2098332</a></td> </tr> <tr> <td>A-69152057</td> - <td>連線</td> + <td>網路連線</td> <td>解決來電轉接問題</td> <td>全部</td> </tr> <tr> <td>A-69209000</td> - <td>連線</td> + <td>網路連線</td> <td>提升 Pixel 2 連線到特定 Wi-Fi 網路時的網際網路連線品質</td> <td>Pixel 2</td> </tr> @@ -735,7 +734,7 @@ QC-CR#2098332</a></td> <td>A-69238007<br /> A-68202289<br /> A-69334308</td> - <td>連線</td> + <td>網路連線</td> <td>調整 APN 設定</td> <td>Nexus 5X、Pixel、Pixel XL、Pixel 2、Pixel 2 XL</td> </tr> @@ -754,7 +753,7 @@ QC-CR#2098332</a></td> </tr> <tr> <td>A-69334266</td> - <td>連線</td> + <td>網路連線</td> <td>將特定電信業者的語音領域變更為電路交換領域</td> <td>Pixel XL</td> </tr> @@ -816,7 +815,7 @@ QC-CR#2098332</a></td> </tr> <tr> <td>A-70576351</td> - <td>連線</td> + <td>網路連線</td> <td>變更為優先使用特定頻帶</td> <td>Nexus 5X、Pixel、Pixel XL、Pixel 2、Pixel 2 XL</td> </tr> @@ -824,13 +823,13 @@ QC-CR#2098332</a></td> <td>A-70580873<br /> A-70912923<br /> A-71497259</td> - <td>連線</td> + <td>網路連線</td> <td>改善部分電信業者的通話效能</td> <td>Pixel、Pixel XL、Pixel 2、Pixel 2 XL</td> </tr> <tr> <td>A-70815434</td> - <td>連線</td> + <td>網路連線</td> <td>改善電信業者 Simyo 的網路效能</td> <td>Nexus 5X</td> </tr> @@ -848,7 +847,7 @@ QC-CR#2098332</a></td> </tr> <tr> <td>A-72119809</td> - <td>連線</td> + <td>網路連線</td> <td>改善裝置在使用特定 SIM 卡時的數據效能</td> <td>全部</td> </tr> diff --git a/zh-tw/security/bulletin/pixel/2018-07-01.html b/zh-tw/security/bulletin/pixel/2018-07-01.html index 976663c7..162900bc 100644 --- a/zh-tw/security/bulletin/pixel/2018-07-01.html +++ b/zh-tw/security/bulletin/pixel/2018-07-01.html @@ -20,10 +20,10 @@ limitations under the License. --> -<p><em>發佈日期：2018 年 7 月 2 日</em></p> +<p><em>發佈日期：2018 年 7 月 2 日 | 更新日期：2018 年 7 月 3 日</em></p> <p> -Pixel/Nexus 安全性公告列舉會對<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">支援的 Google Pixel 和 Nexus 裝置</a> (Google 裝置) 造成影響的安全性漏洞和功能改善項目，並說明各項相關細節。2018-07-05 之後的安全性修補程式等級也已針對 Google 裝置解決了這個公告和 2018 年 7 月 Android 安全性公告列出的所有問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 +Pixel/Nexus 安全性公告列舉對<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">支援的 Google Pixel 和 Nexus 裝置</a> (Google 裝置) 造成影響的安全性漏洞和功能改善項目，並說明各項相關細節。2018-07-05 之後的安全性修補程式等級也已針對 Google 裝置解決了這個公告和 2018 年 7 月 Android 安全性公告列出的所有問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 </p> <p> 所有支援的 Google 裝置都會收到 2018-07-05 修補等級更新。我們建議所有客戶接受這些裝置更新。 @@ -56,21 +56,22 @@ Pixel/Nexus 安全性公告列舉會對<a href="https://support.google.com/pixel </tr> <tr> <td>CVE-2018-9426</td> - <td>A-79148652</td> + <td><a href="https://android.googlesource.com/platform/external/bouncycastle/+/129a20459ea828c1b05f0d5da57f69a2a3212ad7">A-79148652</a></td> <td>ID</td> <td>中</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9376</td> - <td>A-69981755</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/e6655cb8a78b757e9329b8200a90746ffac3a5a9">A-69981755</a></td> <td>EoP</td> <td>中</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9434</td> - <td>A-29833520</td> + <td><a href="https://android.googlesource.com/platform/frameworks/native/+/ab1fb955acc8bbe6b9086a4ab54beab003a887a9">A-29833520</a> +[<a href="https://android.googlesource.com/platform/frameworks/native/+/c4b7338b1a0995222d229a6f794db02c974ba0d8">2</a>]</td> <td>ID</td> <td>中</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> @@ -94,14 +95,14 @@ Pixel/Nexus 安全性公告列舉會對<a href="https://support.google.com/pixel </tr> <tr> <td>CVE-2018-9429</td> - <td>A-73927042</td> + <td><a href="https://android.googlesource.com/platform/frameworks/av/+/7306d8b37c00729dc41d663a4b244a00209d537b">A-73927042</a></td> <td>ID</td> <td>中</td> <td>8.1</td> </tr> <tr> <td>CVE-2018-9423</td> - <td>A-77599438</td> + <td><a href="https://android.googlesource.com/platform/external/libhevc/+/e46e5994a80c31f6533384f0f325555f3a87bee3">A-77599438</a></td> <td>ID</td> <td>中</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> @@ -125,35 +126,35 @@ Pixel/Nexus 安全性公告列舉會對<a href="https://support.google.com/pixel </tr> <tr> <td>CVE-2018-9413</td> - <td>A-73782082</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/97eb2f9cfba4f38d64dffa0558f1c4c3aa91b4f8">A-73782082</a></td> <td>RCE</td> <td>中</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9418</td> - <td>A-73824150</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/8e702ed3539caac44a616243e33aaad1b2b4801f">A-73824150</a></td> <td>RCE</td> <td>中</td> <td>7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9430</td> - <td>A-73963551</td> + <td><a href="https://android.googlesource.com/platform/system/bt/+/605ebb3369b3f961196815065a9fe4ba5bc4d659">A-73963551</a></td> <td>RCE</td> <td>中</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9414</td> - <td>A-78787521</td> + <td><a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/98ff9fe7db5a25fa2c772a85f0b9baa3545228bf">A-78787521</a></td> <td>EoP</td> <td>中</td> <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> </tr> <tr> <td>CVE-2018-9431</td> - <td>A-77600924</td> + <td><a href="https://android.googlesource.com/platform/frameworks/base/+/5c23facbf802c9b4c88ceb60e1b782abcc55ddc9">A-77600924</a></td> <td>EoP</td> <td>中</td> <td>8.0、8.1</td> @@ -186,7 +187,7 @@ Pixel/Nexus 安全性公告列舉會對<a href="https://support.google.com/pixel <tr> <td>CVE-2018-9415</td> <td>A-69129004<br /> - <a href="https://patchwork.kernel.org/patch/9946759/">上游程式庫核心</a></td> + <a href="https://patchwork.kernel.org/patch/10175615/">上游程式庫核心</a></td> <td>EoP</td> <td>中</td> <td>AMBA 驅動程式</td> @@ -431,7 +432,7 @@ Pixel/Nexus 安全性公告列舉會對<a href="https://support.google.com/pixel <strong>4.「參考資料」<em></em>欄中 Android 錯誤 ID 旁邊的星號 (*) 代表什麼意義？</strong> </p> <p> -在「參考資料」<em></em>欄中 Android 錯誤 ID 旁邊標上星號 (*) 代表該問題並未公開，相關的更新通常是直接整合在最新的 Pixel/Nexus 裝置專用驅動程式的安裝檔中。您可以前往 <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程式。 +在「參考資料」<em></em>欄中的 Android 錯誤 ID 旁邊標上星號 (*) 代表該問題並未公開，相關的更新通常是直接整合在最新的 Pixel/Nexus 裝置專用驅動程式的安裝檔中。您可以前往 <a href="https://developers.google.com/android/nexus/drivers">Google Developers 網站</a>下載這些驅動程式。 </p> <p> <strong>5. 為什麼安全性漏洞會分別刊載在這份安全性公告和 Android 安全性公告？</strong> @@ -454,6 +455,11 @@ Pixel/Nexus 安全性公告列舉會對<a href="https://support.google.com/pixel <td>2018 年 7 月 2 日</td> <td>發佈公告。</td> </tr> + <tr> + <td>1.1</td> + <td>2018 年 7 月 3 日</td> + <td>修訂公告內容 (加入 Android 開放原始碼計劃連結)。</td> + </tr> </tbody></table> </body></html>
\ No newline at end of file diff --git a/zh-tw/security/bulletin/pixel/2018-08-01.html b/zh-tw/security/bulletin/pixel/2018-08-01.html new file mode 100644 index 00000000..0be64031 --- /dev/null +++ b/zh-tw/security/bulletin/pixel/2018-08-01.html @@ -0,0 +1,520 @@ +<html devsite><head> + <title>Pixel/Nexus 安全性公告 - 2018 年 8 月</title> + <meta name="project_path" value="/_project.yaml"/> + <meta name="book_path" value="/_book.yaml"/> + </head> + <body> + <!-- + Copyright 2018 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + +<p><em>發佈日期：2018 年 8 月 6 日</em></p> + +<p> +Pixel/Nexus 安全性公告列舉對<a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">支援的 Google Pixel 和 Nexus 裝置</a> (Google 裝置) 造成影響的安全性漏洞和功能改善項目，並說明各項相關細節。2018-08-05 之後的安全性修補程式等級也已針對 Google 裝置解決了這個公告和 2018 年 8 月 Android 安全性公告列出的所有問題。請參閱<a href="https://support.google.com/pixelphone/answer/4457705" class="external">檢查及更新 Android 版本</a>一文，瞭解如何查看裝置的安全性修補程式等級。 +</p> +<p> +所有支援的 Google 裝置都會收到 2018-08-05 修補等級更新。我們建議所有客戶接受這些裝置更新。 +</p> +<p class="note"> +<strong>注意：</strong>您可以前往 <a href="https://developers.google.com/android/images" class="external">Google Developers 網站</a>取得 Google 裝置韌體映像檔。 +</p> + +<h2 id="announcements">公告事項</h2> +<p>我們除了修補 2018 年 8 月 Android 安全性公告中所列出的安全性漏洞外，也針對下文列出的 Google 裝置的安全性漏洞提供修補程式。我們的合作夥伴至少會提前一個月收到這些問題的相關通知，方便他們將相關內容納入其裝置更新中。</p> + +<h2 id="security-patches">安全性修補程式</h2> +<p> +我們依照資安問題本身所影響的元件將各項漏洞分門別類，另外也附上了問題說明和一份 CVE 資訊表，其中包括了相關參考資料、<a href="#type">漏洞類型</a>、<a href="/security/overview/updates-resources.html#severity">嚴重程度</a>，以及更新的 Android 開放原始碼計劃 (AOSP) 版本 (在適用情況下)。假如相關錯誤有公開變更，該錯誤 ID 會連結到相對應的變更 (例如 Android 開放原始碼計劃變更清單)。如果單一錯誤有多項相關變更，您可以透過該錯誤 ID 後面的編號連結開啟額外的參考資料。</p> + +<h3 id="framework">架構</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>更新的 Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2017-1000100</td> + <td> +<a href="https://android.googlesource.com/platform/external/curl/+/1506c0316973bd95d7832891b1aa2258b52a793d">A-64610131</a> +</td> + <td>ID</td> + <td>中</td> + <td>7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="system">系統</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>更新的 Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2018-9435</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/51b05b715024adff4fa59ab2e18c0b56c5d3af5e">A-79591688</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9461</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Messaging/+/17a2579a0aa603a3a7d94e5dc64afeb96e430e8f">A-37629504</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9449</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/27b90f4f6fe3811335e9bb4fac4656bc1df49204">A-79884292</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9457</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Settings/+/a3e94449c8fe0a377b61747b6129fafc930da086">A-72872376</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9441</td> + <td> +<a href="https://android.googlesource.com/platform/system/bt/+/c3c69bed0f76178c640dd8e726967b9cdea5dece">A-74075873</a> +[<a href="https://android.googlesource.com/platform/system/bt/+/3a2799939b2da543ed3a62f29db658cb05f8ad3b">2</a>] +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2017-13322</td> + <td> +<a href="https://android.googlesource.com/platform/packages/services/Telephony/+/c25745addd19b1549b7ec5bdc46d8bf1a1de37ed">A-67862398</a> +</td> + <td>DoS</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> + <tr> + <td>CVE-2018-9447</td> + <td> +<a href="https://android.googlesource.com/platform/packages/services/Telephony/+/19c48992b79df89c730f3619eb69baf03d449e95">A-79995313</a> +</td> + <td>DoS</td> + <td>中</td> + <td>6.0、6.0.1、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="kernel-components">核心元件</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2018-9462</td> + <td>A-78364203<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>中</td> + <td>觸控式螢幕</td> + </tr> + <tr> + <td>CVE-2018-9439</td> + <td>A-79377438<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>中</td> + <td>網路堆疊</td> + </tr> + <tr> + <td>CVE-2018-9463</td> + <td>A-78362414<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>中</td> + <td>觸控式螢幕</td> + </tr> + <tr> + <td>CVE-2018-1068</td> + <td>A-77902350<br /> + <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b71812168571fa55e44cdd0254471331b9c4c4c6"> +上游程式庫核心</a></td> + <td>EoP</td> + <td>中</td> + <td>Netfilter</td> + </tr> + <tr> + <td>CVE-2018-9464</td> + <td>A-68993267<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>中</td> + <td>Taimen 系統啟動載入程式</td> + </tr> +</tbody></table> + +<h3 id="qualcomm-components">Qualcomm 元件</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2018-11263</td> + <td>A-79422278<a href="#asterisk">*</a><br /> + QC-CR#2209106</td> + <td>EoP</td> + <td>中</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-8261</td> + <td>A-35139833<a href="#asterisk">*</a><br /> + QC-CR#2013631</td> + <td>EoP</td> + <td>中</td> + <td>相機驅動程式</td> + </tr> + <tr> + <td>CVE-2018-5910</td> + <td>A-79422277<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=b67e04e3696f05411b7434c8b194895d273b00c5"> +QC-CR#2175499</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=d9344c2f4b60cf5d4c747c11f3cb0b6f1558db78">2</a>] +</td> + <td>EoP</td> + <td>中</td> + <td>MDSS</td> + </tr> + <tr> + <td>CVE-2018-5909</td> + <td>A-79421262<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=2c1716c5afd660651724b6088f2e6301272f4926"> +QC-CR#2174716</a></td> + <td>EoP</td> + <td>中</td> + <td>旋轉器</td> + </tr> + <tr> + <td>CVE-2018-5908</td> + <td>A-79422409<br /> +<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=28e5918c60b832091c6b3618747258803cbd3302"> +QC-CR#2171758</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=4689d03e5db548d263232c274bf307956207da27">2</a>] +</td> + <td>EoP</td> + <td>中</td> + <td>MDSS</td> + </tr> + <tr> + <td>CVE-2018-5905</td> + <td>A-79421261<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=6eb2f4f6fde1b210712d6ac66b40b9e7684d77db"> +QC-CR#2169715</a></td> + <td>EoP</td> + <td>中</td> + <td>Diag 驅動程式</td> + </tr> + <tr> + <td>CVE-2018-5904</td> + <td>A-79421260<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=88b838c8952ec6414c72449ae15768d15d2606dd"> +QC-CR#2184702</a> +[<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.9/commit/?id=8e82c0d84ccee87309fd22f8208915f0ba502b26">2</a>] +</td> + <td>EoP</td> + <td>中</td> + <td>電源驅動程式</td> + </tr> + <tr> + <td>CVE-2018-5903</td> + <td>A-79421737<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=20365fa599f42f6e1f175d9d5d60d964927c2160"> +QC-CR#2185477</a></td> + <td>EoP</td> + <td>中</td> + <td>qcacld 3.0</td> + </tr> + <tr> + <td>CVE-2017-18306</td> + <td>A-73889358<a href="#asterisk">*</a><br /> + QC-CR#2216399</td> + <td>ID</td> + <td>中</td> + <td>v4l2</td> + </tr> + <tr> + <td>CVE-2017-18307</td> + <td>A-73888283<a href="#asterisk">*</a><br /> + QC-CR#2026045</td> + <td>ID</td> + <td>中</td> + <td>qcacld-3.0</td> + </tr> + <tr> + <td>CVE-2017-9711</td> + <td>A-36367253<a href="#asterisk">*</a><br /> + QC-CR#2046006</td> + <td>EoP</td> + <td>中</td> + <td>IPA</td> + </tr> + <tr> + <td>CVE-2018-3587</td> + <td>A-65542521<a href="#asterisk">*</a><br /> + QC-CR#2120605</td> + <td>EoP</td> + <td>中</td> + <td>qcacld-2.0</td> + </tr> +</tbody></table> + +<h3 id="update:-framework">更新項目：架構</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>更新的 Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2017-13295</td> + <td> +<a href="https://android.googlesource.com/platform/frameworks/base/+/da24aa45a8b65a7b9adbe12ff94bf891bdd38825">A-62537081</a> +[<a href="https://android.googlesource.com/platform/packages/apps/PackageInstaller/+/3af01bd93513d902dbb5382b10109fdf3ab29d2d">2</a>] +</td> + <td>DoS</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="update:-system">更新項目：系統</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>更新的 Android 開放原始碼計劃版本</th> + </tr> + <tr> + <td>CVE-2017-13242</td> + <td> +<a href="https://android.googlesource.com/platform/packages/apps/Settings/+/f973e707f50adc0c21599e719be06714f808a333">A-62672248</a> +</td> + <td>ID</td> + <td>中</td> + <td>6.0、6.0.1、7.0、7.1.1、7.1.2、8.0、8.1</td> + </tr> +</tbody></table> + +<h3 id="update:-qualcomm-components">更新項目：Qualcomm 元件</h3> + +<table> + <colgroup><col width="21%" /> + <col width="21%" /> + <col width="14%" /> + <col width="14%" /> + <col width="30%" /> + </colgroup><tbody><tr> + <th>CVE</th> + <th>參考資料</th> + <th>類型</th> + <th>嚴重程度</th> + <th>元件</th> + </tr> + <tr> + <td>CVE-2017-15817</td> + <td>A-68992394<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=fe43c2b64ac81199de17efc258e95546cb0546f1">QC-CR#2076603</a> +[<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/commit/?id=8ba78e506e5002cdae525dd544dbf1df0ccce1ef">2</a>] +<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=343a3f28338788c5c91289f53171c1f71f293cd7">QC-CR#2084599</a> +<br /> +<a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=0c21aaa2fefa6c5919813fdd287436dddda54227">QC-CR#2096512</a> +</td> + <td>RCE</td> + <td>最高</td> + <td>WLAN</td> + </tr> +</tbody></table> + +<h2 id="common-questions-and-answers">常見問題與解答</h2> +<p> +如果您在閱讀這篇公告後有任何疑問，可參考本節的常見問答。 +</p> +<p> +<strong>1. 如何判斷我目前的裝置軟體版本是否已修正這些問題？ +</strong> +</p> +<p> +2018-08-05 之後的安全性修補程式等級完全解決了與 2018-08-05 安全性修補程式等級及所有先前修補程式等級相關的問題。請參閱 <a href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices" class="external">Pixel 與 Nexus 更新時間表</a>中的操作說明，瞭解如何查看裝置的安全性修補程式等級。 +</p> +<p id="type"> +<strong>2.「類型」<em></em>欄中的項目代表什麼意義？</strong> +</p> +<p> +在資安漏洞詳情表格中，「類型」<em></em>欄中的項目代表的是安全性漏洞的類別。 +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>縮寫</th> + <th>定義</th> + </tr> + <tr> + <td>RCE</td> + <td>遠端程式碼執行</td> + </tr> + <tr> + <td>EoP</td> + <td>權限升級</td> + </tr> + <tr> + <td>ID</td> + <td>資訊外洩</td> + </tr> + <tr> + <td>DoS</td> + <td>阻斷服務</td> + </tr> + <tr> + <td>無</td> + <td>未分類</td> + </tr> +</tbody></table> +<p> +<strong>3.「參考資料」<em></em>欄底下列出的識別碼代表什麼意義？</strong> +</p> +<p> +資安漏洞詳情表格中「參考資料」<em></em>欄底下的項目可能會包含一個前置字串，用以表示該參考資料值所屬的機構或公司。 +</p> +<table> + <colgroup><col width="25%" /> + <col width="75%" /> + </colgroup><tbody><tr> + <th>前置字串</th> + <th>參考資料</th> + </tr> + <tr> + <td>A-</td> + <td>Android 錯誤 ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm 參考編號</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek 參考編號</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA 參考編號</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom 參考編號</td> + </tr> +</tbody></table> +<p id="asterisk"> +<strong>4.「參考資料」<em></em>欄中 Android 錯誤 ID 旁邊的星號 (*) 代表什麼意義？</strong> +</p> +<p> +在「參考資料」<em></em>欄中 Android 錯誤 ID 旁邊標上星號 (*) 代表該問題並未公開，相關的更新通常是直接整合在最新的 Pixel/Nexus 裝置專用驅動程式的安裝檔中。您可以前往 <a href="https://developers.google.com/android/nexus/drivers" class="external">Google Developers 網站</a>下載這些驅動程式。 +</p> +<p> +<strong>5. 為什麼安全性漏洞會分別刊載在這份安全性公告和 Android 安全性公告？</strong> +</p> +<p> +為了宣告 Android 裝置最新的安全性修補程式等級，我們必須先在 Android 安全性公告中刊載相關的安全性漏洞。其他安全性漏洞 (例如本安全性公告所刊載的安全性漏洞) 並未強制規定宣告安全性修補程式等級。 +</p> +<h2 id="versions">版本</h2> +<table> + <colgroup><col width="25%" /> + <col width="25%" /> + <col width="50%" /> + </colgroup><tbody><tr> + <th>版本</th> + <th>日期</th> + <th>附註</th> + </tr> + <tr> + <td>1.0</td> + <td>2018 年 8 月 6 日</td> + <td>發佈公告。</td> + </tr> +</tbody></table> + +</body></html>
\ No newline at end of file diff --git a/zh-tw/security/bulletin/pixel/2018.html b/zh-tw/security/bulletin/pixel/2018.html index 051450a1..be6e232d 100644 --- a/zh-tw/security/bulletin/pixel/2018.html +++ b/zh-tw/security/bulletin/pixel/2018.html @@ -34,6 +34,34 @@ <th>安全性修補程式等級</th> </tr> <tr> + <td><a href="/security/bulletin/pixel/2018-08-01.html">2018 年 8 月</a></td> + <td>即將推出 + <!-- + <a href="/security/bulletin/pixel/2018-08-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018 年 8 月 6 日</td> + <td>2018-08-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-07-01.html">2018 年 7 月</a></td> + <td> + <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2018 年 7 月 2 日</td> + <td>2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-06-01.html">2018 年 6 月</a></td> <td> <a href="/security/bulletin/pixel/2018-06-01.html">English</a> / @@ -79,9 +107,7 @@ <a href="/security/bulletin/pixel/2018-03-01.html?hl=ja">日本語</a> / <a href="/security/bulletin/pixel/2018-03-01.html?hl=ko">한국어</a> / <a href="/security/bulletin/pixel/2018-03-01.html?hl=ru">ру́сский</a> / - <!-- - <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / - --> + <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-cn">中文 (中国)</a> / <a href="/security/bulletin/pixel/2018-03-01.html?hl=zh-tw">中文 (台灣)</a> </td> <td>2018 年 3 月</td> diff --git a/zh-tw/security/bulletin/pixel/index.html b/zh-tw/security/bulletin/pixel/index.html index b80f52bb..dcbe0fa6 100644 --- a/zh-tw/security/bulletin/pixel/index.html +++ b/zh-tw/security/bulletin/pixel/index.html @@ -43,6 +43,34 @@ <th>安全性修補程式等級</th> </tr> <tr> + <td><a href="/security/bulletin/pixel/2018-08-01.html">2018 年 8 月</a></td> + <td>即將推出 + <!-- + <a href="/security/bulletin/pixel/2018-08-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-08-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>2018 年 8 月 6 日</td> + <td>2018-08-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2018-07-01.html">2018 年 7 月</a></td> + <td> + <a href="/security/bulletin/pixel/2018-07-01.html">English</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2018-07-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>2018 年 7 月 2 日</td> + <td>2018-07-05</td> + </tr> + <tr> <td><a href="/security/bulletin/pixel/2018-06-01.html">2018 年 6 月</a></td> <td> <a href="/security/bulletin/pixel/2018-06-01.html">English</a> / |
