Skip to content

Bugs/ed keys loading#365

Merged
Spomky merged 6 commits into
3.1.xfrom
bugs/ed-keys-loading
Aug 22, 2022
Merged

Bugs/ed keys loading#365
Spomky merged 6 commits into
3.1.xfrom
bugs/ed-keys-loading

Conversation

@Spomky

@Spomky Spomky commented Aug 22, 2022

Copy link
Copy Markdown
Member
Q A
Branch? 3.0.x
Bug fix? yes
New feature? no
Deprecations? no
Tickets #346
License MIT

@Spomky Spomky added the bug label Aug 22, 2022
@Spomky Spomky added this to the 3.0.8 milestone Aug 22, 2022
@Spomky Spomky self-assigned this Aug 22, 2022
@gitguardian

gitguardian Bot commented Aug 22, 2022

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
3147152 Generic Private Key 4f84a57 tests/Component/KeyManagement/Keys/ED/private-ed25519-with-public.pem View secret
4242658 Generic Private Key 7afba43 foo.key View secret
3147152 Generic Private Key 7afba43 tests/Component/KeyManagement/Keys/ED/private-ed25519-with-public.pem View secret
4242658 Generic Private Key 7afba43 tests/Component/KeyManagement/Keys/ED/private-secp384r1-with-public.pem View secret
4242658 Generic Private Key fc5cf2c foo.key View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@Spomky Spomky changed the base branch from 3.1.x to 3.0.x August 22, 2022 16:14
temp and others added 2 commits August 22, 2022 18:43
@Spomky Spomky changed the base branch from 3.0.x to 3.1.x August 22, 2022 17:50
@Spomky Spomky modified the milestones: 3.0.8, 3.1.0 Aug 22, 2022
@Spomky Spomky force-pushed the bugs/ed-keys-loading branch 4 times, most recently from 54a31fb to 4f84a57 Compare August 22, 2022 17:54
@guardrails

guardrails Bot commented Aug 22, 2022

Copy link
Copy Markdown

All previously detected findings have been fixed. Good job! 👍🎉

We will keep this comment up-to-date as you go along and notify you of any security issues that we identify.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

@Spomky Spomky merged commit 4379a59 into 3.1.x Aug 22, 2022
@Spomky Spomky deleted the bugs/ed-keys-loading branch August 22, 2022 19:38
Spomky added a commit that referenced this pull request Aug 23, 2022
* Add missing context parameters for supportsDenormalization() (#359)

Co-authored-by: Stephan Wentz <swentz@brainbits.net>

* Rebase

* PKCS#8 Loading

* PHPStan errors fixed

* foo.key removed

Co-authored-by: Stephan Wentz <stephan@wentz.it>
Co-authored-by: Stephan Wentz <swentz@brainbits.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants