<?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>macos &#8211; Accidents Happen</title>
	<atom:link href="https://ah.thameera.com/tag/macos/feed/" rel="self" type="application/rss+xml" />
	<link>https://ah.thameera.com</link>
	<description>In the dark</description>
	<lastBuildDate>Mon, 04 Dec 2017 13:05:44 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">56521109</site>	<item>
		<title>Using ncdu to examine disk usage</title>
		<link>https://ah.thameera.com/using-ncdu-to-examine-disk-usage/</link>
					<comments>https://ah.thameera.com/using-ncdu-to-examine-disk-usage/#respond</comments>
		
		<dc:creator><![CDATA[thameera]]></dc:creator>
		<pubDate>Mon, 04 Dec 2017 13:05:44 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[coreutils]]></category>
		<category><![CDATA[du]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[macos]]></category>
		<category><![CDATA[ncdu]]></category>
		<category><![CDATA[unix]]></category>
		<category><![CDATA[utils]]></category>
		<guid isPermaLink="false">http://ah.thameera.com/?p=654</guid>

					<description><![CDATA[du has been my go-to tool for checking disk usage and it&#8217;s wonderfully simple. But I&#8217;ve been using ncdu for a few weeks now. ncdu is short for NCurses Disk Usage. In addition to being able to visualize disk usage by directory, it lets you sort on different parameters, delete files, show hidden files, and [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><a href="https://en.wikipedia.org/wiki/Du_(Unix)"><code>du</code></a> has been my go-to tool for checking disk usage and it&#8217;s wonderfully simple. But I&#8217;ve been using <a href="https://dev.yorhel.nl/ncdu"><code>ncdu</code></a> for a few weeks now. </p>
<p><code>ncdu</code> is short for NCurses Disk Usage. In addition to being able to visualize disk usage by directory, it lets you sort on different parameters, delete files, show hidden files, and a few more stuff that you&#8217;ll miss if you go back to plain <code>du</code>. Most importantly it acts as a file manager, so you can simply enter the directories to see a more fine-grained breakdown of file sizes. As an added bonus it has Vim keybindings along with normal arrow key movements.</p>
<div id="attachment_657" style="width: 540px" class="wp-caption alignnone"><a href="http://ah.thameera.com/wp-content/uploads/2017/11/ncdu.png"><img fetchpriority="high" decoding="async" aria-describedby="caption-attachment-657" src="http://ah.thameera.com/wp-content/uploads/2017/11/ncdu-1024x810.png" alt="ncdu - ncurses disk usage" width="530" height="419" class="size-large wp-image-657" /></a><p id="caption-attachment-657" class="wp-caption-text">Screenshot of ncdu + help popup</p></div>
<p>Installation:</p>
<blockquote><p><code>brew install ncdu   # macOS<br />
sudo apt-get install ncdu  # Ubuntu/debian</code></p></blockquote>
]]></content:encoded>
					
					<wfw:commentRss>https://ah.thameera.com/using-ncdu-to-examine-disk-usage/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">654</post-id>	</item>
		<item>
		<title>How the macOS root user vulnerability happened</title>
		<link>https://ah.thameera.com/how-the-macos-root-user-vulnerability-happened/</link>
					<comments>https://ah.thameera.com/how-the-macos-root-user-vulnerability-happened/#respond</comments>
		
		<dc:creator><![CDATA[thameera]]></dc:creator>
		<pubDate>Fri, 01 Dec 2017 05:00:13 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[macos]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">http://ah.thameera.com/?p=669</guid>

					<description><![CDATA[Mac security specialist Patrick Wardle digs into the root cause (pun intended) behind why a blank password gave you root permissions: * For accounts that are disabled (i.e. don&#8217;t have &#8216;shadowhash&#8217; data) macOS will attempt to perform an upgrade * During this upgrade, od_verify_crypt_password returns a non-zero value, and an error code which is not [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Mac security specialist Patrick Wardle <a href="https://objective-see.com/blog/blog_0x24.html">digs into the root cause</a> (pun intended) behind why <a href="http://ah.thameera.com/root-user-vulnerability-in-macos-high-sierra/">a blank password gave you root permissions</a>:</p>
<blockquote><p>* For accounts that are disabled (i.e. don&#8217;t have &#8216;shadowhash&#8217; data) macOS will attempt to perform an upgrade</p>
<p>* During this upgrade, <code>od_verify_crypt_password</code> returns a non-zero value, and an error code which is not checked</p>
<p>* The user (or attacked) specified password is then &#8216;upgraded&#8217; and saved for the account</p>
<p>It appears that <code>od_verify_crypt_password</code> should fail (update: it does and Apple just didn&#8217;t check for this!).
</p></blockquote>
<p>It might be an oversimplification, but what I gather from the post is that proper handling of the function&#8217;s return value (error code) could have prevented this on hindsight.</p>
<p>Now I&#8217;m pondering about all those times we ignore the error codes returned by the OS for file I/O operations and whatnot.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://ah.thameera.com/how-the-macos-root-user-vulnerability-happened/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">669</post-id>	</item>
		<item>
		<title>Root user vulnerability in macOS High Sierra</title>
		<link>https://ah.thameera.com/root-user-vulnerability-in-macos-high-sierra/</link>
					<comments>https://ah.thameera.com/root-user-vulnerability-in-macos-high-sierra/#respond</comments>
		
		<dc:creator><![CDATA[thameera]]></dc:creator>
		<pubDate>Wed, 29 Nov 2017 05:32:26 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[macos]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">http://ah.thameera.com/?p=663</guid>

					<description><![CDATA[It has been discovered that you can get root permissions on a macOS system running High Sierra without any password. To test, click on the padlock in any System Preferences dialog and enter root as the username and keep the password to blank. Now click Ok (or whatever the confirmation button is) twice and you [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>It has been <a href="https://twitter.com/lemiorhan/status/935578694541770752">discovered</a> that you can get root permissions on a macOS system running High Sierra without any password. To test, click on the padlock in any System Preferences dialog and enter <code>root</code> as the username and keep the password to blank. Now click Ok (or whatever the confirmation button is) twice and you have root privileges! </p>
<p>This is like the worst nightmare ever, but note that the attacker needs to have physical access to the machine. Until Apple sends the patch, <strong>the easiest way to secure the system is by changing the root password</strong> as described here: <a href="https://support.apple.com/en-us/HT204012">https://support.apple.com/en-us/HT204012</a></p>
<p>Unfortunately it looks like the vulnerability was publicly disclosed without letting Apple know and waiting for a patch.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://ah.thameera.com/root-user-vulnerability-in-macos-high-sierra/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">663</post-id>	</item>
	</channel>
</rss>
