Skip to content

Releases: thoughtworks/talisman

scanwithrc

12 Nov 12:34
672c51c
Compare
Choose a tag to compare
scanwithrc Pre-release
Pre-release
Fix markdown syntax for link (#276)

Hacktoberfest contributions

02 Nov 05:54
622f31e
Compare
Choose a tag to compare
  • A CLI flag to make talisman scan only HEAD (latest commit on branch), thanks to @louiedp3
  • A progress bar to display scanning progress, thanks to @dineshba
  • Changes to priority of some default search patterns, thanks to @tinamthomas
  • Clojure keyword additions, thanks to @ravik-karn

Some fixes

17 Sep 06:45
Compare
Choose a tag to compare
  • Disabled interactive mode for pre-push hook
  • Fix for issue where talismanrc ignore directives are not processed by talisman on git-bash for windows, thanks to @dcRUSTy
  • Fix to talisman hook script to process TALISMAN_INTERACTIVE and TALISMAN_DEBUG env flags only when set to true

Reduced binary sizes

31 Aug 09:54
648e456
Compare
Choose a tag to compare

Thanks to @dcRUSTy for setting up upx + lzma compression in CI

Disable interactive mode in windows temporarily

25 Aug 13:29
7e0ea2e
Compare
Choose a tag to compare

Interactive mode for talisman will only work on non-windows machines.
This is till we figure out a way to make it work with gitbash and/or powershell.

Fix File Overwrite issue vulnerability in talisman scan report generation

15 Aug 00:58
1fecebc
Compare
Choose a tag to compare
v1.6.0

Fix Case of Arbitrary File Overwrite while scanning malicious repo (#…

Fix for DOS of CI via talisman by avoiding scan of symlinks

13 Aug 14:08
0855689
Compare
Choose a tag to compare
v1.5.0

[Issue #220] - dcRUSTy - Fix DOS vulnerability related to scanning sy…

Ignored patterns and RCE prevention

08 Aug 17:15
b821169
Compare
Choose a tag to compare
  • Ability to set Base64Entropy threshold in .talismanrc, thanks to @michaellihs
  • Users now have a choice to install talisman hook in interactive mode (instead of having to set the mode manually before invocation), thanks to @harinee
  • Threshold values for various scan matches and ability to configure threshold in .talismanrc, thanks to @tinamthomas (@tt-official ?)
  • .talismanrc now supports allowed patterns at file and repo level to prevent false positives, thanks to @steeve85
  • Fix for an RCE exploit/vulnerability issue raised by @dcRUSTy on windows, thanks to @dineshba and @prabhu43

Wildcard support in talismanrc and other enhancements

12 Jun 10:11
01d957c
Compare
Choose a tag to compare
  • Code Refactorings: Grouped detectors using package (#197)
  • Add some spacing and filename in prompt in interactive mode (#194)
  • Allow usage of wildcards in talismarc file (#196)
  • Code cleanup (#193)
  • Issue #185:Changed the pattern checking for passwords to verify strings succeeding the password phrase. *
  • Detect more sensitive phrases (#188)

Adding support for custom patterns in filecontent detection

12 Mar 10:21
6e6178b
Compare
Choose a tag to compare
#183 Custom patterns  (#187)

* Rename TalismanRCIgnore to TalismanRC

* Code cleanup:
Rename NewtalismanRC to NewTalismanRC
Remove code and tests related to talismanignore

* Code cleanup: Make talismanRC receiver name consistent

* Introduce PatternString type
Omit empty fields when writing yaml

* #183 | Add ability to specify custom scan pattern via talismanrc

* Update Readme:
Update help text for CLI options (fix typo in -i message description)
Add custom_pattern section with example