<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom">
    <title>MK&amp;C</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/" />
    
    <id>tag:blog.karppinen.fi,2008-01-02://1</id>
    <updated>2008-10-15T08:22:05Z</updated>
    <subtitle>Marko Karppinen &amp; Co.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Open Source 4.1-en-release-26-r1131-20080102</generator>

<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/karppinen" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="karppinen" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry>
    <title>Knox 1.6 beta is now available</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/10/knox-16-beta-is-now-available.html" />
    <id>tag:blog.karppinen.fi,2008://1.249</id>

    <published>2008-10-15T08:22:05Z</published>
    <updated>2008-10-15T08:22:05Z</updated>

    <summary>We’ve just pushed out a beta of Knox 1.6. The major feature is support for Mac OS X 10.5 Leopard’s "sparse bundle" vault format. This format improves reliability and is much faster to compact. Please try it out and report...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="MK&amp;C" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[We’ve just pushed out a beta of Knox 1.6. The major feature is support for Mac OS X 10.5 Leopard’s "sparse bundle" vault format. This format improves reliability and is much faster to compact. <a href="http://forum.karppinen.fi/forums/1/topics/266">Please try it out</a> and report any issues you encounter!]]>
        
    </content>
</entry>

<entry>
    <title>Another case of Apple ID theft</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/08/another-case-of-apple-id-theft.html" />
    <id>tag:blog.karppinen.fi,2008://1.248</id>

    <published>2008-08-01T18:31:22Z</published>
    <updated>2008-08-01T18:31:22Z</updated>

    <summary>Looks like Chris Pirillo also got his Apple ID stolen. Like in my case, Apple has assured him that their processes no longer allow this to happen. However, it seems that Apple’s procedures had not been improved during the two-and-a-half-week...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>Looks like <a href="http://chris.pirillo.com/2008/08/01/paypal-denies-450-of-unauthorized-charges/">Chris Pirillo also got his Apple ID stolen</a>. Like in <a href="http://blog.karppinen.fi/2008/07/apple-just-gave-out-my-apple-i.html">my case</a>, Apple has assured him that their processes no longer allow this to happen.</p>

<p>However, it seems that Apple&#8217;s procedures had not been improved during the two-and-a-half-week period between the two incidents. I&#8217;m not taking their word very seriously at this point. Also, the promise to get back to me about their log files detailing my account&#8217;s usage? 30 days on since their initial call, I&#8217;ve heard exactly zip from Apple.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>How Apple replied to the password reset request</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/07/how-apple-replied-to-the-passw.html" />
    <id>tag:blog.karppinen.fi,2008://1.247</id>

    <published>2008-07-10T08:19:23Z</published>
    <updated>2008-07-10T08:19:23Z</updated>

    <summary>We’re on to day three of this saga, with about 80 000 pairs of eyeballs on this thing. No word from Apple yet. Meanwhile, some people have asked for clarification and/or called BS on this, so I thought I’d post...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>We&#8217;re on to day three of this saga, with about 80 000 pairs of eyeballs on this thing. No word from Apple yet. Meanwhile, some people have asked for clarification and/or called BS on this, so I thought I&#8217;d post the email that Apple sent in response to the password reset request. This email was in my .Mac mailbox while the password reset emails mentioned apparently went to the yahoo.com address.</p>

<p>The account continues to get password reset requests, but as people have pointed out, those are harmless unless someone at Apple overrides the procedure manually. Also, to those who asked: my security question and answer are a meaningless challenge/response pair &#8212; there is no chance that someone guessed the answer.</p>

<blockquote>
  <p>Please include the line below in follow-up emails for this request.</p>

<p>Follow-up:  [redacted]</p>

<p>Re: ADC account</p>

<p>Dear Mr Karppinen, </p>

<p>Thank you for contacting the Apple Developer Connection regarding your ADC membership account. </p>

<p>Please accept our apology for the delayed response.</p>

<p>In reviewing your information, I have found the following account:</p>

<p>Marko Karppinen <br />
MK&amp;C <br />
Email address: [redacted]@mac.com <br />
ADC Premier Membership <br />
ADC Member number: [redacted] <br />
Apple ID: [redacted]@mac.com <br />
Last Login Date: 04 Jul 2008  </p>

<p>Please know that I updated your email address for you to: marko.[redacted]@yahoo.com.</p>

<p>Furthermore, the password for your ADC account has been reset. You will receive two additional emails 
from Apple. One will contain your login account name, the other will contain your new temporary login
password.</p>

