Skip to content

Conversation

david-a-wheeler
Copy link
Contributor

Extend the AI guidance to specifically discuss constant-time comparisons. It's common to fail to do this, so
give specific instructions to counter this tendency.

Extend the AI guidance to specifically discuss constant-time
comparisons. It's common to fail to do this, so
give specific instructions to counter this tendency.

Signed-off-by: David A. Wheeler <[email protected]>
@david-a-wheeler
Copy link
Contributor Author

@balteravishay - thoughts?

@balteravishay
Copy link
Contributor

looks great, thanks @david-a-wheeler !

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR enhances the security guidance for AI code assistants by specifically emphasizing constant-time comparisons as a critical security practice. The change addresses a common security vulnerability where timing attacks can be used to extract sensitive information through side-channel analysis.

  • Adds explicit guidance on using constant-time comparisons for sensitive data operations
  • Expands the authentication and authorization section to include timing attack prevention
  • Updates the sample instructions to include specific examples of when constant-time comparisons are necessary

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@balteravishay balteravishay merged commit d24e400 into main Sep 9, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants