NMAP Network Mapper

Comments

Post a Comment

Popular posts from this blog

Managine Hadoop Cluster

If you are working on Hadoop, you’ll realize there are several shell commands available to manage your Hadoop cluster.  Hadoop administration commands. 1. Name node Commands Command Description hadoop namenode -format Format HDFS filesystem from Namenode hadoop namenode -upgrade Upgrade the NameNode start-dfs.sh Start HDFS Daemons                        stop-dfs.sh Stop HDFS Daemons start-mapred.sh Start MapReduce Daemons stop-mapred.sh Stop MapReduce Daemons hadoop namenode -recover -force Recover namenode metadata after a cluster failure (may lose data) 2. fsck Commands Command Description hadoop fsck / Filesystem check on HDFS hadoop fsck / -files Display files duri...
Read more

How to Create a Vanilla Kubernetes Cluster on BareMetal

 Kubernetes (K8s) is a powerful open-source container orchestration system, and deploying it on bare metal provides high performance and direct control over hardware. This guide walks you through setting up a vanilla Kubernetes cluster on bare metal servers. Prerequisites Hardware Requirements : At least 3 machines (1 Control Plane Node and 2 Worker Nodes). Minimum specifications: Control Plane Node : 2 CPUs, 2 GB RAM, 20 GB disk space. Worker Node : 1 CPU, 1 GB RAM, 10 GB disk space. Operating System : Ubuntu 22.04 (recommended) or any other Linux distribution. Network Setup : Unique hostname for each server. Static IP addresses or DHCP reservations. Disabled swap (required by Kubernetes). Tools : SSH access to all nodes. kubectl CLI tool. kubeadm for Kubernetes initialization. containerd or Docker as the container runtime. Step 1: Prepare the Nodes Update and Install Required Packages Log into each node and execute the following commands: sudo apt update && sudo apt upgra...
Read more

VENOM Vulnerability

How to Patch and Protect Linux Server against the VENOM Vulnerability # CVE-2015-3456 A very serious security problem has been found in the virtual floppy drive QEMU's code used by many computer virtualization platforms including Xen, KVM, VirtualBox, and the native QEMU client. It is called VENOM vulnerability. How can I fix VENOM vulnerability and protect my Linux server against the attack? How do I verify that my server has been fixed against the VENOM vulnerability? This is tagged as high severity security bug and it was announced on 13th May 2015. The VENOM vulnerability has existed since 2004, when the virtual Floppy Disk Controller was first added to the QEMU codebase. Since the VENOM vulnerability exists in the hypervisor’s codebase, the vulnerability is agnostic of the host operating system (Linux, Windows, Mac OS, etc.). What is the VENOM security bug (CVE-2015-3456)? An out-of-bounds memory access flaw was found in the way QEMU's virtual Floppy Disk Controller (F...
Read more