Support & Share ❤️👍🏻:

T.me/UndercodeTesting

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

HACK WPA2 ON ANDROID (NO WPS):


The description of WIBR+ WIfi BRuteforce
WIBR+ WIfi BRuteforce without root, is a high-level application for testing WPA / WPA2 PSK WiFi network security.
The Application will try to connect to WPS enabled Wifi Routers that have the WPS vulnerability using some algorithms to connect to the Wifi.
The protocol BRuteforce allows you to connect to a WiFi network using an 8-digit pin number that usually is predefined in the router, the problem is that the pin of many routers from different companies is known or is known how to calculate it.

This app supports two types of Testing:
1. Dictionary Testing: WIBR + tries one-by-one in a predefined list of passwords, and if it can not find a password, it simply means that it is not in the dictionary.
2. Violent Testing - You can select the alphabet, the length of the password, and the application will attempt to combine all the characters in the alphabet.

WIBR+ WIfi How to use BRuteforce:

1) Select the network you want, and WIBR+ will automatically test on a WPA / WPA2 network with pre-shared key (PSK).
2) Select the required dictionary or set bruteforce test.
3) the first two points if you have set up, then please be patient, the results should be tested so wait for the results of some long wait patiently waiting for WiFi during the test has been enabled to ensure smooth.
4) WIBR plus WIfi BRuteforce automatically return the result of testing.

Notice: ROOT is NOT totally required & Location Permission is required for Wibr Wifi Network Scanning
Please understand how the application works before giving an assessment.

FREE DOWNLOAD:

https://m.apkpure.com/wibr-wifi-bruteforce-without-root/io.wibrplus.wpstester

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

Samsung Galaxy Z Fold 2: the new version of One UI 3.0 arrives
#Technologies

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑How to configure a host-based intrusion detection system on CentOS?

1) Install AIDE on CentOS or RHEL

The initial installation (and first run) of AIDE is best performed on the system where the operating system has just been installed, and no service is exposed to the Internet or even to the LAN. In this early stage, we can minimize the risk of all intrusions and tampering from the outside. In fact, this is the only way to ensure that the system is clean when AIDE builds its initial database.

For this reason, after we install AIDE using the command # yum install aide, we need to disconnect our machine from the network and perform some basic configuration tasks, as described below.

2) Configure AIDE

The default configuration file is located in /etc/aide.conf. The file provides several example protection rules (such as FIPSR, NORMAL, DIR, and DATAONLY). Each rule is followed by an equal sign and a list of file attributes to check, or any predefined rules (separated by +). You can also use this format to define any custom rules.

3) FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256

NORMAL = FIPSR+sha512

For example, the above example means that the NORMAL rule will check for inconsistencies in the following attributes: permission (p), index node (i), number of links (n), user (u), user group (g), size (s) ), modification time (m), creation time (c), access control list (acl), SELinux (selinux), xattrs (xattr), and SHA256/SHA512 checksum (sha256 and sha512).

The exclamation mark (!) in front of the entry tells AIDE to ignore subdirectories (or files in the directory), and another rule can be defined for subdirectories.

In addition, if you use the MAILTO variable to specify an email address, you can send the check result to your email address. Put the following line anywhere in /etc/aide.conf.

MAILTO=root@localhost

Run AIDE for the first time

Run the following command to initialize the AIDE database:

# aide --init

The /var/lib/aide/aide.db.new.gz file generated according to /etc/aide.conf needs to be renamed to /var/lib/aide/aide.db.gz so that AIDE can read it:

# mv /var/lib/aide/aide.db.new.gz /var/lib/aide.db.gz

Now, it’s time to perform our first system check against the database. To do this, just run:

# aide

When called without options, AIDE assumes the use of --check.

If no changes have been made since the database was created, AIDE will return an OK message after finishing the check.

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

A new cellular process never seen before discovered.
#Technologies

Qualcomm Snapdragon 888 has launched a dramatically improved performance terminal in the first quarter of next year.
#Technologies

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🐧 How to enable timestamp in Bash history on Linux?

1) This list of commands is saved in a file called .bash_history in our HOME directory.

Most Linux distributions remember the last 1000 commands by default.

We can retrieve recently executed commands using the command history as shown below:

$ history

2) To enable timestamping in Bash history on your Linux, you need to set the HISTTIMEFORMAT environment variable.

This variable is used to display the timestamp associated with each displayed record in history.

Run the following command to set the HISTTIMEFORMAT environment variable:

$ export HISTTIMEFORMAT='%F %T '
Here the% F parameter is used to display the date in YYYY-MM-DD (year-month-date) format.

And the% T option is used to display the time in HH: MM: SS (hours-minutes-seconds) format.

3) If you want to display the timestamps for the most recent “N” commands, for example 10, pipe the output of the history command to the tail command, for example:

$ history | tail -10
Note that this will only time-stamp new history entries after the HISTTIMEFORMAT environment variable has been set for sessions.

4) You can also customize the date format to your liking, as shown in the following command:

$ export HISTTIMEFORMAT='%d/%m/%y %T '
This environment variable shows the date and time in the command history in dd / mm / year format, for example. 11/27/20 7:11:55 PM.

5) To make the HISTTIMEFORMAT environment variable persist across system reboots, edit the ~ / .bashrc file:

$ nano ~/.bashrc
Add the following line to the end:

export HISTTIMEFORMAT='%F %T '
or

export HISTTIMEFORMAT='%d/%m/%y %T '
Press CTRL + O to save the file and press CTRL + X to exit.

