Secret Leak.go help

Issues & Feature Request
1

I have the following solution:

  • using a startup script
  • use uuidgen to generate secret in startup script
  • secret stored in ENV var

I’ve checked that the secret is indeed generated and working with make run. The secret does not exist in any of the source code.

I’m getting the following fail:

  • e[90m3:29AMe[0m e[31mWRNe[0m leaks found: 4

Unsure of why it’s failing and how to continue.

2

Hey @johnzt2020
This may be because secret is still leaked somewhere else. Have you tried opening any of the hints? :slight_smile:

it will give you the direction.

3

Read the hint, that makes a lot of sense haha. Thanks for the challenge :slight_smile:

1 Like
4

“I agree with @johnzt2020, the error messages do not provide any reasonable explanation, and the hints’ explanations do not give sufficient information. Even though I opened the hints, I couldn’t understand how to proceed and what to do.”

1 Like
5

Hey ege359, welcome to the SecDim community :tada:

The error message (upon failed test) you will see in the remote tests is usually the best guide to fine-tuning your solution, remember that challenges are git repositories. Soo lets say you removed the secret in the most recent commit, what happens to that same string in any previous commits?

I would suggest checking the repository history and then searching for a tool that is capable of performing git-repo wizardry.

Good luck!

Matt

Hint $ git log
$ git log -S "stringtofind" -p
6

There is a hint the gives away the command that you can run. Have you tried it?