No keychain access or system profiler or mail - very alarmed

Today I repaired permissions and backed up my system to an external drive with silverkeeper 1.3. I also ran Macjanitor 1.2.1. I have been using OS 10.4.3 for about 3 weeks with no problem although just lately things seemed a little slow, which is why I was doing maintainance. Everything was working fine, includin Mail, after the maintenance. Shut down.
Returned home, started up, Mail icon bounces once, won't open. System Profiler opens but won't run. Keychain access bounces in the dock once, stops. Safari is fine, so is Address book. Disk Utility can open but only gives me the option to restore a disk. The disk utility log says "No icon found for DMdisk object" This is getting VERY SCARY!
Anyone have any ideas? I am pretty sure macjanitor was a dumb thing to do as it wasn't the latest version and maybe isn't tiger compatible.. Has it trashed something essential?
Thanks
Phoebe

This crash followed a backup to an external drive. Didn't read the part in the instructions that say "always create a fresh backup after installing a new system"
Had to reinstall then restore files from the backup.

Similar Messages

Unauthorized Keychain Access - System

When I opened up the keychain access from Utilities I found something very strange. Under "System" I found an access titled " F* Bush", kind="airport network access", keychain="system". It took place on the same day I switched and installed a new wireless modem router (model DLINK DSL-G624T). On that day I also synchronized with my MacbookPro, which had unauthorized access over 1 year ago from this same "user" due to no encryption on the wireless network (didn't work with MacbookPro and former Netopia router which is why I changed).
When I try to "show password" and enter the admin ID and password I get a message "kcproxy wants to use your confidential information stored in "f* bush" in your keychain. Do you want to allow access to this item?"
Should I be concerned about this? I currently have WAP security in place to block unauthorized access. Not sure if it is too late.

Thanks for the link -- the thread was most helpful. Since this all came about as a result of changing my Active Directory password on the corporate network, the info in that thread tends to confirm my suspicion that the system entry is overriding the entry that I changed.
I'm not sure that I agree with Jim R.'s commentary, though:
Nobody owns the system keychain really, not even root. The System keychain is a shared keychain the system uses the store items available for all user accounts on the computer. If it were owned by root and had the root password, then other accounts would need the root password in order to use it. The fact that it doesn't allow you to view stored passwords is a security measure. This way, users can use system-wide resources that have been set up without actually knowing the passwords, not even other admins.
The reason for having root is to be able to alter system resources that others can access. There are many other resources in the system that can be accessed by everyone but altered only by root. Now we can argue about whether others in the System Admin group can modify a resource, but root should definitely be able to access and alter every resource on the system; every other O/S I've used has at least one such account. Without it, you give up the ability to control your own system.
Thanks,
--Gregory

Access system profiler after clean install

I just did a clean install of Mavericks on a laptop that I am going to sell. I forgot to write down the system information (i.e. RAM, processor, version) before doing the install now I can't seem to find a way to access the system profiler to get this info. I can't get the menu to show during the regular install process (though I remember being able to do this before on previous versions), I also looked through the recovery partition but didn't see anything there. Am I missing something?

 menu/About This Mac/More Info/System Report?
Selling old Mac
Selling old Mac (2)
Selling old Mac (3)
Selling old Mac (4) Apple support

Create a Distribution Certificate as a p.12 file in Keychain Access not working?

I need to create a Distribution Certificate as a p.12 file. I downloaded my ios_distribution.cer file from iOS Provisioning Portal/Certificates/Distribution/Download but this file will not install on my Keychain Access Certificates. Once installed I need to export as .p12. Why can't I install this .cer file to my keychain access? Thanks

Hi EDUR142, did you find a way round this? If so, please let me know.
I currently can see that these certificates are there in Keychain Access under System'Certificates'.
However in System'Keys' the relevant keys are not there. And in Login'Keys' there are 4 keys that might be the correct ones: 2 public keys, 2 private keys. BUT they do not have an arrow on the left so I cannot see if the correct certificate is associated with them (as it described in the Adobe step by step guide to DPS pg19).
If this is simliar to your issue last year, and you found a solution, pls reply. Thank you.

Mail.app blocked from Keychain access by Sandboxd

Working on a clean install of Yosemite. Worked perfect for the first 2 weeks. Then mail all of a sudden cannot send without putting in admin creds for keychain access. I have done all the keychain resets, removed the account and re-added it. Obviously there has to be a way to add an application to trusted status for Security Server/sandbox to allow it access. The question is where and how.
From Log Files:
12/8/14 9:44:33.493 AM com.apple.SecurityServer[57]: Sandbox denied authorizing right 'system.keychain.modify' by client '/Applications/Mail.app' [1240]
12/8/14 9:44:34.175 AM sandboxd[302]: ([1240]) Mail(1240) deny authorization-right-obtain system.keychain.modify
12/8/14 9:58:06.604 AM com.apple.SecurityServer[57]: Sandbox denied authorizing right 'system.keychain.modify' by client '/Applications/Mail.app' [1240]
Full Report Output:
Mail(1240) deny authorization-right-obtain system.keychain.modify
Process:         Mail [1240]
Path:            /Applications/Mail.app/Contents/MacOS/Mail
Load Address:    0x104b86000
Identifier:      com.apple.mail
Version:         1993 (8.1)
Build Info:      1-Mail~1993000000000000
Code Type:       x86_64 (Native)
Parent Process: launchd [1]
Date/Time:       2014-12-08 09:44:33.531 -0500
OS Version:      Mac OS X 10.10.1 (14B25)
Report Version: 8
Thread 0:
0   libsystem_kernel.dylib         0x00007fff82a0d52e mach_msg_trap + 10
1   CoreFoundation                 0x00007fff839a7b14 __CFRunLoopServiceMachPort + 212
2   CoreFoundation                 0x00007fff839a6fdb __CFRunLoopRun + 1371
3   CoreFoundation                 0x00007fff839a6838 CFRunLoopRunSpecific + 296
4   HIToolbox                     0x00007fff8f99d43f RunCurrentEventLoopInMode + 235
5   HIToolbox                     0x00007fff8f99d1ba ReceiveNextEventCommon + 431
6   HIToolbox                     0x00007fff8f99cffb _BlockUntilNextEventMatchingListInModeWithFilter + 71
7   AppKit                         0x00007fff80c626d1 _DPSNextEvent + 964
8   AppKit                         0x00007fff80c61e80 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
9   AppKit                         0x00007fff80c55e23 -[NSApplication run] + 594
10 AppKit                         0x00007fff80c412d4 NSApplicationMain + 1832
11 libdyld.dylib                 0x00007fff851d95c9 start + 1
Thread 1:
0   libsystem_kernel.dylib         0x00007fff82a1322e kevent64 + 10
1   libdispatch.dylib             0x00007fff88ac9a6a _dispatch_mgr_init + 0
Thread 2:
0   libsystem_kernel.dylib         0x00007fff82a0d52e mach_msg_trap + 10
1   CoreFoundation                 0x00007fff839a7b14 __CFRunLoopServiceMachPort + 212
2   CoreFoundation                 0x00007fff839a6fdb __CFRunLoopRun + 1371
3   CoreFoundation                 0x00007fff839a6838 CFRunLoopRunSpecific + 296
4   CFNetwork                     0x00007fff89e14d20 +[NSURLConnection(Loader) _resourceLoadLoop:] + 434
5   Foundation                     0x00007fff8ee8bb7a __NSThread__main__ + 1345
6   libsystem_pthread.dylib       0x00007fff8d0cc2fc _pthread_body + 131
7   libsystem_pthread.dylib       0x00007fff8d0cc279 _pthread_body + 0
8   libsystem_pthread.dylib       0x00007fff8d0ca4b1 thread_start + 13
Thread 3:
0   libsystem_kernel.dylib         0x00007fff82a123f6 __select + 10
1   libsystem_pthread.dylib       0x00007fff8d0cc2fc _pthread_body + 131
2   libsystem_pthread.dylib       0x00007fff8d0cc279 _pthread_body + 0
3   libsystem_pthread.dylib       0x00007fff8d0ca4b1 thread_start + 13
Thread 4:
0   libsystem_kernel.dylib         0x00007fff82a0d52e mach_msg_trap + 10
1   CoreFoundation                 0x00007fff839a7b14 __CFRunLoopServiceMachPort + 212
2   CoreFoundation                 0x00007fff839a6fdb __CFRunLoopRun + 1371
3   CoreFoundation                 0x00007fff839a6838 CFRunLoopRunSpecific + 296
4   AppKit                         0x00007fff80dc57a7 _NSEventThread + 137
5   libsystem_pthread.dylib       0x00007fff8d0cc2fc _pthread_body + 131
6   libsystem_pthread.dylib       0x00007fff8d0cc279 _pthread_body + 0
7   libsystem_pthread.dylib       0x00007fff8d0ca4b1 thread_start + 13
Thread 5:
0   libsystem_kernel.dylib         0x00007fff82a0d52e mach_msg_trap + 10
1   QuartzCore                     0x00007fff8ec07d63 CA::Render::Server::server_thread(void*) + 198
2   QuartzCore                     0x00007fff8ec07c96 thread_fun + 25
3   libsystem_pthread.dylib       0x00007fff8d0cc2fc _pthread_body + 131
4   libsystem_pthread.dylib       0x00007fff8d0cc279 _pthread_body + 0
5   libsystem_pthread.dylib       0x00007fff8d0ca4b1 thread_start + 13
Thread 6:
0   libsystem_kernel.dylib         0x00007fff82a12132 __psynch_cvwait + 10
1   libc++.1.dylib                 0x00007fff81f4ac95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   JavaScriptCore                 0x00007fff8df8d2d4 JSC::BlockAllocator::blockFreeingThreadMain() + 228
3   JavaScriptCore                 0x00007fff8df82a9f ***::wtfThreadEntryPoint(void*) + 15
4   libsystem_pthread.dylib       0x00007fff8d0cc2fc _pthread_body + 131
5   libsystem_pthread.dylib       0x00007fff8d0cc279 _pthread_body + 0
6   libsystem_pthread.dylib       0x00007fff8d0ca4b1 thread_start + 13
Thread 7:
0   libsystem_kernel.dylib         0x00007fff82a12132 __psynch_cvwait + 10
1   libc++.1.dylib                 0x00007fff81f4ac95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   JavaScriptCore                 0x00007fff8df8d86b JSC::GCThread::waitForNextPhase() + 171
3   JavaScriptCore                 0x00007fff8df8d6c8 JSC::GCThread::gcThreadMain() + 88
4   JavaScriptCore                 0x00007fff8df82a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib       0x00007fff8d0cc2fc _pthread_body + 131
6   libsystem_pthread.dylib       0x00007fff8d0cc279 _pthread_body + 0
7   libsystem_pthread.dylib       0x00007fff8d0ca4b1 thread_start + 13
Thread 8:
0   libsystem_kernel.dylib         0x00007fff82a12132 __psynch_cvwait + 10
1   libc++.1.dylib                 0x00007fff81f4ac95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   JavaScriptCore                 0x00007fff8df8d2d4 JSC::BlockAllocator::blockFreeingThreadMain() + 228
3   JavaScriptCore                 0x00007fff8df82a9f ***::wtfThreadEntryPoint(void*) + 15
4   libsystem_pthread.dylib       0x00007fff8d0cc2fc _pthread_body + 131
5   libsystem_pthread.dylib       0x00007fff8d0cc279 _pthread_body + 0
6   libsystem_pthread.dylib       0x00007fff8d0ca4b1 thread_start + 13
Thread 9:
0   libsystem_kernel.dylib         0x00007fff82a12132 __psynch_cvwait + 10
1   libc++.1.dylib                 0x00007fff81f4ac95 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
2   JavaScriptCore                 0x00007fff8df8d86b JSC::GCThread::waitForNextPhase() + 171
3   JavaScriptCore                 0x00007fff8df8d6c8 JSC::GCThread::gcThreadMain() + 88
4   JavaScriptCore                 0x00007fff8df82a9f ***::wtfThreadEntryPoint(void*) + 15
5   libsystem_pthread.dylib       0x00007fff8d0cc2fc _pthread_body + 131
6   libsystem_pthread.dylib       0x00007fff8d0cc279 _pthread_body + 0
7   libsystem_pthread.dylib       0x00007fff8d0ca4b1 thread_start + 13
Thread 10:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 11:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 12:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 13:
0   libsystem_kernel.dylib         0x00007fff82a12132 __psynch_cvwait + 10
1   Foundation                     0x00007fff8ee5d400 -[NSCondition waitUntilDate:] + 343
2   IMAP                           0x00007fff8d3df027 -[IMAPGateway isExpensive] + 424
3   IMAP                           0x00007fff8d3fca6b -[IMAPMailboxSyncEngine _cacheMessagesWithMonitor:] + 847
4   IMAP                           0x00007fff8d3f68b2 -[IMAPMailboxSyncEngine _goWithMessages:] + 2339
5   IMAP                           0x00007fff8d3f6c79 -[IMAPMailboxSyncEngine _goWithMessagesIfNeeded:] + 61
6   CoreFoundation                 0x00007fff8397033c __invoking___ + 140
7   CoreFoundation                 0x00007fff83970192 -[NSInvocation invoke] + 290
8   MailCore                       0x00007fff8d2250cc -[MCMonitoredInvocation invoke] + 242
9   MailCore                       0x00007fff8d24f1d4 -[MCThrowingInvocationOperation main] + 48
10 MailCore                       0x00007fff8d1d771d -[_MCInvocationOperation main] + 426
11 Foundation                     0x00007fff8ee2b59c -[__NSOperationInternal _start:] + 653
12 Foundation                     0x00007fff8ee2b1a3 __NSOQSchedule_f + 184
13 libdispatch.dylib             0x00007fff88ac6c13 _dispatch_client_callout + 8
14 libdispatch.dylib             0x00007fff88aca365 _dispatch_queue_drain + 1100
15 libdispatch.dylib             0x00007fff88acbecc _dispatch_queue_invoke + 202
16 libdispatch.dylib             0x00007fff88ac96b7 _dispatch_root_queue_drain + 463
17 libdispatch.dylib             0x00007fff88ad7fe4 _dispatch_worker_thread3 + 91
18 libsystem_pthread.dylib       0x00007fff8d0cc6cb _pthread_wqthread + 729
19 libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 14:
0   libsystem_kernel.dylib         0x00007fff82a0d52e mach_msg_trap + 10
1   CoreFoundation                 0x00007fff839a7b14 __CFRunLoopServiceMachPort + 212
2   CoreFoundation                 0x00007fff839a6fdb __CFRunLoopRun + 1371
3   CoreFoundation                 0x00007fff839a6838 CFRunLoopRunSpecific + 296
4   Foundation                     0x00007fff8ee8dab9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 278
5   AppKit                         0x00007fff80ebfa98 -[NSAnimation(NSInternal) _runBlocking] + 390
6   AppKit                         0x00007fff80ebf8ea -[NSAnimation(NSInternal) _animationThread] + 66
7   libdispatch.dylib             0x00007fff88acb323 _dispatch_call_block_and_release + 12
8   libdispatch.dylib             0x00007fff88ac6c13 _dispatch_client_callout + 8
9   libdispatch.dylib             0x00007fff88ac988f _dispatch_root_queue_drain + 935
10 libdispatch.dylib             0x00007fff88ad7fe4 _dispatch_worker_thread3 + 91
11 libsystem_pthread.dylib       0x00007fff8d0cc6cb _pthread_wqthread + 729
12 libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 15:
0   libsystem_kernel.dylib         0x00007fff82a0d52e mach_msg_trap + 10
1   Security                       0x00007fff8f32cf80 ucsp_client_generateSignature + 200
2   Security                       0x00007fff8f332958 Security::SecurityServer::ClientSession::generateSignature(Security::Context const&, unsigned int, Security::CssmData const&, Security::CssmData&, Security::Allocator&, unsigned int) + 190
3   Security                       0x00007fff8f23a6f6 SSSignatureContext::sign(Security::CssmData&) + 370
4   Security                       0x00007fff8f23a565 SSSignatureContext::outputSize(bool, unsigned long) + 183
5   Security                       0x00007fff8f1bd645 Security::CSPFullPluginSession::CSPContext::final(Security::CssmData&, Security::Allocator&) + 33
6   Security                       0x00007fff8f33bfe0 cssm_SignData(long, unsigned long long, cssm_context const*, cssm_data const*, unsigned int, unsigned int, cssm_data*) + 307
7   Security                       0x00007fff8f34cb66 CSSM_SignData + 103
8   Security                       0x00007fff8f21a7fa SEC_SignData + 256
9   Security                       0x00007fff8f219204 SecCmsSignerInfoSign + 434
10 Security                       0x00007fff8f2183b4 SecCmsSignedDataEncodeAfterData + 264
11 Security                       0x00007fff8f2157d9 nss_cms_encoder_notify + 912
12 Security                       0x00007fff8f1bfd7d SEC_ASN1EncoderUpdate + 385
13 Security                       0x00007fff8f215b5e SecCmsEncoderFinish + 158
14 Security                       0x00007fff8f2618fc CMSEncoderCopyEncodedContent + 136
15 MailCore                       0x00007fff8d246696 -[MCMimePart(SMIMEEncoding) newSignedPartWithData:sender:signatureData:] + 4621
16 MailCore                       0x00007fff8d1f0a24 -[MCMessageGenerator _newOutgoingMessageFromTopLevelMimePart:topLevelHeaders:withPartData:] + 632
17 MailCore                       0x00007fff8d1edd2e -[MCMessageGenerator newMessageWithHtmlString:plainTextAlternative:otherHtmlStringsAndAttachments:he aders:] + 3105
18 Mail                           0x0000000104c26f39
19 Mail                           0x0000000104c25e18
20 Mail                           0x0000000104c243bd
21 CoreFoundation                 0x00007fff8397033c __invoking___ + 140
22 CoreFoundation                 0x00007fff83970192 -[NSInvocation invoke] + 290
23 MailCore                       0x00007fff8d2250cc -[MCMonitoredInvocation invoke] + 242
24 MailCore                       0x00007fff8d24f1d4 -[MCThrowingInvocationOperation main] + 48
25 MailCore                       0x00007fff8d1d771d -[_MCInvocationOperation main] + 426
26 Foundation                     0x00007fff8ee2b59c -[__NSOperationInternal _start:] + 653
27 Foundation                     0x00007fff8ee2b1a3 __NSOQSchedule_f + 184
28 libdispatch.dylib             0x00007fff88ac6c13 _dispatch_client_callout + 8
29 libdispatch.dylib             0x00007fff88aca365 _dispatch_queue_drain + 1100
30 libdispatch.dylib             0x00007fff88acbecc _dispatch_queue_invoke + 202
31 libdispatch.dylib             0x00007fff88ac96b7 _dispatch_root_queue_drain + 463
32 libdispatch.dylib             0x00007fff88ad7fe4 _dispatch_worker_thread3 + 91
33 libsystem_pthread.dylib       0x00007fff8d0cc6cb _pthread_wqthread + 729
34 libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 16:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 17:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 18:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 19:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 20:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 21:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 22:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 23:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 24:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 25:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 26:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 27:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 28:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 29:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 30:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 31:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Thread 32:
0   libsystem_kernel.dylib         0x00007fff82a12946 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8d0ca4a1 start_wqthread + 13
Binary Images:
       0x104b86000 -        0x104f1bff7 com.apple.mail (8.1 - 1993) <dc7d598c-884d-3bc3-9d97-f2cb5d1ed551> /Applications/Mail.app/Contents/MacOS/Mail
    0x7fff80c3e000 -     0x7fff8177ffff com.apple.AppKit (6.9 - 1343.16) <c98db43f-4245-3e6e-a4ee-37daee33e174> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff81f43000 -     0x7fff81f97fff libc++.1.dylib (120) <1b9530fd-989b-3174-bb1c-bdc159501710> /usr/lib/libc++.1.dylib
    0x7fff829fc000 -     0x7fff82a19fff libsystem_kernel.dylib (2782.1.97) <93e0e0a9-75b6-3904-bb4e-4bc7c05f4b6b> /usr/lib/system/libsystem_kernel.dylib
    0x7fff83935000 -     0x7fff83ccbfff com.apple.CoreFoundation (6.9 - 1151.16) <f2b088af-a5c6-3fae-9eb4-7931af6359e4> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff851d6000 -     0x7fff851d9ff7 libdyld.dylib (353.2.1) <19faf435-c165-3374-9def-d7bba7d61db6> /usr/lib/system/libdyld.dylib
    0x7fff88ac5000 -     0x7fff88aefff7 libdispatch.dylib (442.1.4) <502cf32b-669b-3709-8862-08188225e4f0> /usr/lib/system/libdispatch.dylib
    0x7fff89d74000 -     0x7fff89f77ff3 com.apple.CFNetwork (720.1.1 - 720.1.1) <a82e71b3-2cdb-3840-a476-f2304d896e03> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff8d0c9000 -     0x7fff8d0d2fff libsystem_pthread.dylib (105.1.4) <26b1897f-0cd3-30f3-b55a-37cb45062d73> /usr/lib/system/libsystem_pthread.dylib
    0x7fff8d19f000 -     0x7fff8d27eff7 com.apple.MailCore (8.1 - 1993) <dc6b9e54-74a0-37cd-b693-d54e79df491b> /System/Library/PrivateFrameworks/MailCore.framework/Versions/A/MailCore
    0x7fff8d3ab000 -     0x7fff8d42bff7 com.apple.IMAP (8.1 - 1993) <214b764f-2a95-3939-857b-ddaa92a2330d> /System/Library/PrivateFrameworks/IMAP.framework/Versions/A/IMAP
    0x7fff8df78000 -     0x7fff8e48bff3 com.apple.JavaScriptCore (10600 - 10600.1.17) <ce5255cc-e13f-3694-b6dd-5285356bfcc0> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
    0x7fff8ebe0000 -     0x7fff8ed90ff7 com.apple.QuartzCore (1.10 - 361.11) <7382e4a9-10b0-3877-b9d7-fa84dc71ba55> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff8ee23000 -     0x7fff8f151ff7 com.apple.Foundation (6.9 - 1151.16) <18edd673-a010-3e99-956e-da594ce1fa80> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff8f19b000 -     0x7fff8f403ffb com.apple.security (7.0 - 57031.1.35) <96141d1f-614e-32c4-8ac2-f47481f23f43> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff8f96f000 -     0x7fff8fc71fff com.apple.HIToolbox (2.1.1) <9dd121b5-b7eb-3c43-8155-61a4417f8e9a> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox

I'm having the same issue since yesterday night, after changing the configuration of one specific SMTP connection.
Mail has been asking me for passwords several times in a row on every click in the inbox or on sending a mail.
The log message is the same, along the lines of "Mail(xxx) deny authorization-right-obtain system.keychain.modify".

Mail automatically adds certificates to Keychain Access. How to disable?

Is there a way to tell Mail not to automatically store certificates from digitally signed emails (in this case, using Verisign) in Keychain Access?
The problem is this:
When the old certificate expires from someone else, I create a new one, and have them send a signed email to my address. Mail then automatically adds the new certificate to my Keychain Access. I then go into Keychain Access and delete the old certificate, so that I can send secure and encrypted messages to them. However, if I go back to one of their saved OLD emails, it automatically adds the old certificate back to my Keychain Access. And when I go to create a new email to them, it often will use that old certificate, which no longer works for them.
I am looking for a way to better manage this or find out what others are doing out there with the same problem.
Keychain should have an "archive" section to put old certificates into. These then can be referenced to open old secure and encrypted messages, but not allowed to be used for sending new email.

Additionally, lets say something happens to your certificate and you need to download it again. In this case, from Verisign. A problem I have run into is when I go to Verisign, I am presented with the option of re-downloading my certificate. If I do this, there is no way on the Mac system that you specify this re-downloaded is your certificate. So I have to download a new certificate and then re-add my certificate to the rest of the employees and get theirs.
There needs to be an option to select "This is my certificate". Very much like in AddressBook, how you can specify different VCards as your own.

Mail & Mavericks & Keychain Access

Hello,
After updating to Mavericks (from Mountain Lion), I noticed that there's a new keychain called "local items" inside Keychain Access App.
so I have a couple of questions regarding this and my usage of Mail:
1) from what I read in this forum, "local items" is the keychain created by Mavericks, it should sync to the login keychain (which is usually, and certainly in my case, the default keychain, meaning it is in bold face on the left hand side of the Keychain Access window). And as far as I understand, if you have icloud enabled, this keychain would be called "icloud keychain", if not, it will remain the name "local items", is this correct? I do not want to have anything to do with icloud, so I don't have any icloud keychain. When I log into the my account on the mac both the login and the "local items" keychain are unlocked (I guess this makes sense if they are supposed to be synced. So basically this is my understanding of this "local items" keychain, please correct/inform me if this understanding is not correct.
2) now, I noticed that the passwords that I typed in for my e-mail accounts (set up in Apple's Mail) are saved inside this "local items" keychain. So everything seems to be fine. However, I noticed that the passwords saved inside this "local items" keychain cannot be edited in the "access control" panel (this is accessed by double clicking the password item and click on the "access control" tab.) This is odd because all the other items in the "login" keychain can be edited in this way.
3) so my main goal is to ask Mail to NOT remember my password (I know this is not the prefer setting for most users, but I prefer to have it this way). In Leopard, Mail had a little checkbox where you set up your account that asks the application to NOT remember the password. This is really handy because it prompts me to re-enter the password whenever I restart the application, which is exactly what I want it to behave. But since upgrading to Mountain Lion (I'm not sure how it is in Snow Leopard or Lion, as I jumped from Leopard straight to Mountain Lion, and now to Mavericks), this box has disappearred. I found a work around online. Before Mavericks, the mail account passwords are saved (if I remember correctly) in the login keychain, the work around works by saving (i.e. dragging) all your email passwords into a separate/new keychain (let's call it Keychain A) which has a different password than your login keychain (which, by definition, is unlocked upon login). So I set this up and Mail automatically knows to prompt me to enter the password for Keychain A in order to access my e-mail account passwords. This doesn't behave exactly like unchecking "remember the password" box in Leopard, but it comes close. and I was happy with this work around. However, now having upgraded to MAvericks, Mail insisted on using "local items" as keychain, and keeps asking me the passwords for my e-mail accounts (NOT the local item keychain password, since my local item keychain IS synced up with Login keychain, therefore they are both unlocked upon me logging in) so that it can store them. The thing is I do NOT want the e-mail passwords to be stored inside "local items" keychain (because I don't want account access to equal e-mail access (for reasons I do not want to get into, but I feel like this is not too much to ask and was possible before so why not now?).
Could someone please help me out with this? I've called Apple, and they were quite annoyed with me because the person I talked to keeps saying that I'm not using keychain for the way it is suppoed to be used, but my question then, is, if I canot get applications to use special keychains I set up, what's the use of the function "add new keychain" inside keychain access? (in fact, the phone supporter basically keep saying "I don't know" to my questions and finally offered me to talk to a senior advisor, at that point I had to leave (and after 1hour on the phone I was quite fed up anyway). so I thought I should turn to the forum.....
so a recap/summary:
my login and local items keychain sync up fine
but I don't want Mail to store my e-mail passwords in the local items keychain
I want to make Mail use another keychain (i.e. a keychain I set up myself), can we possible to this?
or another other work around that will make Mail to prompt me to enter passwords when I fire up the application (not constantly, but just when I restarting the application, OR after the computer wakes up)
I'd appreciate any pointers!
thank you very much!
sakura

