DeRar is a simple Java program to brute force the keyword of a RAR file.

If there’s any problem regarding the program, please post an issue on the program’s GitHub page.
If you have ideas to improve the code, make sure to post a pull request.

The DeRar project and its modifications are not affiliated with or endorsed by WinRar or RarLab. The program is an independent work and is not officially supported or endorsed by WinRar or RarLab. Use of the program is at your own risk, and the creators of the program cannot be held responsible for any damages or losses that may result from its use.
Also ask the owner of the .rar archive permission before using this tool.

• The user can select several charsets to generate the combinations with, such as lower case, upper case, accented letters, special characters or digits.
• The user can specify the number of threads to run.
• The progress of each thread gets displayed in a window thanks to a progress bar.

• Optimize the code.
• Improve the GUI.
• Translate code, comments and prompts in english.
• Make the user choose between a dictionary or a brute force attack.
• Add more charsets for the user to choose from.

1. Create¹ a folder and put derar.java and utils.java inside it.
2. Place the .rar archive in the same folder.
3. Open the Windows command prompt ² and type the following commands:

• javac -encoding UTF-8 derar.java -> to compile the program
• java derar -> to run the program

The program generates every combination of words up to the user preferred length, then it tries every single one by running a cmd command.

The program asks the user to input the length of the word that will get generated with the combination algorithm. This means that the program will combine the selected characters and create words that go from the length of 1 character to the inputted length.

The user will then be asked to write the name of the file (not including the .rar extension, it is automatically concatenated to the filename string).

The last thing that will be asked to input is the number of threads the user wants to run.

The program will print a recap of the informations and the various user inputs and will prompt several requests for the press of the ENTER key, so the user can check the informations with calm.

After the recap, the open windows will get minimized to show only the desktop where a JFrame for every thread will show the progress in the checking of the combinations.

IMPORTANT: Some threads may work faster than others due to several factors such as how the processor handles them.

If the windows showing the progress of the keyword check close without the progress bars reaching 100% it means the archive got extracted in the folder it got placed in the beginning.

GitHub

Pre-compiled aria2 and AriaNg-Native with QoL modifications for Windows and Linux.

If this project helps you, a star would be greatly appreciated – it lets me know my work is useful 🙂

Make sure you understand the changes (section below) before using any release from this repo.

Please file an issue if you encounter any stability issues, particularly regarding memory leaks. Feedbacks are also much appreciated.

For updates, you can ‘Star’ this repo to see updates in your GitHub feeds, or ‘Watch’ this repo and subscribe to releases to get notified (uncheck others to avoid unwanted pings).

These softwares are mostly stable and complete, and you don’t have to update if it doesn’t deliver a feature you need.

See Releases for all previous binaries. Check out Actions for workflows to produce these binaries.

1. 0001 Configuration max-connection-per-server
   • Patch: Upper limit is removed.
   • Original behaviour: Upper limit is 16.
2. 0002 Configuration min-split-size
   • Patch: Default value is set to 4M (lower limit = 1K).
   • Original behaviour: Default value is 20M (lower limit = 1M).
3. 0003 Download at best effort
   • Patch: When ‘speed drops below lowest-speed-limit‘ or encounter ‘connection closed’, default behaviour is set to restart.
   • Original behaviour: Default behaviour is abrot.
4. 0004 Add option to retry on HTTP 4xx.
   • Patch: New options to automatically retry if http-4xx error is encountered.
     • --retry-on-400[=true|false]
     • --retry-on-403[=true|false]
     • --retry-on-406[=true|false]
     • --retry-on-unknown[=true|false]
5. 0005 New option --http-want-digest to NOT send Want-Digest HTTP header. Deprecated: aria2 has --no-want-digest-header as of 1.37.0.
6. 0006 Download to current path
   • Patch: Default output path is set to the current working path.
   • Original behaviour: Default path is $HOME (i.e. user home dir).
7. 0007 Add support for raw deflate stream.

1. 0001 Configuration max-connection-per-server
   • Patch: Value validation (upper limit) on the GUI is removed.
   • Original behaviour: Upper limit is 16.
2. 0002 Configuration min-split-size
   • Patch: Default value is set to 4M.
   • Original behaviour: Default value is 20M.
3. 0003 Configuration split
   • Patch: Default value is set to 16.
   • Original behaviour: Default value is 5.

ESP8266-based switch for openHAB.

The motivation is to build a small physical Wi-Fi enabled switch that controls lights via openHAB. It should require only a power cable and send the commands via Wi-Fi and MQTT to the openHAB server which then controls the lights.

Besides the openHAB server and some lights (this guide uses Philips Hue lights but others work as well), the following components are used:

• Adafruit Feather HUZZAH with ESP8266
• Adafruit FeatherWing OLED – 128×32 OLED Add-on

The OLED display is used to show network information and confirmation of the commands. The switch setup would probably also work with other ESP8266 boards but Adafruit’s Feather board is nice and easy to use. The buttons on the OLED board are used as the switch buttons but it’s also possible to use externally connected buttons/switches.

Flash the Arduino sketch esp8266-openhab-switch.ino to the board. Don’t forget to adjust the Wi-Fi and MQTT settings at the beginning of the sketch. The sketch requires that the ESP8266 drivers are installed and the Adafruit libraries for the Feather board and the OLED board are loaded in the Arduino IDE.

Detailed instructions on how to use Adafruit’s ESP8266 Feather board with the Arduino IDE can be found here: https://learn.adafruit.com/adafruit-feather-huzzah-esp8266/using-arduino-ide

On the openHAB2 server, first install the MQTT server and the openHAB MQTT binding. When using openHAB2 on a Raspberry Pi with Raspbian, the MQTT server can be installed with the following commands:

wget http://repo.mosquitto.org/debian/mosquitto-repo.gpg.key
sudo apt-key add mosquitto-repo.gpg.key
cd /etc/apt/sources.list.d/
sudo wget http://repo.mosquitto.org/debian/mosquitto-wheezy.list
sudo apt-get install mosquitto

After that the MQTT binding can be installed via the Paper UI. There’s also a good beginner’s guide on MakeUsOf that explains how to setup and test the MQTT server and binding. After installation, the MQTT binding has to be configured as shown in services/mqtt.cfg.

In addition to the Hue light kitchen_ceiling_light_dimmer, two items are defined in the item file items/all.items: A dimmer that represents the ESP8266 board and a string to send a message to the ESP8266 OLED display, both connected to MQTT.

The rule file rules/esp8266_switch.rules defines the dimmer behavior. The ESP8266 board sends values 100, 50, and 0 with the buttons A, B, and C via MQTT. The rule Kitchen Switch sets the Hue light state to the value that the board sent. The rule Kitchen Switch Display sends a string with the Hue light state to the board so it can be displayed. What’s cool here is that this string gets sent whenever the light state is changed, even through another UI (e.g. the Android app).

Reseved Slots is a CS2 plugin that is used to reserve slots for VIP players or Admins.
Designed for CounterStrikeSharp framework

1. Download the lastest release https://github.com/NockyCZ/CS2-ReservedSlots/releases/latest
   • ReservedSlots.zip file is a version that does not support Discord Utilities
   • ReservedSlots_DU_Support.zip file is a version that supports Discord Utilities (You can combine flags and discord roles)
2. Unzip into your servers csgo/addons/counterstrikesharp/plugins/ dir
3. Restart the server

• CS2 Discord Utilities (Only if you want to use a version thats supports Discord Utilities)

configs/plugins/ReservedSlots/ReservedSlots.json

Geekx is a Free and Open Source Four Column portfolio template for Bootstrap with responsive and high quality UI created by Orbit Themes.

View Demo | Download ZIP

View Live Preview

• Responsive Design.
• Developed With Bootstrap 4.
• SEO Semantic Code.
• Simple and Easy To Use.
• HTML5 ready. Use the new elements with confidence.
• Designed with progressive enhancement in mind.

To begin using this template, choose one of the following options to get started:

• Download the latest release on Orbit Themes
• Install via npm: npm i geekx
• Clone the repository: git clone https://github.com/orbitthemes/geekx.git

    # clone the repository
    $ git clone https://github.com/orbitthemes/geekx.git

    # go into the directory
    $ cd geekx

    # install all dependencies
    $ npm install

    #For Development Options
    $ gulp dev

• Fork, Clone, or Download on GitHub

After downloading, simply edit the HTML and CSS files included with the template in your favorite text editor to make changes. These are the only files you need to worry about, you can ignore everything else! To preview the changes you make to the code, you can open the index.html file in your web browser.

After installation, run npm install and then run gulp dev which will open up a preview of the template in your default browser, watch for changes to core template files, and live reload the browser when changes are saved. You can view the gulpfile.js to see which tasks are included with the dev environment.

• gulp the default task that builds everything.
• gulp dev browserSync opens the project in your default browser and live reloads when changes are made.
• gulp css:compile compiles the SCSS into CSS file.
• gulp css:minify minifies the compiled CSS file.
• gulp css compiles SCSS files into CSS and minify the css.
• gulp js Combines all js scripts to one file named main.js, Minify the file, and save it as main.min.js.
• gulp export copies dependencies from node_modules to the dist directory.
• gulp clean Removes all the directories inside dist, minified js files and all compiled css files.

Have a bug or an issue with this template? Open a new issue on GitHub or leave a comment on the template overview page at Orbit Themes.

You can hire Orbit Themes to create a custom build of any template, or create something from scratch using Bootstrap. For more information, visit the Contact Page.

• Album Plus – Album Plus is a Simple Photography and Magazine template for Bootstrap 4.
• Blog – Blog Is The Beautiful Blogger Template For Bootstrap 4.
• My Shop – My Shop is a Simple E-Commerce template for Bootstrap 4.
• Carousel Plus – Clean and Responsive Bootstrap 4 slideshow Template.
• Checkout Plus – Simple, Clean and Stylish Bootstrap 4 Checkout Page Template.
• Cover Plus – Cover Plus Is The Beautiful One Page Template for Bootstrap 4.
• Dashboard – Free and Responsive admin dashboard template for bootstrap 4.
• Healthy – Clean Responsive Fitness Landing Page For Bootstrap 4.
• Kreative – Kreative Business Landing Page Template.
• Pricing Plus – Clean and Responsive Pricing Page Template With High Quality UI.

To contribute, please ensure that you have stable Node.js and npm installed. Test if Gulp CLI is installed by running gulp --version. If the command isn’t found, run npm install -g gulp. For more information about installing Gulp, see the Gulp’s Getting Started!.

To have all gulp dependencies run npm install

If gulp is installed, follow the steps below.

• Fork and clone the repository.
• Run gulp dev, this will open Template on your default browser.
• Now you can code, code and code!
• Submit a pull request.

Orbit Themes is an open source library of free Bootstrap templates and themes. All of the free templates and themes on Orbit Themes are released under the MIT license, which means you can use them for any purpose, even for commercial projects.

• Web: https://orbitthemes.com
• Twitter: https://twitter.com/orbitthemes
• Facebook: https://www.facebook.com/orbitthemes/
• Google Plus: https://plus.google.com/+orbitthemes
• Github: https://github.com/orbitthemes
• Behance: https://www.behance.net/orbitthemes
• Dribble: https://dribbble.com/orbitthemes
• Pinterest: https://www.pinterest.com/orbitThemes/
• Reddit: https://www.reddit.com/user/orbitthemes
• Instagram: https://www.instagram.com/orbitthemes/
• LinkedIn: https://www.linkedin.com/company/orbit-themes/

Orbit Themes was created by and is maintained by Sandeep Prasad Bhatt .

• http://sandeepbhatt.com.np
• https://twitter.com/_MeSandy
• https://github.com/sandy100

Orbit Theme Templates and Themes are based on the Bootstrap framework created by Mark Otto and Jacob Thorton.

• node.js
• gulp
• jQuery
• Bootstrap
• SASS
• Pexels

Copyright 2018 Orbit Themes. Code released under the MIT.

The ICT HelpDesk Application is a web-based solution designed to facilitate the management of technical issues within an organization. It provides a platform for clients to report issues and for HelpDesk officers to manage, assign, and resolve these issues effectively.

• User Authentication: Secure login and registration for clients and HelpDesk staff.
• Role-Based Access Control: Different functionalities for clients, General HelpDesk Officers, and HelpDesk Officers.
• Issue Reporting: Clients can report technical issues they encounter.
• Issue Assignment: General HelpDesk Officers can assign reported issues to specific HelpDesk Officers.
• Issue Management: HelpDesk Officers can view, manage, and resolve assigned issues.
• Notifications: Alerts for issue assignments and updates.

• Backend: Laravel
• Frontend: Blade, Tailwind CSS
• Authentication: Laravel Breeze

Ensure you have the following installed:

• PHP >= 8.1
• Composer
• Node.js and npm
• MySQL or other compatible database

1. Clone the Repository:

   git clone https://github.com/yourusername/ict-helpdesk.git
   cd ict-helpdesk

2. Install Dependencies:

   composer install
   npm install

3. Copy .env.example to .env:

   cp .env.example .env

4. Generate Application Key:

   php artisan key:generate

5. Configure Database:

   Update .env with your database credentials:

   DB_CONNECTION=mysql
   DB_HOST=127.0.0.1
   DB_PORT=3306
   DB_DATABASE=ict_helpdesk
   DB_USERNAME=root
   DB_PASSWORD=yourpassword
   

6. Run Migrations:

   php artisan migrate

   Seed the database

   php artisan migrate:fresh --seed

7. Install Tailwind CSS:

   npm run dev

8. Start the Development Server:

   php artisan serve

9. Access the Application:

   Open your browser and navigate to http://localhost:8000.

1. Register Users:

   • Client: Sign up through the registration form.
   • General HelpDesk Officer & HelpDesk Officers: Create their accounts via the registration form and update their roles in the database.

2. Reporting Issues:

   • Clients can log in and submit a new issue via the “Report Issue” form.

3. Assigning Issues:

   • General HelpDesk Officers can log in and assign pending issues to HelpDesk Officers.

4. Managing Issues:

   • HelpDesk Officers can view their assigned issues, update their status, and mark them as resolved.

• app/Models: Models such as User, Issue, and Assignment.
• app/Http/Controllers: Controllers like IssueController, AssignmentController.
• resources/views: Blade templates for the UI.
• database/migrations: Migration files for database schema.
• routes/web.php: Web routes for the application.

To deploy the application, follow standard Laravel deployment practices:

1. Server Setup: Configure a web server (e.g., Apache, Nginx) and set up the environment.
2. Database Migration: Run migrations on the production database.
3. Optimize: Run optimization commands:

   php artisan config:cache
   php artisan route:cache
   php artisan view:cache

4. Build Assets:

   npm run production

Contributions are welcome! Please fork the repository and submit a pull request.

1. Fork the repository
2. Create a new branch (git checkout -b feature-branch)
3. Commit your changes (git commit -am 'Add new feature')
4. Push to the branch (git push origin feature-branch)
5. Create a new Pull Request

This project is licensed under the MIT License. See the LICENSE file for more details.

• Laravel
• Tailwind CSS
• Laravel Breeze

For any inquiries or issues, please contact tituskiptanuitum@gmail.com.

A blueprint for getting a React web app with a C# API and a SQL database running on Azure. The blueprint includes sample application code (a ToDo web app) which can be removed and replaced with your own application code. Add your own source code and leverage the Infrastructure as Code assets (written in Bicep) to get up and running quickly.

Let’s jump in and get this up and running in Azure. When you are finished, you will have a fully functional web app deployed to the cloud. In later steps, you’ll see how to setup a pipeline and monitor the application.

^{Screenshot of the deployed ToDo app}

This template will create infrastructure and deploy code to Azure. If you don’t have an Azure Subscription, you can sign up for a free account here. Make sure you have contributor role to the Azure subscription.

The following prerequisites are required to use this application. Please ensure that you have them all installed locally.

• Azure Developer CLI
• .NET SDK 8.0 – for the API backend
• Node.js with npm (18.17.1+) – for the Web frontend

To learn how to get started with any template, follow the steps in this quickstart with this template (Azure-Samples/todo-csharp-sql).

This quickstart will show you how to authenticate on Azure, initialize using a template, provision infrastructure and deploy code on Azure via the following commands:

# Log in to azd. Only required once per-install.
azd auth login

# First-time project setup. Initialize a project in the current directory, using this template.
azd init --template Azure-Samples/todo-csharp-sql

# Provision and deploy to Azure
azd up

This application utilizes the following Azure resources:

• Azure App Services to host the Web frontend and API backend
• Azure SQL Database for storage
• Azure Monitor for monitoring and logging
• Azure Key Vault for securing secrets

Here’s a high level architecture diagram that illustrates these components. Notice that these are all contained within a single resource group, that will be created for you when you create the resources.

This template provisions resources to an Azure subscription that you will select upon provisioning them. Refer to the Pricing calculator for Microsoft Azure to estimate the cost you might incur when this template is running on Azure and, if needed, update the included Azure resource definitions found in infra/main.bicep to suit your needs.

This template is structured to follow the Azure Developer CLI. You can learn more about azd architecture in the official documentation.

At this point, you have a complete application deployed on Azure. But there is much more that the Azure Developer CLI can do. These next steps will introduce you to additional commands that will make creating applications on Azure much easier. Using the Azure Developer CLI, you can setup your pipelines, monitor your application, test and debug locally.

Note: Needs to manually install setup-azd extension for Azure DevOps (azdo).

• azd pipeline config – to configure a CI/CD pipeline (using GitHub Actions or Azure DevOps) to deploy your application whenever code is pushed to the main branch.

• azd monitor – to monitor the application and quickly navigate to the various Application Insights dashboards (e.g. overview, live metrics, logs)

• Run and Debug Locally – using Visual Studio Code and the Azure Developer CLI extension

• azd down – to delete all the Azure resources created with this template

• Enable optional features, like APIM – for enhanced backend API protection and observability

The Azure Developer CLI includes many other commands to help with your Azure development experience. You can view these commands at the terminal by running azd help. You can also view the full list of commands on our Azure Developer CLI command page.

This template creates a managed identity for your app inside your Azure Active Directory tenant, and it is used to authenticate your app with Azure and other services that support Azure AD authentication like Key Vault via access policies. You will see principalId referenced in the infrastructure as code files, that refers to the id of the currently logged in Azure Developer CLI user, which will be granted access policies and permissions to run the application locally. To view your managed identity in the Azure Portal, follow these steps.

The template will also create a dedicated Azure SQL user for the application and store its credentials in a KeyVault (see below). The application user’s access is restricted to the ToDo database only; a separate administrator account is set up for managing the whole Azure SQL instance.

This template uses Azure Key Vault to securely store your Azure SQL Database credentials and the connection string used by the application to interact with the database. Key Vault is a cloud service for securely storing and accessing secrets (API keys, passwords, certificates, cryptographic keys) and makes it simple to give other Azure services access to them. As you continue developing your solution, you may add as many secrets to your Key Vault as you require.

If you have any feature requests, issues, or areas for improvement, please file an issue. To keep up-to-date, ask questions, or share suggestions, join our GitHub Discussions. You may also contact us via AzDevTeam@microsoft.com.

Report Bug · Request Feature

I’m already working full time, so there isn’t much time left for this project.

• Support the project on PAYPAL

• Support the project on PATREON

• About the Project
  • Disclaimer
  • Built With
  • Features
  • Roadmap
  • License
  • Contact
• Getting Started
  • Prerequisites
  • Installation
  • Deployment
  • Usage
  • Debugging Issues
  • Build

Educational purpose, command & control, web GUI based Android spyware built around Metasploit & ADB.

The tool:

• Uses Docker containers to simulate a Kali Linux environment with the metasploit framework
• Uses RPC calls to communicate with the Metasploit framework API
• Uses ADB to install the payload on the target device & implement additional functionalities (the device must be in the same LAN)

This software is for educational purposes only. Using the tool for spying real devices is strictly illegal. USE THE SOFTWARE AT YOUR OWN RISK. THE AUTHOR ASSUMES NO RESPONSIBILITY FOR YOUR USAGE.

We strongly recommend you to have coding and Docker knowledge. Do not hesitate to read the source code and understand the mechanism of the tool.

• Bootstrap
• JQuery
• Rails
• Metasploit
• ActiveAdmin
• Docker
• Android Debug Bridge

Available actions using Metasploit framework

• Dump System Info
• Dump Location
• Live Webcam Stream
• Dump Messages
• Change Audio Mode
• Dump Call Logs
• Dump Local Time
• Microphone Recording – Only working for Android < 9.0
• Unistall App
• List Installed Apps
• Send Message
• Dump Contacts
• Lock/Unlock Screen
• Run Shell Command
• Webcam Snap
• Open App
• Install App
• Device Info
• Hide/Show payload app icon

