New bag of holding

Rothco Vintage Classic Army Messenger Heavy Weight Shoulder Bag

Rothco Vintage Classic Army Messenger Heavy Weight Shoulder Bag


I have been carrying a Targus laptop backpack around with me for years. Well, let me qualify that a little. I have been carrying that around with me for years while I have been trying other bags.

Honestly, I was perfectly happy with that Targus bag for the longest time, until I got old 🙂 In the last 4 years or so, I have had some issues with my right shoulder, and slinging that backpack around on that shoulder has occasionally aggravated that. I know what you are saying, why not wear that backback as a backpack? Well, there are a lot of reasons like accessibility and convenience and comfort, along with the face that it makes me look/feel like more of a geek/dork/fat than I am already.

I tried to find a good sling backpack, but they are all either ridiculously expensive, cheaply made, too small or the sling is on the right hand side. Most recently I tried a Solo messenger bag, which worked in form factor, but had it’s own issues like the pocket in the flap bulged out nasty when used, the flap closure clip was single in the middle of the bag which made the bag front roll up on the corners, and the pockets just weren’t adequate enough for my space needs.

Enter the last try, the Rothco Vintage Classic Army Messenger Heavy Weight Shoulder Bag. This is a messenger-style bag made out of heavy/durable canvas material. It has 2 roomy front pockets big enough for me to carry all my odds and ends including my Kindle, usb drives, mail, my little travel hygene/medial kit,etc. The 2 side/drink pockets are great Normally those kinds of pockets are only 3 or 4 inches of mesh, but these are almost full bag height solid canvas pockets which work fantastic for carrying things like all my assorted cables and my glasses case, etc., and can be secured with snaps at the top. There is one small zippered pocket on the inside that is big enough to carry all your assorted pens and paraphernalia. Lastly the single main interior compartment is quite sizable. Although not padded for laptop carry itself, you could easily fit a 15″+ laptop in there with plenty of room to spare for your chargers, books, papers and probably your lunch too. Also, worth noting is that the bag, even when packed, does not look oddly malformed or too bulky to carry comfortably.

I mentioned previously that this was made of durable heavy canvas. That level of durable construction appears in every aspect of the bag. The stitching is solid, the hardware all the way around is metal and build for hard use. I am quite impressed with the strap itself. It too is made of a wide width heavy canvas, attached directly to the bag and is not removable. Many other messenger bags use cheap plastic clips or thin metal dog clips which invariably bind up on something and detach at the most inopportune moment. An added bonus of the strap being canvas is it does NOT slide off my shoulder 🙂

All in all it’s a great bag and so far I am quite happy with it. For around $25 you just can’t beat the price. I highly recommend this for the rest of you commuters, it gets 2 thumbs up!

twidge on CentOS

A couple days ago I was reading a post from Knightwise and he mentioned using twidge on his server to do some fun stuff with his twitter account. Well! That sounded to me like just the thing for me to get some use from my neglected twitter account. Unfortunately, twidge is really best used on a debian type system and *my* server runs CentOS 5. This is a simple recipe to shoehorn twidge onto a CentOS 5 server.

I downloaded the twidge binary from https://github.com/downloads/jgoerzen/twidge/twidge-1.0.6-linux-i386-bin

The binary requires libcurl-gnutls which CentOS just doesn’t have. I snuck around that by doing

ln -s /usr/lib/libcurl.so.3.0.0 /usr/lib/libcurl-gnutls.so.4

Then the binary told me it needed libffi. This I could get from the epel repository. Do that by doing

rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm

and then

yum install libffi

That gets twidge working ….. mostly. Because of the sneaky I pulled with that libcurl-gnutls thing, twidge generates an error message on each run. It still works fine, but gives me a message on each run:

twidge: /usr/lib/libcurl-gnutls.so.4: no version information available (required by bin/twidge)

Undaunted, the easy fix for that is to dump the unneeded error to /dev/null like so

twidge lsrecent 2> /dev/null

And there you have it! For those of you looking to employ twidge on CentOS or similar Linux, this will get you going pretty quickly. Enjoy and I’ll tweet ya later!

Rsync bug

rsync

rsync


Bitten by the rsync bug? I was. Apparently in the new RHEL 5.7, and I am sure the RH clones like CentOS, Scientific Linux and ClearOS(?) as well, there is a bug in rsync when you use it with ssh transport like so:

rsync -avz -e ssh remotehost:/data /data

The fix is to make sure to append a username to your host and then it magically starts working properly again.

rsync -avz -e ssh username@remotehost:/data /data

Enjoy!

