Update: Signing Adium for Gatekeeper

[Evan D. Schoenberg, M.D.]

Folks,

Just a status update.

We now have an approved and identity-verified Apple Developer account, associated with Instant Messaging Freedom, Inc., so we will be able to sign Adium with an Apple-provided Mac Developer ID.

However, the com.adiumX.adiumX bundle identifier is marked as "already registered" so we can't get the certificate yet. I believe I registered it into some other Apple registry a long time ago, but I'm not 100% certain of that… in any case, I can't figure out where, or how to free it. I've emailed Apple developer support for help.

-Evan

[Luke the Hiesterman]

While at it, why not submit to the Mac App Store?

Luke

[Jordan]

Could you change it to im.adium.adium without causing tons of problems?

Jordan

[Eric Richie]

Or even just kill the X's?

-Eric

[Evan D. Schoenberg, M.D.]

If we're changing it, it should be to im.adium.adium, not com.adium.adium, definitely.

We'd need upgrade code for any NSUserDefaults preferences; pretty easily done by something like this untested code snippet:

for (NSString *key in [(NSArray *)CFPreferencesCopyKeyList(oldAppID, kCFPreferencesCurrentUser, kCFPreferencesCurrentHost) autorelease]) {

CFPropertyListRef value = CFPreferencesCopyAppValue((CFStringRef)key, oldAppID);

CFPreferencesSetAppValue((CFStringRef)key,

value,

newAppID);

}

We'll definitely end up re-prompting for keychain access, too, with a new bundle ID, but I think we'll do that anyways because we're changing code signing identities.

-Evan

[Evan D. Schoenberg, M.D.]

Unfortunately because it would be a violation of the GPL license to do so.

[Eric Richie]

As long as the X's die. ;)

-Eric

[David Smith]

CFPreferences{Copy, Set}Multiple() would be more suited, I think. Be wary of sandboxing issues though, if Adium decides to do that.

David

[Evan D. Schoenberg, M.D.]

Good call, thanks.

We'll move to a new bundle ID in one version, and add sandboxing if it's feasible to do so at a later date.  Apple has made the App Store impossible for Adium, so it's not like we have particular urgency to sandbox.

-Evan

[Evan D. Schoenberg, M.D.]

On Tuesday, March 20, 2012 at 8:14 PM, Evan D. Schoenberg, M.D. wrote:

Good call, thanks.

We'll move to a new bundle ID in one version, and add sandboxing if it's feasible to do so at a later date.  Apple has made the App Store impossible for Adium, so it's not like we have particular urgency to sandbox.

Let's hold off on a new bundle ID for now; I'd rather gain active control of the existing one and keep using it for the moment rather than introducing a new one without any real advantage besides us feeling happy for the X being gone.

I just had a pretty funny conversation with a very nice guy, Kyle, in Apple Developer Support:

Him: You've got a bunch of different IDs here.  About 12 spanning a decade or so? adiumx, adium.im, etc.

Me: Yeah, I'm a little schizophrenic in my Apple IDs.

Him: It doesn't help that there's some doctor with your same name who has registered a bunch of different ways, too.

Me: ...

;)

Anyways, I got kicked up to higher-level support as it's a pretty unusual situation, with a bundle id whose registration may go back to the distant past.  They're looking into it and are going to call me back later.

-Evan

[Robert Vehse]

Am 21.03.2012 um 20:14 schrieb Evan D. Schoenberg, M.D.:

> Him: It doesn't help that there's some doctor with your same name who has registered a bunch of different ways, too.
> Me: ...

Hahaha, that's mad stuff.