Additional actions via ADB

• Dump Whatsapp conversations from backup DB (disabled for safety reasons)
• Dump Wi-Fi Information
• Screen Snap
• Upload File
• Record Screen
• Pull File
• Start Monero crypto miner in background

• Docker
• Chocolatey

1. Install ADB via Chocolatey. From an elevated powershell prompt (Run as administrator):

choco install adb --version=1.0.39

2. Create a project directory, and download docker-compose file. You can use curl:

curl https://raw.githubusercontent.com/CanciuCostin/android-spyware/master/docker/docker-compose.yml -o docker-compose.yml

3. Download required images:

docker-compose pull

1. Start ADB server from a command prompt:

adb server

2. Optional, set your Google MAPS API Key in docker-compose file for dashboard widget
3. Start the container (inside the project directory):

docker-compose up

4. Wait for the containers to initialize, and access the application in the browser via http://localhost/admin The files directory will be created. It will contain the payloads and the actions outputs.

1. Ensure USB Debugging is enabled on your Android device tutorial HERE
2. Optional: Plug-in your Android device to the laptop via USB – Otherwise you won’t be able to use ADB functions and you will have to install the malware manually
3. Open the rails app in the browser: http://localhost/admin and login. Default credentials:

User: admin@example.com

Password: password

4. Generate APK

• Check your machine IP address on LAN. For windows you can use

ipconfig

• Go to Payloads (http://localhost/admin/apk_payloads) and Create New
• Select port 4444, input the machine IP address and give a name for the APK
• The APK payload will be generated in [project path]/files/payloads

5. Install APK

• Go to APK Installations (http://localhost/admin/apk_installations) and Create New
• Select your previously generated apk from the list and leave the target as usb
• You might have to approve a prompt on the device

6. Run Actions

• Go to Remote (http://localhost/admin/remote)
• Open the installed app on your device. You should see green light for your MSF connectivity right after. The ADB should also turn green if your device is plugged via USB
• Run actions by clicking on the app-looking icons on the device widget. The output will be displayed in the terminal widget, and the output will be stored in [project path]/files/dumps

MSF/ADB connection issues (green light not appearing in Remote page)

• Ensure you generated the apk with correct machine IP
• Ensure connection from smartphone to your machine is not blocked by local firewall. Otherwise you should allow connection on ports 2222, 3333, 4444. To check that, you can try to access http://[your machine IP]:2222 . You should be able to access the MSF container file system via http server
• Ensure Docker container – HOST connectivity is working. Host machine is accessed via gateway.docker.internal, which is set in docker-compose file. If that doesn’t work for you, you can also try to replace it with docker.host.internal
• For ADB connection, you can try to restart the local server:

adb kill-server
adb server

• For ADB connection, ensure USB debugging is enabled

Software requirements

• Docker
• NodeJS & npm
• Ruby 2.6.6

Rails Server build steps:

git clone https://github.com/CanciuCostin/android-spyware.git
cd android-spyware
gem install bundler:2.1.4
bundle
npm install yarn -g
yarn install --check-files

Ensure the following environment variables are set:

ANDROIDSPYWARE_DATABASE_HOST=localhost
ADB_HOST=localhost
RAILS_HOST=127.0.0.1

Run the server:

rails server

• Note: local postgresql database can also be used as alternative, but you will need to run the rake scripts for initialization:

rake db:create //alternatively run createdb android_spyware_[developmen|test|production]
rake db:schema:load
rake db:seed /too add mock data required for start-up

• Implement “Instructions” page
• Implement option for persistence script (connection is lost after reboot)
• Implement option for public IP handler (either ngrok or cloud solution) to be able to track device outside of LAN

Distributed under the MIT License. See LICENSE for more information.

costin.canciu@gmail.com

• Feat: 새로운 알고리즘 문제 해결
• Modify: 풀었던 알고리즘 코드 수정
• Fix: 못 풀었던 문제 해결
• Comment: 주석 추가 or 수정 or 삭제
• Refactor: 성능에 관계 없는 코드 배치나 레포 구조 등 수정
• Docs: 리드미 업데이트