Custom Query (463 matches)
Results (4 - 6 of 463)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#21 | fixed | build failure on x86_64 with gcc 4 | ||
Description |
Building on x86_64 with gcc 4 fails because of incompatible syntax of the inline assembly: sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm' This is in the optimized assembly code (for the tiger checksum) that is only used on x86_64. |
|||
#28 | fixed | samhainadmin.pl fails at line 453 | ||
Description |
I am using gpg 1.4.2.2 and it returns error code 2 when successfully signing files if the ssh-agent does not run. This is a problem for scripts relying on gpg return error code. I found out that the simple addition of --no-use-agent addition fixes the issue for samhainadmin.pl... See patch below. $ sudo samhainadmin.pl -m F -------------------------------------------------- Please remember that yule will drop root after startup. Signature verification on SIGHUP will fail if you do not import the public key into the keyring of the non-root yule user. -------------------------------------------------- gpg: WARNING: unsafe ownership on homedir `/home/emoret/.gnupg' You need a passphrase to unlock the secret key for user: "Eric Moret <XXXXXXXXXXXXXXX>" 4096-bit RSA key, ID DBC967BC, created 2005-05-11 gpg: gpg-agent is not available in this session system /usr/bin/gpg --homedir /home/emoret/.gnupg -a --clearsign -o /etc/samhainrc.asc --not-dash-escaped /etc/samhainrc failed: 512 at /usr/local/sbin/samhainadmin.pl line 453. diff -ruN samhain-2.2.2/scripts/samhainadmin.pl.in samhain-2.2.2.new/scripts/samhainadmin.pl.in --- samhain-2.2.2/scripts/samhainadmin.pl.in 2006-04-27 13:58:46.000000000 -0700 +++ samhain-2.2.2.new/scripts/samhainadmin.pl.in 2006-07-23 17:23:05.000000000 -0700 @@ -444,12 +444,12 @@ if (defined($passphrase)) { local $SIG{PIPE} = 'IGNORE'; - my $command = "$gpg --homedir $ENV{'HOME'}/.gnupg --passphrase-fd 0 -a --clearsign -o $fileout --not-dash-escaped $file1"; + my $command = "$gpg --homedir $ENV{'HOME'}/.gnupg --no-use-agent --passphrase-fd 0 -a --clearsign -o $fileout --not-dash-escaped $file1"; open (FH, "|$command") or die "can't fork: $!"; print FH "$passphrase" or die "can't write: $!"; close FH or die "can't close: status=$?"; } else { - my $command = "$gpg --homedir $ENV{'HOME'}/.gnupg -a --clearsign -o $fileout --not-dash-escaped $file1"; + my $command = "$gpg --homedir $ENV{'HOME'}/.gnupg --no-use-agent -a --clearsign -o $fileout --not-dash-escaped $file1"; system("$command") == 0 or die "system $command failed: $?"; } |
|||
#55 | duplicate | yule - using socket and port doesn't work | ||
Description |
I run samhain in server-client mode. I donated for Beltane and using Version 2.3.3 I need yule to run with socket activated. but when I activate it in the configuration and restart yule, there is an socket file but the TCP connection isn't open any more and so the clients can't connect. so I can't reload or update the client-servers i've found that with ticket #47 you have fixed a problem with the socket so I tried to compile samhain V 2.3.2 - but yule wont start any more at all so I compiled V 2.3.0 - this version is running but has still the bug with closed tcp port when socket is opened. my system of yule server: SLES 10 64bit kernel 2.6.16.27-0.6-smp samhain 2.2.3 configure parameters (xxxx=overwritten values): ./configure --enable-base=xxxx '--prefix=/usr' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--localstatedir=/var' '--enable- network=server' '--with-gpg=/usr/bin/gpg' '--with-libwrap' '--enable-xml-log' '--enable-udp' '--with-database=mysql' '--with-sender=sam hain@xxxx' '--with-recipient=notifications@xxxx' '--mandir=/usr/share/man' thanks for your help |