search for: ssldirs

[I'm cc:ing openssl-users at openssl.org, because questions about this are getting there over and over...] There's a problem that several people who installed OpenSSL to be able to uyse OpenSSH have faced: Could not find working SSLeay / OpenSSL libraries, please install I don't recall how SSLeay was installed, but for OpenSSL, there's a glitch in the way it tries to find

I have just uploaded a test release of 1.2.3. It includes numerous fixes from the OpenBSD team and should fix the stupid configure bugs of 1.2.2p1. http://violet.ibs.com.au/openssh/files/test/ A detailed ChangeLog is in the directory. Please report successes and failures. Regards, Damien Miller -- | "Bombay is 250ms from New York in the new world order" - Alan Cox | Damien Miller -

Here's a unified diff, proposed by Christos Zoulas (with a little reworking to get the configure.in part a bit cleaner). The main target of the patches are NetBSD compatability, although there are some changes making if (pointer X) into if (X != NULL) as well. Christos also proposed a change to Makefile.in, but I'll send that as a seperate mail. Thanks, David Index: configure.in

Below I've includes a patch which helps build OpenSSH outside from a read-only source tree, find OpenSSL on Mac OS X, and fix a typo. This applies to OpenSSH 2.1.1p4. You should already have gotten a note from Melissa O'Neil about a conflict with the crc32() symbol in zlib, which was causing a crash on Darwin. I've noticed another bug. If ssh is setuid, I get a permission

It's *very* late here (or very early, depending on how you look at it), so please forgive me if this is incoherent. I thought I'd put this out there and perhaps save a few people some frustration. The configure script is much improved, but I still had problems with the OpenSSL detection. Had to tweak it a bit: *** configure-1.2.3pre1 Sat Mar 11 03:29:00 2000 --- configure Sat Mar 11

All, I have --confdir=/etc/puppet/common in my /etc/init.d/puppetmaster and /etc/init.d/puppet files, vardir set to /var/lib/puppet in /etc/puppet/common/puppet.conf, and yet, every time I run puppetca it creates /etc/puppet/ssl. Anyone know why? Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email

Known issues: 1) Linux 'sleep 20' -- Unfixable before 2.5.0 (known work around) 2) HP/UX signal issue -- Patched and HP/UX 11 works in v2 3) SCO 2/ Native Compiler -- Unfixable before 2.5.0 (known work around) 4) NeXTStep -- Resynced, MAX_GROUPS vs NGROUPS unresolved (not major) 5) DG/UX regcomp/regexec -- Fixed. 6) Cray signal issues -- ??? 7) Solaris '$PATH' issue -- ??

Hi, I installed dovecot from dovecot-1.0-test51 with this configure line: ./configure --with-mysql --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-ssldir=/etc/ssl --with-ssl=openssl When I add this to my dovecot.conf: passdb = mysql /etc/dovecot-mysql.conf I get this in /var/log/maillog when I run "dovecot -c /etc/dovecot.conf": Oct 21 13:59:16 one dovecot: Dovecot

Things that are still outstanding: 1) Solaris/Redhat/HPUX session.c patch. I've not seen a ya or na on Kevin's pam patch from the Solaris group. 2) Odd Redhat/Debian scp/ssh issues. .. I'm baffled, and I can't replicate the bug. Nor have I seen anything remotely like it reported. 3) SCO.. Is it happy yet for compiling? =) Completed: 1) mdoc2man.pl .. Commited into

Anyone ever migrated the puppetca to a different host? What are the steps that are involved?

(I'm not subscribed to the list, so if you have any comments, please mail them to me directly.) Thanks for openssh! I downloaded openssh-1.2.2p1 and found I could not configure it on my linux 2.2.15pre13 i686 kernel. The error I got was: configure: error: Could not find working SSLeay / OpenSSL libraries, please install I had previously installed openssl (first 0.9.4 and then 0.9.5) into

Hi Dears, I am installing the puppetmaster server and puppet client is running in the same machine. When i running : puppet agent --test --waitforcert 30 I received the error : Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate'': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed:

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

http://bugzilla.mindrot.org/show_bug.cgi?id=168 Summary: "Could not find working OpenSSL library" Product: Portable OpenSSH Version: older versions Platform: All OS/Version: All Status: NEW Severity: minor Priority: P1 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

Hi Experts, I''m trying to generate my own certificates (all of them, including certs for CA, server and client) for puppet to use. and I''m getting "Could not run: Could not retrieve certificate for puppetsrv and not running on a valid certificate authority" Just wondering what the problem could be? What I did is: 1. generate a self signed CA cert, and save the

Hi, I have a the annoying problem that the puppet master cannot connect to itself. It fails with: puppet# puppetd --test err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read finished A: tlsv1 alert decrypt error History: I have had this problem on our old puppet server: puppet.domain.com. It was annoying but not critical. Recently I built a new

I''m trying to get puppetrun to work, without luck so far. I have my puppetmaster and clients working fine with the clients polling the master. Now I want to be able to force an update. Using version 0.23.2 On the client I set listen=true and created the namespaceauth.conf file. Restarted puppetd and it appears fine. On the master I run puppetrun as root and get root@plane:/etc/puppet#

I would also check where the "... is not portable!" messaage is generated. If it's done by the configure script, you can look at the test to give you a hint as to why this message was generated. For my setup, I did much the same as you but didn't have to set the SSL_CFLAGS, SSL_LIBS environment variables, nor did I set the --with-ssldir configure option (although your setup may

Hi - I a ran puppetd -vt against a brand newly build host (which is what I normally do for a new host) and got the usual message: err: No certificate; running with reduced functionality. info: Creating a new certificate request for sega-dev-1. info: Requesting certificate On the puppetmaster, I then list the waiting host with: puppetca --list then sign the key. In this case, I decided that the

Hi, the following patches are in the NetBSD packages collection to get OpenSSH 1.2.2 going. Changes: * /dev/urandom may be there but not in the kernel - make sure * Pull in some more headers needed by configure * Add proper ld-flags for ELF platforms * Some code cleanup * Install example files always to a different dir, and use out build system to DTRT WRT getting them to /etc.