hacking: security in practice
Hacking a collge portal

My semester is fucked up and I need to know if it is even possible to hack a college portal like https://lms.uet.edu.pk/web/login or portal accounts of some teachers? Seen lots of people on reddit claim to do it but they seem scammy. What would be the best way to go about this by hiring a hacker?

submitted by /u/Sad_Narutard
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
anyway to get an ip address on recroom

little shits keep saying the n word

submitted by /u/Its_squidward
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
anyway to get someone’s exact location lol

please don’t down vote just curiou i know there are no actual ways but eh

submitted by /u/Its_squidward
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
TryHackMe — Ignite Çözümü

https://cdn-images-1.medium.com/max/1214/1*aqTvuG0OQyFAdJrlkn9XKQ.png
Bu yazımda TryHackMe’nin Ignite adlı odasını nasıl çözdüğümü yazacağım. İngilizce kaynak çok fakat Türkçe kaynağın yetersiz olduğunu…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Testing for authentication in WebApplication

https://cdn-images-1.medium.com/max/1600/0*yeoDL8lnE7pc6Lgj
Introduction

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Never Give Up — Story of Hacking Dutch Government and Earning that Swag.
https://medium.com/@bababounty99/never-give-up-story-of-hacking-dutch-government-and-earning-that-swag-b518cca81c78?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