Make it pretty!

   I have had to spend a lot of time this week on my netbook. Normally I really dig the Linux Mint background, but the light background of Mint 11 on my little netbook was just too bright and annoying to me for some reason. So, I set out to find something a little darker.
   Where do you go for a really great wallpaper? Well, my friend Bill just happened to post a link to probably the greatest wallpaper site I have ever seen at http://wallbase.cc/. Warning! You can easily lose several hours looking through wallpapers there.
   Changing your background in Mint or any other Gnome 2 using distribution is pretty straight forward. You right click on your desktop, select “Change Desktop Background” and then pick the one you want. You also have the ability to add other wallpapers not already in your background collection with the “add” button.
   Changing the login screen to match is a different matter altogether. I have found that the easiest way to accomplish this is to install http://ubuntu-tweak.com/. This is a great little package that will let you change all kinds of hard to find settings not the least of which is the login screen background. On ubuntu-tweak, youy simply select login settings, then unlock, click on the old wallpaper, surf to and choose the new one you want, then quit.
   Lastly, there is changing the “lock screen” wallpaper. This is the screen you are presented with when you unlock your computer after locking your session with a -l (that’s an L by the way). I thought it was really odd that that wallpaper isn’t controlled by the login wallpaper, but a little digging revealed a way to change this as well. There is a cute little command line trick to it:

sudo gconftool-2 –direct –config-source xml:readwrite:/etc/gconf/gconf.xml.defaults –set /desktop/gnome/background/picture_filename –type string `gconftool-2 –get /desktop/gnome/background/picture_filename`

(note that the above command is all 1 line)
and then:

killall gconfd-2
killall gnome-screensaver

And that’s it folks! Again, this should all work on any Gnome 2 desktop.

Pakt Publishing WordPress Month!

Many of you know I do book reviews for Pakt Publishing. Well this month is their WordPress Month where they are offering some great special offers on some cool WordPress books. This is the software that runs bunches of your favorite websites, including this one 🙂 So, head on over to http://www.packtpub.com/article/wordpress-month and get a great deal on some cool tech books today! They even offer e-books to help fill up your Kindle / Nook!

Book Review – BackTrack 4: Assuring Security by Penetration Testing

Backtrack4


Right after I got this book, Backtrack 5 was released. My intention was to go through the book and compare/contrast things to Backtrack 5. Well, we all know the saying about the best layed plans…

That being said, I believe the information in this book to be directly applicable to Backtrack 5 and a good reference for it!

The book is a great tutorial and walk-through on how to use Backtrack for security and penetration testing, but, more than that, it offers good information about the field in general. You will go through software installations, software overviews, methodologies, tests / testing, and my favorite part, reporting and deliverables, a MUST for professional computer people.

I think this is an excellent book to add to your knowledge arsenal and you may be surprised at just how much you didn’t know. I know I was. This really is an important subject for computer professionals and I cant think of a better way to brush up than by grabbing a copy today. Thumbs up!

Mint 11 Boot Splash

I have seen a lot of commenting on the decision to use a black screen as the boot splash on Linux Mint 11. One person summed it up well when they said that that black screen is indicative in many other operating systems as something going wrong and it tends to scare people. Well, that being the case, if you are scared or if you just like to see what’s going on behind the scenes like I do sometimes this is how you can fix that fairly easily.

Open up a terminal and do a:
vi /etc/defaults/grub

scroll down to the line that says:
GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”
and change it to:
GRUB_CMDLINE_LINUX_DEFAULT=””
and save the file.

After that do a:
update-grub

When that is finished, reboot your machine and enjoy watching the text based boot process as it occurs. Pay close attention, though, ’cause it sure doesn’t last long! 😉

Why I use OSSEC

There are some great reasons to use OSSEC. One of them is you get emails like these I received this morning:

