similar to: 'ssh -f' option, interoperability with ssh v2.3.0

is there a way of specifying preferred key exchange methods on client end with OpenSSL 3.1 using ssh2? i'm trying to determine which key exchange method is actually being used for a connection but i'm i bit confused by the debug messages: ... debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex:

hello! one thing i'd like to see in OpenSSH is (optional) IDEA algorith support. this would be useful especially in an environment which has a mix of old ssh v1.2.x and OpenSSH installations. according to Ascom non commercial use of IDEA is free (http://www.ascom.com/infosec/idea.html). also, there are countries (e.g. Finland) where IDEA is not patented. here's a patch suggestion for IDEA

pigeonhole 0.5.0 has been already released... ---Aki TuomiDovecot oy -------- Original message --------From: Daniel Kenzelmann <dovecot.org at k8n.de> Date: 03/01/2018 21:31 (GMT+02:00) To: Rhys Williams <lux+mailinglists at melted.me>, dovecot at dovecot.org Subject: Re: dovecot v2.3.0: imap segfault when sieve_extprograms_plugin.so ? called Hi, see the following thread:

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3 release candidate. Of course, a large part of this release consists of compatibility changes for Dovecot v2.3. Apart from that, not much changed, just a few additions and fixes that accumulated over the last few months. Most of these changes will be back-ported to Pigeonhole v0.4, but that release will

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3 release candidate. Of course, a large part of this release consists of compatibility changes for Dovecot v2.3. Apart from that, not much changed, just a few additions and fixes that accumulated over the last few months. Most of these changes will be back-ported to Pigeonhole v0.4, but that release will

Hi, I have recently upgraded to dovecot v2.3 on Ubuntu 16.04.3 from repo.dovecot.org and I switched to IMAPSieve for rspamd with the guide from the wiki. When a mail is moved from Junk to another Inbox or vice-versa imap segfaults. I have posted debug logs and versions below, any help will be greatly appreciated. Thanks, Rhys Williams lux at bifrost:~$ dovecot --version 2.3.0 (c8b89eb) lux at

This is to announce the release of portable openssh-2.3.0p1. This release includes many new features and bug fixes. This is a recommended upgrade if you are using 2.2.0p1 or an older release. Portable OpenSSH is available from one of the many mirrors listed at http://www.openssh.com/portable.html Some of the more notable features include: - Rijndael support for SSH2. Use the "Ciphers"

This is to announce the release of portable openssh-2.3.0p1. This release includes many new features and bug fixes. This is a recommended upgrade if you are using 2.2.0p1 or an older release. Portable OpenSSH is available from one of the many mirrors listed at http://www.openssh.com/portable.html Some of the more notable features include: - Rijndael support for SSH2. Use the "Ciphers"

Hello, After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's managesieve plugin. my emails are not being filtered accordingly into their folders and when i attempt to access the filter interface in roundcube, my maillog reports: Dec 28 12:05:07 mail roundcube: <gs7miohh> PHP Error: Unable to connect to managesieve on 127.0.0.1:4190 in

Hi, I am going to be attempting a build of R for the alphas (our main need is to collate and present graphically, performance metrics we gather on our applications). We have: CC=cc, CXX=cxx, Fortran V5.51 (f77, f95), GNU make 3.80, Perl 5.8.4 I am hesitant to rebuild GCC on this platform, and would like to know if others have success in building R with native C, C++ and Fortran. I plan on

I have just uploaded a new snapshot to: http://www.mindrot.org/misc/openssh/openssh-SNAP-20001114.tar.gz This snapshot includes Markus Friedl's new SSH2 RSA authentication work and -R portforwarding for SSH2. Please give these a good test. The new RSA authentications works similar to the current SSH2 DSA keys, but requires a little modification to config files. Currently RSA key cannot be

https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz.sig It's finally time for v2.3 release branch! There are several new and exciting features in it. I'm especially happy about the new logging and statistics code, which will allow us to generate statistics for just about everything. We didn't have time to implement

https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz.sig It's finally time for v2.3 release branch! There are several new and exciting features in it. I'm especially happy about the new logging and statistics code, which will allow us to generate statistics for just about everything. We didn't have time to implement

December 28, 2017 2:52 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > December 28, 2017 1:21 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: > >>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: >>> >>> December 28, 2017 12:14 PM, "Aki

Hello together, we have very often a problem using OpenSSH v2.3.0 on Solaris 2.6. The daemon hangs up and it is not possible to login in. The -v option for ssh displays the following: # ssh -v zvadm1 SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). debug: Reading configuration data /etc/ssh_config debug: Seeded RNG with 34 bytes from programs debug: Seeded

As soon as possible after release.? I'm the maintainer for pigeonhole, and Adam Weinberger is the maintainer for dovecot (I'm AKA ler at FreeBSD.org). Sent from my T-Mobile 4G LTE Device -------- Original message --------From: "@lbutlr" <kremels at kreme.com> Date: 12/19/17 4:19 AM (GMT-06:00) To: dovecot at dovecot.org Subject: Re: Released Pigeonhole v0.5.0.rc1 for

December 28, 2017 12:14 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: >> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: >> >> Hello, >> >> After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's > > managesieve plugin. my emails are not

That's the point, the fix was committed afterwards... https://github.com/dovecot/pigeonhole/commit/321a39be974deb2e7eff7b2a50 9a3ee6ff2e5ae1 So, any 0.5.1 release on the horizon? Thanks, Daniel Am Mittwoch, den 03.01.2018, 22:14 +0200 schrieb Aki Tuomi: > pigeonhole 0.5.0 has been already released... > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original

Hello Dovecot users, Here's the definitive 0.5.0 release. There is one RC fix regarding the duplicate presence of the session ID in the LMTP/LDA log lines produced by the Sieve interpreter. Since this change is relative to the RC, it is not in the change log below. Changelog v0.5.0: * editheader extension: The implementation of header modifications is heavily updated. Although the

Hello Dovecot users, This is a bugfix release to mend some problems that were found in v0.5.0. The imap4flags bug is actually not first seen in the 0.5.0 release (it is ancient), but I included the fix for it anyway. Changelog v0.5.0.1: - imap4flags extension: Fix binary corruption occurring when setflag/addflag/removeflag flag-list is a variable. - sieve-extprograms plugin: Fix segfault