similar to: Binary compatibility problem in OpenSSH from OpenSSL mailing list

hi i am trying to execute the command from the dialplan as follows: exten => 1987,1,Playback(posix-restarting) exten => 1987,2,wait(1) exten => 1987,3,System(/home/docas/Desktop/python mess1.py) exten => 1987,4,Hangup i get the error on asterisk CLI system_exec_helper:Unable to execute "/home/docas/Desktop/python mess1.py " can anybody please help me on what i am doing

Hello, I've updated sources but forgot to recreate configure so I've ended without #define HAVE_EVP_RIPEMD160 1 and ssh client ended with: OpenSSH_6.7p1, OpenSSL 1.0.1h-fips 5 Jun 2014 debug1: Reading configuration data ssh.config main: mux digest failed The problem was that ssh_digest_by_alg() couldn't verify alg with an index bigger than 1 since the line with SSH_DIGEST_RIPEMD160

OpenSSL 1.1.0 has deprecated this function. --- configure.ac | 1 + openbsd-compat/openssl-compat.c | 2 ++ openbsd-compat/openssl-compat.h | 4 ++++ 3 files changed, 7 insertions(+) diff --git a/configure.ac b/configure.ac index 3f7fe2cd..db2aade8 100644 --- a/configure.ac +++ b/configure.ac @@ -2710,6 +2710,7 @@ if test "x$openssl" = "xyes" ; then ])

On Wed, 19 Feb 2020 at 06:38, Val Baranov <val.baranov at duke.edu> wrote: > AIX 7.1 TL5, OpenSSL ver. 1.1.1d. "vac.C" version 11.0.1.23 > Compilation error " The indirection operator cannot be applied to a pointer to an incomplete struct or union " (see full log below) produced for " libressl-api-compat.c ". > No such error if compiled with OpenSSL

If the standard way works, I am happy to include the original patch I sent, amended so that it checks for presence of LIBRESSL_VERSION_NUMBER. If they keep this promise, then we should have no worries about things breaking up. Aki On 02.11.2016 14:24, Michael A. Peters wrote: > Indeed, which is why I use it. > > But it also is in the minority which is why I find it acceptable for

> I?ve spent some time (together with Christian and Thomas) hacking on > U2F support in OpenSSH, and I?m happy to provide a first patch ? it?s > not complete, but it should be good enough to get the discussion going > :). Please see the two attached files for the patch. This is great - I'm looking forward to it! :) I've implemented U2F into another (C-based) application these

Hi list I just realized that that I don not receive all mails in my mailbox (running dovecot-ee 2.2.23.1-1 on Debian 8). On my frontend servers (running postfix) the queue fills up with mails that cannot be delivered via lmtp to my backend servers. The error message on the frontend is "lost connection with backend while sending data" When I checked the logs on the backend server I found

# 2.2.devel (c73322f): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (fac92b5) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 ==> /var/log/dovecot/dovecot.log <== Oct 15 09:50:15 nihlus dovecot: lmtp(11447): Connect from local Oct 15 09:50:15 nihlus dovecot: lmtp(tlx at leuxner.net): Panic: file lda-sieve-plugin.c: line 447 (lda_sieve_execute_scripts): assertion failed: (script !=

