LeDav1 / Unlock_bit

1 stars 0 forks source link

Unlock_bit

Choice of Programming Language

Ransomware developer team

Plan

Forensics Team

Documentation

I/O calls and best practices are taken from Rust's documentation on I/O

Usage:

cargo run -- command path

Example

cargo run -- encrypt path 

Coding practices

Separation of Concerns for Binary Projects

The organizational problem of allocating responsibility for multiple tasks to the main function is common to many binary projects. As a result, the Rust community has developed guidelines for splitting the separate concerns of a binary program when main starts getting large. This process has the following steps:

The responsibilities that remain in the main function after this process should be limited to the following:

This pattern is about separating concerns: main.rs handles running the program, and lib.rs handles all the logic of the task at hand. Because you can’t test the main function directly, this structure lets you test all of your program’s logic by moving it into functions in lib.rs. The code that remains in main.rs will be small enough to verify its correctness by reading it. Let’s rework our program by following this process.