similar to: Keychain Patch Try II

Hi, I have ported Samba 2.0.6 to run on Linux/IA-64. I had to make a few modifications to get Samba to configure and compile properly. The mods mostly have to do with missing prototypes which weren't present in system include files (e.g. ptsname()). The biggest pain turned out to be a prototype for crypt() which is defined in <unistd.h> only with -D_XOPEN_SOURCE. Defining this caused

I've jsut installed Samba-2.2.4, from source on a Solaris 2.6 box. I'm looking to upgrade from some 2.0.x versions I'm running. I've createed a password entry using smbpasswd -a and added my password. My password has 9 characters in it. Using smbclient on the Solaris box, I can access the share, but I can't from Win95 or Win2000 clients (encryption is on). If I try to access

I've been giving SSH_ASKPASS a hard look, and it's not clear to me how it's supposed to work. The documentation (ssh.1) seems explicit enough: SSH_ASKPASS If ssh needs a passphrase, it will read the passphrase from the current terminal if it was run from a terminal. If ssh does not have a terminal associated with it but DISPLAY and SSH_ASKPASS are set, it will execute

https://bugzilla.mindrot.org/show_bug.cgi?id=69 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djm at mindrot.org Alias| |generalised-askpass -- Configure bugmail:

I would like to use ssh-add to unlock a key with a password provided through a web interface. It seems even though ssh-add calls read_passphrase with RP_ALLOW_STDIN at ssh-add.c:173, stdin is not used as a last resort without a valid terminal or display. Is it an intended behaviour ? And if so, what are the security implications of using popen() to write the password to ssh-add (not using echo

Hello, I'm a Mac OS X user, and I got tired of typing my password every time I want to login, but didn't want to use ssh-agent and the like. So, I grabbed the code for OpenSSH 3.7p1, and made some modifications which allow passwords to be stored and recalled from the OS X Keychain. The reason I'm posting to this list is that I'd like to make these modifications available to

Moin, attached is a patch, which adds a new configuration option "PreferAskpass" to the ssh config. ssh{,-add,-keygen,-agent} will use ssh-askpass to prompt for passwords, if this option is set to "yes", and if ssh-askpass is available. Default for "PreferAskpass" is "no". Pacth is against current CVS. Sebastian -- signature intentionally left blank.

On 02/11/06, Will McDonald <wmcdonald at gmail.com> wrote: > Guys, I wonder if anyone can give me any pointers here, I hope it's > CentOS related enough not to be too off topic, if it is then > apologies. Thanks to Marc and Ingimar for their suggestions, I think we've cracked it. When Keychain runs it prompts the user for their private key password then stores the

Is there a centos recommended repository for centos 7 where I can obtain the keychain package? TIA, Pete

On 11/17/2015 11:27 AM, PS = Pete Stieber wrote: PS>> Is there a centos recommended repository for PS>> centos 7 where I can obtain the keychain PS>> package? On 11/17/2015 8:19 PM, WJ = Wes James wrote: WJ> I can only see a version for centos 6: WJ> WJ> http://pkgs.repoforge.org/keychain/ WJ> WJ> You?ll need to download the src and see if WJ>you can build it.

hello centos.. I am having a very annoying problem on my network right now. it looks like every time I try to add my ssh key to keychain I have to issue a command just to get my ssh subsystem communicating with the ssh-agent: I have this line in my .bashrc file $(keychain --eval --quick --quiet private_key1 private_key2 private_key3) If I try to perform ssh-add I get the message: [bluethundr

I think what Mr. Farr is referring to is keychain support. Keychain is provided as part of OS X. Apple published an API for it. An OS X compile would store and retrieve keys from Keychain in lieu/addition to the SSH Agent. Keychain is to OS-X what the ssh-agent is to ssh. This makes perfect sense, and I haven't been sufficiently peeved to do this yet, but I have dreamt of this myself. It

Keychain is quite a useful tool for automating SSH logins without having to use password-less keys: http://www.gentoo.org/proj/en/keychain/ Normally it is used like this to set the SSH_AUTH_SOC and SSH_AGENT_PID variables: source ~/.keychain/hostname-sh (This is what's in hostname-sh) SSH_AUTH_SOCK=/tmp/ssh-XXn47DUn/agent.16721; export SSH_AUTH_SOCK; SSH_AGENT_PID=16722; export

Hey all, Here's the patch to let SSH store passwords in the Mac OS X Keychain. I don't know whether you guys want to include it or not with the distribution; some people have said that since Keychain is not an open source product, it's not proper to put it in, while others think it's OK. I'll leave it up to you; it's served its purpose to me. The patch is against

Sorry meant to attach my sshd_config file.. here it is! ---------- Forwarded message ---------- From: bluethundr <bluethundr at gmail.com> Date: Sat, Jan 15, 2011 at 11:22 AM Subject: keychain problem To: CentOS mailing list <centos at centos.org> hello centos.. I am having a very annoying problem on my network right now. it looks like every time I try to add my ssh key to keychain

> On Nov 17, 2015, at 11:27 AM, Pete Stieber <pstieber at gmail.com> wrote: > > Is there a centos recommended repository for centos 7 where I can obtain the keychain package? > > TIA, > Pete I can only see a version for centos 6: http://pkgs.repoforge.org/keychain/ <http://pkgs.repoforge.org/keychain/> You?ll need to download the src and see if you can build it.

Hi! In a project I'm working on, I needed a way to run rsync in daemon mode as a regular user without having the passwords readable to everybody accessing the console. With this chance rsync falls back to Apples keychain access if no secrets file is given. You need to put the passwords into the keychain like this (I do it programmatically bit it can be done manually as well):

Guys, I wonder if anyone can give me any pointers here, I hope it's CentOS related enough not to be too off topic, if it is then apologies. I'm attempting to setup a CGI which can connect to a remote system and execute a command. On the 'client', for the Apache user 'apache' I've given it a shell and generated a key-pair. I've configured Keychain [

Hi, What I was trying to do (apart from toying with stuff) was to get a realiable, single, portable/importable credential that would be universally available whenever I need it but in normal operation would be either stored in or wrapped by Secure Enclave (this means EC keys), instead of provisioning 5 resident FIDO keys, one Secretive SE-wrapper key and a backup key. (I know, I could use

Hi, the following problem occurs on Solaris 2.6. openssh-3.7p1 and openssh-3.7.1p1 both show the same behaviour. openssh is configure with: CC='gcc -L/usr/LOCAL/lib -I/usr/LOCAL/include' ./configure --prefix=/usr/LOCAL --sysconfdir=/etc/ssh --sbindir=/usr/local/sbin --libexecdir=/usr/local/libexec --with-pam --with-tcp-wrappers --with-ssl-dir=/usr/LOCAL/ssl