Displaying 20 results from an estimated 200 matches similar to: "Dovecot + SSL + Fedora"
2004 Apr 09
1
dovecot dies - mabye a clue?
Dovecot died twice today. This was in the maillog:
Apr 9 17:50:27 ciscy pop3-login: RAND_bytes() failed: error:24064064:random
number generator:SSLEAY_RAND_BYTES:PRNG not seeded
Apr 9 17:50:27 ciscy dovecot: Login process died too early - shutting down
I think I can cause it to happen reliably and I'm asking for other to test
this scenario:
Open several terminal windows. In each, type
2003 Jun 23
1
OpenSSL on AIX
Hi,
with current test releases SSL doesn't work anymore for me on AIX 4.3
with dovecot-0.99.10-test14. It worked with 0.99.9.1.
dovecot: Jun 23 19:42:23 Info: Dovecot starting up
imap-login: Jun 23 19:42:25 Fatal: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded
imap-login: Jun 23 19:42:25 Fatal: RAND_bytes() failed: error:24064064:random number
2004 Jan 24
1
dovecot crash
I woke up this morning and my dovecot server had died with the following in
the dovecot.log file:
pop3-login: Jan 23 10:23:08 Fatal: RAND_bytes() failed:
error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded
dovecot: Jan 23 10:23:08 Error: Login process died too early - shutting down
dovecot: Jan 23 10:23:08 Error: child 16321 (login) returned error 89
How can I find out
2004 Mar 19
1
Re: Dovecot died due to some SSL related error
(Sorry, just joined the list, can't reply in the original message
from Feb 4.)
> Hi,
> Dovecot (pre-compiled version of Fedora Core 1, configured for Maildir)
> is running fine for me since a few days. It happened now twice to me
> that dovecot died with the following error message in /var/log/maillog:
>
> Feb 4 11:18:27 hundehuette imap-login: RAND_bytes() failed:
>
2004 Mar 30
1
Fatal: RAND_bytes() failed
This morning dovecot died with the following messages in the errorlog.
Any solution to this problem?
I am using Fedora Core 1 on a SMP i686 box.
imap-login: Mar 30 08:08:00 Fatal: RAND_bytes() failed:
error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded
dovecot: Mar 30 08:08:00 Error: Login process died too
2010 Feb 22
3
relative file path
Hello,
Is there a way to find where a script is located within a script? getwd()
doesn't do what I want because it depends on where R was called from. I want
something like source("randomFile") and within randomFile there is a
function called whereAmI() which returns c:\blah\blah2\randomFile.R
In perl there is a library called FindBin and $FindBin::Bin has the
directory of the file
2016 Apr 08
2
slowdown in notmuch perf suite with xapian 1.3.5
Olly Betts <olly at survex.com> writes:
>
> So the T00-new.sh numbers make sense - there's more work to do, and
> we need to read existing positional data more to insert the new stuff,
> so the increased reads and writes make sense.
>
> But guessing at what the other two tests do, I wouldn't expect them to
> be affected by this.
The non-optimized-away cases of
2014 Jul 12
1
openssh portable and libressl portable cause recursion between arc4random and RAND_bytes
Hi,
Yesterday I tried to replace the system openssl in a gentoo system with
libressl.
With openssh an interesting issue popped up:
* RAND_bytes in libressl calls arc4random
* arc4random is a compat function both in openssh and libressl
* arc4random from openssh uses RAND_bytes
So what's happening is a recursion. arc4random wants to use RAND_bytes
and RAND_bytes wants to use arc4random. The
2003 Mar 17
1
RAND_bytes return value
Hello,
I have been doing some looking at openssl 0.9.7 and
openssh3.5p1 and found a minor descrepancy. RAND_bytes() is
called around line 69 of openbsd-compat/bsd-arc4random.c.
It checks to see if the return is not zero. The RAND_bytes
function can also return -1, too. All the code in openssl
uses <=0 for the test rather than !.
Best Regards,
Steve Grubb
2008 Apr 21
3
FIPS 140-2 OpenSSL(2007) patches
Hi,
I am happy to (re)send a set of patches for compiling OpenSSH 4.7p1 with
FIPS 140-2 OpenSSL.
These are based on previously reported patches by Steve Marquess
<marquess at ieee.org> and Ben Laurie <ben at algroup.co.uk>,
for ver. OpenSSH 3.8.
Note that these patches are NOT OFFICIAL, and MAY be used freely by
anyone.
Issues [partially] handled:
SSL FIPS Self test.
RC4,
2004 Feb 04
0
Dovecot died due to some SSL related error
Hi,
Dovecot (pre-compiled version of Fedora Core 1, configured for Maildir)
is running fine for me since a few days. It happened now twice to me
that dovecot died with the following error message in /var/log/maillog:
Feb 4 11:18:27 hundehuette imap-login: RAND_bytes() failed:
error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not
seeded
Feb 4 11:18:27 hundehuette dovecot: Login
2002 Jan 22
4
ssh-rand-helper
Now that ssh-rand-helper has been segregated into a separate program,
I'd like to revisit an old question about its entropy gathering.
- would it be desirable to make it possible for ssh-rand-helper to fall
back to external commands if PRNGD cannot be reached, instead of
choosing one or the other at compile time?
- When using PRNGD, the program gets 48 bytes of entropy from PRNGD,
2006 Mar 17
1
[PATCH] OpenSSL RNG initialization
Hi,
dovecot tries to use OpenSSL's PRNG to generate random numbers if
there is no /dev/urandom found. Unfortunately, it is flawed in its
present
form, since the PRNG is not seeded before RAND_bytes() is called in
src/lib/randgen.c (on systems which have /dev/urandom, OpenSSL
automatically seeds its PRNG from the urandom device).
Here's a patch to address this issue: it tries to seed
2003 Jun 15
3
0.99.10-test12
http://dovecot.procontrol.fi/test/
I should have released 0.99.10 already I think.. There's just two
annoying problems that I think should be fixed first:
- PAM: If user gives a wrong password, dovecot-auth process sleeps for
two seconds, blocking everyone else who are trying to authenticate at
the time. So using PAM isn't very good idea at the moment.
- OpenSSL problems. Are they
2014 Jan 07
1
samba_dnsupdate: could not talk to any default name server
Every 10 minutes, my samba 4.0.9 (active directory domain controller)
is logging messages like these :-
2014-01-07T14:26:09.896260+11:00 gumbo samba[5198]: /usr/sbin/samba_dnsupdate: ; Communication with 127.0.1.1#53 failed: operation canceled
2014-01-07T14:26:09.896281+11:00 gumbo samba[5198]: /usr/sbin/samba_dnsupdate: could not talk to any default name server
2014-01-07T14:26:09.917096+11:00
2001 Dec 01
1
mips/mipsel problem
Hi,
There seems to be a problem with the arc4random code on mips/mipsel,
producing the following error message:
Couldn't obtain random bytes (error 604389476)
To quote the bug submitter:
"On mips and mipsel, the above error message is frequently seen when
calling
ssh with a command, usually several times in rapid succession,
although that
is not always the case. The error appears to
2004 May 27
5
0.99.10.5 released
One more bugfix since rc2:
- Maildir: synchronization might have sometimes set wrong flags to
messages, or crash completely
Quite rare because we were lucky before :)
And list of all the changes one more time:
v0.99.10.5 2003-12-27 Timo Sirainen <tss at iki.fi>
+ MySQL authentication, patch by Matthew Reimer
+ --with-moduledir configure option
- mbox: APPEND reversed given
2013 Nov 26
0
VFS shadow_copy2 with samba 4.0.9
I am trying to use shadow copy with Samba 4.0.9 on Debian 7 (wheezy),
Linux kernel 3.2. Windows 7 clients on the LAN can not see Previous
Verions of files stored on the server, although I believe I have set
up directories with snapshots.
Here are some highlights from smb.conf :-
[global]
server role = active directory domain controller
domain logons = yes
...
[Pluto]
path
2016 Apr 08
0
slowdown in notmuch perf suite with xapian 1.3.5
On Thu, Apr 07, 2016 at 09:40:59PM -0300, David Bremner wrote:
> Olly Betts <olly at survex.com> writes:
>
> >
> > So the T00-new.sh numbers make sense - there's more work to do, and
> > we need to read existing positional data more to insert the new stuff,
> > so the increased reads and writes make sense.
> >
> > But guessing at what the other
2005 Nov 17
3
4.2 and the 'last' command
We've run into an interesting dilemma regarding last log information and
ssh 4.2p1. In 3.8, we didn't see this problem, but now has cropped up
in 4.2.
When a user logs in, sshd seems to call 'last' to get the last log
information. 'last' then opens the /var/log/wtmp file and processes the
information. On some systems, this file can be quite large, and we're
seeing