Dear Yamanaka-san, That did it! Taihen Domoarigatogosaimashita!
The error message was printed out by my code, which catches the java.lang.SecurityException when the session.connect() call failed. Once I included the patch, all the tests I tried (Unix <-> Unix, Win -> Unix) passed with flying colours. I am now eagerly looking forward to 0.1.36. Best regards. --- cllee This e-mail is classified as INTERNAL USE ONLY. -- Chia-Ling LEE IT Security Risk Management UBS AG, Stamford Branch 400 Atlantic St, Stamford, CT 06901 Tel: +1-(203)719-3486 E-mail: [EMAIL PROTECTED] Internet: www.ubs.com -----Original Message----- From: Atsuhiko Yamanaka [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 6:51 PM To: Lee, Chia-Ling Cc: [email protected] Subject: Re: [JSch-users] ANNOUNCE: JSch 0.1.35 Hi, +-From: <[EMAIL PROTECTED]> ---------- |_Date: Wed, 24 Oct 2007 15:52:35 -0400 __ | |Unfortunately, this patch does not work for me. The result is just the |same as if I set useSubjectCredsOnly=false on the command line, that is: |java -Djavax.security.auth.useSubjectCredsOnly=false ... |The error message is: |java.lang.SecurityException: Unable to locate a login configuration I can not reproduce such an exception. May I ask you which method throw that method? If it is from GSSContextKrb5#init(), how about following code, public byte[] init(byte[] token, int s, int l) throws JSchException { try{ if(useSubjectCredsOnly==null){ setSystemProperty(pUseSubjectCredsOnly, "false"); } return context.initSecContext(token, 0, l); } catch(GSSException ex){ throw new JSchException(ex.toString()); } catch(java.lang.SecurityException ex){ // throw new JSchException(ex.toString()); // } // finally{ if(useSubjectCredsOnly==null){ setSystemProperty(pUseSubjectCredsOnly, "true"); } } } Sincrerly, -- Atsuhiko Yamanaka JCraft,Inc. 1-14-20 HONCHO AOBA-KU, SENDAI, MIYAGI 980-0014 Japan. Tel +81-22-723-2150 +1-415-578-3454 Fax +81-22-224-8773 Skype callto://jcraft/ Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mails are not encrypted and cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ JSch-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsch-users