6) Run the following command for the changes to take effect immediately:

$ source ~/.bashrc
The system will only display the time stamp for the current user.

To enable the Bash history timestamp for all users on the system, edit the / etc / profile file:

$ sudo nano /etc/profile
and add there:

7) export HISTTIMEFORMAT='%F %T '
or:

export HISTTIMEFORMAT='%d/%m/%y %T '
Save and close the file.

For the changes to take effect, run:

$ sudo source /etc/profile
For more information, see the man pages:

$ man bash

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑NEW ANDROID/IOS APPS FOR CREDIT CARDS MANAGER :

https://play.google.com/store/apps/details?id=com.syf.amazonstorecard&utm_source=appgrooves&utm_medium=agp_27d4f6fbb0ce1326689b845a300572f1_com.syf.amazonstorecard_us_others_16069045905359

https://play.google.com/store/apps/details?id=com.dreamplug.androidapp&utm_source=appgrooves&utm_medium=agp_27d4f6fbb0ce1326689b845a300572f1_com.dreamplug.androidapp_us_others_16069045918631

https://play.google.com/store/apps/details?id=com.ollocard.mobileapp&utm_source=appgrooves&utm_medium=agp_27d4f6fbb0ce1326689b845a300572f1_com.ollocard.mobileapp_us_others_16069045939717

https://apps.apple.com/us/app/id1427782837?mt=8

https://play.google.com/store/apps/details?id=debit.credit.card.credit.card.manager&utm_source=appgrooves&utm_medium=agp_27d4f6fbb0ce1326689b845a300572f1_debit.credit.card.credit.card.manager_us_others_16069045982069

https://play.google.com/store/apps/details?id=com.alsedi.mycards&utm_source=appgrooves&utm_medium=agp_27d4f6fbb0ce1326689b845a300572f1_com.alsedi.mycards_us_others_16069045434694

https://play.google.com/store/apps/details?id=com.ics.creditcardreader&utm_source=appgrooves&utm_medium=agp_27d4f6fbb0ce1326689b845a300572f1_com.ics.creditcardreader_us_others_16069045472403

https://play.google.com/store/apps/details?id=debit.credit.card.credit.card.manager&utm_source=appgrooves&utm_medium=agp_27d4f6fbb0ce1326689b845a300572f1_debit.credit.card.credit.card.manager_us_others_16069045508143

https://apps.apple.com/us/app/id1128712763?mt=8

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

WhatsApp, the update on the memory that we were all waiting for arrives.
#Updates

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑Digital Marketing best courses :

10 hours
https://www.youtube.com/watch?v=SHI5X6Tre8g

11 h

https://www.youtube.com/watch?v=nU-IIXBWlS4

3h
https://www.youtube.com/watch?v=1Ff2-5Y2dKE

2h
https://www.youtube.com/watch?v=dDWa95CiOYI

1h
https://www.youtube.com/watch?v=kpgerCE095A
▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

Siemens, SAP and BMW have teamed up to push Google and Amazon out of the German car industry.
#international

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

Setup your own webhost:

Step 1: Install Nginx
Open the terminal application and then open the file /etc/apt/source.list in your favorite text editor and then add the below-given lines at the end of this file. In this line, you need to replace the ‘CODENAME’ with your Ubuntu release, which you are using on your system. For example, we have a Ubuntu 20.04 focal fossa on this system. Sp, insert Focal to replace the ‘CODENAME’.

deb http://nginx.org/packages/mainline/ubuntu/ CODENAME nginx

deb-src https://nginx.org/packages/mainline/ubuntu/ <CODENAME> nginx
Next, you have to import the following packages repository signing key and then add it to the apt repository:

$ sudo wget http://nginx.org/keys/nginx_signing.key

$ sudo apt-key add nginx_signing.key
Now, update apt manager packages and install the latest release of Nginx on your system from the official apt repository by running the following command:

$ sudo apt update

$ sudo apt install nginx


Now, start and enabled the Nginx server by using the following commands:

$ sudo systemctl start nginx

$ sudo systemctl enable nginx

$ sudo systemctl status nginx
Step 2: Configurations for Nginx Reverse Proxy
Create a new configuration file custom_proxy /etc/nginx/conf.d/custom_proxy.conf and then paste the following lines of code in it:

server {

listen 80;

listen [::]:80;

server_name myexample.com;


location / {

proxy_pass http://localhost:3000/;

}

}
The directive ‘proxy_pass’ specified inside the location makes this configuration as reverse proxy. This line proxy_pass http://localhost:3000/ directs all requests that match with location root/path must be forwarded to the port 3000 on localhost where your domain website is running.


To activate and link the new configuration file run the below mentioned command:

$ ln -s /etc/nginx/conf.d/custom_server.conf
Step 3: Test Configurations
Now, test the above configurations by using the following command:

$ sudo nginx -t
After successfully testing, if no bug is reported then, reload the new Nginx configuration.

$ sudo nginx -s reload
Configure Buffers
The above configurations are enough to create a basic reverse proxy server. but, for complex applications, you need to enable some advanced options, which are given below:

location / {

proxy_pass http://localhost:3000/;

proxy_buffering off;

}
Configure-Request headers
location / {

proxy_pass http://localhost:3000/;

proxy_set_header X-Real-IP $remote_addr;

}

▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

Microsoft: new system evaluates meetings by monitoring employees.
#Updates

Samsung Galaxy A32 5G: OnLeaks renders reveal the design.
#Leaks #Technologies