similar to: Older ssh clients can't connect to sshd (6.3p1) built using FIPS object module 2.0.5

I am running Win 98 SE and have a Samba server v2.0.5 on a FreeBSD 3.3 system. Both machines sit on the same 100baseTX subnet. I am seeing expected read performance, but writes from Win98 to the Samba share are terrible; upwards of 30 seconds to copy a 900kb file (yes, that's kb). This happens in both Explorer, the DOS "shell", and in the application that actually created the file

Right, Changes made to dovecot-2.0.5/src/lib-master/master-service.c conn.listen_fd = l->fd; conn.fd = net_accept(l->fd, &conn.remote_ip, &conn.remote_port); i_error("conn.fd: %d",conn.fd); i_error("l->fd: %d",l->fd); i_error("&conn.remote_ip:

I am having problems with dovecot regarding base_dir: I have :: base_dir = /opt/dovecot2/var/run/ For some reason, I have to set permissions to(chmod -R 1777 /opt/dovecot2/var/) for dovecot to run properly, but when I start dovecot, I see this: [root at gw] /opt/dovecot2/etc/dovecot# less /var/log/dovecot/dovecot.log Oct 21 16:15:27 master: Warning: Killed with signal 15 (by pid=72634 uid=0

Hello Dovecot v2.0.5 zlib_save_level = 6 # 1..9 zlib_save = gz # or bz2 Is there a config option to disable zlib, even if above config are in place? If so please provide an example. If no, would it be possible to add one? Like if zlib_save_level = 0 disable zlib. So one can configure per mailbox compression level via sql database. KuiZ Thanks

V2 of dovecot has had the following releases (to recap) 2.0.0 2010-08-16 2.0.1 2010-08-24 2.0.2 2010-09-08 2.0.3 2010-09-17 2.0.4 2010-09-26 2.0.5 2010-10-01 I am on FreeBSD, and the port committers want to wait till dovecot V2 "stabilizes" prior to adding it to the FreeBSD ports base. So, my question is, respectfully, is dovecot V2.0.5 stable enough for prime-time on a busy ISP

http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz.sig * master: default_process_limit wasn't actually used anywhere, rather the default was unlimited. Now that it is enforced, you might notice that the default limit is too low and you need to increase it. Dovecot logs a warning when this happens. * mail-log plugin: Log mailbox

http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz.sig * master: default_process_limit wasn't actually used anywhere, rather the default was unlimited. Now that it is enforced, you might notice that the default limit is too low and you need to increase it. Dovecot logs a warning when this happens. * mail-log plugin: Log mailbox

I thought I'd write one mail about this, rather than duplicate the whole thing to both v1.2.15 and v2.0.5 release announcements. So, ever since this commit: 2009-11-10 Timo Sirainen <tss at iki.fi> * src/plugins/acl/acl-backend-vfile.c: acl: Merge group rights if user belongs to more than one. [76ff6831c9ae] The ACLs were being merged, rather than fully replaced, a bit too

I thought I'd write one mail about this, rather than duplicate the whole thing to both v1.2.15 and v2.0.5 release announcements. So, ever since this commit: 2009-11-10 Timo Sirainen <tss at iki.fi> * src/plugins/acl/acl-backend-vfile.c: acl: Merge group rights if user belongs to more than one. [76ff6831c9ae] The ACLs were being merged, rather than fully replaced, a bit too

Hello Few questions regarding Doveadm-Expunge. 1. I have lazy expunge configure with this name space: .EXPUNGED Storage type: mdbox doveadm -Dv expunge -u user at domain mailbox ".EXPUNGED/*" savedbefore 7d I get some interesting outputs. doveadm(user at domain): Debug: expunge: box=.EXPUNGED/INBOX/mon uid=791 doveadm(user at domain): Debug: expunge: box=.EXPUNGED/INBOX/mon

I was reading this SecurID patch to openssh-3.1p1, List: openssh-unix-dev Subject: =?iso-8859-2?Q?SecurID=20support=20for=20OpenSSH?= From: =?iso-8859-2?Q?V=E1clav=20Tomec?= <v_t_m at seznam.cz> Date: 2002-03-25 14:53:34 and think I've found a copy bugs, the patch for which is included below. First there's a an #ifdef'd if-statement which applies to

http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz.sig See the "ACL handling bugs" message for more details about the ACL merging bug. * acl: Fixed the logic of merging multiple ACL entries. Now it works as documented, while previously it could have done slightly different things depending on the order of the entries. *

http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz.sig See the "ACL handling bugs" message for more details about the ACL merging bug. * acl: Fixed the logic of merging multiple ACL entries. Now it works as documented, while previously it could have done slightly different things depending on the order of the entries. *

I have noticed my WINE isn't using mentioned font already for a quiet long time. After having read http://www.winehq.org/site/docs/wine-user/config-fonts-main on this I found paragraph "5.10.1.1. How To Convert Windows Fonts". After I completed first 4 steps I stuck problem with 5th step: 5, Edit the ~/.wine/config file to remove aliases for the fonts you've just installed.

Hi there, has anybody managed to get the eToken Pro Anywhere work with SSH? I'm using the latest SafeNetAuthentication drivers available for Ubuntu 64bit (8.3) and everything is working just fine except for ssh. I can use the eToken for logging in, openvpn, rdestkop, etc. but it seems ssh does not recognize the device properly. The command "ssh -I /usr/lib/libeToken.so.8 user at

Hi there again, I just wanna tell you what little bug we've found... Namespace is in mbox format. After deleting an mbox the entry in the .imap stays so not everyting is moved away and ist just hanging around... not so bad, but would be nice if it was cleaned up... thanks Tobi -- Dr. Nagler & Company GmbH Hauptstra?e 9 92253 Schnaittenbach Tel : 09622-7197-38 Fax : 09622-7197-50

6.2p2 prints the same version string in the debugging output as it does when invoked with -V: % ssh -V OpenSSH_6.2p2, OpenSSL 0.9.8y 5 Feb 2013 % ssh -v nonesuch |& head -1 OpenSSH_6.2p2, OpenSSL 0.9.8y 5 Feb 2013 6.3p1 and newer don't - I don't have anything at hand that runs 6.3p1, but here are 6.[456]p1: % ssh -V OpenSSH_6.4p1, OpenSSL 1.0.1e-freebsd 11 Feb 2013 % ssh -v

Here is a programming question. The code I am using is quite slow and I was wondering if there is a way to get rid of the for loop. I am dealing with "interaction" in 2x2 table, and am using Edwards's G_I (Likelihood, p. 194). I label the cells in the table as follows stim response "y" "n" total -------------------------------- y hit miss nsignal

https://bugzilla.mindrot.org/show_bug.cgi?id=2186 Bug ID: 2186 Summary: ssh-agent crashes when removing PKCS#11 library keys if non-PKCS#11 keys are present Product: Portable OpenSSH Version: 6.3p1 Hardware: All OS: Mac OS X Status: NEW Severity: minor Priority: P5

https://bugzilla.mindrot.org/show_bug.cgi?id=2187 Bug ID: 2187 Summary: ssh-add unnecessarily prompts for PKCS#11 pin when removing key Product: Portable OpenSSH Version: 6.3p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh-add