Keychain Access Question
I purchased iPhoto 11 and when it installed a pop up box asking for Keychain access appeared. I clicked "Allow Every Time." Now that I think about it, should I reverse that and if so, How do I do it.
Also a popuup came up saying UBD wanted access. I didn't give it. Any help appreciated.
Fixed keychain.
Similar Messages
-
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!
sakuraI 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.
-
I am the adminstrator and only user of this MacBook. I need to see an internet password which is not stored on my browser or email client. When I go into Keychain Access and check the Show Password box it asks for Keychain password - that is no problem. Enter password, hit OK, then the message comes up Access to this item is restricted. I have gone into File - Get Info and made it read and write to Administrsators, System, Wheel and myself but it still says Restricted. Any ideas anyone PLEASE!!
I posted the same question elsewhere, but after poking around I discovered the following, which might be helpful.
Open Keychain Access, which is in your Applications/Utilities folder. There should be two sections on the left sidebar, Keychains and Category. When I opened it, only the Category section showed, but I eventually found an arrow which expanded the Keychains section.
Choose Login in the Keychains section, and "Passwords" in the Category section. Use the search field to find the program you need the password for, and double-click on it. A window with that program's label will open. Under the Attributes tab, click on the little Show Password checkbox. You'll be asked for your admin password. Once you've entered it, the password will appear in the Show Password field.
As an aside, I thought this is what I was doing all along, so here's another thing I did before it started working: I found Keychain First Aid and ran both the Verify and Repair options. Both of these reported no problems, but it might have done something to encourage things to work right.*
*As you can tell, I anthropomorphize my electronic devices. It's the only way to cope with the way they misbehave. -
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,
iHopeSeems this is a characteristic of the system keychain.
Check out this thread...and furtwanglerian's response....
http://discussions.apple.com/thread.jspa?messageID=8767033�
closed -
Wishlist: keychain access util to change given password in multiple entries
I use to change passwords often (login, mysql, appleshare...). After that I have to go thru all my keychain entries and adjust all these passwords one by one.
Each time I click on the [x] show password checkbox I am asked for my password, then I can change this single entry. And so on...
It would be really nice if the keychain access utility would offer a feature like 'change a given password' so that I would be asked once for the keychain's password, the old (=to be replaced) and the new(=replace with) password. After that a list with checkboxes could be displayed showing which entries have been found. A proceed button, maybe a 'do you really want...' confirm dialogue - and all desired entries are up to date.
Maybe I've not found this feature - that's why I've marked this post as question. In that case - please tell me how to proceed. Or: maybe someone else can support this idea - and it gets put this on a wishlist.I have encountered this problem today. I need to change the users passwords on local machines across a lot of macs and to be honest a simple change of one password would be a great help rather than having to key in the keychain password, show password and change one by one. Is there a simpler method?
Thanks -
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/HIToolboxI'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". -
Screen went black, restarted to 0:01 on 01/01/01 and keychain access lost
I just had my screen go black and the computer shut down completely. Upon restart after pressing the power button, it powered to 0:01 on 01/01/01 and lost keychain access (WiFi). I restarted it a second time about 5 minutes later and these were restored. However, this is the second time this has happened in less than two days. The first time was at 2am and the screen went black and I had to boot it back up with the power button after determining that it wasn't asleep (which it would have no reason to be, I had just gone to brush my teeth).
I've noticed that both times it happened was while it was plugged in and I moved with it. I am extremely careful with my Mac (it cost an arm and leg and I've been very happy with it until now), and I handle it gently so it cannot be due to me setting it down hard. Also, it doesn't recognize the power adapter after the restarts. It's been about 20 minutes now and it still doesn't show that it is being charged nor is the adapter lit.
The first time, the keychain access and date came to within about 15-20 minutes after the initial restart. This second time, I just restarted the computer again and all was well.
I'm really concerned as I've only had it for four months (purchased brand new). While this is a much better crash to length-of-ownership ratio than I had with my PC's, I was thrilled that my MBP had been flawless thus far.
Any suggestions would be greatly appreciated. The other forum topics I found with this same issue all reported having to seek warranty work. I have no idea how I could be without it right now and I'm leaving for holiday in a week where I'll need it for studying and writing my dissertation.
Thank you in advance!!Your AppleCare coverage is international, I'm not sure who told you it would't be covered however I'm pretty sure they were flat wrong. Call AppleCare and if you are questioned about where you bought the machine ask to speak to a supervisor, explain your situation, have all your receipts and documentation ready and you should be able to get help. At a minimum if the machine is less than a year old you have a warranty and should take it to your local Apple Store.
As far as update ONLY install updates that specifically designed for your machine. -
Enabling OCSB/CRL in Keychain Access slows down Mac App Store
Today I wandered why the Mac App Store on my Macbook Pro is much slower than it used to be, clicking on "Purchased" tab even froze the Mac App Store and I had to force quit of the App Store. Then I remembered that I turned on OCSB/CRL in Keychain Access because of the Comodo security breach. I turned off this feature and instantly the Mac App Store worked as fast as a few weeks ago.
My question: this security feature is very essential, even after the Comodo story. And I don't think that I am the only one who uses this feature, I read several articles about this after the Comodo incident. Will there be a fix for this problem? Will there be a Mac App Store that remains usable with OCSB/CRL enabled?
MarcusI know it's not real helpful, but that's a little better than my 164 KB/s AT&T DSL.
If other sites are loading faster and at the expected speed, then you might try later when there are less user's accessing the App Store. -
Why does the Notes app want Keychain access?
Does anyone know why Notes wants keychain access? It started when I downgraded from Snow Leopard to Mountain Lion. The dialong also won't accept 'no' for an answer. If I select "Deny" it just repeats the question and the only options are to close the program or allow access. Since it doesn't allow secure notes, why does it need the keychain, and why present a dialog with no choices?
Try going to Applications/Utilities/Keychain Access/Secure Notes and see if there is an entry there. If so, you'll need to decide if you want to keep it or not.
-
Password, keychain access to deceased brother's Mac tower
My brother passed away and I purchased his tower and other equipment from his estate. The system is running OS X (10.6.8) and I can not update or install anything due to the password access issue. I have found a 10.4.7 OS X install disk and have read the information about starting up with holding down the C key. Also read about keychain access but when using spotlight to search for the "login.keychain" file, spotlight indicates nothing is found. Obviously I am a little nervous about this as the system has about 9 terabytes of storage with all his digital music and other information on it. He used everything from Digital Performer to Adobe products to Final Cut, etc. I REALLY do not want to lose access to his work. My questions right now are:
1. Do you think it will be ok to use the 10.4.7 disk to restart and reset the password? My guess is any updates were handled online.
2. If no "login.keychain" file is found, does this indicate he never password protected his program access?
3. If he had an Apple account, is it possible to have it assigned to me due to his death so I can access any records/services that may exist?
This makes me a new Apple user so any help, no matter how simple it might sound would be appreciated.
Respectfully,
Jet TaylorSee http://aruljohn.com/info/macpasswordreset/#macosdisk for resetting the password. As for the login.keychain, it should reside in /Users/username/Library/Keychains/. However, it normally uses the same password as the computer, but that's not reset when you reset the user's password. Additionally, it contains passwords for Internet sites and you should just ignore it and set up a new one.
Since you're a new admin user, see these:
Switching from Windows to Mac OS X,
Basic Tutorials on using a Mac,
Mac OS X keyboard shortcuts,
Anatomy of a Mac,
MacTips,
Switching to Mac Superguide, and
Switching to the Mac: The Missing Manual, Mountain Lion Edition.
Additionally, *Texas Mac Man* recommends:
Quick Assist,
Welcome to the Switch To A Mac Guides,
Take Control E-books, and
A guide for switching to a Mac. -
Keychain Access Problem: Correct Access
I hope someone can help me, I accidently choose "Always Allow" instead of "Allow Once" after selecting "Show password" in Keychain Access Attributes. I am not experienced here and cannot find anything to help me change this back. How can I switch back to where this application password does not always allow access?
PowerBook G4 Mac OS X (10.4.3)Before I do anything, one more question:
In: http://www.thexlab.com/faqs/helpviewer.html
Under 'Help Viewer displays a blank window / Solutions' it says to Trash 3 files:
Home > Library > Preferences folder
1. com.apple.help.plist
2. com.apple.helpui.plist
3. com.apple.helpviewer.plist
and 1 folder:
Home > Library > Caches folder
1. com.apple.helpui.
I am missing the 'com.apple.helpui.plist' file. (I did a search and couldn't find it.) At the same time I found a strange one... 'null.plist' which when opened read:
bplist00N_ApplicationCrashedAfterRelaunch-/
What happened... Can this be the missing one?
Where do I go from here, just trash the ones that exist and go on?
What about null.plist?
I could use a little more help please. It would be appreciated. -
Login keychain keeps disappearing from Keychain Access Utility
I'm running OSX 10.8.3 on a mid 2009 MacBook Pro, and having several problems with passwords and perhaps permissions.
There are two users on this computer, one for me and one for my wife. Mine was set up long before hers, but she uses it more because I use a newer Mac now.
On her account, everything seems to function normally. It's my account that is causing problems.
For example, mail can't remember my passwords. I have gmail (and others) configured in Mail, and when I go to check the account settings, everything is right except the password space is blank. When I start mail, it prompts for the passwords for each of the mail accounts, I enter it, and it prompts again, endlessly.
Also, I can't log in to iCloud from that computer, although I can login from my browser on the same Pro, and from my iPhone and from my MacAirbook using the same account and password. (This may or may not be related - I don't know.)
When I open KeyChain Access, the upper left panel shows only two Keychains - System and System Roots.
I tried File/Add Keychain and pointed to the login.keychain in home/library/keychains. The login keychain shows up in the upper left panel, and the passwords for all my previously added logins all show up when I click on the login keychain in the upper left panel and then click on the passwords category in the lower left panel of Keychain Access.
But when I quit keychain access and restart it, or when I restart the computer and go back to keychain access, the login keychain has again disappeared again.
I have tried keychain "verify" and "repair" but verify says everything is OK, no problems, and so repair doesn't fix anything. It checks the login.keychain and says there are no problems.
Any suggestions?OK, I spoke too soon. It's ALMOST fixed, but there's still one niggling litte problem.
When I start up my computer, it first asks me to log in (as it should).
Then, after it begins to load everything, the following message pops up.
"Mac OS wants to use the "myname logins" keychain. Please enter the keychain password"
I enter it and that's the end of the problem until the next time I start up the computer. This is a huge improvement to what it was previously doing, but I'd like to fix that, too.
I am wondering if it's related to a problem with the configuration of my login keychains.
When I open KeyChain Access, it shows 2 login keychains, one called "login" and the other "myname logins" (I added the second one to solve the problem at the beginning of this topic - April 22 above).
The one OS X asks for is myname logins.
Myname logins contains passwords for my LAN, but nothing for the airport itself.
The "Login" keychain contains passwords for my airport/time capsule. But there are 8 different entries for it, 4 of them with the same "Date modified" and 4 more with a second "Date modified".
This login keychain also contains many obsolete entries for ISPs I no longer use, and for routers I used once or twice in clients' offices several years ago.
So, 5 questions.
Can I remove all these obsolete keychain items?
Can I remove some of the duplicate items?
Should I consolidate these to one keychain or should I leave them separate?
If I should consolidate them, how do I do it?
Will consolidating them solve my problem with OS X asking for my keychain login password when my configuration is loading?
Thanks. -
I've gotten used to most of OS X since my slow, late conversion to it two years ago, but its security arrangements still drive me nuts. I don't need them. I have no security concerns about my Powerbook. No master password is set on it. I'm the only user, except on occasions when I set up a new user for test purposes and then delete it. I know the admin password for my usual account, obviously, though I've set the PB up to log me in automatically on startup.
But somehow I've lost track of the password for my keychain(s), which I thought was the same password. I don't really understand what a keychain is, to be honest, and whenever I'm prompted to enter my password for it, I have to cancel out of the dialog box because nothing I can think of to enter is correct. I live in dread that one of these days I'm going to have to know that darn password. So, these questions:
1. Can I set a new password for a keychain without knowing the old one?
2. If not, can I delete a keychain completely without knowing the password, and what am I likely to lose if I do so?
(I regret to say that I find the online Mac Help's information on keychains almost completely opaque. Maybe it's just my anxiety getting in the way.)
3. When I open Keychain Access and click "Show Keychains", two keychains appear: one with my username, which contains three certificates, three application passwords and an internet password; and another called system, which contains only my Airport network password. I've successfully deleted two or three entries that were outdated and superfluous from my user-account keychain, but I have no idea how much trouble I'd be in if I deleted all the rest. To add to my confusion, I get prompted for my admin password when I want to delete things from the keychain — not my keychain password. Can anybody point me toward a clear, cogent explanation of keychains and how to get them under my control instead of being at their mercy? Many thanks...Here are some references that may help:
http://docs.info.apple.com/article.html?artnum=106973
Reset Keychain Password: Assuming that you are using a recent build of OS X, go to /Applications/Utilities and launch the app called Keychain Access. Go to the Window pulldown menu and select "Keychain First Aid". Enter your password, set the radio button to "Repair", and click "Start".
Tutorial: Keychain issues; resolving
If you can't access your keychain, or forget your password If you can't get into your keychain file because you've forgotten your password or the keychain file appears to be corrupt, there are a couple of options.
First, if you've forgotten your password, you can use the "Keychain First Aid" utility to make the keychain password the same as the login password.
This can be accomplished via the following process:
Open Keychain Access (located in Applications/Utilities
Go to the "Keychain Access" menu and select "Preferences"
Click the "First Aid" tab
Make sure the "Synchronize login keychain password" box is checked
Close the Preferences window
Go to the "Keychain Access" menu and select "Keychain First Aid"
Enter your username and password
Click the "Repair" button
Another option is to completely delete your keychain then recreate it. This routine is useful if your keychain appears to be corrupt or otherwise inaccessible.
This can be accomplished as follows:
Launch Keychain Access (located in Applications/Utilities)
Click "Show Keychains" in the lower-left corner of the window.
Select the problematic keychain from the left-hand pane.
Navigate to the "File" menu and select "Delete Keychain '(name of keychain)'"
Check all options for deletion and press "OK"
Create a new keychain by going to the "File" menu, then "New" and selecting "New Keychain"
You can now make this keychain your default if you desire by selecting it, then going to the "File" menu and selecting "Make '(name of keychain)' Default"
Login as root and perform repair In some cases, problems with keychains can only be resolved when logged in as the root user.
First, enable a root user account, as detailed in Knowledge Base article #106290 (briefly: open NetInfo Manager, located in Applications/Utilities, click the lock and enter the administrator password, then select "Enable Root User" from the Security menu and follow on-screen instructions).
After enabling the root user, and logging in under this account, again open Keychain Access. First attempt repairs using Keychain First Aid, and failing that, delete then recreate the keychain as described above while logged in as root.
Persistently asked for stored passwords If you are persistently asked for passwords in various applications that you have specified should be remembered in a keychain, your "login" keychain may not be active for one reason or another.
Navigate to ~/Library/Keychains/ (this is the Library folder inside your user home folder). Find the file named "login.keychain" and double-click it.
Failing that, select the "login" keychain within the Keychain Access application and make sure it is the default keychain by going to the "File" menu and selecting "Make 'Login' Default"
Turn off Keychain synchronization in applications having problems If specific applications are experiencing issues when accessing password-protected material, Keychain may be to blame.
For example, it appears that in some cases, failures in .Mac synchronization transfers are linked to issues with Keychain.
If you are having problems synchronizing data with .Mac servers, you may want to try the following process:
Open System Preferences and access the .Mac pane
Click the "Sync" tab
Uncheck the "Synchronize with .Mac" checkbox
Close System Preferences
Re-open System Preferences and repeat steps 1 and 2
Re-check the "Synchronize with .Mac" checkbox
If the above process does not re-allow synchronization, you may need to leave Keychain synchronization turned off in the "Sync" tab of the .Mac System Preferences pane.
MacFixIt reader Faisal writes:
"I believe the problem may be related to Keychain sync overwriting or mangling the .Mac information in the Keychain. By disabling Keychain sync I seem to be able to sync again without issue."
A keychain is simply a secured database in which you can store userids and passwords securely. OS X integrates most applications to the Keychain so that when a userid and/or password is requested the Keychain fills in the information automatically unless you've elected otherwise. This is especially useful when accessing secure web sites so you don't have to remember every username and password you've assigned.
When you create a new account a new keychain file is created for that account. The account password is the default password used for the keychain so when you log into the account the associated keychain is opened automatically. -
Trying to delete wifi certificate in Keychain Access; continually crashes
Every time I try to delete my wifi certificate in Keychain Access, it continually crashes. Tried it in safe mode, still crashes. I cannot get my Airport extreme 5th gen to pass along an IP address to my Mac even though mac is connected to AE (seen via Network Utility). Thought that deleting keychain password would help.
OSX 10.10.1
retina Macbook Pro 13Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful. -
Keychain - simple question about use
I would like keychain to ask me for the "login" keychain password when I navigate to a page requiring user id and password in Safari. After proving the "login" password, I would like keychain access to insert the appropriate user id and password. How do I accomplish this?
Maybe I've got the wrong understanding. It was my impression that Keychain and Autofill were two distinct things. I have been using autofill all along and when I go to a website, put in my id and password and hit send or continue or whatever, a window comes down from the top of the safari window and asks me if autofill should remember the password. The next time I visit the site, the info appears in the right places.
What I want is for me to go to the site and for a window to pop up and ask me for my keychain password BEFORE putting the site's user id and password in. A friend of mine has this setup on his computer but doesn't know/remember how it got that way so he is no help.
I hope this clarifies my question.
Thank you all for your help.
Maybe you are looking for
-
In Mountain lion, do i have to save Adobe files to the cloud?
Hi there, at this stage i'm not comfortable having my docs, of any sort, be saved to the cloud - whether that be Apple's cloud or Adobe's. I just want to keep them in the machine and saved in the finder - nowhere else. Is that possible with Mountain
-
We have Ebusiness Suite I have been trying to use an external graphic from OA_MEDIA to display on Standard Purchase Order <fo:external-graphic src="url:{${OA_MEDIA}/COMPANY_LOGO.GIF}" /> Please could someone tell me where I am going wrong with the
-
Can't save preferences for CD burner?
I'm trying to change the DVD Rom that I use to burn CDs under "Edit - Preferences - Advanced - Burning". The desired DVD Rom is shown in the pull-down menu but I can't seem to save this preference and it keeps pointing to the wrong device. Any though
-
How to enable PPTP VPN service in OS X Lion Server (10.7.1)
This is pretty strange what Apple has removed the interface of PPTP settingfrom it VPN service!! I trued each and every think i knew and searched a lot over available recourseson the apple knowledge base pages. I also follow the below instructions to
-
After newest update the color of R3D files is off
If you dynamic link them to AE the color is correct. If I open the soucre settings and readjust the color or reload RMD or do anything and then dynamic link to AE the color in AE is now off completly. I assume the RMD's are fine and its just premiere