For some coverity checkers like: -- DC.PREDICTABLE_KEY_PASSWORD -- DC.STREAM_BUFFER -- DC.WEAK_CRYPTO -- DC.STRING_BUFFER -- SECURE_CODING The results are very inaccurate so we should disable them from the analysis.
Bug 1581846 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For some coverity checkers like: - DC.PREDICTABLE_KEY_PASSWORD - DC.STREAM_BUFFER - DC.WEAK_CRYPTO - DC.STRING_BUFFER - SECURE_CODING The results are very inaccurate so we should disable them from the analysis.
For some coverity checkers like: - DC.PREDICTABLE_KEY_PASSWORD - DC.STREAM_BUFFER - DC.WEAK_CRYPTO - DC.STRING_BUFFER - SECURE_CODING The results are very inaccurate so we should disable them from the analysis.
For some coverity checkers like: - DC.PREDICTABLE_KEY_PASSWORD - DC.STREAM_BUFFER - DC.WEAK_CRYPTO - DC.STRING_BUFFER - SECURE_CODING The results are very inaccurate so we should disable them from the analysis. The rest of implementation will be done on the snapshot generating machine that is not currently part of infra.