Set up Fluid Attacks for CASA tier 2 audit

[JaniruTEC]

This PR sets up the Fluid Attacks CLI tool to prepare for the CASA tier 2 audit.

• Add tool to project.
• Add fastlane lane.

Also see: cryptomator/android#523

Summary by CodeRabbit

• Chores
  • Updated .gitignore to exclude specific results files related to Fluid Attacks.

[coderabbitai]

Walkthrough

This update introduces a new exclusion pattern to the .gitignore file, specifically designed to ignore the results.csv file generated by Fluid Attacks within any fastlane directory across the project. This change ensures that sensitive or unnecessary data produced during security assessments by Fluid Attacks does not inadvertently get committed to the repository, maintaining a cleaner and more secure codebase.

Changes

File	Change Summary
.gitignore	Added exclusion for **/fastlane/.../results.csv

Poem

🐇✨
In the burrows of code, where secrets hide,
A rabbit hops, with eyes so wide.
"Fear not," it whispers, "for I've found a way,
To keep the sneaky leaks at bay."
With a hop and a skip, it sets the rule,
In .gitignore, it's no fool.
"Now let's celebrate, for our code is neat,
With Fluid's secrets not on the street."
🌟🐾

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 77db4dd and fec5e01.

Files ignored due to path filters (1)

• fastlane/fluidattacks/config.yaml is excluded by: !**/*.yaml

Files selected for processing (1)

• .gitignore (1 hunks)

Additional comments: 1

.gitignore (1)

• 49-49: The addition of **/fastlane/fluidattacks/results.csv to the .gitignore file is a prudent measure to ensure that sensitive information, such as security scan results from the Fluid Attacks tool, is not inadvertently committed to the version control system. This aligns with best practices for managing sensitive information and helps maintain the security integrity of the project. Good job on implementing this exclusion pattern.