Support secret scanning without getting scan truncated for every commit

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: Secret Scanning
    • None
    • 1
    • 6

      Scan is truncated if customer pushes commit diff that

      • exceeds page.max.diff.lines
      • the number of characters in a single line of the diff exceeds page.max.source.length
      • secret scanning exceeds the timeout secretscanning.scan.timeout{}

       
      Current Behaviour
      Bitbucket truncates secret scan if any of the conditions above are met, however, unscanned diffs could contain secrets.

      Expected Behaviour
      The secret scanning should not be affected by the following properties with a hard limit:

      • exceeds page.max.diff.lines
      • the number of characters in a single line of the diff exceeds page.max.source.length

      Workaround

      Perform the commits in smaller diff batches to avoid exceeding the 10000 page.max.diff.lines hard limit.
       

            Assignee:
            Unassigned
            Reporter:
            Pamara Lim (Inactive)
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: