similar to: [RFE] A way to encode passwords in the /etc/imap.passwd file

Hello, I've recently saw a discussion on this list, about a standardised way of emptying POP3 mailboxes on the server - but no solution came up. Please provide a suggestion for the following situation: - I am running a stock POP3 dovecot server, on Fedora 12 (dovecot version 1.2.9) - passwd-file authentication via /etc/imap.passwd - users are virtual, sharing the same UID/GID; -

Hello, Please tell me if it's possible to use tinc together with OSPF (instead of static routes in LAN). By OSPF I mean Quagga's GNU/Linux daemon. Namely, I have a group of LANs (private 192.168.x.0/24 each). Each LAN has a GNU/Linux default gateway, 192.168.x.1, that also connects to the Internet via a public IP address (does NAT and firewall for the LAN "behind" it). tinc

Hello all, Thank you for tinc, that is an **excellent** and useful package! Taking into account that both Red Hat and Debian (8.x) families now use systemd, there is, IMHO, one small. but important correction to be done: tinc's initialization. IMHO, we need: 1. A proper tinc.service file, included by default (prepackaged) in the stock .deb and .rpm packages in Fedora, Debian, Ubuntu,

Hello, Would you please help me solve the following case? My (CentOS) server runs dovecot and allows both POP3 and IMAP service. Users are virtual users (no home directories), with messages stored in Maildir directories under /var/spool/mail/vhosts/example.com/username Some of them use mobile devices (without local storage space), so I must allow IMAP access, not just POP3. But the storage

hi, I noticed that RPM packages I sign use SHA1 Signature : RSA/SHA1, Fri 08 Jan 2016 10:50:58 AM PST, Key ID ad3b591d147abf59 Signatures from CentOS 7 use SHA256 Signature : RSA/SHA256, Wed 06 Jan 2016 08:54:58 AM PST, Key ID 24c6a8a7f4a80eb5 I'm trying to find where / how to use sha256 when I sign packages but I am not having much luck. Closest I have found is this :

On 01/20/2016 04:39 AM, Johnny Hughes wrote: > On 01/20/2016 01:37 AM, Alice Wonder wrote: >> hi, >> >> I noticed that RPM packages I sign use SHA1 >> >> Signature : RSA/SHA1, Fri 08 Jan 2016 10:50:58 AM PST, Key ID >> ad3b591d147abf59 >> >> Signatures from CentOS 7 use SHA256 >> >> Signature : RSA/SHA256, Wed 06 Jan 2016 08:54:58

