search for: publickeyfil

Hello, can one specify the priv/pub key filepath without the -c switch. I need some more controll over where the keys get stored. tincd.exe, without the -n switch stores it's keys in a static path. Relativ pathes would help. thx, Axel

...NAME -arp ----- tinc.conf ---- ConnectTo = orca Name = pax Hostnames = no InterfaceIP = 24.176.163.186 KeyExpire = 30000000 PrivateKeyFile = /etc/tinc/.rsa-private TapDevice = /dev/tun ------------------ Shared Hosts Files ------------------ --- pax --- Address = x.x.x.x Subnet = 10.11.15.0/24 PublicKeyFile=/etc/tinc/hosts/.pax-rsa-public --- orca --- Address = y.y.y.y Subnet = 10.11.1.0/24 PublicKeyFile=/etc/tinc/hosts/.orca-rsa-public ####################################################### I get a succesfull connection and everything looks to be okay, however, I am unable to ping anything from...

...hkey_copy/sshkey_dup function... A simple way of reproducing the identity_keys part of the problem (I'm not using certificate) is to: - Configure sshd with AuthenticationMethods keyboard-interactive:pam,publickey - Generate a public/private key - Start an ssh agent, add the key - Run ssh -i ${publickeyfile} -o IdentitiesOnly=yes -vv ${host}, properly authenticate with the password and see the publickey authentication failing, logs with contain: ``` debug2: key: ${publickeyfile} (${pointer}), explicit, agent [...] Authenticated with partial success. debug2: key: ${publickeyfile} ((nil)), explicit ```...

...imes. Some problem with the keys is the most likely explaination for "bogus message", however if that is ruled out the next likely problem is the use of "PrivateKey" or "PublicKey" statements in config files, when you actually meant "PrivateKeyFile" or "PublicKeyFile". Check if you have any of those statements. If so, I recommend removing them altogether. If that was not the problem, then another issue might be the version of OpenSSL on your Beaglebone not supporting the Cipher or Digest algorithms that you are using. -- Met vriendelijke groet / with k...

http://bugzilla.mindrot.org/show_bug.cgi?id=1157 Summary: ssh-keygen doesn't handle DOS line breaks Product: Portable OpenSSH Version: 3.8.1p1 Platform: All URL: http://openssh.org/txt/draft-ietf-secsh-publickeyfile- 02.txt OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh-keygen AssignedTo: bitbucket at mindrot.org ReportedBy: pepper at rockefeller.edu ssh-keygen cannot import files with DOS-style li...

Is there a way to automate the rsync password or maybe disable? I am currently running rsync from a Windows command prompt and would like to run it from a .bat file. I have read through the config man pages but not sure if my ssh_config file is even being used. I tried passwordauthentication = no but it still asked for password. I have seen a option for --password-file= but I believe this does not

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greeting- I have tinc on the following: 2 - x86 FreeBSD boxes 1 - ARM FreeBSD box 1 - x86 Macintosh All the x86 boxes can speak with each other, but none of the x86 boxes can speak with the ARM box. The ARM box says: [root at beaglebone /usr/local/etc/tinc/wdl]# tincd -D -n wdl tincd 1.0.24 (Mar 8 2015 14:55:57) starting, debug level 0

(Second try to send this. I wonder if the first one gotten eaten by a spam filter; I'll link to patches instead of attaching them.) Here are the tincctl patches I've been working on. They apply to http://www.tinc-vpn.org/svn/tinc/branches/1.1@1545. I intend to commit them once the crypto stuff's fixed. Since they're basically done, I'm emailing them now for review and in case