<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>code signing on Madison&#39;s Blog</title>
    <link>https://solarana.dev/tags/code-signing/</link>
    <description>Recent content in code signing on Madison&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Jan 2019 09:00:00 -0600</lastBuildDate><atom:link href="https://solarana.dev/tags/code-signing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Breaking Code Signing via SSH</title>
      <link>https://solarana.dev/2019/01/20/breaking-code-signing-via-ssh/</link>
      <pubDate>Sun, 20 Jan 2019 09:00:00 -0600</pubDate>
      
      <guid>https://solarana.dev/2019/01/20/breaking-code-signing-via-ssh/</guid>
      <description>Ok, so the title is a bit misleading. Code signing wasn&amp;rsquo;t broken by SSH itself, it was the keychain interactions that occur when using SSH, but some context is needed. When you sign into the developer portal in Xcode, Xcode stores two items in the keychain that allows developer tools to access the developer portal on your behalf: Xcode-Token &amp;amp; Xcode-AlternateDSID. Prior to Xcode 9.3, these items were stored in the normal login keychain.</description>
    </item>
    
  </channel>
</rss>
