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/ios#340

Summary by CodeRabbit

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

[coderabbitai]

Walkthrough

This update enriches the .gitignore file with additional entries specifically designed to exclude files associated with Fluid Attacks. By doing so, it ensures that sensitive or unnecessary files related to this security tooling are not inadvertently included in the project's version control system, maintaining a cleaner and more secure codebase.

Changes

Files Changed	Summary of Changes
.gitignore	Added entries to exclude files related to Fluid Attacks

🐰✨
In the burrow of code, where secrets lie deep,
A rabbit hopped in, making not a peep.
With a flick and a hop, it weaved its charm,
Keeping the burrow safe, away from harm.
"Fear not," it whispered, "for I've made a pact,
To guard our secrets, with .gitignore intact."
🌟🐾

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 c994b12 and 2c2b57c.

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: 2

.gitignore (2)

• 56-56: The addition of **/fastlane/fluidattacks/results.csv to the .gitignore file is a good practice to ensure that sensitive data, potentially contained within the results file generated by the Fluid Attacks tool, is not accidentally committed to the version control system. This change aligns with the objective of enhancing the project's security posture.
• 57-57: The inclusion of /apk_files/ in the .gitignore file suggests that this directory is used to store APK files that should not be tracked by version control. This is a sensible addition, especially if the directory is used to store APKs generated during testing or other processes that involve the Fluid Attacks tool. However, it's important to ensure that this directory is indeed used for such purposes and that excluding it from version control does not inadvertently ignore files that should be tracked.

Verification successful

---

The reference found in fastlane/fluidattacks/config.yaml confirms that the /apk_files/ directory is indeed used for temporary purposes, specifically mentioning its deletion post-use by a tool. This supports the inclusion of /apk_files/ in the .gitignore file, aligning with the rationale that it's used to store APK files generated during processes that should not be tracked by version control. Therefore, the review comment is consistent with the codebase's usage of the directory.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the usage of /apk_files/ directory to ensure it's intended for temporary or sensitive files not meant for version control.
fd 'apk_files' --exec ls -l {}

Length of output: 32

---

---

Script:

#!/bin/bash
# Search for references to 'apk_files' within the codebase to understand its usage context.
rg 'apk_files'

Length of output: 112