<p>Once you have logged in with the temporary password, you will be presented with a &#8220;Password Expired&#8221;
page. Enter the temporary password as the &#8220;old password&#8221; and select and enter a new personal password
of your choice as the &#8220;new password&#8221;.</p>

<p>After you have logged in, please take a moment to review the information in your account profile to ensure the information is up to date.</p>

<p>Please know that it is possible to reset your password yourself online. We have included this process below:</p>

<p>1) Go to the Member Site at <a href="http://connect.apple.com">http://connect.apple.com</a>. <br />
2) Enter your Apple ID and select the &#8220;Forgot Password&#8221; button. <br />
3) Enter your Date of Birth. <br />
4) Choose your password reset option. </p>

<p>&#8212;The easiest option is to have your temporary password emailed to the email address listed on your ADC account. You also have the option to reset your password 
online by answering the challenge question you chose when you created your ADC account.</p>

<p>I hope this information is useful to you. Please let me know if you have any questions or need further assistance.</p>

<p>Best regards,</p>

<p>[redacted]</p>

<p>Apple Developer Connection <br />
Worldwide Developer Relations</p>

<p>Inquiry from marko  regarding Reset Password <br />
Email address: [redacted]@mac.com <br />
Region: Europe</p>

<p>am forget my password of mac,did you give me password on new email marko.[redacted]@yahoo.com</p>
</blockquote>
]]>
        

    </content>
</entry>

<entry>
    <title>Apple just gave out my Apple ID password because someone asked</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/07/apple-just-gave-out-my-apple-i.html" />
    <id>tag:blog.karppinen.fi,2008://1.246</id>

    <published>2008-07-08T06:05:32Z</published>
    <updated>2008-07-08T06:05:32Z</updated>

    <summary>I tried to log in to Apple Developer Connection this morning to find out that my password had been changed and the email associated with my account was now a yahoo.com address that wasn't mine. Luckily, my "security question" was...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>I tried to log in to Apple Developer Connection this morning to find out that my password had been changed and the email associated with my account was now a yahoo.com address that wasn't mine. Luckily, my "security question" was still the same, so I was able to reset the password and email address back.</p>

<p>Based on the emails that have appeared in my .Mac mailbox, this was accomplished by sending this classy one-liner to Apple:</p>

<blockquote>am forget my password of mac,did you give me password on new email marko.[redacted]@yahoo.com</blockquote>

<p>To which Apple reacted by doing the only reasonable thing – saying <b>Sir, Yes Sir!</b> and handing my account over. Here's the email I just sent Apple:</p>

<blockquote>
<p>Dear ADC,</p>

<p>You have reset my password based on a request by someone other than me. Rather than checking if the requester was actually me by comparing the information in their personal profile, you have allowed a third party access my Apple ID for no reason whatsoever.</p>

<p>I tried to log in today and saw that my password had been changed, and the email address associated with my account changed to "marko.[redacted]@yahoo.com".</p>

<p>Apparently based on a single-line email inquiry, you have allowed a third party access to:<br>
- My personal details<br>
- My personal email<br>
- All the files stored on my iDisk<br>
- Everything I've synchronized to .Mac, including my Address Book, Bookmarks, Keychain items, etc.<br>
- My credit card details as stored in my Apple Store profile<br>
- My iTunes Music Store Account<br>
- My ADC Premier membership, including the software seed key and other assets<br>
- The iPhone Developer Program's Program Portal, including details of our development team</p>

<p>Frankly, this makes me so angry that I can't see straight. Did it not occur to you at all that someone at "marko.[redacted]@yahoo.com" was not actually me? For example, because the names didn't match?</p>

<p>Can you even begin to appreciate the amount of work I need to do to re-secure all the information that you have compromised? How do you propose to restore confidence that I, or indeed anyone, should ever store anything confidential on your systems again?</p>

<p>With best regards,<br>
Marko Karppinen</p>
</blockquote>

<p><b>Update:</b> A few hours after posting this, a team lead from Apple Developer Connection's European support organization called me, apologized for the mess, and assured me that they don't normally operate this way. He promised to find out if Apple can determine, based on their logs, where and how my Apple ID was used in between the password reset and myself discovering all this about 12 hours later. I know that my .Mac mail was accessed, but luckily I don't use it for anything other than ADC-related communications. In fact, I'd be home free if it wasn't for .Mac Sync and some old, unencrypted backups on my iDisk (I've since then smartened up and my backups are now encrypted). I hope the logs will allow Apple to confirm that these services were not accessed by the third party.</p>

<p><b>Update 2:</b> So it's soon 48 hours after the password reset, but no further contact from Apple. Perhaps I should let them know that, so far, 65 000 people have seen this and many might be wondering how Apple will end up handling the case?</p>