I have the same concerns. I'm frustrated that the Mail app doesn't currently allow you to use a separate keychain for the passwords. After many years with Keychain I am being tempted to look to a third party. Or perhaps it's time to look for a third party mail app? This is a security issue since email is the primary way that a password change is verified with other accounts.

How can I access an unsupported usb device that's seen by system profiler

is there a way to access an unsupported usb device? my parents bought my daughter a cheap and easy to use digital camera and I am looking for a way to access the photos. the camera's manual mentions that there is no mac driver and there are no plans to develop one. I plug it in anyways in the event the system / Iphoto recognizes this, But I get nothing on the desktop as in a generic disk image icon. I open system profiler and My G4 knows the camera is plugged in. If this interface between the two is recognized how can I access the camera?
does a driver have to be written to allow access? I saw a usb dev kit on version tracker but I have no clue as to how to write a driver. I could get a flash card reader but I was hoping that there may be some back door or an app somewhere to allow me to get the photos off the camera.
thanks!!!

Hi, Israel.
You wrote: " I plug it in anyways in the event the system / Iphoto recognizes this"See if Image Capture recognizes the camera. Launch Image Capture, which is in the Macintosh HD > Applications folder.
Otherwise, you're probably going to have to go the route of using a card reader. While the connection may be USB, they may be using some non-standard implementation that requires a driver.
Writing drivers is not something you'd want to even attempt since you didn't create the hardware!
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

Should the passwords in 'System keychain' (in Keychain Access) normally be accessible to the owner/administrator?

Should the passwords in 'System keychain' (in Keychain Access) normally be accessible to the owner/administrator or not?
If not, would it be possible to gain access via the Root Account?
I can access the passwords in 'Login keychain' (in Keychain Access). But when I try to access the passwords in 'System keychain' I'm asked for the Keychain Access password! I've never set such a password. I've only ever used one password - my owner/administrator password. But this isn't accepted when I try to access the passwords in 'System keychain'.
Please note, this question was previously posted in the OSX Tiger forum but no-one offered an answer
Thanks,
iHope

Seems this is a characteristic of the system keychain.
Check out this thread...and furtwanglerian's response....
http://discussions.apple.com/thread.jspa?messageID=8767033&#8767033
closed

Two System keychains in Keychain Access

Hi there
When I go into Keychain Access I see two 'system' keychains listed. I believe they are multiple references to the same keychain. Is this something I should worry about and might it affect system performance?
Many thanks
Paul Blake
Macbook Mac OS X (10.4.8)

it's still just one system keychain. you just opened it twice. this is quite harmless. if it really bothers you quit keychain access and delete the file /users/username/library/preferences/com.apple.security.plist. then start keychain access and there will be just one system keychain there.

