Forem: Ian Muchina

Stop chrome from pausing when switching desktops

Ian Muchina — Sat, 03 Apr 2021 21:00:00 +0000

Sometimes I switch desktop environments because, why not? Every time I switch between gnome and kde, I face the same issue. Chrome pauses.

When chrome displays the paused sign, it’s an issue with cookies. In this case, the cookies are encrypted, and chrome can’t decrypt them because it’s looking for the decryption key in the wrong keyring.

Too many keyrings

A keyring is a lot like a password manager. The only difference is that keyrings are meant for programs, and password managers are meant for humans. For security, chrome stores the key used to decrypt cookies in the keyring.

All major operating systems have some sort of keyring implementation. Windows has one, Mac has one. Linux has several. On Linux, chrome decides the keyring it will use based on the current desktop environment.

When switching desktop environments, chrome will switch keyrings without migrating the keys. This makes chrome forget the key needed to decrypt the cookies.

Stick with one

The solution is to hardcode the keyring chrome will use. You can do this with the –password-store flag, which has 3 options:

gnome (to use GNOME Keyring)
kwallet (to use KDE’s KWallet)
basic (to use the plain text store. No encryption)

To set the flag, first install menu-libre.

sudo apt install menulibre

Then using menu-libre, edit chrome’s command.

/usr/bin/google-chrome-stable --password-store=kwallet5 %U

Hopefully, that works, and you can switch desktops without breaking your browser.

Some youtube-dl aliases

Ian Muchina — Fri, 26 Mar 2021 05:00:00 +0000

defaults

alias ydl='youtube-dl -o "./%(title)s.%(ext)s"'

Doesn’t change much of the defaults. Only removes unnecessary info from filename eg: video-title-dQw4w9WgXcQ.mp4 to video-title.mp4

720p single video

alias yhd='youtube-dl -f "[height<=720]" -o "~/Videos/%(uploader)s/%(title)s.%(ext)s" --no-playlist '

720p
Single video. No playlist
Saves to ~/Videos/Uploader/Title.mp4

720p video playlist

alias ypl='youtube-dl -f "[height<=720]" -o "~/Videos/%(uploader)s/%(playlist)s/%(title)s.%(ext)s" '

720p
Downloads entire playlist
Saves to ~/Videos/Uploader/Playlist/Title.mp4

Audio

alias ymp3='youtube-dl -f "bestaudio" -o "~/Music/%(uploader)s/%(title)s.%(ext)s" --no-playlist -x --audio-format mp3 --embed-thumbnail '

mp3
Single audio. No playlist
Saves to ~/Music/Uploader/Title.mp3
Adds thumbnail as cover art

Audio Playlist

alias ypl3='youtube-dl -f "bestaudio" -o "~/Music/%(uploader)s/%(playlist)s/%(title)s.%(ext)s" -x --audio-format mp3 --embed-thumbnail'

Downloads entire playlist
Saves to ~/Videos/Uploader/Playlist/Title.mp3
Adds thumbnail as cover art

Reproducible Builds

Ian Muchina — Sun, 24 Jan 2021 08:30:00 +0000

A reproducible build is one that produces the same byte for byte output when given the same input. These builds aren’t common. Mostly because of compiler defaults.

The things that can make a build non-reproducible are:

Timestamps
Unique IDs
Build paths
etc

Why they matter

Reproducible builds have inherent security. They allow us to verify the source code a binary comes from. This makes detecting changes or tampering straightforward.

Compile the program on at least two different systems
Compare the checksums.
If they match, that’s good. If they don’t match, something is wrong.

The builds have more integrity, which benefits everyone. For security-minded people, it means a straightforward way of detecting backdoors in the build process. For open source enthusiasts, it means a clear way of detecting GPL violations. For everyone else, we get safer software.

You can find out how to acheive reproducible builds at reproducible-builds.org/docs.

Attacks on build systems

Back-doors introduced in the build process are not easy to detect. Most of the detection happens too late when the damage is already done. The attacks can have a high impact in a short period, so early detection is important.

There have been many attacks like this in the past. Some of them are:

SUNSPOT, An attack on SolarWinds that affected lots of important people
XcodeGhost - Attack on an IDE for Mac. Lots of iOS apps were affected. Including Angry Birds

Defending against them

Reproducible builds are the best way to defend against these kinds of attacks. Attackers lose their incentive bacause they are detected quickly and need to compromise more systems.

The disadvantages

Like everything there are downsides. Some of them are:

Need to use a specific compiler version
No Profile-guided optimization

What they don’t protect us from

Reproducible builds don’t protect us from malicious developers. A developer could knowingly write vulnerable code that it looks like a mistake when discovered. This called underhanded code.

In the paper titled Trusting Trust Ken Thompson asks us:

To what extent should one trust a statement that a program is free of Trojan horses? Perhaps it is more important to trust the people who wrote the software.

Who does reproducible builds?

Many open-source projects have reproducible builds to assure users of their integrity. Some of them include:

Linux distros

Around 80%-90% of the packages in Linux distributions like ( Arch, Debian, OpenSUSE, NixOS, Guix) are already reproducible. You can find the exact numbers here.

Digital signatures

Digital signatures still have their place. They are useful when verifying who a document or message comes from. However, they aren’t useful when verifying the source code a binary comes from. Some forms of digital signatures can get in the way, as explained by telegram developers in this article.

Conclusion

You can’t trust non-reproducible software. It’s a single point of failure. Mike Perry of the tor project described it in 2013 as follows:

I don’t believe that software development models based on trusting a single party can be secure against serious adversaries anymore, given the current trends in computer security.

This statement is true to this day.

Building a Pentest lab with Docker

Ian Muchina — Sat, 13 Jun 2020 11:30:00 +0000

What is Docker?

Docker is a container platform that is similar to a Hypervisor like Virtualbox. Containers use less storage and RAM and are portable.

Docker can run on:

Linux
Windows
Mac OS

In this article I will go over how to set up a penetration testing lab entirely in docker

It will consist of two types of containers.

Attacker Machine
Target Machines

Installation on Linux

The Docker engine is in the official repositories of most Linux distributions.

Ubuntu/Debian

Anything that uses apt to install software is Debian based. Find a complete list here

To install on Ubuntu :

$ sudo apt install docker.io

Fedora

To install on fedora:

$ sudo dnf install docker

Start the Docker service

$ sudo systemctl start docker

Arch/Manjaro

To install Arch based distros:

$ sudo pacman -Syu

Enable the loop kernel module

$ sudo tee /etc/modules-load.d/loop.conf <<< "loop"
$ modprobe loop

Install Docker

$ sudo pacman -S docker

Start and enable the service

$ sudo systemctl start docker.service
$ sudo systemctl enable docker.service

Docker on Windows

To run docker in windows, install Docker desktop.

Docker Desktop is an awesome app with a graphical interface. It can run Linux containers from windows. However, there’s one major deal-breaker.

Docker Desktop cannot co-exist with VirtualBox or VMware, because it requires Hyper-V to run Linux containers😤¹.

Hyper-V is Microsoft’s hardware virtualization product

As a workaround.

Use Docker Toolbox 👨‍💻
Learn Hyper-V 📚
Install Linux 🤷‍♀️

This is also the same reason WSL cannot co-exist with VMware/Virtualbox.

Now I’m starting to see why people hate Microsoft. They lock users to their ecosystem.

Hello World

After you have installed docker, run this command as a test

$ sudo docker run hello-world

If it completes successfully, you can follow along

The Network

The network will be called vulnerable. It will have a 10.0.0/24 subnet

Create it with this command

$ sudo docker network create vulnerable --attachable --subnet 10.0.0.0/24

Attacker Container

For this, I will use Parrot OS. It’s docker images are better Kali Linux Images.

First download the Parrot OS Docker image. This command will take a while depending on your internet connection.

$ docker pull parrotsec/security:latest

Create and run the container .

sudo docker run \
    --name parrot \
    -it \
    --hostname parrot \
    --network vulnerable \
    --ip="10.0.0.2" \
    --env DISPLAY=$DISPLAY \
    -v /dev/shm:/dev/shm \
    --device /dev/snd \
    --device /dev/dri \
    --mount type=bind,src=/tmp/.X11-unix,dst=/tmp/.X11-unix \
    parrotsec/security:latest \
    /bin/bash

All tools available in Parrot OS are now an apt-get away.

Use this command to restart the parrot OS container after a reboot.

$ sudo docker start -a parrot

Target container:Metasploitable2

This is a very vulnerable test machine. It is what I recommend for anyone starting out.

Open another terminal and pull the metasploitable image. The image is around 500MB.

$ docker pull tleemcjr/metasploitable2

To run a metasploitable container:

docker run \
    -it \
    --network vulnerable \
    --ip="10.0.0.3" \
    --name metasploitable \
    --hostname metasploitable2 \
    tleemcjr/metasploitable2 \
    bash

