Welcome back, this will be the last post in the build process for the Xubuntu OSINT system. After I finish this post, I’m going back to Michael Bazzell’s video training courses, which is why I built the VM to begin with.
Welcome back. Sorry about the delay, but I wanted to get the post about fixing the NAS posted before I continued. This post has also been sitting waiting for editing for a bit. Picking up where we left off, I’m going to discuss the changes between Michael Bazzell’s book, and my experiences of setting up the system using Xubuntu.
Shortly after rebuilding my Raspberry NAS last year, it stopped working again. The system wouldn’t boot right, even after changing the micro-SD card with a new build of Raspbian. A few weeks ago, I bought a new Pi 3 b and rebuilt the NAS again. When the system powered on, one of the USB drives wasn’t working. It looked like the file system was corrupt. During attempts to recover the USB drive, it stopped being readable. Both my Windows and Linux computers could see the USB drive, but not the file system, or the data. I re-formatted the disc drive, and it started working fine, it just had no data on it.
Sorry, this was a little late, I spent the last few weeks rebuilding my Raspberry Pi NAS, again. I’ll be doing a write up on that in the near future.
This post is the fourth part of the series building my OSINT VM to do Open Source Intelligence. These are my experiences using a different Xubuntu for my base, compared to Michael Bazzell’s walkthrough in his book, which used Ubuntu.
There are two sections to this posting. Chrome, and TOR. Though I didn’t do much with TOR.
Welcome back to my series of setting up Virtual Machined to do OSINT. I’m setting up an OSINT investigation system based on Michael Bazzell’s 7th Edition OSINT book, but I’m using Xubuntu instead of Ubuntu. Remember, this series is about the differences I found between the walkthrough in the book and setting up my environment on a different Distribution.
In this post, I’ll be talking about the personalization steps covering the differences between Michaels’s text and the steps to do the same in Xubuntu. As I stated in the last post, I’m building a new OSINT Investigations VM based on Michael Bazzel’s book. In the previous post, I covered the differences between his book and my choice of using Xubuntu instead of Ubuntu.
In the latest edition of his book, Michael Bazzell has decided to teach OSINT investigators to be self-sufficient when it comes to their tools. Gone is his OSINT powerhouse VM Buscador. Gone are the free tools he used to host. Instead, because things change and disappear, he has decided to teach people to build their own tools.
He uses Ubuntu as the base for the Virtual Machine in the walkthroughs. I didn’t care for Ubuntu, mainly because I’m not too fond of the default desktops. Honestly, I prefer running Debian with XFCE. But for quick installations, I go with Xubuntu. I say quick installs because it usually works out of the box, whereas Debian usually takes me days of tweaking to get it right.
In the past, before his old investigation image, and it’s replacement Buscador, I would build my own VMs based on either Debian or Xubuntu, and replicate the things he had done in his builds. This time around, I decided to build my own Xubuntu image, following his guide for the tools.
Here are the things I had to change to get Xubuntu based system set up.
I got an email saying that my site auto-upgraded. I wasn’t happy about it, some of the settings I on the server should have prevented that. But it did the auto-upgrade anyway.
When I logged in, the dashboard said to update to PHP I checked the terminal, since I’m self-hosting, and saw I had the newest available in the repo installed on the server. I had to do testing to find out, no it kept pulling the older version.
I searched around, and all the howto guides were for people using Cpanel or some other hosting tool. They also suggested the PHP text tool. Which I used, and it said all my plugins would work. But the howto guides for hosted accounts past that point wouldn’t work for me though. I’m self-hosted. I finally found a blog post by someone saying what to change, the webserver to point to the right files. So I did.
And the site broke.
The error wasn’t much help, but more searching found I could turn debug on get better information. So I did that. The page was tossing errors. Google those, and found a walkthrough to fix Crayon Syntax Highlighter.
I also had to toss Attack Scanner, which made me sad, but that plugin was shut down in 2017.
And I thought getting Let’s Encrypt fixed a couple of weeks ago was a pain.
Over the weekend I updated my mail server. Turns out if you have Dovecot installed and configured with Postfix, and Dovecot fails, Postfix stops working too. When I was trying to fix Dovecot I had mail in my mailbox, I could see it if I ran the mail command on the server. But I couldn’t see the email in my desktop client. After fixing Dovecot, I couldn’t see any new email in either place.
There was a poll on twitter recently asking about making a new blog. My suggestion was to self-host WordPress on a VPS, and then use the attacks against both as case studies for the blog itself.
The real question comes down to, “what is your goal?”