Hmm!! Dutch Swag!! Who Wants it ?Almost everybody wants it. It was one of my goals to earn Dutch Swag. I started this journey almost 6 to…Continue reading on Medium » (https://medium.com/@bababounty99/never-give-up-story-of-hacking-dutch-government-and-earning-that-swag-b518cca81c78?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

Dockerized-Android - A Container-Based Framework To Enable The Integration Of Mobile Components In Security Training Platforms
http://www.kitploit.com/2021/10/dockerized-android-container-based.html

___________________________
@hacking_Attack
@Hacking_Video

Dockerized Android is a container-based framework that allows to execute and Android Emulator inside Docker and control it through a browser. This project has been developed in order to provide a starting point for integrating mobile security components into Cyber Ranges but it can be used for any purpose. Anyway, for development and testing purposes the project suggested is docker-android (https://github.com/budtmo/docker-android).

___________________________
@hacking_Attack
@Hacking_Video

Intro
As stated in the brief description above this project has been created in order to provide a starting point for the introduction of mobile security components into Cyber Ranges. For this reasons the features already developed and the ones that will be added in the feature will help the user to make easier to setup a realistic simulation (https://www.kitploit.com/search/label/Simulation) (for example for security training). This README is quite long, maybe you just wanna skip to the "How to run" part.Features (https://github.com/cybersecsi/dockerized-android#features)Architecture (https://github.com/cybersecsi/dockerized-android#architecture)List of Docker Images (https://github.com/cybersecsi/dockerized-android#docker-images)How to run (https://github.com/cybersecsi/dockerized-android#how-to-run)Configuration (https://github.com/cybersecsi/dockerized-android#configuration)
Features
The following features are currently available:Run an Android Emulator in DockerControl the device through the web browserInstall applicationsEnable port forwardingReboot the deviceEmulate SMSUse the terminal from the web browserAttach also a physical deviceCustomize startup behaviour (see Configuration section)Easily manage multiple instancesInitial setupInstance Manager SetupManual Setupinitial-setup (https://github.com/cybersecsi/dockerized-android/blob/main/docs/initial-setup.png)instance-manager-setup (https://github.com/cybersecsi/dockerized-android/blob/main/docs/instance-manager-setup.png)manual-setup (https://github.com/cybersecsi/dockerized-android/blob/main/docs/manual-setup.png)Toolbox featuresInstance Switchtoolbox (https://github.com/cybersecsi/dockerized-android/blob/main/docs/toolbox.png)instance-switch (https://github.com/cybersecsi/dockerized-android/blob/main/docs/instance-switch.png)
Architecture
The project is composed by three main pieces:Dockerized Android CoreDockerized Android UIDockerized Android Instance Manager (optional) The following figure provides an overview of the actual architecture of the two mandatory components

___________________________
@hacking_Attack
@Hacking_Video

Core Component
The Core component is the one that executes all the processes needed to run an Android Com-ponent (Emulated or Real) inside a Docker container, also ex-posing some features to the outside. It is with no doubt the most complex part becauseit has to manage different processes in order to provide a set of features. The above figure shows a clear distinction between long-lived processes,start processes and util scripts. Besides, this figure shows that there are 6 long-lived processes, this is a little inaccuracy added to provide a general overview of the Core component, in reality there are two different flavours of the Core component:Core for EmulatorCore for Real Device The main architectural difference is the one regarding the long-lived processess: the Core for Emulator runs the long-lived emulator process while the Core for Real Device runs the long-lived scrcpy process to display and control the physical device. The other parts are quite similar with just some logic to follow a different behaviour based on the type of the Core component.
UI Component
The UI component provides a simple way to use all the features exposed by the backend and also adds the ability to display and control the device. The user has to manually insert the address of the Core component and the corresponding ports (the port exposed by the backend and the port exposed by websockify); through this manual setup it is possible to change the default ports (which are 4242 for the backend and 6080 for websockify).
Instance Manager Component
The Instance Manager component has the job to provide all the informations(i.e., addresses and ports) about the running Cores through a single REST API. This is done by writing a simple JSON configuration file that contains all the information about the Cores that are present into the docker-compose in order to avoid the painful job of manually adding one by one. The structure of the JSON configuration file is the following:{
"instances": [
{
"name": [Generic string to identify the device],
"address": [Address of the component],
"core_port": [Port of the backend],
"vnc_port": [Port of VNC]
}
]
}

List of Docker images
Android VersionAPIImage5.0.121secsi/dockerized-android-core-emulator-5.0.15.1.122secsi/dockerized-android-core-emulator-5.1.16.023secsi/dockerized-android-core-emulator-6.07.024secsi/dockerized-android-core-emulator-7.07.1.125secsi/dockerized-android-core-emulator-7.1.18.026secsi/dockerized-android-core-emulator-8.08.127secsi/dockerized-android-core-emulator-8.19.028secsi/dockerized-android-core-emulator-9.010.029secsi/dockerized-android-core-emulator-10.011.030secsi/dockerized-android-core-emulator-11.0--secsi/dockerized-android-core-bare--secsi/docker-android-core-real-deviceThe secsi/dockerized-android-core-bare does not download any system image and you may mount the folder on your host machine where you have all the SDK folders
How to run
In order to see a full example on how to run the platform you may watch the docker-compose available in the root directory. This setup contains two different cores and also the optional Instance Manager component. Once you understood how it works you may change it to satisfy any needs you have.
Prerequisites
Docker and Docker Compose have to be installed on your machine.
OS compatibility
This platform behaves in different ways based on the host OS, here is a table that summarizes the current compatibility:LinuxWindowsOS XCore for EmulatorFull compatibilityNot supported (yet)Not supportedCore for Real DeviceFull compatibilityFull compatibilityWorkaroundFor Windows and OS X you have to use a Linux VM with nested virtualization.To check if your Linux machine supports nested virtualization (https://www.kitploit.com/search/label/Virtualization) you may run the following commands:sudo apt install cpu-checker
kvm-ok

OS X Workaround for Real Device

___________________________
@hacking_Attack
@Hacking_Video

To use the Core for Real Device on OS X you may:Use the adb of the hostUse wireless connectionFor the wireless connection Google provides a simple tutorial (https://developer.android.com/things/hardware/wifi-adb). To connect to the host adb from within the container (https://www.kitploit.com/search/label/Container) you have to manually enter inside the container and run:adb -H host.docker.internal devices

One line command to run
The command to start using the framework with two cores and a instance manager is simply:docker-compose up

Build
You may also build the images yourself throught the scripts placed in the utils folder
Configuration
You may configure some features to customize the setup through ENV variables, the following table provides a list of all of them:ComponentENV NameDefault valueDescriptionCoreTARGET_PORT6080Websockify portCoreCUSTOM_APP_DEFAULT_PORT4242Node.js backend portCoreDEVICEINFOUnset, but behaves like trueEnables/Disables the device info featureCoreTERMINALUnset, but behaves like trueEnables/Disables the terminal featureCoreAPKUnset, but behaves like trueEnables/Disables the install APK featureCoreFORWARDUnset, but behaves like trueEnables/Disables the port forward (https://www.kitploit.com/search/label/Port%20Forward) featureCoreSMSUnset, but behaves like trueEnables/Disables the SMS emulation (https://www.kitploit.com/search/label/Emulation) featureCoreREBOOTUnset, but behaves like trueEnables/Disables the reboot featureCoreINSTALL_ON_STARTUPfalseEnables/Disables the feature that allows to install all the apks placed in the/root/dockerized-android/apk foldeCoreENABLE_UNKNOWN_SOURCESfalseEnables the install from unknown sourcesCoreREAL_DEVICE_SERIALunsetIf there is more than one physical device connected this value must be set to the serial of the device that has to be controlled otherwise all the other features won't workInstance ManagerDEFAULT_PORT7373Port of the REST APIThe REAL_DEVICE_SERIAL variable is fundamental if there is more than one physical device attached because if missing nothing will work. Finally there is a list of exposed ports by each component:ComponentPort #DescriptionCore5555ADB portCore4242Node.js BackendCore6080Websockify (for noVNC)UI80FrontendInstance Manager7373REST API

Download Dockerized-Android (https://github.com/cybersecsi/dockerized-android)

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
Dockerized-Android - A Container-Based Framework To Enable The Integration Of Mobile Components In Security Training Platforms

https://blogger.googleusercontent.com/img/a/AVvXsEgeowcsKCMVPyaZsQn6SZi8MrrM0NPE5maOqZg-v-ReB_yU73Rp3LSxUzVErwsG_SjLxhojczDmDxEXDEc-LcHxL-RR12ywWelQ6hCiCc_b_zMTMPM0MY2JFOU9nt77E4gy5CtIZoE9GAcTYe3Uo95IBm4SS7XIiC3lIgKhprgD8EvhSavlibOwHg06hw=w640-h122 Dockerized Android is a container-based framework that allows to execute and Android Emulator inside Docker and control it through a browser. This project has been developed in order to provide a starting point for integrating mobile security components into Cyber Ranges but it can be used for any purpose. Anyway, for development and testing purposes the project suggested is docker-android. https://blogger.googleusercontent.com/img/a/AVvXsEi_OshfZ-QPpxW-PaiLDbveR1bzEadu8WkAK64ajR_WgWHk7SZgnFp_v5CtJiQKkdGGQcxTTDyqQjEJlm2SjByhHqHqBISHHYGtOOZ5TL8iyNM_Mpo9tMernMioVEoM24zJ8jtInnfj8HyxOPxflzx5Kx_6wSZGbEH7DVKBTQgwnvOKBPQ7nMpIwz0X9A=w640-h466 IntroAs stated in the brief description above this project has been created in order to provide a starting point for the introduction of mobile security components into Cyber Ranges. For this reasons the features already developed and the ones that will be added in the feature will help the user to make easier to setup a realistic simulation (for example for security training). This README is quite long, maybe you just wanna skip to the "How to run" part.

1. Features
2. Architecture
3. List of Docker Images
4. How to run
5. Configuration Features The following features are currently available:

* Run an Android Emulator in Docker
* Control the device through the web browser
* Install applications
* Enable port forwarding
* Reboot the device
* Emulate SMS
* Use the terminal from the web browser
* Attach also a physical device
* Customize startup behaviour (see Configuration section)
* Easily manage multiple instances
Initial setupInstance Manager SetupManual Setupinitial-setupinstance-manager-setupmanual-setupToolbox featuresInstance Switchtoolboxinstance-switch Architecture The project is composed by three main pieces:

* Dockerized Android Core
* Dockerized Android UI
* Dockerized Android Instance Manager (optional) The following figure provides an overview of the actual architecture of the two mandatory components https://blogger.googleusercontent.com/img/a/AVvXsEiKmU4xQqns6ZzTW22iW2tAbHscB7Tp7_Enav6FF3X54XlACdOG4ES4FOT9WvbbpYEHEWSaI_JzwrCAU_rVhXhWG8JKhdcGIYeEvept3Ms33t33m_spDbPymMTyxWoI_NaOK50g4QGF-ppuuVu6VblNccIXGGEFE1_EbmkhDiabShMB8QXt7muw-ibIHg=w438-h640 Core ComponentThe Core component is the one that executes all the processes needed to run an Android Com-ponent (Emulated or Real) inside a Docker container, also ex-posing some features to the outside. It is with no doubt the most complex part becauseit has to manage different processes in order to provide a set of features. The above figure shows a clear distinction between long-lived processes,start processes and util scripts. Besides, this figure shows that there are 6 long-lived processes, this is a little inaccuracy added to provide a general overview of the Core component, in reality there are two different flavours of the Core component:

* Core for Emulator
* Core for Real Device The main architectural difference is the one regarding the long-lived processess: the Core for Emulator runs the long-lived emulator process while the Core for Real Device runs the long-lived scrcpy process to display and control the physical device. The other parts are quite similar with just some logic to follow a different behaviour based on the type of the Core component. UI ComponentThe UI component provides a simple way to use all the features exposed by the backend and also adds the ability[...]

___________________________
@hacking_Attack
@Hacking_Video

to display and control the device. The user has to manually insert the address of the Core component and the corresponding ports (the port exposed by the backend and the port exposed by websockify); through this manual setup it is possible to change the default ports (which are 4242 for the backend and 6080 for websockify). Instance Manager ComponentThe Instance Manager component has the job to provide all the informations(i.e., addresses and ports) about the running Cores through a single REST API. This is done by writing a simple JSON configuration file that contains all the information about the Cores that are present into the docker-compose in order to avoid the painful job of manually adding one by one. The structure of the JSON configuration file is the following: {
"instances": [
{
"name": [Generic string to identify the device],
"address": [Address of the component],
"core_port": [Port of the backend],
"vnc_port": [Port of VNC]
}
]
} List of Docker images Android VersionAPIImage5.0.121secsi/dockerized-android-core-emulator-5.0.15.1.122secsi/dockerized-android-core-emulator-5.1.16.023secsi/dockerized-android-core-emulator-6.07.024secsi/dockerized-android-core-emulator-7.07.1.125secsi/dockerized-android-core-emulator-7.1.18.026secsi/dockerized-android-core-emulator-8.08.127secsi/dockerized-android-core-emulator-8.19.028secsi/dockerized-android-core-emulator-9.010.029secsi/dockerized-android-core-emulator-10.011.030secsi/dockerized-android-core-emulator-11.0--secsi/dockerized-android-core-bare--secsi/docker-android-core-real-device
The secsi/dockerized-android-core-bare does not download any system image and you may mount the folder on your host machine where you have all the SDK folders How to run In order to see a full example on how to run the platform you may watch the docker-compose available in the root directory. This setup contains two different cores and also the optional Instance Manager component. Once you understood how it works you may change it to satisfy any needs you have. PrerequisitesDocker and Docker Compose have to be installed on your machine. OS compatibilityThis platform behaves in different ways based on the host OS, here is a table that summarizes the current compatibility:
LinuxWindowsOS XCore for EmulatorFull compatibilityNot supported (yet)Not supportedCore for Real DeviceFull compatibilityFull compatibilityWorkaround
For Windows and OS X you have to use a Linux VM with nested virtualization.

To check if your Linux machine supports nested virtualization you may run the following commands: sudo apt install cpu-checker
kvm-ok OS X Workaround for Real DeviceTo use the Core for Real Device on OS X you may:

* Use the adb of the host
* Use wireless connection

For the wireless connection Google provides a simple tutorial. To connect to the host adb from within the container you have to manually enter inside the container and run: adb -H host.docker.internal devices One line command to runThe command to start using the framework with two cores and a instance manager is simply: docker-compose up BuildYou may also build the images yourself throught the scripts placed in the utils folder Configuration You may configure some features to customize the setup through ENV variables, the following table provides a list of all of them:
ComponentENV NameDefault valueDescriptionCoreTARGET_PORT6080Websockify portCoreCUSTOM_APP_DEFAULT_PORT4242Node.js backend portCoreDEVICEINFOUnset, but behaves like trueEnables/Disables the device info featureCoreTERMINALUnset, but behaves like trueEnables/Disables the terminal featureCoreAPKUnset, but behaves like trueEnables/Disables the install APK featureCoreFORWARDUnset, but behaves like trueEnables/Disables the port forward featureCoreSMSUnset, but behaves like trueEnables/Disables the SMS emulation featureCoreREBOOTUnset, but b[...]

___________________________
@hacking_Attack
@Hacking_Video