You should see a terminal prompt like this

root@metasploitable2:/#

Start the vulnerable services

root@metasploitable2:/# services.sh

You can now access metasploitable from 10.0.0.3

If you want to stop the container, close the terminal with CTRL + D

Run this command to start metasploitable again

$ sudo docker start -a parrot

Then start the vulnerable services.

root@metasploitable2:/# services.sh

Guides & Tutorials

There are tons of free guides out there on metasploitable.

If you don’t know what guide to use, I recommend this one.

More vulnerable containers 🧑‍💻

You can extend the lab with any of these containers depending on your learning goal.

OWASP Juiceshop

This container focusses on web application security.

To create and start the juiceshop container for the first time

docker run -d \
    --name juiceshop \
    --network vulnerable \
    --ip="10.0.0.6" \
    bkimminich/juice-shop

Check if it is running

$ docker ps

Access the web interface from this URL

http://10.0.0.6:3000/

Stop the container when you’re done

docker stop juiceshop

Start the container again

docker start juiceshop

Juiceshop Guides

OWASP Webgoat 🐐

Webgoat is a ctf-style vulnerable container focused on web application security.

Create and run the container for the first time

docker run -d \
    --name webgoat \
    --network vulnerable \
    --ip="10.0.0.4" \
    -e TZ=$(cat /etc/timezone) \
    webgoat/goatandwolf

Access Webgoat and Webwolf from these URLs

10.0.0.4:8080/WebGoat

10.0.0.4:9090/WebWolf

To stop the container

docker stop webgoat

To Start the container again.

docker start webgoat

If you can’t access the url, check if it is running.

$ docker ps -a

Why I use docker for a pentest lab

Two Operating systems make my computer painfully slow. Containers aren’t resource-intensive and perform well. This fits my use case.

If you have RAM to spare then it’s really not that much of a difference.

When not to use Docker

If you want to run Windows containers on a Linux host. You can run linux containers on WIndows though

Common Docker Commands

Stop a container:

$ sudo docker stop containerName

Start a container

$ sudo docker start containerName

List running and stopped containers

$ sudo docker ps -a

Spawn a bash shell in a running container

$ sudo docker exec -it containerName bash

Docker has tab completion for each of these commands.

Graphical apps inside docker

Sometimes you may want to run a GUI tool like firefox or burpsuite.

The Parrot OS commands above are already set for running graphical apps. You only need to install these packages

$ apt install hicolor-icon-theme \
    libcanberra-gtk* libgl1-mesa-dri \
    libgl1-mesa-glx libpangox-1.0-0 \
    libpulse0 libv4l-0 fonts-symbola \

You can run a few commands to avoid some errors encountered when running GUI apps

Burpsuite

Burp Suite is a web app pentesting tool for monitoring http requests and responses.

To install and run burpsuite inside the parrot os container.

# sudo apt update
# sudo apt install burpsuite
# java -jar -Xmx2G /usr/bin/burpsuite

You can then point your browser to use 10.0.0.2:8080 as the proxy and burp will intercept everything

Firefox

Firefox, is a free and open-source web browser.

To install and run firefox:

$ apt install firefox ca-certificates

Credits

Illustrations from Freepik

Footnotes

Docker requires a Linux kernel to run Linux containers on Windows. Docker accomplishes this by running a Linux Virtual Machine inside Hyper-V. This is still more resource-efficient than full VM’s. Plus there’s the added benefit of running both Windows and Linux containers. This is not possible on Linux ↩

Automating updates on Debian

Ian Muchina — Sun, 31 May 2020 08:30:00 +0000

Debian is a good operating system. Forming the basis for Ubuntu, Kali Linux and many others it is one of the most stable operating systems out there.

In this post, I will go over how to configure automatic security updates on Debian, which are not enabled by default.

Introduction

Debian uses the apt package manager. A system update is done with the following commands:

$ apt update
$ apt upgrade

The importance of security updates

Security updates contain fixes for security vulnerabilities. They are an overlooked protection measure against many attacks.

In 2017 there was a ransomware attack named Wannacry. All the infected computers had one thing in common. They weren’t updated.

Updating a system regularly can prevent lots of attacks.

Why Automate?

Performing manual updates is repetitive and can be a huge burden to system administrators.

Setting up automatic updates

First update the package list.

$ apt update

Install these 2 packages

$ apt install unattended-upgrades apt-listchanges

Perform a quick configuration

$ sudo dpkg-reconfigure -plow unattended-upgrades

At this point, automatic upgrades have been configured and will run every 24 hours.

Automatic reboots

The next thing is to set up automatic reboots. Some updates such as those to the Linux kernel require a reboot.

With a text editor open the unattended-upgrades configuration file.

$ vim /etc/apt/apt.conf.d/50unattended-upgrades

Uncomment the line with Automatic-Reboot and set it to True.

Unattended-Upgrade::Automatic-Reboot "true";

This step is not neccesary but makes updates predictable.

Unattended-Upgrade::Automatic-Reboot-Time "23:00";

Commented lines are those that start with two slashes // , remove the slashes to uncomment the lines.

// This line is commented
This line is not commented

Live Patching

If server uptime is important to you, a good solution is Livepatch by Cannonical, the company behind Ubuntu. It is free for up to 3 devices.

Livepatch allows you to install some critical kernel security updates without rebooting your system, by directly patching the running kernel. … It’s mainly intended for servers which are supposed to have months and years of continuous uptime without reboots

You can read more on kernel live patching here.

Alerts on update failure

Debian is a very stable OS, however, updates can fail when using software that is not in the official repos. When that happens you will want to receive an alert.

I will be setting up email alerts in case of update failure.

Configuring `unattended-upgrades` to send email

With a text editor modify the following lines in the unattended-upgradesconfiguration file

$ vim /etc/apt/apt.conf.d/50unattended-upgrades

Uncomment and modify these lines.

Unattended-Upgrade::Mail "your@email.address";
Unattended-Upgrade::MailOnlyOnError "true";

Setting up postfix to send email

To send the email alerts you need a working email setup. For this, I will be using postfix to send email from a Gmail account

Create an app password

If you use Gmail, a good way to control access is by using app passwords. I use this method because I can revoke app passwords in case of compromise.

An App Password is a 16-digit passcode that gives a non-Google app or device permission to access your Google Account

To create an app password, go to the Google account security page while signed in.
Under Signing into Google , Select App Passwords
Generate a custom App password, name it to something relevant like server-x email alerts and copy it. We’ll need it later.

Install and Configure Postfix

The next thing is to install Postfix and other required packages. They are required to send emails using the app passwords we just created.

Install postfix, libsasl and bsd-mailx

$ apt install postfix libsasl2-modules bsd-mailx

When prompted, select Internet site.

Configure postfix

The first step is to configure postfix. Follow these steps.

Open the postfix configuration file.

$ vim /etc/postfix/main.cf

Find the line with relayhost and add this.

relayhost = [smtp.gmail.com]:587

Set up TLS

The next step is to configure TLS. It stands for Transport Layer Security This ensures the email contents and credentials are encrypted in transit.

Open the postfix configuration file.

$ vim /etc/postfix/main.cf

Append the following lines to the end of the file

# Enable SASL authentication
smtp_sasl_auth_enable = yes
# Disallow methods that allow anonymous authentication
smtp_sasl_security_options = noanonymous
# Location of sasl_passwd
smtp_sasl_password_maps = hash:/etc/postfix/sasl/sasl_passwd
# Enable STARTTLS encryption
smtp_tls_security_level = encrypt
# Location of CA certificates
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt

Set up the credentials

The next step is to configure postfix to use the Gmail app passwords we have created.

Open /etc/postfix/sasl/sasl_passwd

$ vim /etc/postfix/sasl/sasl_passwd

Add the following contents

[smtp.gmail.com]:587 yourusername@gmail.com:password

Generate the password database

$ postmap /etc/postfix/sasl/sasl_passwd

Secure the credentials

By default, the files containing the email credentials are readable by everyone. We can change this.

Modify the permissions so that the root user owns them with chown

$ sudo chown root:root /etc/postfix/sasl/sasl_passwd /etc/postfix/sasl/sasl_passwd.db

With chmod, change the permissions so that only root can the file.

$ sudo chmod 0600 /etc/postfix/sasl/sasl_passwd /etc/postfix/sasl/sasl_passwd.db

Restart Postfix

$ systemctl restart postfix

Test the email setup

Send yourself a test email from the terminal

$ echo "Test completed" | mail -s “Test From server” your_email@gmail.com

If the email is received, then congratulations. The email setup is comlete. You now have:

Automatic daily updates
Automatic reboots
A feedback system incase updates fail

Image Credits

Illustrations from Stories by Freepik

