similar to: Solaris hardware crypto engines

When compiling the software it breaks with an error on the cipher.c file. Lot's of warnings and error of undeclared stuff. Snippet follows: gcc -g -O2 -Wall -Wpointer-arith -Wno-uninitialized -I. -I. -I/usr/local/ssl/include -Iyes -I/usr/local/include -DSSHDIR=\"/etc\" -D_PATH_SSH_PROGRAM=\"/usr/bin/ssh\"

hello, can anyone help me? im gettitng this error when i tried runnin make on solaris 9 rm -f include/asterisk/version.h.tmp make[1]: `ast_expr.a' is up to date. make[1]: Leaving directory `/export/home/fst/chris/cvs/asterisk' gcc -g -o asterisk io.o sched.o logger.o frame.o loader.o config.o channel.o t ranslate.o file.o say.o pbx.o cli.o

On Fri, 12 Oct 2018, Jakub Jelen wrote: > Something like this can be used to properly initialize new OpenSSL > versions: > > @@ -70,12 +70,19 @@ ssh_compatible_openssl(long headerver, long libver) > void > ssh_OpenSSL_add_all_algorithms(void) > { > +#if OPENSSL_VERSION_NUMBER < 0x10100000L > OpenSSL_add_all_algorithms(); > > /* Enable use of crypto

Hi all, attached is a patch that enables using hardware crypto accelerators available through OpenSSL library for SSH operations. Especially in ssh/sshd it can bring a significant speed improvement. OTOH if no crypto engine is available, nothing bad happens and default software crypto routines are used. This patch is used in SUSE Linux OpenSSH package and proved to work (at least it didn't

One of my hosts just rebooted for the first time in ages, and now it won't connect to any other nodes. The log just contains continual "error while decrypting metadata" errors. tincd[8324]: Error while decrypting: error:060A7094:digital envelope routines:EVP_EncryptUpdate:invalid operation tincd[8324]: Error while decrypting metadata from fairfield_gw (yy.yy.yy.yy port 655)

Hello, I am tying to compile Dovecot 2.2.27 on Solaris 10, and I get this error: test-ioloop.c: In function `test_ioloop_pending_io': test-ioloop.c:188: error: size of array `type name' is negative My configuration is like this: Install prefix . : /usr/local File offsets ... : 64bit I/O polling .... : poll I/O notifys .... : none SSL ............ : yes (OpenSSL) GSSAPI ......... : no

Hello, We are running units in the field that are headless. Sometimes we get units returned that we when we boot them up have some type of filesystem inconsistency that the default preen doesn't fix but running fsck -y does. I want to eliminate the -p (preen option) and always do the -y option anyone know where to make this change? Thanks, -- Stephen Clark *NetWolves* Director of

Hello, I just found this message in our dovecot logfiles: "Disconnected: BUG: Unknown internal error" Should I worry about this ? There are no complaints yet (although it is not limited to one user). It seems to occur with different clients (Apple/MacOS mail, Windows/Thunderbird, Pine). We're running dovecot 1.0.10 on Solaris 10 with mboxes (NFS) and local index storage. There are

Hello, a few days ago I switched out UW-server installation to dovecot 0.99.14 (Solaris 9). There were a few client issues, but mostly the migration was ok. But I have still some questions/problems: +) dovecot-auth: ... PAM: pipe() failed: Too many open files I increased the max. number of open files. Is this normal behaviour, that more than 512 open files are needed ? +) we're using mbox

stuck on this in spite of finding a few items in the archive that seemed pertinent. just configuring a new installation of 2.2.8 from SunFreeware on a Solaris 8 system. installation done, swat running, did simple basic configuration. then went to terminal window and got /usr/local/samba/bin# ./smbpasswd -j provost -r umapvstads1 -U libadmin Password: Error connecting to

Hello, I have a question about the way Dovecot limits file system access. Currently we're using Dovecot 1.0.5 (Solaris 10). In some cases users have a symbolic link like "z: -> /" in their mail directory. As a result there are log entries like Jan 25 13:30:31 imap1 dovecot: [ID 107833 mail.error] IMAP(xyz):

Hi, thank You for a reply, compiling with Solaris Studio 12.5 solved this case. Martin Preen <preen at informatik.uni-freiburg.de> ra??: > Hello, > I don't have problems building 2.2.27 on Solaris 10 > (using Sun Workshop compiler 5.11). > > The configuration is the same as your. > Maybe a compiler/version problem on your system ? > > Regards, > Martin >

Hello everybody, I get the following assertion error with dovecot 1.0-stable when accessing a large folder: file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) There is no error when using dovecot 0.99.14. Any ideas ? Martin ----------------------------------------------------------------- Martin Preen, Universitaet

Hello, with some mbox folders I got this error: Mar 18 14:48:12 imap2 dovecot: [ID 107833 mail.crit] Panic: IMAP(xyz): file charset-iconv.c: line 122: unreached I assume that this is related to the folder contents (and not the configration). What does that mean to me ? Martin --------------------------------------------------------------- Martin Preen, Universit?t Freiburg, Institut f?r

I'm bringing up a system with dovecot that has been running for years with uw-imap. In making the switch, I put a tail on the log file, made the switch, and sent a test mail and received it. I was able to receive mail with no apparent difficulties, but the log file was disconcerting. A number of users connected during the few minutes I had it running, and for each of them there was an

We've been happily running Dovecot in Solaris 10 for about 8 months now. Yesterday, Solaris 10's SMF put it in maintenance mode (shut it down) seemingly out of the blue. The only thing going on was that I had updated the ssl certificate. We had previously been using a self signed cert. Now we have a cert from InCommon. We had a problem with a few users who are still on ancient Eudora

http://dovecot.org/test/ Two potentially dangerous changes: - mbox parser should now be able to handle CR+LF linefeeds. Hopefully doesn't break anything. - Some mail header parser changes. Hopefully doesn't break anything. And other stuff: - COPY shouldn't crash anymore with 64bit systems - If PAM modifies username, keep it - When auth workers died they leaked file

Hi, My setup: Solaris 9, /var/mail is NFS mounted from another Solaris 9 box, home directories and dovecot index stuff is on local ufs filesystems. I upgraded from alpha4 to a5 about 36 hours ago. Dovecot is configured like so during the build: VERSION=1.0.alpha5 CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure

Engine keys are private key files which are only understood by openssl external engines. ?The problem is they can't be loaded with the usual openssl methods, they have to be loaded via ENGINE_load_private_key(). ?Because they're files, they fit well into openssh pub/private file structure, so they're not very appropriately handled by the pkcs11 interface because it assumes the private

Hello, I'm currently testing dovecot/imap (Version 0.99.13). I found this in the log: imap(xxxxx): [ID 265587 mail.crit] file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) dovecot: [ID 684838 mail.error] child 7376 (imap) killed with signal 6 The user tried to setup a new folder (with Thunderbird)