Can't Access System Profiler Or Disc Utility

Hi! I have a iMac G5 With leopard software, 10.5.8 version. And I can't open the system profiler or disc utilities at all. I've tried everything basically, Should I reinstall my Leopard software?

Something that came to mind after rereading you post relates to the particulars of a "hard" reset on the Snow.
A “hard” reset removes current setting from the base station. You must then connect to the base station using the AirPort Admin Utility and upload AirPort 2.0 or later software to return the base station to its default settings. A base station in a hard reset is only accessible through the LAN port, not via wireless connections ... so attempting to access with the AAU, via a wireless client, will not work.
The following is the process to reload the AirPort software: AirPort Base Station (Dual Ethernet) : How to reload software from Mac OS X

Keychain Access is crashing my system

I'm having a problem, the root of which I believe is Keychain Access.app. Not exactly sure when it started happening. I'm on a Dual 2.5 G5 PowerMac, 4GB RAM, 250GB HD, OS 10.4.10.
Here's the progression of events:
If I update an app that has passwords stored in my keychain (any app, Apple or 3rd party), the next time I open that app I'm greeted with the following message:
Appname has been updated. Do you want to allow the new version to access the same keychain items (such as passwords) as the previous version?
This change is permanent and affects all keychain items used by Appname.
Don't Change/Change All
If I click Change All the system pauses for a few moments and I get a message saying:
Your startup disk is almost full.
You need to make more space available on your startup disk by deleting files.
? Do not warn me about this disk again.
And if I Get Info on my hard drive I can see that it has 138.37 GB available, which is correct.
The system continues to act wonky until I restart. For example, I can't empty the trash because I do not have enough permissions. Any applications that require Keychain Access.app for passwords can't access their passwords. I can't even unlock the system prefs after this happens, it just hangs when I click the lock icon. Upon opening Keychain Access.app after the events described above (but before restarting) all of my keychains are missing! They come back after I restart. Before I restart, if I try to Fast User Switch to a different account, the system turns the screen-cube, but it never brings up a user list; instead it sits at a blue screen until I do a hard shutdown.
This happens every single time an app wants to update my keychain, without fail. I've tried running Keychain First Aid, Disk First Aid, and fsck (in single user mode). I've repaired the permissions. I've installed system updates (10.4.10) since this started happening. I made a new user and opened an app that requires keychain to update, and I ran into the exact same problems.
How can I fix this without resorting to Archive and Install? (Please don't just tell me to install Leopard---I'm going to do this eventually, and hopefully it will fix my problem, but I'm quite busy for the next few weeks and I can't take time enough away from my projects to do this.)