On Thu, 2015-08-06 at 09:12 +0200, Stephan Bosch wrote: > Could you provide a full backtrace using the gdb command `bt full'? Thanks for the reply. Is this everything you need? #0 0x00007f8553969626 in sieve_validator_register_command () from /usr/lib/dovecot/libdovecot-sieve.so.0 No symbol table info available. #1 0x00007f8552eff4e6 in ext_extdata_validator_load (ext=0x7f8556f60280,

OpenSC has taken a different approach to OpenSSL-1.1. Rather then writing a shim for OpenSSL-1.1, the OpenSC code has been converted to the OpenSSL-1.1 API and a sc-ossl-compat.h" file consisting of defines and macros was written to support older versions of OpenSSL and Libressl. https://github.com/OpenSC/OpenSC/blob/master/src/libopensc/sc-ossl-compat.h The nice part of this approach is

On Thu, 2015-08-06 at 09:49 +0200, Stephan Bosch wrote: > You have no debug symbols installed. Could you install dovecot-dbg > package and try again? Sorry, how's this: #0 sieve_validator_find_command_registration (valdtr=0xffffffff, command=0x7fc573c4bcd8 "extdata") at sieve-validator.c:309 No locals. #1 sieve_validator_register_command (valdtr=0xffffffff,

Hello, I use dovecot 2.0.1 and pigeonhole Sieve (version of August), I try to create a deliver plugin (lda or lmtp), but if I declare, in addition to my plugin, sieve, sieve is called first, and my plugin is never called. I tried to change the order of declaration of plugins, but nothing changes. If I remove Sieve, my plugin is properly called. protocol lmtp { #mail_plugins = $mail_plugins

On Thu, 2015-08-06 at 16:10 +0200, Stephan Bosch wrote: > Since the extdata plugin is not part of the normal Debian packages (not > afaik anyway), you likely compiled and installed the extdata plugin > manually in the past while using Dovecot 2.1. Do that again, but use > this repository: http://hg.rename-it.nl/pigeonhole-0.4-sieve-extdata/ I'm just trying to install this now,

This has the advantage of being more efficient than the included routines and allows distros to centralize crypto mainteniance on a few libraries. --- configure.ac | 4 +- m4/ax_check_openssl.m4 | 124 +++++++++++++++++++++++++++++++++++++ src/libFLAC/Makefile.am | 2 +- src/libFLAC/include/private/md5.h | 8 ++- src/libFLAC/md5.c

Topic 6: RE:unable to execute command hi there i tried to execute the command as suggest like exten => 1987,1,Playback(posix-restarting) exten => 1987,2,wait(1) exten => 1987,3,System(/usr/bin/python /home/docas/Desktop/mess1.py) exten=> 1987,4,Hangup it still doesn't work,now it does it give unable to execute command but it doesn't reach the system command it just

Hi Stephan, Here it is: Program received signal SIGSEGV, Segmentation fault. p_strdup (pool=pool at entry=0x55555579bc20, str=0x6d65642e6c69616d <error: Cannot access memory at address 0x6d65642e6c69616d>) at strfuncs.c:51 51????? strfuncs.c: No such file or directory. (gdb) bt full #0? p_strdup (pool=pool at entry=0x55555579bc20, str=0x6d65642e6c69616d <error: Cannot access memory at

Playing around with the [wonderful] GSS-API patches for OpenSSH [1] I noticed that there is a bit of functionality missing from OpenSSH/GSS-API, namely that authorized_keys2 has no meaning when using GSS authentication. Yes, ~/.k5login can be used to grant access to an account for applications that support Kerberos, as does OpenSSH with those GSS patches, but .k5login does not and cannot provide

On 2016-11-02, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > If the standard way works, I am happy to include the original patch I > sent, amended so that it checks for presence of LIBRESSL_VERSION_NUMBER. > If they keep this promise, then we should have no worries about things > breaking up. Diff below is what I've added to OpenBSD ports. The libressl API is not cast in

From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> This is a huge all-in-one patch and deserves a little cleanup and splitting. However, I wanted to get it out here for some feedback. My primar motivation to use SHA1 for checksumming (by default) instead of MD5 is not the additional security bits but performance. On a decent x86 box the SHA1 performance is almost the same as

On Mon, 5 Nov 2018, Darren Tucker wrote: > On 5 November 2018 at 16:41, Michael Forney <mforney at mforney.org> wrote: > > > This causes EVP_CIPHER_CTX_set_iv to get replaced unnecessarily (or > > a duplicate symbol error if linking statically). > > > > Applied, thanks. should this go on the V_7_9 branch too? > >