Ethical Hacking Tutorials

https://infosecsanyam.medium.com/bug-bounty-methodology-ttp-tactics-techniques-and-procedures-v-2-0-2ccd9d7eb2e2 More Hacking at @ethicalhackx && @ehackx

https://infosecwriteups.com/bug-bounty-hunting-methodology-toolkit-tips-tricks-blogs-ef6542301c65 More Hacking at @ethicalhackx && @ehackx

DevSecOps: The Big Picture | by Tushar Verma | Jul, 2022 | Medium https://tushara2517.medium.com/devsecops-the-big-picture-a5db8e3a8b4e

Microsoft: Phishing bypassed MFA in attacks against 10,000 orgs https://www.bleepingcomputer.com/news/security/microsoft-phishing-bypassed-mfa-in-attacks-against-10-000-orgs/

CompTIA Linux+ (XK0-004) - ITProTV Tools and skills for Linux systems administrators Duration - 22 H ITProTV Link - https://www.itpro.tv/courses/comptia/linux-xk0004/ Password - @ethicalhackx Size : 5.5GB #HowToExtract

How does 𝐆𝐨𝐨𝐠𝐥𝐞 𝐀𝐮𝐭𝐡𝐞𝐧𝐭𝐢𝐜𝐚𝐭𝐨𝐫 work? We use this authenticator a lot for logging into our accounts and transferring money online. Found this online, this is interesting read, More Hacking at @Ethicalhackx && @ehackx But how does it guarantee security? Google Authenticator is a software-based authenticator that implements two-step verification service. The diagram below provides detail. There are two stages involved: 🔹 Stage 1 - The user enables Google two-step verification 🔹 Stage 2 - The user uses the authenticator for logging in, etc. Let’s look at these stages. 𝐒𝐭𝐚𝐠𝐞 1 Steps 1 and 2: Bob opens the web page to enable two-step verification. The frontend requests a secret key. The authentication service generates the secret key for Bob and stores it in the database. Step 3: The authentication service returns a URI to the frontend. The URI is composed of key issuer, username and secret key. The URI is displayed in the form of a QR code on the web page. Step 4: Bob then uses Google Authenticator to scan the generated QR code. The secret key is stored in the authenticator. 𝐒𝐭𝐚𝐠𝐞 2 Steps 1 and 2: Bob wants to log into a website with Google two-step verification. For this he needs the password. Every 30 seconds, Google Authenticator generates a 6-digit password using TOTP (Time-based One Time Password) algorithm. Bob uses the password to enter the website. Steps 3 and 4: The frontend sends the password Bob enters to the backend for authentication. The authentication service reads the secret key from the database and generates a 6-digit password using the same TOTP algorithm as the client. Step 5: The authentication service compares the two passwords generated by the client and the server, and returns the comparison result to the frontend. Bob can proceed with the login process only if the two passwords match. Is this authentication mechanism 𝐬𝐚𝐟𝐞? 🔹 Can the secret key be obtained by others? We need to make sure the secret key is transmitted using HTTPS. The authenticator client and the database store the secret key, and we need to make sure the secret keys are encrypted. 🔹 Can the 6-digit password be guessed by hackers? No. The password has 6 digits, so the generated password has 1 million potential combinations. Plus, the password changes every 30 seconds. If hackers want to guess the password in 30 seconds, they need to enter 30,000 combinations per second.

How does 𝐆𝐨𝐨𝐠𝐥𝐞 𝐀𝐮𝐭𝐡𝐞𝐧𝐭𝐢𝐜𝐚𝐭𝐨𝐫 work? We use this authenticator a lot for logging into our accounts and transferring money online. Found this online, this is interesting read, More Hacking at @Ethicalhackx && @ehackx But how does it guarantee security? Google Authenticator is a software-based authenticator that implements two-step verification service. The diagram below provides detail. There are two stages involved: 🔹 Stage 1 - The user enables Google two-step verification 🔹 Stage 2 - The user uses the authenticator for logging in, etc. Let’s look at these stages. 𝐒𝐭𝐚𝐠𝐞 1 Steps 1 and 2: Bob opens the web page to enable two-step verification. The frontend requests a secret key. The authentication service generates the secret key for Bob and stores it in the database. Step 3: The authentication service returns a URI to the frontend. The URI is composed of key issuer, username and secret key. The URI is displayed in the form of a QR code on the web page. Step 4: Bob then uses Google Authenticator to scan the generated QR code. The secret key is stored in the authenticator. 𝐒𝐭𝐚𝐠𝐞 2 Steps 1 and 2: Bob wants to log into a website with Google two-step verification. For this he needs the password. Every 30 seconds, Google Authenticator generates a 6-digit password using TOTP (Time-based One Time Password) algorithm. Bob uses the password to enter the website. Steps 3 and 4: The frontend sends the password Bob enters to the backend for authentication. The authentication service reads the secret key from the database and generates a 6-digit password using the same TOTP algorithm as the client. Step 5: The authentication service compares the two passwords generated by the client and the server, and returns the comparison result to the frontend. Bob can proceed with the login process only if the two passwords match. Is this authentication mechanism 𝐬𝐚𝐟𝐞? 🔹 Can the secret key be obtained by others? We need to make sure the secret key is transmitted using HTTPS. The authenticator client and the database store the secret key, and we need to make sure the secret keys are encrypted. 🔹 Can the 6-digit password be guessed by hackers? No. The password has 6 digits, so the generated password has 1 million potential combinations. Plus, the password changes every 30 seconds. If hackers want to guess the password in 30 seconds, they need to enter 30,000 combinations per second.

expect ur msges to be deleted

some cleaning up in progress, dont panic

LinEnum.sh Edit to get more detailed reports #!/bin/bash #A script to enumerate local information from a Linux host thorough=1 version="version 0.982" #@rebootuser

https://medium.com/maverislabs/lock-screen-bypass-exploit-of-android-devices-cve-2022-20006-604958fcee3a More hacking at @ethicalhackx and @ehackx

@ehackx is for helping others. Not for settling scores and settle who is a better hacker. This is no arena to fight. So people, stop fexling around Any1 flexing and demeaning and not respecting others, you maybe good hacker and all, not good human. Getting into useelss chats in group === expect to be banned. Only serious learners for Hacking and Security join @ethicalhackx

Want to share how and form where you are learning Hacking ? Lets connect and talk on group call.