<p><b>Update 3:</b> <a href="http://blog.karppinen.fi/2008/07/how-apple-replied-to-the-passw.html">How Apple replied to the password reset request</a> and other clarifications.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Cocoa method name of the day</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/05/cocoa-method-name-of-the-day.html" />
    <id>tag:blog.karppinen.fi,2008://1.245</id>

    <published>2008-05-22T10:10:33Z</published>
    <updated>2008-05-22T10:10:33Z</updated>

    <summary>From the ISyncConcreteSession private interface: - (void)attentionClassDumpUser:(id)fp8 reverseEngineeringThisClassAndCallingPrivateMethodsIsFun ButMayLeadToCompleteAndIrrevocableDataLoss:(id)fp12 atTheVeryLeastItWillCauseUnexpectedBehaviourForOtherApplications:(id)fp16 youHaveBeenWarnedAgainstDoingSo:(id)fp20; Indeed. But the question is… what does it do?...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>From the <i>ISyncConcreteSession</i> private interface:</p>

<blockquote><small>
- (void)<b>attentionClassDumpUser</b>:(id)fp8<br>
<b>reverseEngineeringThisClassAndCallingPrivateMethodsIsFun
ButMayLeadToCompleteAndIrrevocableDataLoss</b>:(id)fp12<br>
<b>atTheVeryLeastItWillCauseUnexpectedBehaviourForOtherApplications</b>:(id)fp16<br> 
<b>youHaveBeenWarnedAgainstDoingSo</b>:(id)fp20;
</small></blockquote>

<p>Indeed. But the question is… <i>what does it do?</i></p>]]>
        
    </content>
</entry>

<entry>
    <title>Pyro 1.7 is out</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/05/pyro-17-is-out.html" />
    <id>tag:blog.karppinen.fi,2008://1.244</id>

    <published>2008-05-13T14:36:56Z</published>
    <updated>2008-05-13T14:36:56Z</updated>

    <summary>After only eleven-or-so months in the making, Pyro 1.7 is finally out. This long-overdue update to our Mac-native Campfire group chat client makes Pyro more compatible with Leopard and Safari 3. It's still not perfect, but it's a big step...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="MK&amp;C" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[After only eleven-or-so months in the making, <a href="http://www.karppinen.fi/pyro/">Pyro 1.7</a> is finally out. This long-overdue update to our Mac-native <a href="http://www.campfirenow.com/">Campfire</a> group chat client makes Pyro more compatible with Leopard and Safari 3. It's still not perfect, but it's a big step forward from 1.6. Pyro is free, so go try it out now!]]>
        
    </content>
</entry>

<entry>
    <title>The evolution of Mac OS X and iPhone OS names</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/05/the-evolution-of-mac-os-x-and.html" />
    <id>tag:blog.karppinen.fi,2008://1.243</id>

    <published>2008-05-13T13:57:47Z</published>
    <updated>2008-05-13T13:57:47Z</updated>

    <summary>First there was Mac OS X. Then came iPhone, running OS X (see apple.com). At this point, dropping the "Mac" was widely considered to be semantically significant. Next, at the March 6 special event and the iPhone SDK, Apple started...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>First there was <b>Mac OS X</b>. Then came iPhone, running <b>OS X</b> (see <a href="http://www.apple.com/iphone/specs.html">apple.com</a>). At this point, dropping the "Mac" was widely considered to be <a href="http://daringfireball.net/2007/01/os_x">semantically significant</a>.</p>

<p>Next, at the <a href="http://www.apple.com/quicktime/qtv/iphoneroadmap/">March 6 special event</a> and the iPhone SDK, Apple started referring to iPhone's operating system as the <b>iPhone OS</b>. This seemed like a smart choice to me — the distinction between OS X and <i>Mac</i> OS X was probably lost on all but the nerdiest of Mac fans.</p>

<p>But now, with today's <a href="http://www.apple.com/pr/library/2008/05/13wwdc.html">press release about the WWDC keynote</a>, the names have seemingly changed again. Throughout the release, Apple consistently refers to <b>OS X Leopard</b> and <b>OS X iPhone</b>.</p>

<p>Speculate away.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Share your flights with flightagenda.com</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/04/share-your-flights-with-flight.html" />
    <id>tag:blog.karppinen.fi,2008://1.242</id>

    <published>2008-04-09T15:30:12Z</published>
    <updated>2008-04-09T15:30:12Z</updated>

    <summary>We just opened the doors to flightagenda.com, a small but useful site we've been working on for a while now. With flightagenda.com, you can enter in your upcoming flights and get back an iCal calendar with all the flight details....</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="MK&amp;C" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>We just opened the doors to <a href="http://flightagenda.com/">flightagenda.com</a>, a small but useful site we've been working on for a while now. With flightagenda.com, you can enter in your upcoming flights and get back an iCal calendar with all the flight details. The focus has been on making the site as small and as quick to use as possible, and I'm pretty happy with the results: you can go from sign up to having a shared flights calendar in less than a minute (yes, we've timed it).</p>

