<?xml version="1.0" encoding="utf-8"?>
<feed xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom">
  <title>morty@home</title>
  <link rel="alternate" type="text/html" href="http://blog.morty.info/" />
  <link rel="self" href="http://blog.morty.info/SyndicationService.asmx/GetAtom" />
  <icon>favicon.ico</icon>
  <updated>2009-12-10T03:03:18.6845-08:00</updated>
  <author>
    <name>morty</name>
  </author>
  <subtitle>The Future is a Mix of Violet and Blue</subtitle>
  <id>http://blog.morty.info/</id>
  <generator uri="http://dasblog.info/" version="2.2.8279.16125">DasBlog</generator>
  <entry>
    <title>Mono C# 4.0 Compiler Feature Complete</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=0d75a5eb-41d9-4d19-9efc-4c7d9ff85ff3" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=0d75a5eb-41d9-4d19-9efc-4c7d9ff85ff3</id>
    <published>2009-12-10T02:51:29.6845-08:00</published>
    <updated>2009-12-10T03:03:18.6845-08:00</updated>
    <category term="Mono" label="Mono" scheme="http://blog.morty.info/CategoryView.aspx?category=Mono" />
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
It is fantastic to see that Mono is keeping up with the CLR / .Net evolution. They
just reached the feature complete state for their C# 4.0 compiler, as reported by <a href="http://mareksafar.blogspot.com/2009/12/mono-and-c-40.html">Marak
Safar</a> from the Mono compiler team.
</p>
        <p>
Optional parameters, named arguments, dynamic binding and of course covariance and
contravariance. I’m especially excited about the last one as it will help a lot with
complex generics-based frameworks. That said, dynamic binding remains the most general
purpose feature in this version.
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>ReSharper and VS2010</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=0ea087f2-89dd-47c2-b7ad-8199c73f0d99" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=0ea087f2-89dd-47c2-b7ad-8199c73f0d99</id>
    <published>2009-05-26T00:51:43.6665-07:00</published>
    <updated>2009-05-26T00:51:43.6665-07:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
Great <a href="http://blogs.jetbrains.com/dotnet/2009/05/preview-of-resharper-for-visual-studio-2010-coming-soon/">news</a> from
the ReSharper team. They are just weeks away from releasing a preview for VS2010 Beta
1 sometime in June. Their blog article also shows you screenshots of ReSharper integrated
with the new windowing system in VS2010.
</p>
        <p>
This is great news for enthusiast and early adopters!
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>Office 2007 Service Pack 2 is out and interoperability is in</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=2a09730e-56f4-41b8-887e-7fad40956cec" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=2a09730e-56f4-41b8-887e-7fad40956cec</id>
    <published>2009-04-29T02:06:37.71875-07:00</published>
    <updated>2009-04-29T02:06:37.71875-07:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
Finally Office 2007 has built-in support for <a href="http://en.wikipedia.org/wiki/OpenDocument">OpenDocument</a> making
it interoperable with Open Office and other tools that use this OASIS standard. Together
with Microsoft’s own creation <a href="http://en.wikipedia.org/wiki/Office_Open_XML">Office
Open Xml</a>, an ECMA standard, this package becomes a very compelling option for
editing, storing, printing and converting documents in both of these standards.
</p>
        <p>
Another important tidbit is that PDF/XPS support is finally in the box, and there
is no reason to dig around the web to find the right add-ins anymore.
</p>
        <p>
In short, time to drop by Windows Update.
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>Chrome(ium) fixed for Windows 7 x64 Beta</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=90a41ab4-f94e-4234-aa53-b3394515b5f7" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=90a41ab4-f94e-4234-aa53-b3394515b5f7</id>
    <published>2009-02-04T00:43:38.346875-08:00</published>
    <updated>2009-02-04T00:43:38.346875-08:00</updated>
    <category term="Browsers" label="Browsers" scheme="http://blog.morty.info/CategoryView.aspx?category=Browsers" />
    <category term="Windows 7" label="Windows 7" scheme="http://blog.morty.info/CategoryView.aspx?category=Windows+7" />
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
The latest nightly builds of Chromium now includes a fix for the sandboxing issues
experienced on Windows 7 x64 Beta, and the –no-sandbox hack is no longer needed and
security and stability is restored. I’m certain this fix will make it into the developer,
beta and release channels soon.
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>Multi-monitor and Windows 7</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=5588aff2-ebb8-4a63-b09c-ccc3488c8cbe" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=5588aff2-ebb8-4a63-b09c-ccc3488c8cbe</id>
    <published>2009-01-15T10:49:49.125-08:00</published>
    <updated>2009-01-15T10:50:03.125-08:00</updated>
    <category term="Windows 7" label="Windows 7" scheme="http://blog.morty.info/CategoryView.aspx?category=Windows+7" />
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
A just noticed that Windows 7 has added support for moving windows between monitors.
</p>
        <p>
