From 52c023f215bfe90d611bf0605c07bbadbce61e54 Mon Sep 17 00:00:00 2001 From: Aban Ahmed <119570462+iamthgeawsomboi2099@users.noreply.github.com> Date: Tue, 17 Sep 2024 17:02:31 +0400 Subject: [PATCH] Index.html Security patch MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-Security-Policy (CSP): This controls where content can be loaded from, preventing loading of malicious scripts. We’ve restricted it to self-hosted sources ('self') and whitelisted cdnjs for FontAwesome and Google Fonts. default-src 'self': Allows content to be loaded only from the same origin. script-src 'self' https://cdnjs.cloudflare.com: Allows scripts to be loaded from the same origin and FontAwesome’s CDN. style-src 'self' https://fonts.googleapis.com: Allows styles to be loaded from the same origin and Google Fonts. font-src 'self' https://fonts.gstatic.com: Allows fonts to be loaded from the same origin and Google Fonts. X-Frame-Options: Prevents clickjacking attacks by restricting iframes to only allow the site to be embedded in frames from the same origin (SAMEORIGIN). X-Content-Type-Options: Prevents MIME type sniffing by browsers by setting nosniff. This forces the browser to use the content type as declared and not attempt to guess it. Referrer-Policy: Controls what information is sent in the Referer header when navigating away from your site. Setting it to strict-origin-when-cross-origin ensures minimal referrer data is sent when navigating to other domains. Important Notes: Meta Tags vs. Server Headers: These tags are not as robust as setting the actual HTTP headers on the server. For production use, configure these headers on your web server (Apache, Nginx, etc.). Adjust CSP for Your Needs: If your website includes other external scripts, images, or styles, you may need to whitelist those domains in the Content-Security-Policy. --- Logicytics/index.html | 45 +++++++ Logicytics/install.html | 33 +++++ Logicytics/styles.css | 280 ++++++++++++++++++++++++++++++++++++++++ Logicytics/wiki.html | 65 ++++++++++ Logicytics/wiki1.html | 68 ++++++++++ Logicytics/wiki2.html | 116 +++++++++++++++++ Logicytics/wiki3.html | 140 ++++++++++++++++++++ Logicytics/wiki4.html | 50 +++++++ 8 files changed, 797 insertions(+) create mode 100644 Logicytics/index.html create mode 100644 Logicytics/install.html create mode 100644 Logicytics/styles.css create mode 100644 Logicytics/wiki.html create mode 100644 Logicytics/wiki1.html create mode 100644 Logicytics/wiki2.html create mode 100644 Logicytics/wiki3.html create mode 100644 Logicytics/wiki4.html diff --git a/Logicytics/index.html b/Logicytics/index.html new file mode 100644 index 0000000..1fd5076 --- /dev/null +++ b/Logicytics/index.html @@ -0,0 +1,45 @@ + + + + + + + Logicytics - Forensic Analysis Tool + + + + + + + + + + + + + + + + + + + +
+
+

Logicytics

+

+ Logicytics is a cutting-edge tool designed to meticulously harvest and collect a vast array of Windows system data for forensic analysis. + Crafted with Python 🐍, it's an actively developed project dedicated to gathering as much sensitive data as possible and packaging it neatly into a ZIP file 📦. + This comprehensive guide is here to equip you with everything you need to use Logicytics effectively. +

+ + Learn How to Install Logicytics + + + Check out my Github + + Check My Wiki Out +
+
+ + diff --git a/Logicytics/install.html b/Logicytics/install.html new file mode 100644 index 0000000..c677ac9 --- /dev/null +++ b/Logicytics/install.html @@ -0,0 +1,33 @@ + + + + + + + How to Install Logicytics + + + +
+

How to Install Logicytics

+

To install and set up Logicytics, follow these steps:

+ +

Prerequisites

+ +

Step-by-Step Installation