Why SSH certificates are awesome

Ian Muchina — Fri, 15 May 2020 08:30:00 +0000

Big Tech companies such as Facebook, Google, Netflix, Uber with thousands of users and servers use SSH Certificates to manage access. This post will go over why that’s the case

What is SSH?

SSH is a protocol used by system administrators and developers to communicate securely with a server. Authentication can be done with SSH keys or passwords.

Passwords and why they’re not recommended

We all know passwords and have used them at some point. Those secret string of characters you have to remember to prove your identity.

Passwords are good and better than nothing, but securing a server with just a password is not recommended especially on critical systems.

Weak passwords can be brute-forced
Sometimes passwords have to be shared for group accounts.
Only one compromised server is enough to phish all user credentials.
Revocation of compromised user passwords is not easy or convenient
Without a second factor, they are a single point of failure

You can improve the security by using tools like fail2ban to block IP addresses that have multiple failed login attempts.

Why use keys?

Keys are the default authentication method on most cloud providers eg: Digital Ocean. There is a good reason for this. Keys are more secure than passwords

SSH keys are a matching set of cryptographic keys which can be used for authentication.

Each set contains a public and a private key. The public key can be shared freely without concern, while the private key must be vigilantly guarded and never exposed to anyone. source

Why SSH Keys are more secure

One user account can have multiple keys. This makes auditing easier
Keys can be password protected. Note the password is just for unlocking the key and never sent to the server
Keys can be combined with passwords
Keys can be revoked

Keys are created with the ssh-keygen command.

When creating keys, it is a good idea to encrypt them with a password. So that even if the key is leaked, the password will add another layer of security.

Managing SSH keys

To connect to a server using keys, a user’s public key has to be in the authorized_keys file on every server they want to connect to.

This method of managing keys is the most common and works okay for small teams but it can be a burden for large organizations with many users.

But growth creeps upon you, and before you know it you are securing significant assets with sub-standard methods

Key management issues

The authorized_keys file on all servers has to be maintained regularly
Issuing a new key is a long process
Losing a key locks you out

The task of updating the authorized_keys file can and should be automated for large companies. This method “works” but there is a much better alternative

SSH Certificates

This is where public keys are signed by a Certificate Authority(CA). This method scales very well across thousands of machines. It can be used for both user and host verification. This method eliminates the Trust on first use requirement.

Advantages of certificates

SSH certificates are underrated and awesome in my opinion. They have some good features:

Server configuration is done only once
Updating the authorized_keys file on every server is not needed.
Audits are easier since every key is unique
Works perfectly for giving users access to offline/air-gapped servers
Keys can expire

Available Metadata

The signed key can contain the following useful information

1. Key Expiry date & time

This is how long a key is valid. The value can range from minutes to years. Netflix set their certificates to expire after two minutes. That’s enough time for a developer to login into a server and start an ssh session. Note that the session does not terminate when a certificate expires, only when a user logs out

2. Principals

Principals control which user accounts and hosts a user has access to. For example, there can be a root_staging principal which allows users to login as root on a staging server

You can Parse this data offline with ssh-keygen -Lf /Path/To/Signed_Cert

You can also use this site

Open Source Implementations

There are many solutions to giving users SSH access. All these are available on GitHub. Note that documentation is not that good for some tools though

1. Keybase Certificate Authority bot

This is a keybase chatbot that signs public keys. it is cli based. The bot doesn’t need any ports open.

Used internaly @ Keybase
Only supports keybase Authentication
Good Documentation

Blog post on keybase SSH

2. Cashier

Controlled via a web interface
Integrates well with LDAP or Active Directory
Google, Github or Gitlab login available
Key revocation page

Video on The Tool

3. BLESS - By Netflix

Used internally @ Netflix,
Runs on AWS Lambda
Video on the tool

4. SSHrimp - by Stoggi

Runs on AWS Lambda
Authenticate with OpenID connect
Still in Beta

5. Keymaster - Symantec

Supportts Oauth2 login
Integrates well with LDAP/Active Directory
Made by Symantec
Documentation

More Tools

Video Resources

For those that prefer videos to blog posts

Image Credits

Illustrations from Stories by Freepik

Isolating vocals from songs using Spleeter

Ian Muchina — Sun, 08 Mar 2020 07:00:00 +0000

Introduction

Isolating vocals from a song in the past has had a high barrier to entry. It is now an easy thing to do . In this article, I will go over the various methods.

1. The browser method