Yep, tried that too.
I don't have time to reinstall anything that might break in the Archive and Install process. Even if it's not likely that anything will break, I don't want to risk it. This computer is also currently being used to backup multiple TBs of data over the network. Guess I'll just A&I Leopard in a couple weeks.

MB Air won't let me sign in to iCloud from System Preferences. I reset Keychain Access and deleted Accounts plist. No problem signing in via web and on other Mac.

Hi all.
I've just been given an Air. I used Migration Assistant to transfer everything (which didn't work very well: no Contacts transferred and the Air Contacts application can't even open manually transferred Contacts Archive .vcf).
Trying to transfer contacts led me to iCloud - I thought I could copy them from there. Then I discovered that I can't sign in to iCloud via System Preferences. I get two error messages. The most common one is 'you cannot sign in at this time'. I've tried every solution on the web: I reinstalled Yosemite. I reset Keychain Access. I deleted Accounts plist.
The other message I occasionally get is 'This is a valid Apple ID but not an iCloud account'. It is: I'm logged on fine on my MBP, iPhone and iPad.
Any ideas? Thanks in advance,
Aida

So - I have been having this same issue, and while it's not totally resolved for me, I have figured out what's causing it. I am running a machine with two hard drives and to keep my documents on a separate drive from the OS/Applications, I used the Advanced Option to specify the location of my home drive for my user account under "Users & Groups". I've found that if I reset this to the default path of /Macintosh HD/Users/{username}, that it works fine. However Apple has a bug in that this functionality breaks when you specify your own home directory. Hopefully, this will be addressed in an update.

