rabbitmq basics

A quick guide to some basics of running a RabbitMQ server:

Start the service:
service rabbitmq-server start

Remove the default ‘guest’ user:
rabbitmqctl delete_user guest

Set up a new user for administrative purposes:
rabbitmqctl add_user <admin_user> <password>
rabbitmqctl set_user_tags <admin_user> administrator

Set up a new user for the specific instance (vhost) you’ll be using:
rabbitmqctl add_vhost <vhostname>
rabbitmqctl add_user <username> <password>
rabbitmqctl set_permissions -p <vhostname> <username> "^<username>.*" ".*" ".*"

Check that everything looks OK:
rabbitmqctl list_vhosts
rabbitmqctl list_users
rabbitmqctl list_permissions -p dev
rabbitmqctl status

 

notes on using Kali Linux – KDE version

For some reason, the folks at Offensive Security removed the KDE build of Kali from their download list (the Enlightenment, XFCE, and LXDE versions are still there, but KDE is absent). Since KDE is my preferred window manager, this made me sad, until I found out you can grab them in the weekly and daily builds.

Once I had Kali/KDE up and running, the first thing I noticed was there was no GUI way to manage network interfaces. Having a background in Linux sysadmin, that wasn’t a huge obstacle – ifconfig, iwconfig, wpasupplicant, all were there and working. However, anyone that’s ever had to configure a WPA2/PSK interface by hand can testify that this is one of the few places where having a simple GUI management interface is just plain nice to have. I did some digging, and discovered that the problem was the plasma-nm applet was not installed. A simple apt-get install plasma-nm took care of that problem – and handily pulled in all the required dependencies for the rest of the KDE network management tools as well.

Other than that, the rest of the stuff I like about KDE was there, along with all the usual Kali tools and resources. Finally, I get the best of both worlds!

DROWNing in bad crypto

If you are still running SSL to “protect” your website at all, you need to shut it off. Yes, really.

If you have some kind of load balancer in front of your server, disable SSL on that also.

Using SSL on a mailserver? Kill it there too.

SSL is seriously broken (see: CRIME, BEAST, BREACH, FREAK, and now DROWN). It does not protect data, though it may appear to.

If you want to keep data safe configure your system to use TLS only, enable HSTS, and accept only strong cipher suites. Sound complicated? It’s really not.

Here are some configuration examples to get you rolling.

TL;DR:

View post on imgur.com