This is done entirely online. Open a browser, go to a upload a song and get vocal and instrumental stems. This is a simple method which relies on third party websites to process the music.

Steps

The only requirement is a browser.

Go to moises.ai
Create an account
Upload a song
Wait for the isolation to be done
Enjoy !!

Demo

Here’s a sample of the results:

.embed-container { position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; max-width: 100%; } .embed-container iframe, .embed-container object, .embed-container embed { position: absolute; top: 0; left: 0; width: 100%; height: 100%; }

Advantages]

Can be done from any device with a browser even a mobile phone
Requires no special knowledge
Easy user interface ##### Disadvantages
Only 5 uploads per month
There’s a queue that may affect your waiting time

You can use ezstems.com as an alternative for more upload options and it works in a simmilar way.

2. The App Method

This second method is simmilar to the first, but only uses the computer’s resources.

Steps

This method only works on windows

Download and install the latest version of Python
During the installation make sure add to path checkbox is selected.
Download SpleetGUI
Extract the zip file
Install SpleetGUI

*I have no idea if it is safe to use

3. Command line Method

This last is done entirely from the command line and is great for those familiar with.

Steps

For this method, you will require git and conda already installed on your computer. Then type the following commands:

$ sudo apt install git


$ git clone https://github.com/Deezer/spleeter
$ conda install -c conda-forge spleeter

To run spleeter

$ python3 -m spleeter -i your_song.mp3 -p spleeter:2stems -o output

How Does it Work?

Machine learning is artificial intelligence that can automatically learn from past data. You give it enough data and it can literally learn like humans, through practice

For more detailed information, check out the documentation here

Conclusion

This is a great tool that can be used to get clean vocals from almost any song. It also works well to de-noise a track.

Tracking documents with Canarytokens

Ian Muchina — Sat, 15 Feb 2020 08:30:00 +0000

Introduction

The ability to track Documents might come in handy in some situations. To do this we use Canarytokens. These are files and links that trigger email alerts anytime anyone accesses them.

In this article, I will go over how to create and deploy these tokens.

Things You Will Need

Email Address
Target With An Internet Connection

1. Creating the file

Go to canarytokens.org
Choose either a Word Document or an Adobe PDF token
Enter an email address where alerts will be sent
Choose an appropriate reminder eg: “Opened”
Click on “Create My Canary Token”
Download the token

2. Setting up the file

After Downloading the file you should:

Rename the file
Edit the content of the file
Send the file to someone
Wait for an alert

3. Receiving Alerts

The alerts contain:

The IP address the file was opened from
A Reminder if you wrote one
The time and date when the file was opened

If someone with internet access opens the document, you will be alerted. Usualy within seconds.

Forem: Ian Muchina

Stop chrome from pausing when switching desktops

Too many keyrings

Stick with one

Further reading

Some youtube-dl aliases

defaults

720p single video

720p video playlist

Audio

Audio Playlist

Reproducible Builds

Why they matter

Attacks on build systems

Defending against them

The disadvantages

What they don’t protect us from

Who does reproducible builds?

Linux distros

Digital signatures

Conclusion

Further reading

reproducible-builds.org

Reflections on Trusting Trust

Countering Compiler backdoors

The Octopus Scanner Malware

Verifying the source code for binaries

Building a Pentest lab with Docker

What is Docker?

Installation on Linux

Ubuntu/Debian

Fedora

Arch/Manjaro

Docker on Windows

Hello World

The Network

Attacker Container

Target container:Metasploitable2

Guides & Tutorials

More vulnerable containers 🧑‍💻

OWASP Juiceshop

Juiceshop Guides

OWASP Webgoat 🐐

Why I use docker for a pentest lab

When not to use Docker

Common Docker Commands

Graphical apps inside docker

Burpsuite

Firefox

Credits

Further reading/research

Footnotes

Automating updates on Debian

Introduction

The importance of security updates

Why Automate?

Setting up automatic updates

Automatic reboots

Live Patching

Alerts on update failure

Configuring unattended-upgrades to send email

Setting up postfix to send email

Create an app password

Install and Configure Postfix

Configure postfix

Set up TLS

Set up the credentials

Secure the credentials

Test the email setup

Image Credits

Why SSH certificates are awesome

What is SSH?

Passwords and why they’re not recommended

Why use keys?

Why SSH Keys are more secure

Managing SSH keys

SSH Certificates

Advantages of certificates

Available Metadata

1. Key Expiry date & time

Configuring `unattended-upgrades` to send email