On Thu, 18 Jul 2013 12:36:25 +0200, Félix Sipma writes:
>I think I've found the source of this "No such file or directory: 'none'". 

i thought so - your bug reports weren't completely consistent 
wrt. ssh config and observed behaviour...

>I'm using "IdentityFile none" in /etc/ssh_config, as I want to force ssh 
>to use ssh-agent. 

man ssh_config says 'Additionally, any identities represented by the 
authentication agent will be used for authentication.', so your agent
will be consulted without you having to disable identity files.

>That works well with ssh, but not with duplicity. 
>Shouldn't duplicity add an exception for the "none" value?

no, for two reasons: a) because that's completely undefined behaviour 
as per my copy of man ssh_config; it just /happens/ that ssh currently 
ignores dud file names, and b) it's paramiko that is parsing and 
using the ssh config files, not duplicity - if you insist that 'none' be 
treated specially then please raise that as a bug against python-paramiko.

why not try IdentityFile /dev/null, or the name of an existing blank file?

regards
az


-- 
Alexander Zangerl + GPG Key 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
REAL*8 RESPONSE(8)
DATA /RESPONSE/ 8HYOU EVER,8H DONE IT,8H IN FORT,8HRAN IV?$
 -- Peter da Silva about the joys of string handling

Attachment: signature.asc
Description: Digital Signature

Reply via email to