A few months ago the company that I formally had my site (and a few others) hosted on was purchased by another big company that I don’t like. Although they stated that they were going to operate independently, within a short amount of time I started to notice some degradation of the services. This was probably due to the networks being merged, or possibly the cloud offerings being moved to a new datacenter. Whatever the reason I felt that this was probably a first sign that things were going to change one way or another, so it was time for me to move on.
Since I have talked about private clouds before, I decided to set up my own little private cloud. So I picked a provider, spun up a few servers, and started going through the motions of getting them ready to host sites. A few days later, here we are, in my new little home. So far so good. Got everything set up on a few different servers, using both private and public connections, and got monitoring set up on the servers as well.
There is probably some stuff that hasn’t moved over yet, but everything should be completely back up in a few days (including all the project2501 downloads).
Unless you are living under a rock (no offense to my rock-dwelling friends) you have heard at least some of the news surrounding the NSA and their broad spying programs in the US and abroad. The fallout has not been small either, companies like Groklaw have had to shut down because email can no longer be considered even the least bit secure. Companies that did offer some great encrypted services, such as Lavabit or Silent Circle, have either had to shut down or preemptively shut down because the NSA is now requiring them to hand over encryption keys (although this might not have been explicitly stated in the news outlets, anyone with a brain can figure out this is the reason). Companies like Google, Microsoft, Dropbox, and other cloud providers are keeping their collective mouths shuts (because they have to) about how much of your data is accessible to the NSA … here’s a hint, all of it.
Being the command line junky that I am (and working remotely via ssh all the time) led me to want to make vim a little more user friendly for working with python code. Don’t get me wrong, the basic features that vim includes by default (such as syntax highlighting) are great for quick tweaks or quick little scripts, but I wanted something more robust than that. Basically I wanted syntax highlighting, auto-spacing, code completion, documentation look-up, and syntax highlighting.
Every so often I get tired of paying for services that I deem I can do myself. This was the case this weekend when I was working on some python code and wanted to have it tracked in git. I have a github account, but I didn’t have any private repositories left open. I really didn’t feel like paying for more repositories, so I started looking into hosting my own git server. I didn’t really need multiple user management, which is what programs like gitolite offered, but I did want a good front end web interface for people to be able to easily pull and look through any code I did post. Essentially I really liked what github did, but didn’t really want to continue using it. Anyway, after some searching around I found gitlab, which is (from what I can tell) almost an exact clone of github.
I pretty much followed the guide verbetim from the gitlab github site (I know, ironic isn’t it). I did however substitute public-gitlab for gitlab code so that people can browse the code without having an account. All you have to do is substitute the instruction for public-gitlab when you get to section 6 of the gitlab install. It sounds complicated but it’s really not.
So now I have my own gitlab server, and all the files for anything I post here (such as the project2501 repo, or my config files for xmoand) will now be posted on the site.
lifeafter2am gitlab server
After struggling for quite some time getting metasploit to play nicely with arch linux, I found that if you use rvm to install ruby-1.9, and set that to the default ruby environment, it installs quite easily with the bundle command:
$ cd /usr/src/metasploit-git
$ bundle install
New build of project2501 up that now includes the tools in the BlackArch repository. For those who don’t know, BlackArch is a repository (and soon to be live distro) that is like a Kali (or BackTrack) but is built upon Arch Linux. I included this repository because it makes it much easier to get the security tools I use on there, without having to do as many custom repo stuff on my end.
The only drawback thus far is that increased size of the image. This was to be expected, and it’s still smaller than Kali or any of the other live security distros out there, coming in at 2.6G. So at least it fits on a 4G USB drive.
There is still some stuff that doesn’t work quite right (like Metasploit), and some other stuff that needs to be edited, but its moving along quite nicely.
Download on the download page.
Finally got around to updating the scripts and getting all the packages compiled for a dual architecture build of the distro. Almost nothing has changed, except all the normal Arch updates and stuff that has happened in between now and the last build. Otherwise everything else is the same, just updated.
File size is obviously larger now, but it’s still pretty small overall at 1.4G which I am okay with for having dual architectures.
Download is on the download page.
So as I was building the new version of my distribution, there are a few packages that need to be compiled from the aur and then added to a custom repository. In the past this wasn’t an issue because I only had the i686 version of the distribution. But now with the dual architecture version of the distribution I had to find out how to make the repository take both i686 and x86_64 versions of packages. The documentation on the wiki page wasn’t clear on the issue, so I figured I would quickly type up what I did here. »Read More
I found this online and it is super useful for me. I do most of my work in the terminal, so with lots of terminal emulators open, some with active SSH connections, you don’t want to loose what you are working on if you accidentally kill a terminal window or the X server. Tmux solves this problem, and it is easy enough to log into the machine in question and simply type ‘tmux’ or ‘tmux attach’ to get back to where you were. I thought about putting something in my .zshrc though that would automatically either start a new tmux session, or drop me back into the old one where I left off, but low and behold there was already some code out there on the Arch Wiki. Although it is written for the bash shell, I have found that this works for zsh as well:
if which tmux 2>&1 >/dev/null; then
test -z "$TMUX" && (tmux attach || tmux new-session)
Simple enough, and now I will always be in a Tmux session and don’t have to worry about getting busy and forgetting to do it.
I keep a Windows partition on my machine just for gaming and other things that I might have to do for work. I had some motherboard issues, and ended up having to replace the whole motherboard. I booted into Windows and low and behold I now have to reactivate it. I already had to go though that phone bullshit once on this machine (wouldn’t activate online), I’m not doing it again. Seriously though, a slight hardware change (same make/model motherboard) and you freak out and make me reactivate the computer all over again?? What irritates me even more is that if you don’t activate all it does is annoy you about doing it. It doesn’t hinder the OS at all (minus not being able to change your lockscreen picture and shit like that), everything still works. So basically people who do want to steal this godawful software can deal with the little annoyances since they got it for free. Meanwhile, you take customers who actually shelled out money for this shit (luckily it was a company expense) and annoy the piss out of them until they spend 15 minutes typing (or reciting) numbers into an automated number. If your not going to lock the software than quite frankly its stupid to do anything at all.
This is why I almost never boot into Windows .. gah, such bullshit.