Hot answers tagged

51

Import/Export works differently in Xcode 5+. This Apple Developer guide shows you how to do it. Your account is shown under Xcode → Preferences → Accounts, and can be exported by clicking the gear icon () in the lower-left.


49

The reason: After installing Security Update 2015-004, multiple users found that they couldn't browse to any website using the root certificate "VeriSign Class 3 Public Primary Certification Authority - G5" without a security warning ("invalid certificate"). 2015-004 updated the list of trusted root CAs, and for a reason I'm still unclear about, many of us ...


15

You can do this from within Xcode. From the Organiser, on the devices tab, you can export your developer profile to a file which you can then import into Xcode on another computer. The step by step process is explained in http://developer.apple.com/library/ios/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/080-Manage_Your_Devices/manage_devices....


12

A report on forums.macrumors.com seems to be fairly similar to yours. This happens as well in Safari 5.1 and is very recent. The solution was to delete: ~/Library/Preferences/com.apple.security.plist


12

Apple KB article HT3930 explains how to configure SSL for servermgrd, the Server Admin web interface. It applies to Mac OS X Server 10.6 so until Apple updates this article part of the steps are confusing / obsolete. Luckily, on Mountain Lion Server (10.8) servermgrd's certificate is stored in the same location as on Mac OS X Server Snow Leopard: in the ...


9

There is no way to add Certificate Authorities to Chrome.app on iOS. The only way to manage them is in Settings > General > Profiles. It seems like this is an issue with Chrome.app that's not resolved yet. See Chrome for iOS ignores trusted root CA certificate. You may get additional help by posting to the Google Chrome Forum (linked before).


9

The answer, as discovered by shizmob, is that Apple moved the location of this preference in Maverics to /Library/Preferences/com.apple.security. So what you need to run is sudo defaults write /Library/Preferences/com.apple.security RSAMaxKeySize -int 8192


9

I had the same problem when logged in via VNC / remote desktop - it appears that if your mac detects a 'security risk' it will prevent you from pressing the "Always Allow" / "Allow" buttons. No error message is shown and the box doesn't shake (although the button does highlight blue when clicked.) The same issue seems to exist with KVM programs such as ...


8

Recent versions of Safari do not appear to display the lock icon or certificate unless all content loaded by the page is https. For example, if the page URL is https but it loads a JavaScript file via http, no lock icon. The only workaround I've found so far is to run the openssl command in Terminal, like this: echo ^d | openssl s_client -connect host....


8

Firstly you'll need to obtain the SSL certificate, sending it to you via email or grabbing it from a web. Once opened (tapping on it from the email attachment, for instance) an installation process will start. On the Install Profile screen, tap on Install. A warning message saying that Installing this profile will change settings on your iPhone will ...


7

Check that the date is correct. This is an error that can be received if your date is set utterly incorrectly, typically due to a flat battery prior to install and not being able to connect to an NTP server to correct.


6

I've since solved the problem, though I'm not sure if this is the right answer for everyone. The problem seemed to come from the certificate automatically generated from apple (com.apple.idms.appleid.prd.[large character string]). A quick Google search didn't tell me what this certificate was for, but I'm sure that deleting it was probably not the best ...


4

Restore the contents of these three directories from a recent backup: ~/Library/Keychains /Library/Keychains /System/Library/Keychains On my system this comprises 18 files and a subdirectory in the user folder ~/Library/Keychains


4

Chances are you installed the certificate that was required by your employers network. For example at my work place we have 802.1x authentication on our Wifi, basically users log in with their normal username and passwords instead of a pre-shared Wifi key. When they log in they must accept a certificate from our servers. This doesn't necessarily mean that ...


3

Apple's .mobileconfig files are signed using PKCS7. The signing certificate data can be shown using the following command: openssl pkcs7 -inform DER -print_certs -in ~/Settings.mobileconfig You can copy/paste ASCII certificate data from the output into a plain text file (with a .cer filename extension) to create copies of the certificates: -----BEGIN ...


3

Unfortunately, Keychain Access (Certificate Assistant) does not have the ability to include a CRL Distribution Point inside of a certificate's extensions section in certificates that it generates. You'll likely notice that your current CA does not have a CRL distribution point specified (even if you've enabled CRL signing as an allowed usage of that ...


3

Yes the installed certificates are valid, however I would advise updating to the latest version of Leopard and make sure that the compromised Diginotar certificates are uninstalled: This link at ps Enable provides an easy method for this. On Root Certificates, they are by their nature long lived since they are the "Master" certificates and having them ...


3

Currently this is how the Apple Configurator works - it doesn't have a provision to load a certificate but instead generates self-signed ones automatically. If I run across a way to hack this, I'll link it here, but if you need profiles to arrive with a signed certificate look into Lion server or another MDM solution. In practice - you only see the ...


3

If You want to change set of system root certificates, they are in /System/Library/Keychains/. Example of using security there is in this answer to similar question.


3

I think this Apple support article has the list you're looking for. It is updated as changes are made: iOS: List of available trusted root certificates And StartCom is on there.


3

The padlock should still be there and by clicking on it, you get the certificate information as before: Clicking on «Show Certificate» gives the details:


3

via Terminal.app and type something like: openssl x509 -noout -text -in ~/Desktop/yourcertificate.crt Where last parameter is a path your certificate file(you can drag and drop that if you like) gives us: Certificate: Data: Version: 3 (0x2) Serial Number: 27 (0x1b) Signature Algorithm: sha1WithRSAEncryption Issuer: ...


3

TextWrangler is also available outside the Mac App Store, and older versions which are compatible with Snow Leopard and Lion can be downloaded from BareBones website This standalone version launches without complaining about being damaged, regardless of the date (so far?).


3

You don't see a profile entry until the first one is saved. It's listed when it shows up immediately below the VPN entry, so be sure you scroll the content up so that VPN and below are visible. Other than that, you can tap through each profile and see details about what entitlements it controls and how it's authenticated and/or cryptographically singed in ...


2

You can script keychain events from the command line with the security command. On Lion and earlier, the worst that will happen if you delete all the system roots is you won't be able to run software update or use iTunes and other applications that interface with secure web services. It might be easier just to make a keychain file you like and shove that in ...


2

It took me a minute to find what he was talking about but near the right corner of the message toolbar you will see an icon that looks like a burst with a checkmark. Click this and it will turn to a burst with an x. Here is a screen shot.


2

Did you perhaps upgrade from an earlier version of OS X? Apparently this error is benign: The X509Anchors keychain is harmless and can be left in place. If you do not use any third-party software that requires this keychain, it can be deleted.


2

This just reared its ugly head again, this time with Yosemite. It also affected all of the browsers I commonly use (Firefox, Chrome, Chrome Canary). I tried to follow the advice here, which involved getting information about the root certificate used by the offending website via the web browser: How to fix: Safari can’t open the page because Safari can’...


2

You need to export your private key from Key Chain access of Mac OSX in which certificates are running successfully or from which developer certificate made and download certificates from Apple Developer Portal, it will work as it works for me.


2

Source of everything I'm about to say: iOS developership. First of all... You can not deploy a development app on a second device without using another one of your 100 devices. You just can't. Now, the list of questions. Yes, you can run development apps that haven't been signed with a distribution certificate. No. The development cert may only be ...



Only top voted, non community-wiki answers of a minimum length are eligible