I am getting unacceptable performace problems by using the roo gem for reading a file by using XLSX or XLS library from this gem. Someone may suggest me an alternative about how to parse an .XLSX file? <code> parsed_file = Excel.new(filename,false, :ignore) if (file_format.upcase == "XLS") parsed_file = Excelx.new(filename,false, :ignore) if (file_format.upcase ==

On 01/20/2016 04:52 AM, Johnny Hughes wrote: > On 01/20/2016 04:48 AM, Johnny Hughes wrote: >> On 01/20/2016 04:39 AM, Johnny Hughes wrote: >>> On 01/20/2016 01:37 AM, Alice Wonder wrote: >>>> hi, >>>> >>>> I noticed that RPM packages I sign use SHA1 >>>> >>>> Signature : RSA/SHA1, Fri 08 Jan 2016 10:50:58 AM PST, Key

Pe 7 Aug 2013 11:35, Timo Sirainen a scris: >> Thank you, but doveadm expunge will ask for the mailbox name: >> >> [root at mail1 ~]# doveadm expunge -u john.doe at example.com ON >> 2013-08-07 doveadm(root): Fatal: expunge: To avoid accidents, >> search query must contain MAILBOX in all search branches > > Add: mailbox '*' Thank you, it works! May I

Hello again, >From the point of view of a Red Hat *user*, the standardised way of doing things would be to have an /etc/sysconfig/tinc file containing something like: NETWORKS="vpn1 vpn2 vpn3" (one or more names separated by spaces) At initialization, each name should launch a separate tinc instance (a different VPN) tinc service should not start until the user adds at least

La 25.09.2015 13:00, tinc-request at tinc-vpn.org a scris: > Unfortunately, this is not something that maps well to systemd. It would > require a systemd to run a script that parses the sysconfig file and > start all the tinc daemons. Systemd will then put all those daemons in > the same control group and won't recognize something is wrong if only > one of the daemons fail. So

On 01/20/2016 04:48 AM, Johnny Hughes wrote: > On 01/20/2016 04:39 AM, Johnny Hughes wrote: >> On 01/20/2016 01:37 AM, Alice Wonder wrote: >>> hi, >>> >>> I noticed that RPM packages I sign use SHA1 >>> >>> Signature : RSA/SHA1, Fri 08 Jan 2016 10:50:58 AM PST, Key ID >>> ad3b591d147abf59 >>> >>> Signatures from

On Thu, Sep 24, 2015 at 05:45:36PM +0200, Guus Sliepen wrote: > On Thu, Sep 24, 2015 at 05:51:30PM +0300, R?zvan Sandu wrote: > > > IMHO, we need: > > > > 1. A proper tinc.service file, included by default (prepackaged) in the > > stock .deb and .rpm packages in Fedora, Debian, Ubuntu, CentOS, etc. > > > > By "proper" I mean it will start

I am looking for PHP functions that implement passwords that much the dovecotpw implementation. I downloaded one from PEAR, Crypt_HMAC, but the passwords it generates look nothing like the dovecotpw passwords, which could be my fault because I know nothing about the field. Is there a guide or some library that implements them to match dovecotpw?

Platform is Solaris 8 on a 280R. I'm setting up a new installation of Dovecot, and I ran into some troubles that I've partly tracked down. I setup auth/user dbs with LDAP initially, and things worked well. Passwords are stored as "{crypt}zxcv..." in LDAP. I setup SQL, and began getting this: dovecot: Jan 23 16:37:47 Error: child 8718 (auth-worker) killed with signal 11

Hi, please apply the following patch to dovecotpw. Without this, it will be unusable on powerpc and (maybe) other architectures where the char is unsigned by default. --- dovecot-1.0/src/util/dovecotpw.c (revisione 2066) +++ dovecot-1.0.new/src/util/dovecotpw.c (copia locale) @@ -40,7 +40,7 @@ const char *user = NULL; char *scheme = NULL; char *plaintext = NULL; - char ch; +

The idea of salted hash algorithms is to generate a different hash even if the same text is entered. That can be easily seen with dovecotpw: using NON-salted SHA256, same hash is generated for a given password [root at correio ~]# dovecotpw -s SHA256 -p 123 {SHA256}pmWkWSBCL51Bfkhn79xPuKBKHz//H6B+mY6G9/eieuM= [root at correio ~]# dovecotpw -s SHA256 -p 123

Is there any other mechanism than using passwd files with md5-hashed passwords created by dovecotpw that will support cram-md5 authentication? Has anyone created setups where the passwd databases reside in the individual users home directories? Is it possible to persuade dovecotpw to update the passwd databases automatically. Having to use a text editor to paste in the passwords sets a high

Where can I find documentation on how to use the "dovecotpw" program that I was referred to? No man page. No wiki. Very little from "dovecotpw -h". What I need to do is generate the "passwd-file" contents with an MD5 scheme (the one equivalent to /etc/shadow is preferred).

Hi I would like to simulate dovecot's dovecotpw with a perl script I tried / used use Crypt::SaltedHash; my $csh = Crypt::SaltedHash->new(algorithm => 'SHA-1'); $csh->add($passwd_string); my $salted = $csh->generate; also use Digest::SHA1; use MIME::Base64; $ctx = Digest::SHA1->new; $ctx->add($passwd_string); $ctx->add('salt'); my $salted =