Jun 10 09:24:51 pukwudgie sshd[28651]: Failed password for invalid user pureftp from 202.121.49.62 port 45542 ssh2
Jun 10 09:24:48 pukwudgie sshd[28651]: Invalid user pureftp from 202.121.49.62
Jun 10 09:24:29 pukwudgie sshd[28630]: Failed password for invalid user tom from 202.121.49.62 port 37388 ssh2
Jun 10 09:24:28 pukwudgie sshd[28630]: Invalid user tom from 202.121.49.62
Jun 10 09:24:11 pukwudgie sshd[28628]: Failed password for invalid user peter from 202.121.49.62 port 57468 ssh2
Jun 10 09:24:09 pukwudgie sshd[28628]: Invalid user peter from 202.121.49.62
Jun 10 09:23:52 pukwudgie sshd[28610]: Failed password for invalid user thom from 202.121.49.62 port 49315 ssh2
Jun 10 09:26:39 pukwudgie sshd[28730]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.121.49.62 user=root
Jun 10 09:25:43 pukwudgie sshd[28690]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.121.49.62
Jun 10 09:25:24 pukwudgie sshd[28672]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.121.49.62
Jun 10 09:25:05 pukwudgie sshd[28653]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.121.49.62
Jun 10 09:24:48 pukwudgie sshd[28651]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.121.49.62
Jun 10 09:24:28 pukwudgie sshd[28630]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.121.49.62
Jun 10 09:24:09 pukwudgie sshd[28628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.121.49.62Jun 10 09:44:08 pukwudgie sshd[29440]: pam_succeed_if(sshd:auth): error retrieving information about user recruit
Jun 10 09:44:46 pukwudgie sshd[29478]: pam_succeed_if(sshd:auth): error retrieving information about user office
Jun 10 09:45:25 pukwudgie sshd[29497]: pam_succeed_if(sshd:auth): error retrieving information about user tomcat
Jun 10 09:45:05 pukwudgie sshd[29480]: pam_succeed_if(sshd:auth): error retrieving information about user samba
Jun 10 09:45:42 pukwudgie sshd[29514]: pam_succeed_if(sshd:auth): error retrieving information about user webadmin
Jun 10 09:47:02 pukwudgie sshd[29555]: Failed password for invalid user spam from 202.121.49.62 port 45351 ssh2
Jun 10 09:46:59 pukwudgie sshd[29555]: Invalid user spam from 202.121.49.62
Jun 10 09:46:43 pukwudgie sshd[29538]: Failed password for invalid user ssh2 from 202.121.49.62 port 37198 ssh2
Jun 10 09:46:40 pukwudgie sshd[29538]: Invalid user ssh2 from 202.121.49.62
Jun 10 09:46:03 pukwudgie sshd[29518]: Failed password for invalid user jambo from 202.121.49.62 port 49116 ssh2
Jun 10 09:46:01 pukwudgie sshd[29518]: Invalid user jambo from 202.121.49.62
Jun 10 09:45:45 pukwudgie sshd[29514]: Failed password for invalid user webadmin from 202.121.49.62 port 40961 ssh2

Etcetera, etcetera…

Please excuse the mess…

Something odd with the LinuxPlanet.Org blog site right now. Many multiple posts. I hope i have a handle on it and this is the test! Please disregard 🙂

Mint 11 / Ubuntu 11.04 – vpnc+ssh issue

Linux Mint


Yes, I know.. Long time since a post, but I have been waiting ’till I had something interesting to comment on 🙂

You should all know by now that Ubuntu 11.04 and Mint 11 are now out in the wild, and both are very nice IMHO. I have been a “Minty” guy now for quite sometime but I thought it would behoove me to at least try the new Ubuntu 11.04 and it’s Unity interface, so I stuck it on a netbook to test it out and I can say this: It doesn’t suck at all! In fact, I was pleasantly surprised. Compared to Gnome 3 (more on that later), Unity is quite usable.

That brings me to Mint 11. A beautiful distribution as I have come to expect. Not too much to say about it for those familiar with Mint except it’s a worthy successor in a long line of great releases. If you haven’t yet tried Mint, you are really doing yourself a disservice.

There are of course problems with everything. Mine was with my vpn connection. I use vpnc to connect to my works’ cisco vpn, and I have been doing so successfully now for many years. In fact, vpnc is my preferred method of connecting over any other client including the cisco client itself. It just works. It’s very easy to configure and use and it stays out of my way. That is until recently.

After I installed Mint 11 on my daily carry, I eventually needed to vpn into work and fix something. Well, I immediately noticed that ssh through vpnc would not connect. I could ping, http, rdesktop, whathaveyou, but no ssh. I looked at the routes, I looked at the tunnel, I looked at the verbose messages from vpnc. Nothing worked. If, however, I walked over to my other laptop that is running Mint 10 with the very same vpnc config, I got right through. This was quite perplexing. I eventually tried connecting with the Ubuntu 11.04 install, and I got the exact same results. I was grasping at straws. Maybe all new distributions were broken in this manner? The horror actually forced me to install Fedora 15 (sorry Fedora folks) and test that. To my surprise, F15’s vpnc+ssh worked just fine. This also gave me an opportunity to find out how dysfunctional and horrible an interface Gnome 3 is (KDE and Unity are gonna become big real soon I guarantee it).

As a last ditch effort to narrow things down, I decided to try a different ssh client. I tried both putty and dropbear. THEY WORKED! YAY! This meant I could go back to running the new Mint on my netbook. I fully intend to just try my own compile of ssh sometime in the future, or perhaps the package maintainers will catch wind of this and fix it (I did send some emails to Clem). Until then, I am happy that I can still use my beloved Mint and I can live temporarily with dropbear and / or putty for ssh through my vpn when I need it. I just hope this post gets around a bit so the other guy that uses vpnc+ssh to connect to his cisco vpn doesn’t think he’s going crazy like I did 🙂