search

thoughtworks / talisman

Using a pre-commit hook, Talisman validates the outgoing changeset for things that look suspicious — such as tokens, passwords, and private keys.
https://thoughtworks.github.io/talisman/
MIT License
1.91k stars 242 forks source link

how to setup Talisman CLI in RHEL7 #373

Open venkatn087 opened 2 years ago

venkatn087 commented 2 years ago

Hi Team,

Hope you are doing well.

I have gone through the github page to set up Talisman as a CLI utility in RHEL7, but i am unable to set it up .Could you please let me know the steps to setup the Talisman as CLI and also could you please share talisman command to scan the entire git repo.

I have followed below steps to do the same. mkdir ~/.talisman cd ~/.talisman curl -L -O https://github.com/thoughtworks/talisman/releases/download/v1.28.0/talisman_linux_386 chmod +x talisman_linux_386 go to githubrepo directory then execute the below command ~/.talisman/talisman_linux_386 --scan

But if i given talisman --version getting an error as brsubbareddy123@instance-5 ~]$ talisman --version -bash: talisman: command not found --------------------------------->Error. [brsubbareddy123@instance-5 ~]$

Best Regards Venkat

svishwanath-tw commented 2 years ago

@venkatn087 : Please use official installation script. If you download binary using curl, you risk being unable to verify checksum.

Alternatively you can add the path to talisman binary to the shell path.

export PATH="$HOME/.talisman:$PATH"

In either case, the executable is still called talisman_linux_386 . So it can be invoked using plain talisman. The steps you claim to have followed explicitly says:

# go to githubrepo directory then execute the below command
~/.talisman/talisman_linux_386 --scan