Can't Get Mail Password From Keychain Access.

My neighbour wanted to be reminded of his Mail password.
So we opened Keychain Access and clicked on his internet password and then clicked the i at the bottom of the window.
A new window opened with "Attributes" at the top and we clicked on the "Show Password" box at the bottom.
A window then opened for his Keychain Password. It was different from mine. Mine simply has a Sancel and an OK button at the bottom.
His had 3 buttons - "Deny", "Allow Once" and "Allow Always". (I am not sure whether I have got those last two exactly right).
When he first got his G5 iMac he did not use a password in the initial setup of the computer and never has had one. So we left it blank (except for the flashing cursor) and pressed the Allow Always button.
It said the wrong password had been entered. We tried again several times using each of the Allow buttons but were refused each time.
As the computer has never had a login password what should we do?
I assume that his keychain access password window looks different from mine because he has an earlier version of Tiger than I do.
Ian.

Thanks Matt.
I can't try it now but I suspect it will work.
The big puzzle is why it said the wrong password had been entered when he has no password and we left the box empty.
Four years ago when I too had no password, simply leaving a password request box empty and clicking OK worked.
Ian.

Mail can't write internet accounts in keychain access

Hello,
After having resetted (is this right?) my login keychain, i've noticed *Mail can't write any of my pop and smtp passwords in my new keychain*.
I've tried the *UnlockCaptcha page* from Google, but Mail still won't save my passwords ;(.
_Is this a problem from Mail, Keychain Access or the fact i'm using a laptop?_
Thank you very much.

I can't help you but you are not alone. I am having the same problem.
After using MobileMe to sync my keychains all my macs no longer have mail.app keychain entries. Even after turning off MobileMe keychain syncing Mail.app fails to write a new entry into the keychain for my mail accounts. I am asked for the server passwords each new mail session. It's highly annoying.
I have tried keychain first aid and disk utility. Neither one found any errors.
I'm bumping this to a new thread.

No keychain access or system profiler or mail - very alarmed

Similar Messages

Maybe you are looking for