<p>We're calling the site an alpha for the time being, but there are no known issues. <a href="http://flightagenda.com/">Sign up</a> and let us know what you think!</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Apple TV Take Two, first impressions</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/02/apple-tv-take-two-first-impres.html" />
    <id>tag:blog.karppinen.fi,2008://1.241</id>

    <published>2008-02-12T20:16:34Z</published>
    <updated>2008-02-12T20:16:34Z</updated>

    <summary>This is easily the slickest video-on-demand service to date. A newly released movie (we went for Superbad) in 720p HD cost $5 and was ready for playing within 15 seconds of the purchase. And the cost of a 40GB Apple...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[This is easily the slickest video-on-demand service to date. A newly released movie (we went for <i>Superbad</i>) in 720p HD cost $5 and was ready for playing within 15 seconds of the purchase. And the cost of a 40GB Apple TV is about what you'd pay for 10 movies on blu-ray. This seems to be a no-brainer if there ever was one.]]>
        
    </content>
</entry>

<entry>
    <title>Reboot</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2008/02/reboot.html" />
    <id>tag:blog.karppinen.fi,2008://1.240</id>

    <published>2008-02-08T19:40:52Z</published>
    <updated>2008-02-08T19:40:52Z</updated>

    <summary><![CDATA[I&#8217;ve moved this blog to a new address to make way for a brand new MK&amp;C web site. Some long-overdue updates to the blog are coming as well. My apologies for the fact that you are likely to see all...]]></summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="MK&amp;C" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>I&#8217;ve moved this blog to a new address to make way for a brand new MK&amp;C web site. Some long-overdue updates to the blog are coming as well. My apologies for the fact that you are likely to see all my old posts again in your feed reader due to the source change.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Quay</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2007/11/quay.html" />
    <id>tag:blog.karppinen.fi,2007://1.239</id>

    <published>2007-11-28T17:07:20Z</published>
    <updated>2008-01-02T11:16:34Z</updated>

    <summary>Our friend Rainer Brockerhoff just released Quay, a $10 utility that brings hierarchical menus back to the Leopard dock. It does what it says on the box, and does it well. Go get it!...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="Elsewhere" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>Our friend Rainer Brockerhoff just released <a href="http://www.brockerhoff.net/quay/">Quay</a>, a $10 utility that brings hierarchical menus back to the Leopard dock. It does what it says on the box, and does it well. Go get it!</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Scary SSL certificate bug in Mac OS X is now fixed</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2007/11/scary-ssl-certificate-bug-in-mac-os-x-is-now-fixed.html" />
    <id>tag:blog.karppinen.fi,2007://1.238</id>

    <published>2007-11-15T10:55:15Z</published>
    <updated>2008-01-02T11:16:34Z</updated>

    <summary>Back in May, we discovered and reported to Apple a serious vulnerability in Mac OS X. The issue was silently fixed in Leopard, but yesterday Apple made fixes available for 10.3 and 10.4 as well. Here’s how Apple describes the...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="MK&amp;C" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>Back in May, we discovered and reported to Apple a serious vulnerability in Mac OS X. The issue was silently fixed in Leopard, but yesterday Apple made fixes available for 10.3 and 10.4 as well. Here&#8217;s how Apple describes the issue:</p>

<blockquote>An issue exists in the validation of certificates. A man-in-the-middle attacker may be able to direct the user to a legitimate site with a valid SSL certificate, then re-direct the user to a spoofed web site that incorrectly appears to be trusted. This could allow user credentials or other information to be collected. This update addresses the issue through improved validation of certificates. Credit to Marko Karppinen, Petteri Kamppuri, and Nikita Zhuk of MK&C for reporting this issue.</blockquote>

<p>This generic language often used in vulnerability descriptions doesn’t really drive home the impact of the issue. To start, I’d change &#8220;may be able&#8221; to &#8220;is able&#8221; and &#8220;could allow&#8221; to &#8220;allows&#8221;. This vulnerability is exploitable every time. Here’s a real world example:</p>

<ul>
<li>You connect your MacBook to a Wi-Fi access point, such as a T-Mobile HotSpot. But the access point isn’t really what it seems — someone’s just announcing a rogue network with the &#8220;tmobile&#8221; SSID. This could happen anywhere.</li>
<li>When you start surfing, the access point redirects you to the login page as normal. Before the SSL-encrypted login page is downloaded, however, a non-encrypted redirection page appears for a fraction of a second. Again, this is normal. But this time, the page includes a 1x1 pixel image from a server the attacker has a real SSL certificate for. Let’s call it www.validcertificate.example. Real SSL certificates that are trusted by Mac OS X are available from a number of vendors without any verification of the site’s identity.</li>
<li>Loading that single image from www.validcertificate.example has now &#8220;seeded&#8221; that certificate as being trusted by the system. From this point on, the affected Mac OS X systems will trust this certificate <b>no matter which domain name it is being served from</b>.</li>
<li>Since the owner of the rogue hotspot controls your DNS as well, he can now direct all your traffic through his own servers. The T-Mobile login page, PayPal.com, your web email — all will appear in their correct addresses, with SSL enabled, and with the SSL lock icon on the corner of your Safari window. Everything seems to be just fine, but behind the scenes, all of those sites are using the www.validcertificate.example certificate and the owner of the hotspot is recording all of your seemingly-encrypted traffic.</li>
</ul>

<p>Scary? Yeah. If you’re still on Tiger or Panther, install the software update immediately. If you can’t, at least click the SSL icon on all sites you navigate to — the certificate details will not be right if you are being spoofed. For more info, keep checking the DHS&#8217;s <a href="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-4680">National Vulnerability Database</a> for their take on the issue (not online yet).</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Knox 1.5.3 for Leopard is coming, but…</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2007/10/knox-153-for-leopard-is-coming-but.html" />
    <id>tag:blog.karppinen.fi,2007://1.237</id>

    <published>2007-10-26T16:52:48Z</published>
    <updated>2008-01-02T11:16:34Z</updated>

    <summary>Here’s a quote from Apple’s ADC Membership Agreement, the contract that governs the use of pre-release seeds of Leopard: Further, you certify that you will not transfer or export any product, process or service that is the direct product of...</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="MK&amp;C" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Mac" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>Here’s a quote from Apple’s <a href="http://developer.apple.com/membership/pdf/terms.pdf">ADC Membership Agreement</a>, the contract that governs the use of pre-release seeds of Leopard:</p>

<blockquote>Further, you certify that you will not transfer or export any product, process or service that is the direct product of any Apple pre-release software and that <b><i>final testing will be done with any finished product that will be released to the mass market.</i></b> [emphasis ours]</blockquote>

<p>So, yes, a couple more days before the free Leopard update for <a href="http://www.knoxformac.com/">Knox</a>. We’re very far in its development, but only got the final Leopard DVDs today. Please bear with us as we work to bring this update to you.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>Embedding frameworks in loadable bundles</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2007/08/embedding-frameworks-in-loadable-bundles.html" />
    <id>tag:blog.karppinen.fi,2007://1.236</id>

    <published>2007-08-11T22:11:47Z</published>
    <updated>2008-01-02T11:16:34Z</updated>

    <summary>Jeff Johnson delves deep into framework linking on Mac OS X on this great post about his one BaseTen commit....</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="Elsewhere" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p>Jeff Johnson delves deep into framework linking on Mac OS X on this great post about his <a href="http://lapcatsoftware.com/blog/2007/08/11/embedding-frameworks-in-loadable-bundles/">one BaseTen commit</a>.</p>
]]>
        

    </content>
</entry>

<entry>
    <title>The 64bit transition is complete</title>
    <link rel="alternate" type="text/html" href="http://blog.karppinen.fi/2007/08/the-64bit-transition-is-complete.html" />
    <id>tag:blog.karppinen.fi,2007://1.235</id>

    <published>2007-08-08T08:34:20Z</published>
    <updated>2008-01-02T11:16:34Z</updated>

    <summary>The new Mac mini has a Core 2 Duo processor, meaning that the last of Apple’s Mac products has now transitioned to a 64-bit CPU. For the first time ever, all shipping Macs are 64-bit computers. Welcome to the future....</summary>
    <author>
        <name>Marko Karppinen</name>
        
    </author>
    
        <category term="Elsewhere" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.karppinen.fi/">
        <![CDATA[<p><a href="http://www.apple.com/macmini/">The new Mac mini</a> has a Core 2 Duo processor, meaning that the last of Apple&#8217;s Mac products has now transitioned to a 64-bit CPU. For the first time ever, all shipping Macs are 64-bit computers. Welcome to the future.</p>
]]>
        

    </content>
</entry>

</feed>