+
  • Learn the instalation Steps On my Github
    • + + Back to Home +
    + + diff --git a/Logicytics/styles.css b/Logicytics/styles.css new file mode 100644 index 0000000..a132577 --- /dev/null +++ b/Logicytics/styles.css @@ -0,0 +1,280 @@ +/* General Reset */ +* { + margin: 0; + padding: 0; + box-sizing: border-box; + font-family: 'Poppins', sans-serif; +} + +/* Hero Section */ +.hero { + display: flex; + justify-content: center; + align-items: center; + height: 100vh; + background: url('https://images.unsplash.com/photo-1564149508614-9453f0859d7e?fit=crop&w=1920&q=80') no-repeat center center/cover; + color: #fff; + text-align: center; + position: relative; +} + +/* Overlay Effect */ +.hero::before { + content: ''; + position: absolute; + top: 0; + left: 0; + right: 0; + bottom: 0; + background: rgba(0, 0, 0, 0.5); + z-index: 1; +} + +/* Content Styling */ +.content { + position: relative; + z-index: 2; + padding: 20px; + max-width: 800px; +} + +/* Title Styling */ +.title { + font-size: 60px; + margin-bottom: 20px; + font-weight: 600; + animation: fadeIn 2s ease-out; +} + +/* Description Styling */ +.description { + font-size: 20px; + line-height: 1.6; + font-weight: 300; + animation: fadeIn 3s ease-out; +} + +/* Link Styling */ +.install-link { + display: inline-block; + margin-top: 20px; + padding: 10px 20px; + background-color: #ff4757; + color: #fff; + text-decoration: none; + border-radius: 5px; + transition: background-color 0.3s; + animation: fadeIn 3.5s ease-out; +} + +.install-link:hover { + background-color: #ff6b81; +} + +/*Github and Wiki Button Design for index page*/ + +.github { + display: inline-block; + margin-top: 20px; + margin-bottom: 20px; + margin-left: 10px; + padding: 10px 20px; + background-color: black; + color: #fff; + text-decoration: none; + border-radius: 5px; + transition: background-color 0.3s; + animation: fadeIn 3.5s ease-out; +} + +.github:hover { + background-color: darkgray; + color: black; +} + +.wiki-button{ + display: inline-block; + margin-top: 20px; + padding: 10px 20px; + background-color: rgb(247, 245, 245); + color: #000000; + text-decoration: none; + border-radius: 5px; + transition: background-color 0.3s; + animation: fadeIn 3.5s ease-out; +} + +.wiki-button:hover { + background-color: blanchedalmond; +} + +.install-link i, .github, .wiki.wiki.button i { + margin-right: 8px; /* Adjust spacing between icon and text */ + font-size: 16px; /* Adjust icon size */ + vertical-align: middle; +} + +/* Fade In Animation */ +@keyframes fadeIn { + from { + opacity: 0; + transform: translateY(20px); + } + to { + opacity: 1; + transform: translateY(0); + } +} + +/* Styles for Installation Page */ +.installation { + padding: 40px; + max-width: 800px; + margin: auto; + text-align: left; +} + +.installation h2 { + font-size: 36px; + margin-bottom: 20px; +} + +.installation p, .installation ul { + font-size: 18px; + line-height: 1.6; + margin-bottom: 20px; +} + +.installation ul { + padding-left: 20px; +} + +.installation li { + margin-bottom: 10px; +} + + +/* About Page Styles */ +.wiki-page { + padding: 40px; + max-width: 800px; + margin: auto; + text-align: left; + color: #333; +} + +.wiki-page h1 { + font-size: 48px; + margin-bottom: 20px; + text-align: center; +} + +.section { + margin-bottom: 40px; +} + +.section h2 { + font-size: 32px; + margin-bottom: 10px; +} + +.section p { + font-size: 18px; + line-height: 1.6; +} + +/* Link styling to maintain consistency */ +.install-link { + display: inline-block; + margin-top: 20px; + padding: 10px 20px; + background-color: #ff4757; + color: #fff; + text-decoration: none; + border-radius: 5px; + transition: background-color 0.3s; +} + +/* General container to hold sidebar and main content */ +.container { + display: flex; + min-height: 100vh; +} + +/* Sidebar Styles */ +.sidebar { + width: 250px; + background-color: #333; + padding: 20px; + color: #fff; + position: fixed; + height: 100%; +} + +.sidebar nav ul { + list-style: none; + padding: 0; +} + +.sidebar nav ul li { + margin-bottom: 15px; +} + +.sidebar nav ul li a { + color: #fff; + text-decoration: none; + font-size: 18px; + transition: color 0.3s; +} + +.sidebar nav ul li a:hover { + color: #ff4757; +} + +/* Main Content Styles */ +.wiki { + margin-left: 270px; /* Adjust margin to fit sidebar */ + padding: 40px; + max-width: 800px; + color: #333; +} + +.wiki h1 { + font-size: 48px; + margin-bottom: 20px; + text-align: center; +} + +.section { + margin-bottom: 40px; +} + +.section h2 { + font-size: 32px; + margin-bottom: 10px; +} + +.section p { + font-size: 18px; + line-height: 1.6; +} + +/* Link styling */ +.install-link { + display: inline-block; + margin-top: 20px; + padding: 10px 20px; + background-color: #ff4757; + color: #fff; + text-decoration: none; + border-radius: 5px; + transition: background-color 0.3s; +} + +.install-link:hover { + background-color: #ff6b81; +} + +/*By Aban Mahmood Ahmed Github: https://github.com/iamthgeawsomboi2099 */ + + diff --git a/Logicytics/wiki.html b/Logicytics/wiki.html new file mode 100644 index 0000000..375902d --- /dev/null +++ b/Logicytics/wiki.html @@ -0,0 +1,65 @@ + + + + + + + About Logicytics + + + + + + +
    + + + + +
    +

    Welcome to Logicytics!

    + +
    +

    About Logicytics

    +

    + Logicytics is a cutting-edge project aimed at revolutionizing the way we manage data collection operations. +

    +
    + +
    +

    Getting Started

    +

    + Whether you're new to Logicytics or a seasoned user, navigating our wiki is straightforward. +

    +
    + +
    +

    Contributing

    +

    + We believe in the power of community. Whether you're a developer wanting to contribute to the codebase or a user with feedback, we welcome you to join us. + Check out our contribution guidelines for more information. +

    +
    + +
    +

    Contact Us

    +

    + For any inquiries, feedback, or collaboration opportunities, feel free to reach out to us via our contact page or directly through our GitHub profiles. +

    +
    + + Back to Home +
    +
    + + diff --git a/Logicytics/wiki1.html b/Logicytics/wiki1.html new file mode 100644 index 0000000..498d262 --- /dev/null +++ b/Logicytics/wiki1.html @@ -0,0 +1,68 @@ + + + + + + + What is Logicytics? + + + + + + +
    + + + + +
    +

    What is Logicytics?

    + +
    +

    Overview of Logicytics

    +

    + Logicytics is a specialized software tool designed for the purpose of collecting and harvesting a broad spectrum of data from Windows systems. + This data is crucial for forensic investigations, allowing investigators to analyze system activities, identify potential security breaches, + and reconstruct events leading up to incidents. The tool is particularly valuable in digital forensics, where the ability to extract detailed + information from a system under investigation is paramount. +

    +
    + +
    +

    Key Features

    +
      +
    • + Comprehensive Data Collection: Logicytics is engineered to gather a wide array of data types, including system logs, + application data, network traffic information, and more. This ensures that investigators have access to a comprehensive dataset for their analysis. +
      • +
    • + Python-Based Development: Being a Python-based project, Logicytics benefits from the flexibility, readability, and extensive + library support offered by Python. This allows for easy integration with other tools and libraries commonly used in the field of digital forensics. +
      • +
    • + Output Flexibility: The tool outputs collected data into a ZIP file, making it convenient for storage and transfer. + Investigators can easily share these files with others involved in the case or import them into forensic analysis tools for further examination. +
      • +
    • + Active Development: Logicytics is an actively developed project, meaning that new features, improvements, and bug fixes are + regularly introduced. This ensures that users benefit from the latest advancements in data collection techniques and forensic analysis methods. +
      • +
    +
    + + Back to Home +
    +
    + + diff --git a/Logicytics/wiki2.html b/Logicytics/wiki2.html new file mode 100644 index 0000000..b5f2bf5 --- /dev/null +++ b/Logicytics/wiki2.html @@ -0,0 +1,116 @@ + + + + + + + Contribution Guidelines + + + + + + +
    + + + + +
    +

    How to Contribute

    + +
    +

    Getting Started

    +

    Contributing to open-source projects is a rewarding way to give back to the community while enhancing your skills. Here's how you can get started:

    +
      +
    1. Fork the Repository: Visit the project's GitHub page and click on the 'Fork' button at the top right corner. This creates a copy of the repository in your GitHub account.
      2. +
    2. Clone the Repository: Clone the forked repository to your local machine using Git. Open your terminal or command prompt and run:
      + git clone https://github.com/DefinetlyNotAI/Logicytics.git +
      3. +
    3. Create a New Branch: Create a new branch for your changes. This keeps the main branch clean and makes merging easier. Run:
      + git checkout -b feature/your-feature-description
      + Replace + your-feature-description with your feature description. +
      4. +
    4. Make Your Changes: Navigate through the files and make your contributions. Remember to adhere to the project's coding standards and practices outlined below.
      5. +
    5. Commit Your Changes: After making your changes, stage them for commit. Then, commit with a meaningful message:
      + git add .
      + git commit -m "Your descriptive commit message" +
      6. +
    6. Push Your Changes: Push your committed changes to your forked repository on GitHub:
      + git push origin feature/your-feature-description +
      7. +
    7. Open a Pull Request (PR): Go to your forked repository on GitHub, switch to your feature branch, and click 'New pull request'. Fill out the form, describing your changes and why they should be included. Submit the PR for review.
      8. +
    +
    + +
    +

    Contributors

    +

    Contributors play a vital role in the growth and success of open-source projects. They come in various forms, each contributing uniquely:

    +
      +
    • Functionality Adders: Introduce new features and functionalities to the project, expanding the software's capabilities.
      • +
    • Code Cleaners: Focus on improving the existing codebase by refactoring, optimizing performance, and simplifying complex logic.
      • +
    • QoL Enhancers: Improve the usability and enjoyment of the software without necessarily adding new features. This includes UI improvements, documentation updates, or bug fixes.
      • +
    • Bug Hunters: Find and fix bugs of all sizes, contributing to both minor fixes and major stability improvements.
      • +
    +
    + +
    +

    Basic Code Practices

    +
      +
    • Coding Style: Align your code with the project's established coding style, including consistent indentation and naming conventions.
      • +
    • Docstrings and Comments: Include comprehensive docstrings for functions and classes, explaining their purpose, parameters, and return values. Use comments sparingly for clarity.
      • +
    • Functions and Modularity: Break down your code into reusable functions and modules for enhanced readability and maintainability.
      • +
    +
    + +
    +

    File Adding

    +
      +
    • Language Preference: Prefer Python, Batch, or PowerShell for compatibility and ease of maintenance. Ensure any other language used is well-documented and easily maintainable.
      • +
    • File Naming and Organization: Follow the project's directory structure and naming conventions for logical organization.
      • +
    +
    + +
    +

    Coding Rules

    +

    Printing Rules

    +
      +
    • Python Users: Utilize the built-in class CODE/__lib_log.py for colored output and structured logging. Avoid using print() directly.
      • +
    • Other Languages: Start messages with appropriate keywords (INFO:, WARNING:, ERROR:) followed by the message, e.g., "INFO: Your Message".
      • +
    + +

    For Python's CRITICAL Method:

    +
      +
    • Filecode: First letter of the filename, except if the file starts with an underscore, then use the first two letters.
      • +
    • Errorcode: U for Unknown, G for General (exceptions), P for Privileges error, C for Corruption, O for OS errors, L for Library Errors.
      • +
    • Functioncode: X for Unknown, first letter of the function name, BA for base code, C# for class and first function letter, CC# for nested class in a method.
      • +
    +
    + +
    +

    Credits

    +

    Acknowledge your contributions appropriately in the CREDITS.md file. Use the following template:

    + 
    +### File-Created by Your-Username
+What you did, created, removed, or refactored.
+- [Your GitHub Username](Your GitHub Link)
+
    +

    This ensures proper attribution and recognition for your efforts.

    +
    + + Back to Home +
    +
    + + diff --git a/Logicytics/wiki3.html b/Logicytics/wiki3.html new file mode 100644 index 0000000..ab99ee6 --- /dev/null +++ b/Logicytics/wiki3.html @@ -0,0 +1,140 @@ + + + + + + + Usage - Logicytics + + + + + + +
    + + + + +
    +

    Introduction

    +

    Logicytics.py is a comprehensive tool designed to streamline and automate various tasks related to software development, system management, and data processing. It offers a wide range of functionalities through command-line flags, allowing users to customize their experience according to their needs.

    + +
    +

    Flags

    + +

    General Usage

    +

    Flags are command-line arguments that modify the behaviour of the Logicytics.py script. They provide a flexible way to execute specific parts of the program or alter its default behaviour. To use a flag, include it after the script name when running it from the command line, preceded by two hyphens (--). For example:

    + 
    .\Logicytics.py -h
    +

    This command would run the help menu of Logicytics.

    + +

    Specific Flags

    +

    Below is a list of specific flags you can use with Logicytics.py:

    + 
    +Logicytics.py [-h] [--default] [--minimal] [--unzip-extra] [--backup]
+                     [--restore] [--update] [--extra] [--dev] [--exe]
+                     [--debug] [--modded] [--threaded] [--webhook] [--reboot]
+                     [--shutdown]
+
+-h: Show this help message and exit
+--default: Runs Logicytics default
+--minimal: Run Logicytics in minimal mode. Just bare essential scraping
+
+--unzip-extra: Unzip the extra directory zip File - Use on your own device 
    only
+--backup: Backup Logicytics files to the ACCESS/BACKUPS directory - Use on your own device 
     only
+--restore: Restore Logicytics files from the ACCESS/BACKUPS directory - Use on your own device
     only
+--update: Update Logicytics from GitHub - Use on your own device only
+--extra: Open the extra directory for more tools
+--dev: Run Logicytics developer mode, only for registering contributions properly - Use on your 
    own device only
+--exe: Run Logicytics using its precompiled EXE files. These may be outdated and not optimal,
     use only if the device doesn't have Python installed
+--debug: Runs the Debugger, checks for any issues, warnings, etc. Useful for debugging and 
     issue reporting
+--modded: Runs the normal Logicytics, as well as any file in the MODS directory. Useful for 
    custom scripts
+--threaded: Runs Logicytics using threads, allowing it to run in parallel
+--webhook: Sends the output ZIP file via webhook
+--reboot: Reboots the device after execution
+--shutdown: Shuts down the device after execution
+
    +
    + +
    +

    Flags Compatibility and Restrictions

    +

    Certain flags can only be used by themselves, while others can be combined. It's important to understand the compatibility and restrictions of these flags:

    +
      +
    • Flags that must be used alone:
      • +
        +
      • --unzip-extra
        • +
      • --backup
        • +
      • --restore
        • +
      • --update
        • +
      • --extra
        • +
      • --dev
        • +
      • --debug
        • +
      +
    • Unique flags that can't be used with each other but can be used with sub-action flags:
      • +
        +
      • --default
        • +
      • --minimal
        • +
      • --extra
        • +
      • --exe
        • +
      • --modded
        • +
      • --threaded
        • +
      +
    • Sub-action flags that can't be used with each other and must be paired with a primary action flag:
      • +
        +
      • --webhook
        • +
      • --reboot
        • +
      • --shutdown
        • +
      +
    +

    Choosing multiple incompatible flags will result in an error, emphasizing the need for specificity in how you wish to execute the script. Understanding the nuances of flag compatibility and the strict requirement for a single run flag is crucial for effectively leveraging the full potential of Logicytics.py.

    +
    + +
    +

    File Structure

    +

    The Logicytics project is organized into several directories, each serving a distinct purpose:

    + 
    +/Logicytics
+├─── /.github [You may ignore this]
+│    ├─── /ISSUE_TEMPLATE
+│    └─── /workflows
+├─── /.idea [You may ignore this]
+│    └─── inspectionProfiles
+├─── /ACCESS [Generated files output]
+│    ├─── /BACKUP
+│    ├─── /DATA
+│    │    ├─── /Hashes
+│    │    └─── /Zip
+│    └─── /LOGS
+│         └─── /DEBUG
+├─── /CODE
+│    ├─── /SysInternal_Suite
+│    │    └─── # SYS INTERNAL EXE #
+│    ├─── # THE CODE #
+│    └─── /__pycache__ [You may ignore this]
+├─── /EXTRA
+│    └─── # ZIPPED EXTRA FEATURES #
+├─── /IMG [You may ignore this]
+└─── /MODS [You add your own mods]
+
    + +

    Access Directory

    +

    The ACCESS directory is crucial for monitoring the progress and results of Logicytics operations. The LOGS subdirectory contains the most recent debugger logs, which can be invaluable for diagnosing issues or understanding the behaviour of the script. The DATA subdirectory holds all compressed files produced by Logicytics as well as hashes. Finally, the BACKUP subdirectory contains the necessary backups, providing a centralized location for managing these resources.

    + +

    By thoroughly understanding and utilizing these sections and flags, users can maximize the efficiency and effectiveness of Logicytics.py, tailoring its capabilities to meet their specific needs and workflows.

    +
    + + Back to Home +
    +
    + + diff --git a/Logicytics/wiki4.html b/Logicytics/wiki4.html new file mode 100644 index 0000000..6bf0310 --- /dev/null +++ b/Logicytics/wiki4.html @@ -0,0 +1,50 @@ + + + + + + + Debugging & Diagnostics - Logicytics + + + + + + +
    + + + + +
    +

    Debugging & Diagnostics

    +

    Logicytics provides powerful debugging and diagnostic tools to help developers identify and resolve issues efficiently. Understanding and utilizing these features will greatly enhance your development workflow and ensure your application runs smoothly.

    + +
    +

    Methods

    + +

    1. Live Feedback

    +

    During the execution of a program, live feedback provides immediate insights into the application's behaviour. This feature is crucial for identifying issues early in the development process. It might include outputting logs to the console or real-time analysis of performance metrics. Live feedback helps developers quickly understand the flow of their program and spot any irregularities as they occur.

    + +

    2. Debug Mode

    +

    Debug mode enhances the live feedback mechanism by providing more detailed information during runtime. This involves inspecting variable values at specific points and offering extra insights into the main program to aid developers in understanding how their code is executing. To activate debug mode, set debug to true in the config.json file. This mode is particularly useful when troubleshooting complex issues or when additional context is needed during the program's operation.

    + +

    3. Debugger

    +

    The debugger component is a powerful tool for analyzing the state of a program at various points in time. It checks for file integrity, updates, and file structure, ensuring that the codebase is consistent and up-to-date. Additionally, the debugger can analyse the operating system and other external factors that might affect the application's behaviour. Debuggers are essential for diagnosing subtle bugs that are difficult to reproduce consistently. You can run the debugger by using the --debug flag.

    +
    + + Back to Home +
    +
    + +