﻿<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Blog | Security Whole: Recent Comments</title><link>http://blog.securitywhole.com</link><description /><generator>Quick Blogcast</generator><lastBuildDate>Sat, 31 Jul 2010 03:57:16 GMT</lastBuildDate><item><title>Comment on Finding Meterpreter</title><link>http://blog.securitywhole.com/2010/01/31/finding-meterpreter.aspx#comment-3338057</link><dc:creator>Ryan M. Ferris</dc:creator><description>Thanks for this post. I extended your post some. I found this PS code of interest:&lt;br /&gt;$findMM=foreach ($id in ( Get-Process | ? { $_.Modules -like "*(rsaenh.dll)*"  -and $_.Modules -like "*(iphlpapi.dll)*"} )) {write $id.MainModule}&lt;br /&gt;$findMM | Select Modulename,FileName,ModuleMemorySize,Size,EntryPointAddress,BaseAddress,Description,Company | ft -auto</description><guid isPermaLink="true">http://blog.securitywhole.com/2010/01/31/finding-meterpreter.aspx#comment-3338057</guid><pubDate>Wed, 21 Jul 2010 01:37:06 GMT</pubDate></item><item><title>Comment on Finding Old or Unused Accounts with Powershell v2</title><link>http://blog.securitywhole.com/2009/08/12/finding-old-or-unused-accounts-with-powershell-v2.aspx#comment-2952593</link><dc:creator>Tim Medin</dc:creator><description>The property you need is called whenChanged. &lt;BR&gt;Just add this line:&lt;BR&gt;&lt;FONT face="Courier New"&gt;&lt;FONT size=2&gt;$searcher.PropertiesToLoad.Add("whenChanged") | out-null&lt;/FONT&gt;&lt;BR&gt;&lt;/FONT&gt;</description><guid isPermaLink="true">http://blog.securitywhole.com/2009/08/12/finding-old-or-unused-accounts-with-powershell-v2.aspx#comment-2952593</guid><pubDate>Mon, 29 Mar 2010 04:37:03 GMT</pubDate></item><item><title>Comment on Finding Old or Unused Accounts with Powershell v2</title><link>http://blog.securitywhole.com/2009/08/12/finding-old-or-unused-accounts-with-powershell-v2.aspx#comment-2951886</link><dc:creator>Chris</dc:creator><description>Thanks for the pagesize fix.&lt;br /&gt;&lt;br /&gt;I'm trying to add another property, modificationdate, but aren't having much luck. I tried replacing one of your properties as a test as I thought it would be simple, but nope :(&lt;br /&gt;&lt;br /&gt;Can you point me in the right direction please?</description><guid isPermaLink="true">http://blog.securitywhole.com/2009/08/12/finding-old-or-unused-accounts-with-powershell-v2.aspx#comment-2951886</guid><pubDate>Sun, 28 Mar 2010 21:03:53 GMT</pubDate></item><item><title>Comment on Finding Old or Unused Accounts with Powershell v2</title><link>http://blog.securitywhole.com/2009/08/12/finding-old-or-unused-accounts-with-powershell-v2.aspx#comment-2939651</link><dc:creator>Tim Medin</dc:creator><description>An Active Directory search, by default, returns only 1000 items. To around the issue you have to use the PageSize property.&lt;br /&gt;
&lt;br /&gt;
$searcher.PageSize = 1000&lt;br /&gt;
&lt;br /&gt;
"The way to get around that issue is to assign a value to the PageSize property. When you do that, your search script will return (in this case) the first 1,000 items, pause for a split second, then return the next 1,000. This process will continue until &lt;i&gt;all&lt;/i&gt; the items meeting the search criteria have been returned." from &lt;a href="http://www.microsoft.com/technet/scriptcenter/topics/winpsh/searchad.mspx"&gt;http://www.microsoft.com/technet/scriptcenter/topics/winpsh/searchad.mspx&lt;/a&gt;</description><guid isPermaLink="true">http://blog.securitywhole.com/2009/08/12/finding-old-or-unused-accounts-with-powershell-v2.aspx#comment-2939651</guid><pubDate>Wed, 24 Mar 2010 16:04:00 GMT</pubDate></item><item><title>Comment on Finding Old or Unused Accounts with Powershell v2</title><link>http://blog.securitywhole.com/2009/08/12/finding-old-or-unused-accounts-with-powershell-v2.aspx#comment-2937904</link><dc:creator>Chris</dc:creator><description>Any reason it's only doing 1000 users?</description><guid isPermaLink="true">http://blog.securitywhole.com/2009/08/12/finding-old-or-unused-accounts-with-powershell-v2.aspx#comment-2937904</guid><pubDate>Wed, 24 Mar 2010 03:57:15 GMT</pubDate></item><item><title>Comment on Finding Meterpreter</title><link>http://blog.securitywhole.com/2010/01/31/finding-meterpreter.aspx#comment-2827956</link><dc:creator>Tim Medin</dc:creator><description>Interesting idea. I would imagine would difficult to implement with reasonable accuracy.&lt;BR&gt;&lt;BR&gt;And great post.</description><guid isPermaLink="true">http://blog.securitywhole.com/2010/01/31/finding-meterpreter.aspx#comment-2827956</guid><pubDate>Mon, 15 Feb 2010 03:40:44 GMT</pubDate></item><item><title>Comment on Finding Meterpreter</title><link>http://blog.securitywhole.com/2010/01/31/finding-meterpreter.aspx#comment-2822208</link><dc:creator>jah</dc:creator><description>I know that when you migrate meterpreter to a different process, you can see the change in that processes memory usage (private bytes, working set, etc). I bet if you did enough measuring, you could come up with a ballpark size as a signature for meterpreter. The problem with this approach is that you would need a baseline for the memory usage of each process on the machine.&lt;BR&gt; &lt;BR&gt;This was a very interesting article and showed some nice techniques. I was recently doing some experimentation with metasploit and wrote a blog entry on my findings. If you're interested, the url is: &lt;A href="http://jah-internship.blogspot.com/2010/02/simwitty-internship-week-4.html"&gt;http://jah-internship.blogspot.com/2010/02/simwitty-internship-week-4.html&lt;/A&gt;</description><guid isPermaLink="true">http://blog.securitywhole.com/2010/01/31/finding-meterpreter.aspx#comment-2822208</guid><pubDate>Sat, 13 Feb 2010 02:18:15 GMT</pubDate></item><item><title>Comment on Getting registry last write time with PowerShell</title><link>http://blog.securitywhole.com/2010/02/02/getting-registry-last-write-time-with-powershell.aspx#comment-2816782</link><dc:creator>Tim Medin</dc:creator><description>The problem is each value does not have a timestamp, just the key. That means that you can't get the detail you want. It just isn't a feature that Windows provides.&lt;br&gt;&lt;br&gt;To get the LastWriteTime of the Devices Key run the command at one key higher.&lt;br&gt;&lt;br&gt;Get-RegTimestamp.ps1 HKCU "Software\Microsoft\Windows NT\CurrentVersion"&lt;br&gt;&lt;br&gt;&lt;font face="Courier New"&gt;Key&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LastWriteTime&lt;br&gt;---&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; -------------&lt;br&gt;...&lt;br&gt;Devices&amp;nbsp;&amp;nbsp;&amp;nbsp; 2/11/2010 1:31:22 PM&lt;br&gt;...&lt;/font&gt;&lt;br&gt;</description><guid isPermaLink="true">http://blog.securitywhole.com/2010/02/02/getting-registry-last-write-time-with-powershell.aspx#comment-2816782</guid><pubDate>Thu, 11 Feb 2010 16:38:13 GMT</pubDate></item><item><title>Comment on Getting registry last write time with PowerShell</title><link>http://blog.securitywhole.com/2010/02/02/getting-registry-last-write-time-with-powershell.aspx#comment-2815900</link><dc:creator>Paul</dc:creator><description>Hello,&lt;br /&gt;&lt;br /&gt;    I`m trying to find out the date on which a network printer was installed on the workstation. I`m using the registry keys in "HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices\" to find this out. Unfortunately the above command does not return the information needed. all i get is " .\Get-RegKeyLastWriteTime.ps1 &lt;br /&gt;HKCU Software\Microsoft\Windows NT\CurrentVersion\Devices&lt;br /&gt;&lt;br /&gt;Key                                     LastWriteTime&lt;br /&gt;---                                     -------------&lt;br /&gt;CurrentVersion                          27.01.2010 13:54:08&lt;br /&gt;Shell                                   06.01.2010 14:18:47&lt;br /&gt;ShellNoRoam                             06.01.2010 15:02:40</description><guid isPermaLink="true">http://blog.securitywhole.com/2010/02/02/getting-registry-last-write-time-with-powershell.aspx#comment-2815900</guid><pubDate>Thu, 11 Feb 2010 11:46:06 GMT</pubDate></item><item><title>Comment on Finding Meterpreter</title><link>http://blog.securitywhole.com/2010/01/31/finding-meterpreter.aspx#comment-2777407</link><dc:creator>Tim Medin</dc:creator><description>You would not be able to find it with this method since explorer already loads these dll's.</description><guid isPermaLink="true">http://blog.securitywhole.com/2010/01/31/finding-meterpreter.aspx#comment-2777407</guid><pubDate>Mon, 01 Feb 2010 15:00:22 GMT</pubDate></item></channel></rss>