Re: Call for assistance (Was: [Issue 3061] username + password + non-interactive caches creds wrong)

On Mon, Jun 9, 2008 at 5:00 PM, Jack Repenning <jackrepenning_at_tigris.org> wrote:
> On Jun 9, 2008, at 1:50 PM, Mark Phippard wrote:
>
>> FWIW, Subclipse (and other JavaHL consumers) also create these creds.
>> When the keychain support was added in 1.4, it was not added to
>> JavaHL. Until the recent Gnome/KDE stuff was added, I did not know it
>> needed to be.
>
> You mean, "in cleartext, in the file system," I take it. So that's a good
> argument for the fix I already made, to use such creds if they exist.
>
> Any idea how these behave under the broken Leopard
> SecKeychainSetUserInteractionAllowed()?
>
> Do they even call that? If not, they needn't care that it's broken.

If there is even an equivalent of --non-interactive in JavaHL, we do
not use it. I have never noticed any problem going between the
command line and Subclipse. Although perhaps I was prompted to cache
credentials twice and just did not pay attention. Basically, I never
noticed it until looking at the code to add the new stuff in and
seeing that the command line had code to use the Keychain and JavaHL
did not.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org