Use <strong>Win+Shift</strong> with Left or Right arrow key to move the current window
around. You can also do some fun positioning when combining the Windows key with the
arrow keys.
</p>
        <p>
Much appreciated improvements!
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>Live Mesh ready for Windows 7</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=d4d14ab5-d23d-47c7-8937-debfc506bead" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=d4d14ab5-d23d-47c7-8937-debfc506bead</id>
    <published>2009-01-15T10:44:13.421875-08:00</published>
    <updated>2009-01-15T10:45:18.8125-08:00</updated>
    <category term="Windows 7" label="Windows 7" scheme="http://blog.morty.info/CategoryView.aspx?category=Windows+7" />
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
The latest version of Live Mesh doesn’t disable Aero anymore, and throws in better
conflict handling as a bonus.
</p>
        <p>
Live Mesh has become a critical part of my computer setup, and this is the final piece
that completes my Windows 7 installation --  and everything is working great!
</p>
        <p>
You can get the updated build at <a href="http://www.mesh.com">mesh.com</a> or simply
trough the built-in updater if you were tough enough to survive without Aero.
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>DEP is useless?</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=58903296-1529-4208-8828-06b46820b407" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=58903296-1529-4208-8828-06b46820b407</id>
    <published>2009-01-15T10:35:06.453125-08:00</published>
    <updated>2009-01-15T10:37:11.9375-08:00</updated>
    <category term="Security" label="Security" scheme="http://blog.morty.info/CategoryView.aspx?category=Security" />
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
Interesting point by <a href="http://akselvoll.net/blog/2009/01/15/dep-is-useless/">Magnus
Akselvoll</a>.
</p>
        <p>
Perhaps two of the most malware-facing application are the ones that don’t quite work.
Enough said.
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>Windows 7 x64 Beta 1 and Google Chrome</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=93fefe3a-1b04-441a-878d-e6f40264e6da" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=93fefe3a-1b04-441a-878d-e6f40264e6da</id>
    <published>2009-01-09T07:04:41.083625-08:00</published>
    <updated>2009-01-09T07:05:59.052375-08:00</updated>
    <category term="Browsers" label="Browsers" scheme="http://blog.morty.info/CategoryView.aspx?category=Browsers" />
    <category term="Windows 7" label="Windows 7" scheme="http://blog.morty.info/CategoryView.aspx?category=Windows+7" />
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
If you you’ve tried to install Google Chrome v1.0 on Windows 7 x64 Beta 1 you have
seen a number of warnings about compatibility, and Chrome crashes whenever you load
a page. There are some problems with the Chrome sandboxing model and Windows 7 x64,
so if you run Chrome with the parameter <em>–no-sandbox</em> everything should work
fine.
</p>
        <p>
Happy testing :)
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>MD5-signed X.509 certificates in trouble</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=91817476-8f30-46a1-bb1e-c84d8313bb58" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=91817476-8f30-46a1-bb1e-c84d8313bb58</id>
    <published>2008-12-31T02:25:26.194125-08:00</published>
    <updated>2008-12-31T04:13:08.616-08:00</updated>
    <category term="Security" label="Security" scheme="http://blog.morty.info/CategoryView.aspx?category=Security" />
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
          <a href="http://www.phreedom.org/research/rogue-ca/">Security researchers</a> have
proven a successful collision attack against MD5-signed X.509 certificates. This would
enable an attacker to create their own X.509 certificate with same digital signature
as the original certificate. This certificate can then be used to sign additional
certificates and provide whatever details they please, all trusted by existing security
infrastructures. This will work great phishing and man-in-the-middle attacks.
</p>
        <p>
This was performed using a cluster of 200 PlayStation 3’s and is reproducible with
a couple of days of computing.
</p>
        <p>
The risks inherent when using the MD5 hash algorithm have been known for quite some
time and the recommendation is to move to the SHA family. Most certificates should
as such be signed with SHA-1 instead of MD5, but history has proven that there are
always old installations and old configurations around.
</p>
        <p>
The following public Certificate Authorities are still using MD5 signing:
</p>
        <ul>
          <ul>
            <li>
RapidSSL 
</li>
            <li>
FreeSSL 
</li>
            <li>
TrustCenter 
</li>
            <li>
RSA Data Security 
</li>
            <li>
Thawte 
</li>
            <li>
verisign.co.jp</li>
          </ul>
        </ul>
        <p>
The security researchers sampled 30.000 certificates, whereof 9.000 were using MD5
and 97% of those were issued by RapidSSL.
</p>
        <p>
It’s time to review the algorithm used on your certificates; hopefully it is using
SHA. This is easily verifiable if you look at the certificate properties. This is
not a problem with EV certificates as they do not support the MD5 algorithm.
</p>
        <p>
