similar to: [PATCH] Caching passphrase in ssh-add.

[ I'm not subscribed to this list; please CC any followups to me as well ] When a user invokes "ssh-add" with no arguments, I think we should default to adding both version 1 and version 2 keys. Here's a patch against the source included with my Debian package of OpenSSH: walters at space-ghost:/usr/src/ssh/openssh-2.9p2$ diff -u ssh-add.c~ ssh-add.c --- ssh-add.c~ Thu Apr

NOTE: If you know how to properly use load_private_key for dsa keys and NOTE: don't want to read my long post, simply reply with that info and NOTE: I will really appreciate it. thanks. I've been playing with the source code and trying to create extra apps. All has been going well except the fact that I can't load a dsa private key. To highlight my problem I stole some code

ssh-add on OpenBSD current (with malloc -S enabled) crashes ("chunk is already free") when loading my password-protected SSHv1 key (used only for testing). "ssh-add ~/.ssh/identity" also fails to format the prompt properly ("Enter passphrase for :"). The issue is as follows: Starting at ssh-add.c:158 in add_file(ac, filename = "~/.ssh/identity"), we call

===== I believe that each private key file read is closed twice as load_private_key(filename, ...) fd = open(filename, ...) ... load_private_key_rsa1(fd, ...) ... load_private_key_ssh2(fd, ...) ... close(fd); Unfortunately, "load_private_key_rsa1" and "load_private_key_ssh2" also close the file. It would simplest to remove the `close()'s in the rsa2 and ssh2

Enclosed is a patch against 2.2.0p1 that teaches ssh (and therefore slogin and scp) how to invoke ssh-askpass to request a password, RSA/DSA key passphrase, or an skey challenge response. I've tested this on Linux (i386), for passwords and RSA/DSA key passphrases. I cannot easily test whether the Right Thing will happen for skey challenge responses; I would appreciate it if someone who uses

https://bugzilla.mindrot.org/show_bug.cgi?id=2442 Bug ID: 2442 Summary: comment is not set to the filename for identity files with already entered passphrase Product: Portable OpenSSH Version: 6.7p1 Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5

Regarding "rsync error code 23" could the below "delete_file: ...file exist" failures cause the error code 23? Or, how can I resolve this as these are the only errors I see in the log files. Thank you! START Tue Aug 26 11:10:12 PDT 2008 /home/filerep/bin/rsync -e /var/openssh/bin/ssh --archive --stats --timeout 3600 fmttcesrv1::tce_data

Add support to load additional certificates for already loaded private keys. Useful if the private key is on a PKCS#11 hardware token. The private keys inside ssh-agent are now using a refcount to share the private parts between "Identities". The reason for this change was that the PKCS#11 code might have redirected ("wrap") the RSA functions to a hardware token. We don't

Hi All, I have an issue with the ODBC voicemail storage option with asterisk. All appears to work fine, however, I get several sql execute warnings. I was wondering if anyone out there could help me get to the bottom of what is causing this and how I could possibly go about rectifying it. The warning message we are getting is as follows: WARNING[30115]: app_voicemail.c:1280 delete_file: SQL

Hello list. I've got following: rsync: opendir "client05" (in Profili) failed: Permission denied (13) rsync: delete_file: rmdir(client02/SendTo) failed: Permission denied (13) Am I correct if I say that the "opendir" is related to the source I'm trying to rsync, but the "delete_file" is related to the destination? Flavio Boniforti PIRAMIDE INFORMATICA

My keys are secured with a passphrase. That's good for security, but having to type the passphrase either at every login or at every invocation of ssh(1) is annoying. I know I could invoke ssh-add(1) just before invoking ssh(1), if I keep track of whether I invoked it already, or write some hacky scripts; but the rest of OpenSSH is wonderfully usable without any hacks. Hence, this patch.

Hello, I'm backing up a file server using rsync from a cron job, which recently started to give me errors like: delete_file: rmdir "/some/path" failed: Directory not empty symlink "/some/path" -> "/some/other/path" failed: File exists Looking at the involved files and directories, it looks like the user decided to replace a directory with a symlink, but

https://bugzilla.samba.org/show_bug.cgi?id=12741 Bug ID: 12741 Summary: stop rsync on "No space left on device" Product: rsync Version: 3.1.2 Hardware: x86 OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayned at samba.org

Executive summary: Why can I not have a private key which is `public' ? Gory details .... I'm new to openssh. I've been using ssh for years. However, I'm in the process of investigating RH 7.* (0.91 at the moment) and am wanting to be as `standard' as possible, so trying openssh. I looked on http://www.openssh.com/list.html but could not find a list for "general

I'm trying to use zfs acls in solaris 10. I've looked at past posts regarding this and some online help, but am stuck. I'm currently using samba 3.3.9; I've had the same problem with 3.3.7. samba is compiled and running as an Active Directory member server (compiled with ldap and kerberos). The zfs disk is local. I'm not using winbind. I compiled with zfsacl module.

Does anybody have experience of running Samba on a domain and getting inherited file permissions on a Samba server to more closely match the permissions you would see on a Windows 2000 box? I'm trying to reproduce our departmental folders on a Samba box, running on ZFS with NFSv4 ACL's, but I'm struggling to get inherited permissions working properly when new files are created.

Hi, How about adding now option '--backup-only' that means making backups only and don't change any destination files? (I posted similar patch a month ago, but the patch was made for nightly snapshot of 20020808, which was tooo old! Laugh at me...) I want to use rsync with LVM snapshot to make incremental backups like below: 1) Make LVM snapshot of file system and mount it.

Hi, About a year and a half ago I brought up the topic of encrypted hostkeys and posted a patch (http://marc.info/?l=openssh-unix-dev&m=132774431906364&w=2), and while the general reaction seemed receptive to the idea, a few problems were pointed out with the implementation (UI issues, ssh-keysign breakage). I've finally had some spare time in which to get back to this, and I've

The attached patch for 4.6p1 adds a feature (-u) that will check to see if a key exists on a remote host. I use this for auditing my users transition to v2 keys very useful. If there is any interest I'll provide a patch for v2 ssh keys also. http://vapid.dhs.org/dokuwiki/doku.php?id=vapidlabs:openssh_check_key_patch -- Thanks Larry --- orig/openssh-4.6p1/sshconnect1.c 2006-11-07

I have what I believe to be a bug in the behavior of the current (2.6.4) version of rsync. While trying to upgrade from version 2.5.2 to the current version (for security concerns), I noticed the following difference in behavior between the two versions which is preventing the upgrade: If you have a directory tree on the target such as the following: dir/pdf/file1.pdf dir/pdf/file2.pdf