<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MacSecure.com &#187; Tools</title>
	<atom:link href="http://macsecure.com/category/tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://macsecure.com</link>
	<description>A Mac Security Blog</description>
	<lastBuildDate>Tue, 18 Nov 2008 00:46:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>TrueCrypt for Mac &#8211; Version Update !</title>
		<link>http://macsecure.com/2008/03/05/truecrypt-for-mac-version-update/</link>
		<comments>http://macsecure.com/2008/03/05/truecrypt-for-mac-version-update/#comments</comments>
		<pubDate>Wed, 05 Mar 2008 05:56:24 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[truecrypt]]></category>

		<guid isPermaLink="false">http://macsecure.com/2008/03/05/truecrypt-for-mac-version-update/</guid>
		<description><![CDATA[The new revision of TrueCrypt &#8211; Version 5.0(a) &#8212; has now been released for Mac.   Downloads are available here.  I haven&#8217;t had a change to work with it since I&#8217;m traveling, but initial word from some colleagues is that it works as expected.
]]></description>
			<content:encoded><![CDATA[<p>The new revision of TrueCrypt &#8211; Version 5.0(a) &#8212; has now been released for Mac.   Downloads are available <a href="http://www.truecrypt.org/downloads.php" target="_blank">here</a>.  I haven&#8217;t had a change to work with it since I&#8217;m traveling, but initial word from some colleagues is that it works as expected.</p>
]]></content:encoded>
			<wfw:commentRss>http://macsecure.com/2008/03/05/truecrypt-for-mac-version-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TrueCrypt Notes</title>
		<link>http://macsecure.com/2008/02/08/truecrypt-notes/</link>
		<comments>http://macsecure.com/2008/02/08/truecrypt-notes/#comments</comments>
		<pubDate>Sat, 09 Feb 2008 02:56:16 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[truecrypt]]></category>

		<guid isPermaLink="false">http://macsecure.com/2008/02/08/truecrypt-notes/</guid>
		<description><![CDATA[Got to do some testing with TrueCrypt on the Mac &#8211; and immediately hit a wall.  One of the unique features of TrueCrypt is the ability to create a hidden TrueCrypt volume inside of another TrueCrypt volume.  The idea is that if you were forced to reveal a passphrase, you give up the passphrase to [...]]]></description>
			<content:encoded><![CDATA[<p>Got to do some testing with TrueCrypt on the Mac &#8211; and immediately hit a wall.  One of the unique features of TrueCrypt is the ability to create a hidden TrueCrypt volume inside of another TrueCrypt volume.  The idea is that if you were forced to reveal a passphrase, you give up the passphrase to the &#8216;outer&#8217; volume, and nobody would know that another volume exists inside of the main one.</p>
<p>This isn&#8217;t a requirement for many folks, but the ability to do it is going to be missed for the time being.  Regular TrueCrypt volumes are working great though.</p>
<p>More info about TrueCrypt Hidden volumes is available <a href="http://www.truecrypt.org/docs/?s=hidden-volume" target="_blank">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://macsecure.com/2008/02/08/truecrypt-notes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TrueCrypt for Mac &#8211; Released</title>
		<link>http://macsecure.com/2008/02/06/truecrypt-for-mac-released/</link>
		<comments>http://macsecure.com/2008/02/06/truecrypt-for-mac-released/#comments</comments>
		<pubDate>Wed, 06 Feb 2008 17:10:22 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[truecrypt security]]></category>

		<guid isPermaLink="false">http://macsecure.com/2008/02/06/truecrypt-for-mac-released/</guid>
		<description><![CDATA[A staple on the Windows OS for quite a while, TrueCrypt has finally been ported to OS X.    While it doesn&#8217;t have a lot of polish yet, it does indeed seem to work like the Windows version does.   TrueCrypt has the ability to create an encrypted volume &#8212; which can [...]]]></description>
			<content:encoded><![CDATA[<p>A staple on the Windows OS for quite a while, TrueCrypt has finally been ported to OS X.    While it doesn&#8217;t have a lot of polish yet, it does indeed seem to work like the Windows version does.   TrueCrypt has the ability to create an encrypted volume &#8212; which can be stored as random data on your disk &#8212; essentially hiding the fact that you have any hidden data.   If nobody knows you have something encrypted, how would they know to even ask for your passphrase?        As a note, TrueCrypt on Windows has been used by folks doing various illegal things over the years, and using it to hide data;  real Dateline kinds of stuff.      It&#8217;s good at what it does, but having it around could make someone think you have something to hide.</p>
<p>Try it out here:  <a href="http://www.truecrypt.org/downloads.php" target="_blank">http://www.truecrypt.org/downloads.php</a></p>
]]></content:encoded>
			<wfw:commentRss>http://macsecure.com/2008/02/06/truecrypt-for-mac-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top Mac Security Tools, Part 2</title>
		<link>http://macsecure.com/2007/11/19/top-mac-security-tools-part-2/</link>
		<comments>http://macsecure.com/2007/11/19/top-mac-security-tools-part-2/#comments</comments>
		<pubDate>Tue, 20 Nov 2007 01:31:51 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[How-To's]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[]]></category>
		<category><![CDATA[nessus]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[syslog]]></category>
		<category><![CDATA[vnc]]></category>

		<guid isPermaLink="false">http://macsecure.com/2007/11/19/top-mac-security-tools-part-2/</guid>
		<description><![CDATA[Part two (part one is here) of an expanding series where I&#8217;m providing an overview of some of the InfoSec tools that I use on a daily basis on my Mac.    Down the line I&#8217;ll expand this series and write up each tool in more detail.
Nessus
Despite the controversy about Nessus going proprietary [...]]]></description>
			<content:encoded><![CDATA[<p>Part two (part one is <a href="http://macsecure.com/2007/11/12/top-mac-security-tools-part-1/">here</a>) of an expanding series where I&#8217;m providing an overview of some of the InfoSec tools that I use on a daily basis on my Mac.    Down the line I&#8217;ll expand this series and write up each tool in more detail.</p>
<p><strong>Nessus</strong></p>
<p><br class="webkit-block-placeholder" />Despite the controversy about <a href="http://www.nessus.org/" target="_blank">Nessus</a> <a href="http://www.linux.com/articles/48745" target="_blank">going proprietary</a> in 2005, it remains one of the gold standards for network vulnerability scanning.  Installed as a server (nessusd) and a client (typically just called nessus), the client has options to control what hosts are scanned and what specific services and vulnerabilities it scans for.   Some of the things Nessus can detect are services that have vulnerabilities, common misconfigurations,  and default passwords &#8212; among about a thousand other things.   As a note, Nessus has been known to break a services / tip over a server now and then.   It&#8217;s not something you want to point at your production server during business hours!   Tenable Network Security now owns Nessus and sells a commercial version and support.<br class="webkit-block-placeholder" /></p>
<p><strong>SSH / SFTP</strong></p>
<p><br class="webkit-block-placeholder" />There&#8217;s not much to say &#8212; where there once was Telnet, now there&#8217;s SSH.  I have SSH (previously via <a href="http://iterm.sourceforge.net/" target="_blank">iTerm</a> &#8212; no using the Leopard Terminal) sessions up just about 24&#215;7 on my Mac, as well as my work Dell.  From remote shell access, to tunneling through firewalls, to SFTP, and on and on.  Wherever possible, it&#8217;s almost always advisable to run SSH instead of Telnet.   I know some things have been written about it, but the <a href="http://www.apple.com/macosx/technology/unix.html" target="_blank">Leopard Terminal</a> seems good so far.<br class="webkit-block-placeholder" /></p>
<p><strong>VNC<br class="webkit-block-placeholder" /></strong></p>
<p>Originally developed at AT&amp;T labs, the name &#8220;vnc&#8221; is really a number of things, including a server, a client, and even a protocol.    VNC (Virtual Network Computing) was designed to allow a remote graphical desktop session without much overhead.  VNC (the protocol) isn&#8217;t natively encrypted, but is commonly tunnelled over SSH.   On the Mac you can run a VNC server for remotely controlling your Mac (from another Mac, a Windows PC, or even a Linux box).   Some of the more common Mac VNC clients are:  <a href="http://www.jinx.de/JollysFastVNC.html" target="_blank">JollysFastVNC</a> and <a href="http://sourceforge.net/projects/cotvnc/" target="_blank">Chicken of the VNC</a>.  I&#8217;d previously used CotVNC, but I&#8217;m now using JollysFastVNC most of the time.<br class="webkit-block-placeholder" /></p>
<p><strong>Syslog Server and KiwiLog Viewer</strong></p>
<p><br class="webkit-block-placeholder" />One of the things that has a more limited use until you need is is a syslog server.   All Unix servers, all Cisco network devices, your home Wi-Fi router, and even your Mac can send system logs to a syslog server &#8212; but wait, there&#8217;s more!  Mac OS X Leopard has a syslog server included, that can receive logs from all of those other devices.  My Wi-Fi router (as well as other devices) all send Syslog to one of my Macs.    The <a href="http://www.kiwisyslog.com/kiwi-log-viewer-downloads/" target="_blank">Kiwi Log Viewer for Mac</a> is a free utility that makes looking through syslog files much, much more convenient by color coding them, as well as allowing for easy searching.<br class="webkit-block-placeholder" /></p>
<p><strong>Mac OS Disk Utility</strong></p>
<p><br class="webkit-block-placeholder" />While the Windows and Linux platforms have <a href="http://www.truecrypt.org/" target="_blank">TrueCrypt</a> for creating encrypted disks and volumes, the Mac port of TrueCrypt still seems to be a way off.  For most uses however, it&#8217;s possible to use the Mac OS  Disk Utility to create an encrypted, mountable volume without too much trouble.  In Leopard, the Disk Utility has been upgraded to allow for 256-bit AES encryption, which is a little slower, but much more secure.   For securing personal data, this method works well.   What TrueCrypt does that doesn&#8217;t exist on the Mac yet is that when data is encrypted, it doesn&#8217;t create an &#8216;encrypted file&#8217; that can be identified, therefore a casual user looking for your &#8217;sensitive&#8217; files wouldn&#8217;t ever know that your &#8217;secret&#8217; data existed.</p>
]]></content:encoded>
			<wfw:commentRss>http://macsecure.com/2007/11/19/top-mac-security-tools-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top Mac Security Tools, Part 1</title>
		<link>http://macsecure.com/2007/11/12/top-mac-security-tools-part-1/</link>
		<comments>http://macsecure.com/2007/11/12/top-mac-security-tools-part-1/#comments</comments>
		<pubDate>Mon, 12 Nov 2007 20:00:19 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[gpg]]></category>
		<category><![CDATA[netcat]]></category>
		<category><![CDATA[nmap]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[security tools]]></category>
		<category><![CDATA[wireshark]]></category>

		<guid isPermaLink="false">http://macsecure.com/2007/11/12/top-mac-security-tools-part-1/</guid>
		<description><![CDATA[Every blog has a &#8216;Top 10&#8242; list of something &#8212; and I&#8217;m fairly sure that someone has probably even done a &#8220;Top xx Mac Security Tools&#8221; list, but I figured I&#8217;d go with the list of the tools that I use the most, and then as time permits, go through and write up something about [...]]]></description>
			<content:encoded><![CDATA[<p>Every blog has a &#8216;Top 10&#8242; list of something &#8212; and I&#8217;m fairly sure that someone has probably even done a &#8220;Top xx Mac Security Tools&#8221; list, but I figured I&#8217;d go with the list of the tools that I use the most, and then as time permits, go through and write up something about using each tool in more detail.</p>
<p><span id="more-15"></span></p>
<p><strong>The List:</strong></p>
<p><strong>WireShark </strong></p>
<p><a href="http://www.wireshark.org/" target="_blank">Wireshark</a> is the the new (circa 2006) name for Ethereal, probably the single most popular graphical network protocol analyzer ever.  Open-source, Wireshark is available on multiple platforms and is available in binary and source forms in most cases.  Commonly called a &#8216;network sniffer&#8217;, Wireshark is protocol aware, so it can intelligently follow streams of different traffic to be analyzed.   The functionality of Wireshark is similar to the command-line utility &#8216;tcpdump&#8217; (Which is included with OS X) but in most cases people find working with Wireshark easier.  Wireshark uses an extensible (and extensive) plug-in format for decoding new protocols &#8212; these decoders have been <a href="http://www.google.com/search?q=wireshark+vulnerabilities" target="_blank">subject to vulnerabilities</a> over the years, so keeping Wireshark up to date is important.</p>
<p><strong>Mac GPG</strong></p>
<p><a href="http://macgpg.sourceforge.net/" target="_blank">Mac GPG</a> is the Mac port of <a href="http://www.gnupg.org/" target="_blank">GPG, the Gnu Privacy Guard</a>, which in turn is a free (and open source) implementation of OpenPGP.   This project is available in source code or binary forms, and the MacGPG site has <a href="http://macgpg.sourceforge.net/docs/howto-build-gpg-osx.txt.asc" target="_blank">directions for compiling it yourself</a>.   As a start it&#8217;s useful to download or build the main GPG package, the GPG Keychain Access, and the GPG File Tool.</p>
<p><strong>Nmap</strong></p>
<p>Volumes <a href="http://www.google.com/search?hl=en&amp;q=using+nmap" target="_blank">have been written</a> about <a href="http://insecure.org/nmap/" target="_blank">nmap</a>, the platforms it runs on, and the ways it can be used.   The Mac port of nmap can be installed using <a href="http://darwinports.com/" target="_blank">DarwinPorts</a> or <a href="http://www.google.com/search?q=fink+project" target="_blank">FinkInstaller</a>, the most current stable version is 4.20.   Nmap&#8217;s usefulness for exploring networks and systems is immeasureable.</p>
<p><strong>Netcat</strong></p>
<p>Often called the &#8220;Swiss-Army knife of networking&#8221; &#8211; <a href="http://netcat.sourceforge.net/" target="_blank">netcat</a> is another GNU free (and open source) tool for doing all kinds of network and host-based testing.   In my day job I use netcat regularly for testing TCP and UDP connections through firewalls.   Ever needed to test UDP connectivity but wished you had a way to do a &#8216;udp telnet&#8217; ?  Netcat can be run as a client or a server piece, and can be used for a multitude of things, including &#8217;shoveling&#8217; shell access through firewalls, as well as port scanning and a number of settings to make netcat use harder to detect.  <strong>Note:</strong> Netcat is considered a &#8216;hacking tool&#8217; in some places.  This is mostly a concern with Windows A/V programs.</p>
<p>End of Part 1.</p>
]]></content:encoded>
			<wfw:commentRss>http://macsecure.com/2007/11/12/top-mac-security-tools-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Managing the Leopard Firewall with WaterRoof</title>
		<link>http://macsecure.com/2007/11/09/managing-the-leopard-firewall-with-waterroof/</link>
		<comments>http://macsecure.com/2007/11/09/managing-the-leopard-firewall-with-waterroof/#comments</comments>
		<pubDate>Fri, 09 Nov 2007 05:11:38 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[How-To's]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[leopard]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[waterroof]]></category>

		<guid isPermaLink="false">http://macsecure.com/2007/11/09/managing-the-leopard-firewall-with-waterroof/</guid>
		<description><![CDATA[This is the last Leopard firewall post for a while&#8230;
Over the last week or two of Leopard firewall discussions across the web, quite a bit of info has come out about how the Leopard firewall works, and what&#8217;s going on &#8216;under the hood&#8217; when you change the options under System Preferences.
The firewall used by OS [...]]]></description>
			<content:encoded><![CDATA[<p>This is the last Leopard firewall post for a while&#8230;</p>
<p>Over the last week or two of Leopard firewall discussions across the web, quite a bit of info has come out about how the Leopard firewall works, and what&#8217;s going on &#8216;under the hood&#8217; when you change the options under System Preferences.</p>
<p>The firewall used by OS X is <a href="http://en.wikipedia.org/wiki/Ipfw" target="_blank">ipfw</a>, the FreeBSD sponsored open source firewall package.   Contrary to the limited configuration options presented in the System Preferences Security section, ipfw is extremely configurable and sophisticated.   Whole books could be written about configuring ipfw, but the <a href="http://www.freebsd.org/cgi/man.cgi?query=ipfw&amp;sektion=8" target="_blank">man page for it</a> is a good place to start.<br />
<span id="more-13"></span><br />
Let&#8217;s look at a few simple things to start.  From a Terminal:</p>
<p>- sudo su<br />
- ipfw show</p>
<p>This will show what rules are currently set on your system.   As an example, this is what my Macbook Pro shows:</p>
<p>33300      0         0 deny icmp from any to me in icmptypes 8<br />
65535 309194 202763184 allow ip from any to any</p>
<p>We&#8217;ll start at the end.   The second line is what&#8217;s called the default rule (it always has a rule number of 65535) and it always has to match all packets.  The scope of how to make the various rules, rule sets, and specific configurations are covered better in other places &#8211; but for now this will suffice.  This particular system only has two Static Rules at this point.</p>
<p>Which brings us to <a href="http://www.hanynet.com/applications/" target="_blank">WaterRoof</a>.   WaterRoof is a graphical front-end to ipfw for OS X.  To be clear &#8212; if you don&#8217;t understand the basics of how ipfw works (or firewalls in general), WaterRoof isn&#8217;t going to get you very far.    Once installed, if you go to &#8220;Static Rules&#8221;, you should see the same rules that you saw from the command-line.   It has configuration options for Static and Dynamic rules, Logging, NAT, and even a Wizard that can lead you through the steps of configuring ipfw from scratch.</p>
<p>One of the best things about WaterRoof is that it allows you to easily import and export your rule sets, so if you decide that you want to experiment, you can backup you rules and keep them around to restore them without needing to know all of the command-line options.</p>
<p>There has been talk on some of the other blogs and forums about coming up with an &#8216;ideal&#8217; set of ipfw rules for use on Leopard systems &#8212; if you familiarize yourself with WaterRoof now, putting those rules into practice shouldn&#8217;t be hard.   For now the rules I&#8217;m doing testing with are for when I&#8217;m on &#8216;hostile&#8217; networks.   I&#8217;ll probably keep a copy of these around for when I need to know that I&#8217;m blocking everything possible.    A sample output of &#8216;ipfw show&#8217; would look something like this:</p>
<p>00001    388     17858 deny ip from any to me<br />
00002      0         0 deny tcp from any to me<br />
00003      0         0 deny udp from any to me<br />
33400      0         0 deny icmp from any to me<br />
65535 325675 210533693 allow ip from any to any</p>
<p>WaterRoof gets you a much more detailed set of controls than anything built into OS X.  Not everyone needs it, but it&#8217;s good to know the basics at least.   Just as a note &#8211; you can absolutely set settings in ipfw that will prevent your system from being able to access the internet.   If you&#8217;re the experimental type, make sure you save a copy of your rules before tinkering.</p>
]]></content:encoded>
			<wfw:commentRss>http://macsecure.com/2007/11/09/managing-the-leopard-firewall-with-waterroof/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
