Forwarded from UNDERCODE NEWS
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦Make Windows faster and more secure :
Speed up your system and network performance
Disable unnecessary Windows services
Disable Windows telemetry
Disable Office telemetry (works only with 2016)
Disable Cortana
Disable Windows 10 automatic updates
Uninstall UWP apps
Block Skype ads
Clean up your system drive
Fix common registry issues
Remove unwanted programs running at startup
Change Microsoft Edge download folder
Edit your hosts file
Add items in desktop right-click menu
Define custom commands for run dialog
Supports silent run using configuration file
πΈπ½π π π°π»π»πΈπ π°π πΈπΎπ½ & π π π½ :
π¦Make Windows faster and more secure :
Speed up your system and network performance
Disable unnecessary Windows services
Disable Windows telemetry
Disable Office telemetry (works only with 2016)
Disable Cortana
Disable Windows 10 automatic updates
Uninstall UWP apps
Block Skype ads
Clean up your system drive
Fix common registry issues
Remove unwanted programs running at startup
Change Microsoft Edge download folder
Edit your hosts file
Add items in desktop right-click menu
Define custom commands for run dialog
Supports silent run using configuration file
πΈπ½π π π°π»π»πΈπ π°π πΈπΎπ½ & π π π½ :
1) Download https://github.com/hellzerg/optimizer/releasesβ β β Uππ»βΊπ«Δπ¬πβ β β β
2) run the exe file
Forwarded from UNDERCODE NEWS
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦Mounting disk images and access to files on them on linux:
How to view information about images to mount?
How to determine the file system of an image ?
1) You can use the file command to analyze which file system is used in files that are disk images.
An example of checking the test.image file :
file /mnt/disk_d/test.image
/mnt/disk_d/test.image: ISO 9660 CD-ROM filesystem data 'ARCH_202010' (bootable)
This is an ISO image.
2) An example of analyzing the disk.ntfs image :
file /mnt/disk_d/disk.ntfs
/mnt/disk_d/disk.ntfs: DOS/MBR boot sector, code offset 0x52+2, OEM-ID "NTFS ", sectors/cluster 8, Media descriptor 0xf8, sectors/track 63, heads 255, dos < 4.0 BootSector (0x0), FAT (1Y bit by descriptor); NTFS, sectors/track 63, physical drive 0x80, sectors 15654911, $MFT start cluster 786432, $MFTMirror start cluster 2, bytes/RecordSegment 2^(-1*246), clusters/index block 1, serial number 06258074758071a05; contains bootstrap BOOTMGR
As you can see, this is an image with the NTFS file system.
3) Checking the rootfs.sfs image :
file /mnt/disk_d/rootfs.sfs
/mnt/disk_d/rootfs.sfs: Squashfs filesystem, little endian, version 4.0, zstd compressed, 625010200 bytes, 58466 inodes, blocksize: 262144 bytes, created: Sat Jun 6 08:14:32 2020
This is a Squashfs file system image.
4) Analysis of the ext3-img-kw-1.dd image :
file /mnt/disk_d/ext3-img-kw-1.dd
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦Mounting disk images and access to files on them on linux:
How to view information about images to mount?
How to determine the file system of an image ?
1) You can use the file command to analyze which file system is used in files that are disk images.
An example of checking the test.image file :
file /mnt/disk_d/test.image
/mnt/disk_d/test.image: ISO 9660 CD-ROM filesystem data 'ARCH_202010' (bootable)
This is an ISO image.
2) An example of analyzing the disk.ntfs image :
file /mnt/disk_d/disk.ntfs
/mnt/disk_d/disk.ntfs: DOS/MBR boot sector, code offset 0x52+2, OEM-ID "NTFS ", sectors/cluster 8, Media descriptor 0xf8, sectors/track 63, heads 255, dos < 4.0 BootSector (0x0), FAT (1Y bit by descriptor); NTFS, sectors/track 63, physical drive 0x80, sectors 15654911, $MFT start cluster 786432, $MFTMirror start cluster 2, bytes/RecordSegment 2^(-1*246), clusters/index block 1, serial number 06258074758071a05; contains bootstrap BOOTMGR
As you can see, this is an image with the NTFS file system.
3) Checking the rootfs.sfs image :
file /mnt/disk_d/rootfs.sfs
/mnt/disk_d/rootfs.sfs: Squashfs filesystem, little endian, version 4.0, zstd compressed, 625010200 bytes, 58466 inodes, blocksize: 262144 bytes, created: Sat Jun 6 08:14:32 2020
This is a Squashfs file system image.
4) Analysis of the ext3-img-kw-1.dd image :
file /mnt/disk_d/ext3-img-kw-1.dd
β β β Uππ»βΊπ«Δπ¬πβ β β β
Forwarded from UNDERCODE NEWS
Forwarded from UNDERCODE NEWS
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦Mac Decrypting Tools
> Cerbero ProfileR
http://cerbero-blog.com/?p=1311) - Select all -> Copy to new file
> AppEncryptor
https://github.com/AlanQuatermain/appencryptor
- Tool for decrypting
> Class-Dump
http://stevenygard.com/projects/class-dump/
- use deprotect option
> readmem
https://github.com/gdbinit/readmem
- OS X Reverser's process dumping tool
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦Mac Decrypting Tools
> Cerbero ProfileR
http://cerbero-blog.com/?p=1311) - Select all -> Copy to new file
> AppEncryptor
https://github.com/AlanQuatermain/appencryptor
- Tool for decrypting
> Class-Dump
http://stevenygard.com/projects/class-dump/
- use deprotect option
> readmem
https://github.com/gdbinit/readmem
- OS X Reverser's process dumping tool
β β β Uππ»βΊπ«Δπ¬πβ β β β
GitHub
GitHub - AlanQuatermain/appencryptor: A command-line tool to apply or remove Apple Binary Protection from an application.
A command-line tool to apply or remove Apple Binary Protection from an application. - AlanQuatermain/appencryptor
Forwarded from UNDERCODE NEWS
After corona of the town factory talked about by the top two, new business for digital weapons.
#international
#international
Forwarded from UNDERCODE NEWS
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦βΈοΈ How to install Netdata on Kubernetes using Helm :
Netdata is an open source solution for monitoring and troubleshooting systems.
It can be used to monitor your Kubernetes cluster and display information about your cluster, including node memory usage, CPU, network, and more.
The Netdata dashboard will give you a broad overview of your Kubernetes cluster, including the services and pods running on each node.
In this post, we will show you how to deploy Netdata on a Kubernetes cluster using the Helm chart.
This type of installation deploys one parent module to the master and child modules to each worker node.
Child pods collect metrics from the nodes they run on, and kube-proxy, kubelet and cgroup metrics from hosts.
πΈπ½π π π°π»π»πΈπ π°π πΈπΎπ½ & π π π½ :
Step 1 - Install Helm on Linux | macOS
Next, we'll show you the steps you need to take to install Helm on Linux | macOS.
Download the Helm package from this link : https://github.com/helm/helm/releases
Unpack the package using tar -xvzf <downloaded-package>
Move the binary to usr / local / bin / helm
We will be using an install script that automates the steps above.
curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3
chmod 700 get_helm.sh
sudo ./get_helm.sh
MacOS users can also use brew's package management tool.
$ brew install helm
After installation, confirm that everything is ok by checking the current version:
$ helm version
version.BuildInfo{Version:"v3.4.0", GitCommit:"7090a89efc8a18f3d8178bf47d2462450349a004", GitTreeState:"clean", GoVersion:"go1.14.10"}
Add the helm-charts repository then update helm
$ helm repo add stable https://charts.helm.sh/stable
$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "stable" chart repository
Update Complete. βHappy Helming!β
Step 2 - Installing Netdata Using the Helm Chart
You can install Helm Chart in two ways:
Install from Netdata's Helm repository
Clone the Netdata Git repository.
How to clone a Github repository
Make sure you have git installed on your system
Clone the git repository locally
git clone https://github.com/netdata/helmchart.git netdata-helmchart
Let's install the chart:
helm install netdata ./netdata-helmchart/charts/netdata
Now you can see the Helm deployed:
$ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
netdata default 1 2020-11-20 18:41:46.244774507 +0000 UTC deployed netdata-3.1.0 v1.26.0
To check if the parent and child pods have been successfully deployed:
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
netdata-child-fgh5c 2/2 Running 0 16h
netdata-child-qzhjp 2/2 Running 0 16h
netdata-child-ssmhp 2/2 Running 0 16h
netdata-parent-55d88fc784-x66ss 1/1 Running 0 16h
Step 3. Open Netdata-parent with NodePort
In this tutorial, we will introduce deployment using NodePort.
Netdata is configured by default to run on port 19999.
To open the port, use the command shown below:
$ kubectl expose deployment netdata-parent --type="NodePort" --port 19999
Now you can check the port on which the service was provided with the kubectl get service command:
$ kubectl get service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 21h
netdata ClusterIP 10.99.202.135 <none> 19999/TCP 17h
netdata-parent NodePort 10.97.24.181 <none> 19999:30939/TCP 16h
Any doubt feel free to ask @Undercode_Testing
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦βΈοΈ How to install Netdata on Kubernetes using Helm :
Netdata is an open source solution for monitoring and troubleshooting systems.
It can be used to monitor your Kubernetes cluster and display information about your cluster, including node memory usage, CPU, network, and more.
The Netdata dashboard will give you a broad overview of your Kubernetes cluster, including the services and pods running on each node.
In this post, we will show you how to deploy Netdata on a Kubernetes cluster using the Helm chart.
This type of installation deploys one parent module to the master and child modules to each worker node.
Child pods collect metrics from the nodes they run on, and kube-proxy, kubelet and cgroup metrics from hosts.
πΈπ½π π π°π»π»πΈπ π°π πΈπΎπ½ & π π π½ :
Step 1 - Install Helm on Linux | macOS
Next, we'll show you the steps you need to take to install Helm on Linux | macOS.
Download the Helm package from this link : https://github.com/helm/helm/releases
Unpack the package using tar -xvzf <downloaded-package>
Move the binary to usr / local / bin / helm
We will be using an install script that automates the steps above.
curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3
chmod 700 get_helm.sh
sudo ./get_helm.sh
MacOS users can also use brew's package management tool.
$ brew install helm
After installation, confirm that everything is ok by checking the current version:
$ helm version
version.BuildInfo{Version:"v3.4.0", GitCommit:"7090a89efc8a18f3d8178bf47d2462450349a004", GitTreeState:"clean", GoVersion:"go1.14.10"}
Add the helm-charts repository then update helm
$ helm repo add stable https://charts.helm.sh/stable
$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "stable" chart repository
Update Complete. βHappy Helming!β
Step 2 - Installing Netdata Using the Helm Chart
You can install Helm Chart in two ways:
Install from Netdata's Helm repository
Clone the Netdata Git repository.
How to clone a Github repository
Make sure you have git installed on your system
Clone the git repository locally
git clone https://github.com/netdata/helmchart.git netdata-helmchart
Let's install the chart:
helm install netdata ./netdata-helmchart/charts/netdata
Now you can see the Helm deployed:
$ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
netdata default 1 2020-11-20 18:41:46.244774507 +0000 UTC deployed netdata-3.1.0 v1.26.0
To check if the parent and child pods have been successfully deployed:
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
netdata-child-fgh5c 2/2 Running 0 16h
netdata-child-qzhjp 2/2 Running 0 16h
netdata-child-ssmhp 2/2 Running 0 16h
netdata-parent-55d88fc784-x66ss 1/1 Running 0 16h
Step 3. Open Netdata-parent with NodePort
In this tutorial, we will introduce deployment using NodePort.
Netdata is configured by default to run on port 19999.
To open the port, use the command shown below:
$ kubectl expose deployment netdata-parent --type="NodePort" --port 19999
Now you can check the port on which the service was provided with the kubectl get service command:
$ kubectl get service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 21h
netdata ClusterIP 10.99.202.135 <none> 19999/TCP 17h
netdata-parent NodePort 10.97.24.181 <none> 19999:30939/TCP 16h
Any doubt feel free to ask @Undercode_Testing
β β β Uππ»βΊπ«Δπ¬πβ β β β
GitHub
Releases Β· helm/helm
The Kubernetes Package Manager. Contribute to helm/helm development by creating an account on GitHub.
Forwarded from UNDERCODE NEWS
Japan Exchange Group Holds Postponed CEO Kiyota Regular Press Conference on November 30.
#international
#international
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦PAYOAD AND MALWARE TOOLS :
https://github.com/n1nj4sec/pupy
Pupy is an opensource, cross-platform (Windows, Linux, OSX, Android) remote administration and post-exploitation tool mainly written in python
https://github.com/foospidy/payloads
Git All the Payloads! A collection of web attack payloads.
https://github.com/swisskyrepo/PayloadsAllTheThings
A list of useful payloads and bypass for Web Application Security and Pentest/CTF
https://github.com/nathanlopez/Stitch
Python Remote Administration Tool (RAT)
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦PAYOAD AND MALWARE TOOLS :
https://github.com/n1nj4sec/pupy
Pupy is an opensource, cross-platform (Windows, Linux, OSX, Android) remote administration and post-exploitation tool mainly written in python
https://github.com/foospidy/payloads
Git All the Payloads! A collection of web attack payloads.
https://github.com/swisskyrepo/PayloadsAllTheThings
A list of useful payloads and bypass for Web Application Security and Pentest/CTF
https://github.com/nathanlopez/Stitch
Python Remote Administration Tool (RAT)
β β β Uππ»βΊπ«Δπ¬πβ β β β
GitHub
GitHub - n1nj4sec/pupy: Pupy is an opensource, cross-platform (Windows, Linux, OSX, Android) C2 and post-exploitation frameworkβ¦
Pupy is an opensource, cross-platform (Windows, Linux, OSX, Android) C2 and post-exploitation framework written in python and C - n1nj4sec/pupy
Forwarded from UNDERCODE NEWS
Re-promotion of unification? Microsoft is exposed to develop Win10 system that runs Android App natively, see you next year at the earliest.
#Updates
#Updates
Forwarded from UNDERCODE NEWS
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦Hashcat command structure:
In its most general form, the command to start Hashcat looks like (in it, the | symbol means "OR"):
1) hashcat
In subsequent commands, HASH, FILE-WITH-HASHEM and hccapxfile will be designated as simply "HASH" - remember that this can be either a hash string or the path to the file in which the hash is stored.
General view of the command for launching a dictionary attack:
hashcat -m 0
If the hash is placed in a file, then the command:
2) hashcat -m -a 0 /dir
General view of the command to launch a mask attack:
3) hashcat -m -a 3 'ΠΠΠ‘ΠΠ'
If the hash is placed in a file, then the command:
4) hashcat -m -a 3 /
With the -m option, you need to specify the TYPE of the hash to crack, which is indicated by a number. The hash numbers are given below when describing the hash extraction process.
π¦Examples of Hashcat masks
Dictionary attack
Iβll first start with a dictionary attack against the list of MD5 hashes:
hashcat64.exe -a 0 -m 0 example_md5_hashes.txt combined_seclists_password_list.txt -O
The result of the command cracked zero hashes. Bummer.
You may have noticed I added the -O flag to the end of the command. The -O will greatly increase the cracking speed, but will limit the password length that youβll be able to crack. This is usually fine, unless you are cracking passwords greater than 27 characters.
Dictionary attack with rules
Letβs try a rule. As mentioned earlier, hashcat ships with several rules located in the rules directory. You use the -r <rulefile.rule> option to apply a rule. For example, Iβll use the d3ad0ne.rule:
hashcat64.exe -a 0 -m 0 example_md5_hashes.txt combined_seclists_password_list.txt -r rules\d3ad0ne.rule -O
Within a few seconds hashes will start to crack. You can press the βsβ key to get an estimated time of completion, as well as see other data about the session. For me, this ran for 8 minutes and recovered 26 of the passwords.
Not bad! And that is just one rule! Cycling through the rules will recover new passwords, but Iβm just going to skip to a different attack. More on rules in a follow-on post (eventually), but you can take a look at my follow-on post about rule writing, or the hashcat wiki to get started with writing your own rules.
π¦Combinator attack
A combinator attack is an attack that combines two dictionaries. To perform this attack Iβll first create a copy of my wordlist with a few modifications. First Iβll use a script, wordlist_cleaner.py to lowercase all letters, and remove any numbers and special characters from each word. Then Iβll use another script, capitalize_letters.py, to capitalize the first letter of each word.
C:\Users\Jake\hashcat-4.2.1>python3 wordlist_cleaner.py -f combined_seclists_password_list.txt -o combined_seclists_password_list_clean.txt
[*] Reading file: combined_seclists_password_list.txt
[*] Processing 13272929 words.
[*] Changing all words to lowercase...
[*] Removing numbers and special characters...
[*] Removing duplicate words...
[*] Printing cleaned words to combined_seclists_password_list_clean.txt
C:\Users\Jake\hashcat-4.2.1>python3 capitalize_letters.py -f combined_seclists_password_list_clean.txt -o combined_seclists_password_list_caps.txt
[*] Reading file: combined_seclists_password_list_clean.txt...
[*] Processing 7243374 words...
[*] Changing all words to lowercase...
[*] Capitalizing first letter of each word...
[*] Writing to combined_seclists_password_list_caps.txtβ¦
Now Iβll try an attack:
hashcat64.exe -a 1 -m 0 example_md5_hashes.txt combined_seclists_password_list_caps.txt combined_seclists_password_list_caps.txt -k "$!" -O
β β β Uππ»βΊπ«Δπ¬πβ β β β
π¦Hashcat command structure:
In its most general form, the command to start Hashcat looks like (in it, the | symbol means "OR"):
1) hashcat
In subsequent commands, HASH, FILE-WITH-HASHEM and hccapxfile will be designated as simply "HASH" - remember that this can be either a hash string or the path to the file in which the hash is stored.
General view of the command for launching a dictionary attack:
hashcat -m 0
If the hash is placed in a file, then the command:
2) hashcat -m -a 0 /dir
General view of the command to launch a mask attack:
3) hashcat -m -a 3 'ΠΠΠ‘ΠΠ'
If the hash is placed in a file, then the command:
4) hashcat -m -a 3 /
With the -m option, you need to specify the TYPE of the hash to crack, which is indicated by a number. The hash numbers are given below when describing the hash extraction process.
π¦Examples of Hashcat masks
Dictionary attack
Iβll first start with a dictionary attack against the list of MD5 hashes:
hashcat64.exe -a 0 -m 0 example_md5_hashes.txt combined_seclists_password_list.txt -O
The result of the command cracked zero hashes. Bummer.
You may have noticed I added the -O flag to the end of the command. The -O will greatly increase the cracking speed, but will limit the password length that youβll be able to crack. This is usually fine, unless you are cracking passwords greater than 27 characters.
Dictionary attack with rules
Letβs try a rule. As mentioned earlier, hashcat ships with several rules located in the rules directory. You use the -r <rulefile.rule> option to apply a rule. For example, Iβll use the d3ad0ne.rule:
hashcat64.exe -a 0 -m 0 example_md5_hashes.txt combined_seclists_password_list.txt -r rules\d3ad0ne.rule -O
Within a few seconds hashes will start to crack. You can press the βsβ key to get an estimated time of completion, as well as see other data about the session. For me, this ran for 8 minutes and recovered 26 of the passwords.
Not bad! And that is just one rule! Cycling through the rules will recover new passwords, but Iβm just going to skip to a different attack. More on rules in a follow-on post (eventually), but you can take a look at my follow-on post about rule writing, or the hashcat wiki to get started with writing your own rules.
π¦Combinator attack
A combinator attack is an attack that combines two dictionaries. To perform this attack Iβll first create a copy of my wordlist with a few modifications. First Iβll use a script, wordlist_cleaner.py to lowercase all letters, and remove any numbers and special characters from each word. Then Iβll use another script, capitalize_letters.py, to capitalize the first letter of each word.
C:\Users\Jake\hashcat-4.2.1>python3 wordlist_cleaner.py -f combined_seclists_password_list.txt -o combined_seclists_password_list_clean.txt
[*] Reading file: combined_seclists_password_list.txt
[*] Processing 13272929 words.
[*] Changing all words to lowercase...
[*] Removing numbers and special characters...
[*] Removing duplicate words...
[*] Printing cleaned words to combined_seclists_password_list_clean.txt
C:\Users\Jake\hashcat-4.2.1>python3 capitalize_letters.py -f combined_seclists_password_list_clean.txt -o combined_seclists_password_list_caps.txt
[*] Reading file: combined_seclists_password_list_clean.txt...
[*] Processing 7243374 words...
[*] Changing all words to lowercase...
[*] Capitalizing first letter of each word...
[*] Writing to combined_seclists_password_list_caps.txtβ¦
Now Iβll try an attack:
hashcat64.exe -a 1 -m 0 example_md5_hashes.txt combined_seclists_password_list_caps.txt combined_seclists_password_list_caps.txt -k "$!" -O
β β β Uππ»βΊπ«Δπ¬πβ β β β
Forwarded from UNDERCODE NEWS