[Alpine-info] How to get Alpine-1.10 to use Mac OS 10.4 Default
Keychain via SSH ?
Dr. Gary E. RAFE
drgerlists at gmail.com
Mon Mar 24 11:45:41 PDT 2008
My wife is a long-time pine(1) user,
and I've ported versions of UW-pine for her
on various platforms over the years.
The last was pine-4.64 with the Chappa combined patches
on a Mac G4 running 10.4.x.
I was made aware recently of the new Alpine project,
and built binaries of it on the same Mac G4, running
The first version was built with the local disk password
file (I know, ill advised), which worked perfectly with
the local password file from the older Pine-4.64 binary.
The second version enabled the local password cache,
which in this case, uses the native Mac OS X Keychain.
This appeared to build without complaint, and the binary
executes as it should.
The trouble is that passwords don't appear to be saved
(in ~/Library/Keychains/), thus are not applied when needed
subsequently (in our case, when sending messages through an
authenticated SMTP service).
Relevant entries from .pinedebug follow:
q_status_message(Stop "Preserve passwords?" prompts by deleting Alpine Keychain entry)
imap_set_passwd: user=MyUsername altflag=1
write_passfile: SecKeychainAddGenericPassword returned rc=-25308
The return code of SecKeychainAddGenericPassword indicates
that "Interaction with the Security Server is not allowed".
Are we missing some prior setup, outside of alpine(1)
(say, with security(1) and the Security.framework)
to make this work correctly ?
Security(1) reports that a default keychain is enabled,
and has entries from other Internet applications.
I'm wondering if this (security/keychains) is one of those
services (securityd(1)) that needs to be run on the console
in order for it to work as advertised.
The work I reported above was all performed remotely via an
We won't have access to the console until later this afternoon.
Dr Gary E RAFE: drgerlists at gmail dot com
More information about the Alpine-info