Microsoft recently issued <a href="http://www.microsoft.com/technet/security/advisory/961509.mspx">this</a> security
advisory.
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>Internet Explorer HttpOnly Cookie extension implemented in all major browsers</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=5a89c773-6b89-4c12-b50e-abdaa34e6ab2" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=5a89c773-6b89-4c12-b50e-abdaa34e6ab2</id>
    <published>2008-12-31T01:36:17.287875-08:00</published>
    <updated>2008-12-31T01:36:17.287875-08:00</updated>
    <category term="Browsers" label="Browsers" scheme="http://blog.morty.info/CategoryView.aspx?category=Browsers" />
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
The WebKit engine was recently enhanced with the HttpOnly Cookie feature originally
introduced in Internet Explorer. This is a security feature that restricts access
to certain cookies making them only available for HTTP requests and not from JavaScript
running within the browser; a feature originally developed to help with XSS attacks.
</p>
        <p>
The next versions of Safari and Google Chrome will most likely include these updated
bits completing the browser lineup as Internet Explorer, FireFox and Opera already
have this feature implemented.
</p>
        <p>
Nice to see innovation being accepted and implemented across the board. 
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>ReSharper v4.5 nightly previews started</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=b8a5026f-2be9-4cae-97cc-cedfc859ad38" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=b8a5026f-2be9-4cae-97cc-cedfc859ad38</id>
    <published>2008-12-25T16:31:13.244375-08:00</published>
    <updated>2008-12-25T16:31:13.244375-08:00</updated>
    <category term="Tools" label="Tools" scheme="http://blog.morty.info/CategoryView.aspx?category=Tools" />
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
The Early Access Program for ReSharper v4.5 just started and nightly builds are available
for download. Keep in mind that these are not official beta releases, but automated
builds straight from the development branch. The current release has a few very useful
features as well as performance and memory optimizations.
</p>
        <p>
Solution-wide analysis has been updated with unused code detection that will highlight
unneeded code segments throughout your solution. If you have a layered architecture
with multiple solutions you will have to up a new solution that includes all your
projects for this to work correctly. If you are doing some Christmas cleaning you
may want take these new bits for a spin. It also features a much more flexible naming
standard configuration.
</p>
        <p>
Download <a href="http://www.jetbrains.net/confluence/display/ReSharper/ReSharper+Early+Access+Program">here</a>.
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>Update for .Net Fx 3.5 SP1 available</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=1d47323a-8f0d-4b00-913b-d19951dc2a38" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=1d47323a-8f0d-4b00-913b-d19951dc2a38</id>
    <published>2008-12-21T09:54:02.976-08:00</published>
    <updated>2008-12-21T09:57:35.7885-08:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
If you had any issues with .Net FX 3.5 SP1, or if you are holding it back for some
reason, it’s time to head over to <a href="http://support.microsoft.com/kb/959209">KB959209</a> and
get this patch. 
</p>
        <p>
It contains a set of fixed for both the .Net 2.0 and the .Net 3.0 bits that were patched
as a part of this release. There is also a list of fixes incase you have been noticing
some strange behavior lately.
</p>
        <p>
The .Net Fx 3.5 Service Pack 1 contained quite a few interesting optimizations, and
is well worth the install.
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>Google Chorme v1.0 is out</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=6f5a6540-8e05-4ac3-b49b-b3585fa8e7fc" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=6f5a6540-8e05-4ac3-b49b-b3585fa8e7fc</id>
    <published>2008-12-16T00:57:04.8911959-08:00</published>
    <updated>2008-12-16T00:57:04.8911959-08:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
It looks like Google decided to fast track a version 1 release, probably hoping it
will be an acceptable deployment for enterprise and computer manufacturers. 
</p>
        <p>
It is still lacking a few important features like client certificate support, but
it’s fast and stable. If you are heavy user of Google web applications and want the
extra features or simply looking for new browser alternative head on over to <a href="http://www.google.com/chrome">Google</a> to
give it a spin. If you just want to test it you can simply leave the ‘make it my default
browser’ setting unchecked, it’s easy to change that once you become a true believer.
</p>
      </div>
    </content>
  </entry>
  <entry>
    <title>Live Client Applications Wave 3 Updated</title>
    <link rel="alternate" type="text/html" href="http://blog.morty.info/PermaLink.aspx?guid=33b080eb-623e-4fe6-90eb-000bfefafcdf" />
    <id>http://blog.morty.info/PermaLink.aspx?guid=33b080eb-623e-4fe6-90eb-000bfefafcdf</id>
    <published>2008-12-16T00:47:45.3492029-08:00</published>
    <updated>2008-12-16T01:10:31.3754301-08:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
A update to the Windows Live Essentials package has been released. This includes Live
Messenger, Live Mail, Live Writer, Live Photo Gallery and more. Make sure you uncheck
any checkboxes for things you don’t want, and be mindful of the last settings page
with home page and search engine settings.
</p>
        <p>
This appears to be a release candidate build, and we should expect a final release
very soon.
</p>
        <p>
Get your bits at <a href="http://download.live.com">download.live.com</a>.
</p>
      </div>
    </content>
  </entry>
</feed>