<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by matty jones on Medium]]></title>
        <description><![CDATA[Stories by matty jones on Medium]]></description>
        <link>https://medium.com/@caffeinatedengineering?source=rss-7d527f570edd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IOjddo8c49jtgiXKY2kbKQ.jpeg</url>
            <title>Stories by matty jones on Medium</title>
            <link>https://medium.com/@caffeinatedengineering?source=rss-7d527f570edd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:29:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@caffeinatedengineering/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ParrotOS And i3 Part 1]]></title>
            <link>https://caffeinatedengineering.medium.com/parrotos-and-i3-part-1-399a118f619f?source=rss-7d527f570edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/399a118f619f</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[i3wm]]></category>
            <category><![CDATA[parrotos]]></category>
            <dc:creator><![CDATA[matty jones]]></dc:creator>
            <pubDate>Wed, 09 Dec 2020 20:52:45 GMT</pubDate>
            <atom:updated>2020-12-09T20:52:45.056Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WuVD3XkXupg3GHzNGkknJw.png" /></figure><p><a href="https://parrotlinux.org/">ParrotOS</a> is a relative newcomer in the Linux security and privacy world, having started in 2013. While Kali is a great choice for penetration testing, Parrot is more pliable. It will certainly work out of the box but can be made better with some tweaks.</p><p>If you haven’t read <a href="https://medium.com/bugbountywriteup/parrotos-and-hack-the-box-buildout-part-1-9ced497169c9"><em>ParrotOS And Hack The Box Buildout Part 1</em></a> and <a href="https://medium.com/bugbountywriteup/parrotos-and-hack-the-box-buildout-part-2-4bf04b0efcd3"><em>ParrotOS And Hack The Box Buildout Part 2</em></a> yet, you should skim them for installing a virtual machine of ParrotOS, configuring the sharing, and then updating the OS, tools, and some simple configurations. This article takes nothing for granted and assumes a completely untouched install of ParrotOS Mate in a virtual machine to keep things simple for those that just want i3.</p><p>This series will be less about HTB and more about installing and setting up a Parrot specific i3 on top of Mate. I will then provide insight into some of the challenges with stripping Mate and Gnome entirely from Parrot in Part 2.</p><p>While this can be done, you need to ask yourself why you are doing this and how comfortable are you with the i3 way of doing things. It is easy to do, but not so easy to come back from.</p><p>The next several parts of this series will be more spread out and will deal with stripping everything out from a Mate install and for those that want ultimate control, building ParrotOS directly from Debian 11, with i3 as the native window manager.</p><p>Clap {1…50} and follow me to keep an eye out when the later parts to this series and my others drop.</p><p><strong>Note:</strong> There is an effort underway to build a supported version of Parrot with i3.</p><h3>Install i3</h3><p>Before we do anything we need to make sure i3 is installed. By default, it should be, but we need to update it and we can install<a href="https://polybar.github.io/"> polybar</a> and <a href="https://github.com/davatorium/rofi">rofi </a>as well. I will try to keep this as unopinionated as possible, but a few things are just too useful. Remember to do sudo apt update first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x_uL0vhy5GvuiX78_XMKJg.png" /></figure><p>At this point, you can reboot and select i3 at the login manager to get things started. You can automate all of this from installing i3 -&gt; fully configured environment but I am not going to touch on that much as doing so is generally very opinionated I will leave it up to you, the reader, to automate where it makes sense for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/1*pNXsu22sYnBEaYIVnLZf0g.png" /></figure><h3>Initial Configuration</h3><p>At this point, i3 is installed and running, trust me. The screen is blank as there is no valid configuration out of the box. Bring up a terminal window with <em>Alt + Enter</em>, if you are on OSX as I am it is <em>Option + Return</em>.</p><p>The first thing is to remove the existing config file with rm ~/.config/i3/config then we can create a valid config, using the configuration wizard, i3-config-wizard. It will ask a few questions and you are on your way.</p><p>As a word of note, it may make sense to select the Windows/Command key as the modifier but at least with VMWare Fusion, you may run into issues cutting and pasting, so you should select <strong>Alt</strong> as the modifier key. You can also just copy the default config cp /etc/i3/config ~/.config/i3/.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mZ44T1-OcHBtLrEEsfCIzw.png" /></figure><p>Whenever you make config changes, it is a good idea to reload the config, to be certain you didn’t break something. In this case, you should restart i3 with Alt + Shift + e, to be sure everything is set right. If you have an issue you will see a nagbar and box at the top of the screen giving you a general idea of what is borked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KcWOp6i4BJlxRkBJ5qH_jw.png" /></figure><p>At this point, you have a clean, abet sparse workspace. The only thing you will notice is the stock status bar at the bottom right of the screen.</p><p>There are some changes that need to be made to the config file before we can call it baseline. The major one is addingexec --no-startup-id vmware-user-suid-wrapper to the bottom to allow cut/paste between host and VM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Ln3Y_UDoehQGBT6qjdpsg.png" /></figure><h3>Polybar</h3><p>If the stock bar on the bottom is not doing it for you, there are ways to configure it via <a href="https://i3wm.org/i3status/manpage.html">i3status</a>, it is fairly straight forward but not the best middle ground between performance and eye candy.</p><p>Getting an example polybar up and running is fairly basic but will require a few additional packages.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a79fb54368ed31a4e853e647c883f203/href">https://medium.com/media/a79fb54368ed31a4e853e647c883f203/href</a></iframe><p>When doing the font config, you can leave all the defaults as they are except you want to enable bitmap fonts by default. There is also mention of setting some bits in your X config file, you shouldn’t need them for this use case and setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AVAQJu0nNhegd9cbUuHVcw.png" /></figure><p>Back in the i3 config file, you will need to comment out the <strong>bar</strong> section and add exec_always --no-startup-id $HOME/.config/polybar/launch.sh at the bottom of the file.</p><p>We then need to reflect the correct bar in the launch script. vim ~/.config/polybar/i3 and change the last line from <em>parrot</em> to <em>example </em>and make the script executable with chmod +x ~/.config/polybar/launch.sh .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Zxs-3draAOOKPFWSwxyRA.png" /></figure><h3>rofi</h3><p>The last piece I recommend is replacing the stock dmenu with <a href="https://github.com/davatorium/rofi">rofi</a>. Again I am not going to run through all the configuration options and themes available, except to say the possibilities are enormous. Reditt as well as other sites have many examples of the uses and themes you can have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a6Ow7ing-nzSbardrn13VA.png" /></figure><p>Here is a simple generic implementation. I pulled the theme from a Reddit post and made a few changes under the hood, namely replacing the keyboard shortcut for dmenu. Now instead of a run box at the top of the screen, I have a mouse aware workspace switcher, run menu, and application menu front and center when I need it.</p><p>Once you have it installed you can do the same by commenting out the existing dmenu shortcut and adding bindsym Mod1+d exec --no-startup-id “rofi -combi-modi window,drun,ssh -theme solarized -font “hack 10” -show combi” to your i3 config file.</p><h3>Wrap UP</h3><p>This is by far the simplest method to use i3 with ParrotOS till the supported version drops. There is no timeframe for this though. If you want a lighter, slightly more performant box, you can use sudo autoremove --purge mate-* and sudo autoremove --purge gnome-* if you really want to take it to that level. I caution, this can be a rabbit hole if you don’t have some experience with Linux, especially networking. Do yourself a huge favor and create a snapshot before doing it.</p><p>In order to get this working, you will need to reinstall several packages, including network management interfaces, a display manager, and some other random packages related to VPN&#39;s.</p><p>This is rather extreme and we will look to tackle this in a future post. The second part to this series will cover some of the configurations in greater detail as well as how to get started creating a custom ParrotOS specific configuration including themes, backgrounds, and adding some additional eye candy including <a href="https://github.com/brndnmtthws/conky">conky</a>, for those that like those things.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=399a118f619f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ParrotOS And Hack The Box Buildout Part 2]]></title>
            <link>https://infosecwriteups.com/parrotos-and-hack-the-box-buildout-part-2-4bf04b0efcd3?source=rss-7d527f570edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bf04b0efcd3</guid>
            <category><![CDATA[vulnhub]]></category>
            <category><![CDATA[parrotos]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[hackthebox]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[matty jones]]></dc:creator>
            <pubDate>Sun, 29 Nov 2020 15:07:57 GMT</pubDate>
            <atom:updated>2020-11-29T15:35:55.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h_FT1Qp3kNlrJMKU0F_qBg.png" /></figure><p><a href="https://parrotlinux.org/">ParrotOS</a> is a relative newcomer in the Linux security and privacy world, having started in 2013. While Kali is a great choice for penetration testing, Parrot is more pliable. It will certainly work out of the box but can be made better with some tweaks.</p><p><strong>Full Disclosure</strong>, I include some links to paid services and subscriptions. I have <strong>no </strong>financial ties to any of them and receive <strong>no</strong> commissions or products from them. Some of them may belong to friends or professional contacts though.</p><p>If you need help installing ParrotOS and getting shared folders to work properly, check out <a href="https://medium.com/bugbountywriteup/parrotos-and-hack-the-box-buildout-part-1-9ced497169c9">part 1</a> of this series.</p><p>As promised part 2 will deal with installing new and updated general use tools as well as configuring an example <a href="https://mate-desktop.org/">Mate</a> desktop environment so you can focus on the task at hand.</p><h3>Initial Update</h3><p>One thing to note, unlike vanilla Kali, ParrotOS does not give the user a re-badged root account. You will see sudo used a lot. I <strong>strongly</strong> urge you to keep it this way. I can’t think of a time when I have needed a root account. If you are doing penetration tests and CTF’s you should have a good grasp on user and group permissions, make any changes that way.&lt;/end_sermon&gt;</p><p>Let’s do an update and upgrade first. There are probably a few popups to read and click yes or no on so don’t stray far or this will turn into a three-hour endeavor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QsXH5kXRhdIinMiK8qMdiw.png" /></figure><p>Do not run the standard sudo apt update &amp;&amp; sudo apt upgrade, this will break rolling distributions. For specifics, check out this <a href="https://www.reddit.com/r/linuxquestions/comments/estn3i/linux_upgrades/">Reddit thread</a>.</p><p>While this is running it would be a great time to learn about the HTB platform and get acquainted with how it works. If you are completely new to it, you could sign-up at the VIP level. The retired boxes all have written and video walkthroughs. Watching the video walkthrough and following along is a great way to get your feet wet and learn a ton in the process.</p><p>If you are strapped for cash <a href="https://www.youtube.com/channel/UCa6eh7gCkpPo5XXUDfygQQA">IppSec</a> is a great choice for the walkthroughs on the retired boxes, this is especially important if a goal is <a href="https://www.offensive-security.com/pwk-oscp/">OSCP</a> prep.</p><p>Pay attention to the methodology used. Developing your own workflow and creating your own automated tools can be crucial and save a lot of time in owning many of these boxes.</p><h3>Shell</h3><p>I am not going to say a lot about shell configurations as most people have strong opinions and can figure out how to configure it to their liking from the massive amount of blog posts out there. I will show the two shells that I find most useful though, along with some simple, universal aliases.</p><p>In part 3, I will walk through my specific ParrotOS <a href="https://i3wm.org/">i3</a> environment including installation, configuration, shell, and, editor choices. It is heavily geared towards penetration testing, and exploit development so please follow me.</p><p>Many like zsh, some may like <a href="https://fishshell.com/">fish</a> as well, both are modern upgrades to Bash and other shells. It comes down to what you feel comfortable using. I would caution you though against writing scripts in anything but Bash for portability reasons.</p><p>If you want to use fish you will need to install it.</p><p>sudo apt install fish</p><p>You can configure it using the web interface with fish_config or via <em>$HOME/.config/fish/config.fish</em>. More info can be found on the <a href="https://fishshell.com/">site</a>. Fish has all of the components I need for a general-purpose system built right in so for me it makes sense.</p><p>ParrotOS already has zsh installed out of the box. The easiest way to set it up is to use <a href="https://ohmyz.sh/">oh-my-zsh</a>. Installing that will automatically set the default shell to zsh. You should also install the <a href="https://github.com/zsh-users/zsh-syntax-highlighting">syntax highlighting plugin</a>. Check out the site for additional configuration options and plugins.</p><p>I typically run <a href="https://starship.rs/">starship</a> on development machines as well. When working with several different languages and environments starship makes it easy to know your repo status, and the language version right on the prompt without having to play with a lot of plugins for various shells. It sits on top of the shell and does the fancy stuff without any configuration.</p><p>It operates with the principle that everything is installed initially and items need to be turned off if you wish to not use them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*8B7O6VDVxCUkD84lGaJcZw.png" /></figure><p><strong>TL;DR</strong> Fish and starship can replace all my zsh plugins and the various debris I have collected over the years, while still allowing me to link my dotfiles in a GitHub repo.</p><p>My personal penetration testing virtual machine is set up differently and significantly pared down and streamlined. Centered around <a href="https://i3wm.org/">i3</a> and zsh, it provides a completely distraction-free, performant environment that stays out of my way. I will talk more about this in part 3.</p><p>Aliases are like opinions, everyone has a list of them. Here are a few I find useful.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e9b276e217a69a26c4c0fb65c6ec7b08/href">https://medium.com/media/e9b276e217a69a26c4c0fb65c6ec7b08/href</a></iframe><h3>Tools</h3><p>Parrot comes with almost everything you need, and in some cases a lot you won’t use. As with Kali though, there are some gaps.</p><h4>Wordlists</h4><p>The standard ones are all there but rockyou is compressed, so you want to uncompress that for starters.</p><p>sudo gzip -d /usr/share/wordlists/rockyou.txt.gz</p><p>The seclists group is a really good one to use for a lot of web-based enumerations.</p><p>sudo wget -c https://github.com/danielmiessler/SecLists/archive/master.zip -O SecList.zip</p><p>This is a big package and once unzipped should be moved to the default wordlist directory /usr/share/wordlists/ You can remove the non-wordlist files if you want, I never bothered. You can also do a git clone directly into this directory but I hate to have repositories everywhere.</p><p>A good compromise may be to drop all these updates and additional packages into <em>/opt</em> and use symlinks or group permissions to configure the needed access if you feel the need to be fancy.</p><h4>masscan</h4><p><a href="https://github.com/robertdavidgraham/masscan">Masscan</a> is one of my favorite tools but there is a bug in the version installed on Parrot as well as possibly Kali that makes it impossible to automate. We need to use at least 1.0.6, which means we need to build from the source.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8a3ffcd7e6e859544457a3728ec7ab6b/href">https://medium.com/media/8a3ffcd7e6e859544457a3728ec7ab6b/href</a></iframe><h4>searchsploit</h4><p>If you want to do local exploit searches, install <a href="https://www.exploit-db.com/searchsploit">searchsploit</a>, which is basically a local version of exploit-db.</p><p>sudo apt install exploitdb</p><h4>random tools</h4><p>I like to have <a href="https://stedolan.github.io/jq/">jq</a> for those times when I need to process JSON on the command line using Bash. You can pretty print, slice/dice, and map various structures. It is much easier than working with sed/awk/grep. I have a fairly long beard now so I switched back to writing Perl after a hundred lines or so of Bash.</p><p><a href="http://lnav.org/">Lnav</a> is a great tool for working with logs and other types of structured files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nsHmBaBGPZbtQvt10r8zMw.png" /></figure><p><a href="https://github.com/sharkdp/bat">Bat</a> is a replacement for cat that has syntax highlighting, paging functionality, and regex searching. I use on occasion for large well-defined files that I don’t want to open in an editor. In reality, I mentioned it because it’s a cool Rust project. Most of the time I tend to use nvim for this task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D57VSaUNnuCe8wPU3d7nxQ.png" /></figure><h3>Pretty Desktop (ADHD and OCD people beware)</h3><p>Feel free to walk away at this point if you already have a desktop you love. I traditionally use a tiling window manager, specifically <a href="https://i3wm.org/">i3</a>, as an easy 80% of my time is in <a href="https://github.com/tmux/tmux/wiki">tmux</a> anyway and I don’t care about a menu. That will all be laid out in part 3.</p><p>For a more general purpose setup, or one for my wife or kids, I stick with <a href="https://mate-desktop.org/">Mate</a> or <a href="https://en.wikipedia.org/wiki/Cinnamon_(desktop_environment)">Cinnamon</a>. I will show Mate here as that is the default ParrotOS desktop.</p><p>To start with, I strip the login window down to a single input box and desktop picker.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2l4V1E0eAN4YR1SrOl5iZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Blhp3JAQdXuJUIcEMoZlHA.png" /></figure><p>When it comes to the desktop itself, I am a sucker for <a href="https://www.nordtheme.com/">Nord</a> and minimalism. It’s set up on the interfaces I use most frequently:</p><ul><li>terminal</li><li>tmux</li><li>nvim</li><li>file manager</li><li>desktop environment</li></ul><p>I also strip all the cruft out, starting with making the upper and lower panel 100% translucent. Then I remove all desktop items.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WEw0EAkbS80yqt5BhPzGHg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NryovE-WuOKt4T7_KuZ3Zg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xtEBkKWWo2RMe3XDK4hNA.png" /></figure><p>I also strip out stuff I don’t need from the system tray. Keep in mind this is a VM, on bare metal or general purpose systems you will need some of these applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v2CDfXTWO6hvTDcFKNOqNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D-1PESmTzsYqmVbsl2z34Q.png" /></figure><p>I also remove any of the panel items that do not serve a very specific purpose, such as the workspace shifter, extra custom launchers, and application menus.</p><p>The final result is a fairly distraction-free UI that allows me to just focus on the tasks at hand. This is simpler to do with a virtual machine as I don’t need to worry about Bluetooth, battery, and other common widgets because I can simply go to the host.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*869IQLRnm2l1l4Zzm3KimA.png" /></figure><h4>Wrap up</h4><p>By no means is this a perfect setup out of the box, nothing ever is, but once you get it up and running with a basic configuration and fill in some of the tooling gaps you’ll be good to go. You may want to customize your desktop further or install additional tools, the choice is yours.</p><p>As I said earlier, I prefer tiling window managers, in my case i3. The next part will focus on this. Please follow me to get notifications when it drops.</p><p>Other planned posts will go into further details, focusing on editors, debuggers, and other analysis tools and tips useful for exploit development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bf04b0efcd3" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/parrotos-and-hack-the-box-buildout-part-2-4bf04b0efcd3">ParrotOS And Hack The Box Buildout Part 2</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ParrotOS And Hack The Box Buildout Part 1]]></title>
            <link>https://infosecwriteups.com/parrotos-and-hack-the-box-buildout-part-1-9ced497169c9?source=rss-7d527f570edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ced497169c9</guid>
            <category><![CDATA[hackthebox]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[parrotos]]></category>
            <category><![CDATA[vulnhub]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[matty jones]]></dc:creator>
            <pubDate>Tue, 24 Nov 2020 15:33:32 GMT</pubDate>
            <atom:updated>2020-11-29T15:10:35.736Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h_FT1Qp3kNlrJMKU0F_qBg.png" /></figure><p><a href="https://parrotlinux.org/">ParrotOS</a> is a relative newcomer in the security and privacy Linux world, having started in 2013. While Kali is a great choice for penetration testing, Parrot is more pliable. It will certainly work out of the box but can be made better with some tweaks.</p><p>A lot of this series is general tools and settings that will benefit most anyone using <a href="https://www.hackthebox.eu/">HTB</a>. The finer details of which shell to use or how to set up an editor are very subjective, and therefore I keep those topics to a minimum in a later post. I will merely offer some useful aliases and other notes that I have found helpful.</p><h3>Prep</h3><p>Download the <a href="https://www.parrotsec.org/download/">iso</a> of your choice. I tend to go with the security mate version and will be using version 4.10, the latest stable release, for this walkthrough.</p><p>My virtual host is VMWare Fusion 12 on macOS Big Sur, and I use BIOS as my firmware of choice. I gave it a 60GB disk and 8GB of ram. Those resources are probably overkill, but I have them to spare, so why not.</p><p>While you certainly can install ParrtOS on bare metal, you should use a virtual machine if you are doing exercises like this. Not saying you are at risk, but these are hostile networks you are playing in.</p><h3>Virtual Machine Setup</h3><p>Create a new virtual machine using the ISO you chose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cdzKz2ZV_nwkRmSiR4pGYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yEFeu1MAXvDrFPaPTV32gA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyUUdn5L7YxYJMO-_OQ14g.png" /></figure><p>Click finish or customize the settings and available resources. One thing to keep in mind is that the network settings should stay NAT and autoselect. Selecting a bridged network may open the host up to malicious traffic.</p><h3>Installation</h3><p>Boot into the Live installation, which is the first item in the boot menu and the default choice. From here on out, the choices are the same regardless of where you are installing the OS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohNqHQPeh0W-6bWBtNseQQ.png" /></figure><p>Click on <strong>Install Parrot</strong> and then click through the menu till you get to Partitions. I recommend you choose to erase the disk and let it partition automatically. It’s your choice to encrypt or not, I never bother encrypting VM’s as my host is always full-disk encrypted, and I turn it off when not using it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQ-eD78AgoUP829SMj7Kmg.png" /></figure><p>Add your login details. I personally never set my machines to log me in automatically, but feel free if you want to for ease of use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J3ngU9omR6OHeMzOdD7MYA.png" /></figure><p>Review all the settings and make sure everything is as it should be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1nGNxXRSdKupKtuOBzFmWg.png" /></figure><p>Go ahead and install. This will take a while, so if you haven’t already, go <a href="https://www.hackthebox.eu/invite">sign up</a> for HTB. When this finishes, restart the machine and select the first item on the boot screen which again, is the default.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zrIFHkHjfeeoMvi6-Ud2OA.png" /></figure><h3>Sharing</h3><p>Let&#39;s set up the sharing as that will make things a whole lot easier. This will also enable cut and past between the host and the virtual machine if it does not already work. At this point, I would create a snapshot so you have a functional clean image in case something breaks.</p><p>I put the folder I want to share at my root, but really the location does not matter as long as you have the proper permissions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hMdAmt0RNqiiTt0RsNRLOQ.png" /></figure><p>Now we set it up in the VMware settings. Don’t worry about the warning message at the bottom. It is shown regardless.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*va9Ben4L092EZgwrjjV2Lg.png" /></figure><p>We now configure it in Parrot. After you update <em>/etc/fstab</em> bounce the box just to make sure all is light and bright. If you get an error message saying root is locked and you end up in a loop, the restore the snapshot you created and double check your fstab line. If you are following this, it is all but certain you mistyped something in there.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4231ebe05fdcd68ebf349e6033605c6a/href">https://medium.com/media/4231ebe05fdcd68ebf349e6033605c6a/href</a></iframe><h3>Next Steps</h3><p>At this point, you have a very capable foundation for working on HTB and various types of CTF’s. A few tweaks, though, can go a long way towards making your life a little easier and the OS a little more comfortable.</p><p>If you are more inclined towards the Offensive Security side of the fence, adding some additional tools and updating others would be a good idea.</p><p>If working on bug bounties, malware analysis, and exploit development, there are some additional tweaks that make development and debugging tasks easier.</p><p>Continuing with <a href="https://medium.com/bugbountywriteup/parrotos-and-hack-the-box-buildout-part-2-4bf04b0efcd3">Part 2</a>, we will dig into OS updates, an upgraded environment, additional tooling, and fixing some bugs in Parrot that are also present in other security-related distributions.</p><p>Further additions to the series will include methodologies, specific techniques, write-ups, and live hunts through the deep and dark web, using this specific box.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ced497169c9" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/parrotos-and-hack-the-box-buildout-part-1-9ced497169c9">ParrotOS And Hack The Box Buildout Part 1</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Human Side of Secure Development]]></title>
            <link>https://medium.com/salesforce-engineering/the-human-side-of-secure-development-24080963b99c?source=rss-7d527f570edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/24080963b99c</guid>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[matty jones]]></dc:creator>
            <pubDate>Wed, 09 Jan 2019 16:51:00 GMT</pubDate>
            <atom:updated>2019-01-09T16:51:00.789Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iCHk6wiBkWxocDOo9Ociiw.jpeg" /></figure><p>DevSecOps — what does that even mean these days? The truth is, it means a lot of different things to a lot of different people. Like its counterpart DevOps, which means to bridge the gap between development and operations, I believe DevSecOps means to bridge the gap between development, security, and operations.</p><p>The focus of this post will be to bridge the human gap between security, development, and the users. We will start this process by talking about a few of the common interactions developers usually have with security teams and how they can be made easier and more productive. In a future post, we will lay out some tools that will also greatly aid in this process.</p><p>For perspective, my background is in Operations, Support and Infrastructure Engineering. I have since transitioned over to Infrastructure Security, with the primary responsibility of helping teams build security from the outset rather than a tacked on measure.</p><p>In today’s Infrastructure Engineering circles, we have a concept of Infrastructure As Code (IAC). The basic idea of this is that you codify not only the products, but also the pipelines used to build them, and the server architecture used to run and manage them. This has brought much needed discipline to infrastructure and leads to the first item on our list.</p><h3>Infrastructure Engineering == Software Engineering</h3><p>It may not be Java or .Net, but working with <a href="https://www.chef.io/">Chef</a>, <a href="https://puppet.com/">Puppet</a>, and <a href="https://www.terraform.io/">Terraform</a> is most certainly worthy of being called software development and even Software Engineering. The code certainly needs tests, and it should be stored in a revision control system and documentation consummate with its complexity needs to be written.</p><p>The testing and documentation will go a long way towards showing your security team that your infrastructure is solid, has the proper posture and takes threats seriously. Storing the code in a repository will provide the audit capabilities that keeps everyone honest. It also provides the benefit of increasing productivity by providing new workflows for development teams.</p><h3>The First Day of School</h3><p>Many times when beginning the software development process, the first step(s) include requirements gathering. There are several points that could be made here that will be incredibly helpful and will make the security and developer interactions flow better. The most important thing to do is to build a rapport with the users and with security. It is much easier to work together if you can share a common goal.</p><p>The users have to get something done, the developers need to build something useful for them, and security needs to ensure the company and users are safe. The common thread here is getting the task accomplished in a safe and efficient manner. From a security perspective I would rather not say no to a project that a team is working on, and I am sure most security people would agree. I can’t say yes to what I don’t understand though. Try to develop some shared experiences, find some common ground that a relationship can be built from, and have some empathy.</p><p>Most security professionals are aware that security may not be the first priority for a development team and want to help. The user just wants their widget and most likely has no clue how to build it and what the development process entails. I have found the best way to improve the relationship between users and developers is to involve the users as much as possible. Explain to the users why the security controls are necessary, and you empower them to be invested in the security process.</p><h3>What is …</h3><p>Just talking with the users is not enough, you need to ask questions. I can’t tell you what questions to ask as that is very subjective. I can say that in my experience asking the right questions was the difference between a successful design that would not draw red flags and a project that would end up with serious refactoring at a late stage.</p><p>The classic example is asking what ports need to be opened on a firewall. This is a fairly simple question, but don’t forget the user may not understand networking or security. For example, you may open port 456 on the firewall for tcp connections, but the user is actually using udp.</p><h3>Driven by Design</h3><p>The collaboration doesn’t end with asking questions. Once you have finished with the questions and created a design, you should engage security and have them help with a design review at this point before any code has been written. Engaging early will give security and the development teams plenty of time to work through any sticky points and save the project from costly late-stage redesigns.</p><p>After this is complete, it is time to take the design back to the users and review it with them as well. This will avoid any other late-stage issues where users were under a different assumption than the development team. The key here goes back to building a rapport. These meetings, while time-consuming and certainly not what everyone wants to be doing, are critical to a successful project.</p><h3>Web Scale…Not so much</h3><p>Most of developers don’t need to roll their own major tools. Many companies, especially those operating at an exceptionally large scale, have written and open sourced their toolkits. More importantly they have built a community around those tools and continue to support them. Whenever possible these or other open source solutions that have wide exposure should be used. If the use case or tool is common enough, security may have already vetted it and you can just go on your merry way.</p><p>Trying to roll your own homegrown monitoring solution, which seems to be a common thing these days, is generally not necessary and will only lead to long meetings with security and users when your glorified command and control server is rooted due to a bug in some functionality. The message is simple, please don’t roll your own tools unless you really need to. Your users will thank you, future maintainers will thank you, and security will certainly thank you.</p><p>These are but a few thoughts to get you pointed in the right direction. Later I can talk about several software tools that can be used to make everyone’s life a lot easier and help hold the momentum through the various design iterations.</p><p><em>Originally published at </em><a href="https://www.devseccon.com/blog/2018/11/07/the-human-side-of-secure-development/"><em>www.devseccon.com</em></a><em> on November 7, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24080963b99c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-engineering/the-human-side-of-secure-development-24080963b99c">The Human Side of Secure Development</a> was originally published in <a href="https://medium.com/salesforce-engineering">Salesforce Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>