> On 18/04/2023 02:03 EEST Paul Kroitor wrote:
>
>
> Hello,
>
> It seems from this thread at letsencrypt :
> https://community.letsencrypt.org/t/changing-permissions-for-pem-files/196561
> (see especially second post from _az) that doveadm pw now parses all files in
Hello,
It seems from this thread at letsencrypt :
https://community.letsencrypt.org/t/changing-permissions-for-pem-files/19656
1 (see especially second post from _az) that doveadm pw now parses all files
in the config, even ones not relevant to the pw aspect of the request. If
it's not ab
as linux passwd does.
doveadm pw -s [scheme]
onf -f service=doveadm -c /etc/dovecot/dovecot.conf -m
> doveadm -e /usr/bin/doveadm pw -p asdf
Can this problem not be solved by using `pw -p "$(some cmd to echo the
password)"`?
E.g. if using Jason Donenfeld's password store application "pass",[1]:
pw -p "$(
ownside of putting the password on the command line is that it will
(briefly) be visible in the output of 'ps':
richard 9449 0.0 0.0 5040 3616 pts/4R+ 19:27 0:00
/usr/bin/doveconf -f service=doveadm -c /etc/dovecot/dovecot.conf -m
doveadm -e /usr/bin/doveadm pw -p asdf
Cheers,
Richard
On Sun, Apr 24, 2022 at 06:45:19PM +0800, ミユナ (alice) wrote:
> Bernardo Reino wrote:
>> The argument to "-p" is not a file containing the password, but the
>> password itself!
>
> ok the helps says:
>
> pw [-l] [-p plaintext]
>
> i just thought it specifies the text file.
>
> thanks fo
ok the helps says:
pw [-l] [-p plaintext]
i just thought it specifies the text file.
thanks for clarifying it.
Bernardo Reino wrote:
The argument to "-p" is not a file containing the password, but the
password itself!
On Sun, 24 Apr 2022, ミユナ (alice) wrote:
Hello
when i want to assign a password to a user, I need to write the plain passwd
to a text file then do:
# doveadm pw -p input.txt
{CRAM-MD5}77180880...
it's not that convenient to write to a file first.
does it support the format below?
do
Hello
when i want to assign a password to a user, I need to write the plain
passwd to a text file then do:
# doveadm pw -p input.txt
{CRAM-MD5}77180880...
it's not that convenient to write to a file first.
does it support the format below?
doveadm pw "plain password"
prov
Aki;
I know most likely this isn't dovecot's fault, however upgrading from
2.3.8 to 2.3.16 broke the password plugin for roundcube. Im only asking
if you might know what changes in dovecot might have caused this
incompatibility so i can fix it myself or point roundcube in the right
direction
> On 7 August 2021, at 09:50, Timo Sirainen wrote:
>
> On 7. Aug 2021, at 14.07, Alexander Dalloz <mailto:ad+li...@uni-x.org>> wrote:
>>
>> Am 07.08.2021 um 08:06 schrieb Doug Hardie:
>>> mail# doveadm pw
>>> Enter new pass
On 7. Aug 2021, at 14.07, Alexander Dalloz wrote:
>
> Am 07.08.2021 um 08:06 schrieb Doug Hardie:
>> mail# doveadm pw
>> Enter new password:
>> Retype new password:
>> {CRYPT}$2y$05$oSB6end9V.YumJMzON7lfeOL9N8TXK6jhYqjHOEnPd1NLZ9.QNaTy
>> I thought the def
Am 07.08.2021 um 08:06 schrieb Doug Hardie:
mail# doveadm pw
Enter new password:
Retype new password:
{CRYPT}$2y$05$oSB6end9V.YumJMzON7lfeOL9N8TXK6jhYqjHOEnPd1NLZ9.QNaTy
I thought the default was supposed to be CRAM-MD5. I don't find anywhere I
have entered CRYPT. There is one referen
mail# doveadm pw
Enter new password:
Retype new password:
{CRYPT}$2y$05$oSB6end9V.YumJMzON7lfeOL9N8TXK6jhYqjHOEnPd1NLZ9.QNaTy
I thought the default was supposed to be CRAM-MD5. I don't find anywhere I
have entered CRYPT. There is one reference to it in auth-passwdfile.conf.ext,
but cha
er enters it's password through a 'dialog --passwordbox'.
> >
> > I guess my question is: it possible to pipe that into 'doveadm pw' directly
> > from memory, without using any kind of on-disk temp file?
>
> $ dialog --passwordbox .. | sed p |
s my question is: it possible to pipe that into 'doveadm pw' directly
from memory, without using any kind of on-disk temp file?
$ dialog --passwordbox .. | sed p | doveadm pw
with "sed p" you print explicitly (p) and implicitly (default in sed) the input
lines (i.e. whatever d
Oscar del Rio wrote:
> On 2021-06-16 5:23 a.m., Kevin N. wrote:
> > I am using 'doveadm pw' from inside a bash script to generate the salted
> > hash for a user provided password.
> > I call it like: doveadm pw -s SHA256-CRYPT -u $user -p $password
> >
On 2021-06-16 5:23 a.m., Kevin N. wrote:
I am using 'doveadm pw' from inside a bash script to generate the salted hash
for a user provided password.
I call it like: doveadm pw -s SHA256-CRYPT -u $user -p $password
Is there any possible way to use piping (so it won't show up in
Hello everybody,
I am using 'doveadm pw' from inside a bash script to generate the salted hash
for a user provided password.
I call it like: doveadm pw -s SHA256-CRYPT -u $user -p $password
Is there any possible way to use piping (so it won't show up in ps for example)
to pass t
Hi all,
Some time ago, I wrote a small CGI script to let users change their IMAP
password. The script runs as www-data user and uses "doveadm pw" to check if a
password hash matches a password.
Unfortunately, this means that I have to make large parts of my dovecot config
world-re
On 9/26/18 2:42 AM, Aki Tuomi wrote:
The reason it fails is because auth process runs out of memory and there
is a bug in libsodium which causes it to crash in this scenario. The fix
is to do
service auth {
vsz_limit = 0 # or 2G at least
}
After testing this evening, I can confirm that thi
2.3.2.1 (0719df592) and trying to use the
> ARGON2ID crypt scheme for authentication using the passdb passwd-file
> driver. My passdb config is very simple:
>
> passdb {
> driver = passwd-file
> args = username_format=%u
> }
>
> If I generate a passw
s way:
doveadm pw -s ARGON2ID -p 'This is a test'
I get a crypt value for the password that I can place in the password
file like:
testuser:{ARGON2ID}$argon2id$v=19$m=65536,t=3,p=1$UuqF25QtumNBe9R2FmUZvA$5avvHY5TIaj5Wl5C4k8BOI4bcmNei7BwPLlXYQVybMc
And if I test authentication wi
Am Donnerstag, den 04.06.2015, 08:15 +0200 schrieb Hardy Flor:
> doveadm pw -t
> '{SHA512-CRYPT}$6$8FfoioQWQDR/Vuzu$ynKiO/E6Xf4dMvfx2LsP9KQotqy5cEOEppnEh5Hqe1UpCYAgOwSIJlNb0O65fxdYcRZH3gNFQ7ZOM/2kD/R811'
> -p test
>
> You have $ in the password, see man-page of sh
doveadm pw -t
'{SHA512-CRYPT}$6$8FfoioQWQDR/Vuzu$ynKiO/E6Xf4dMvfx2LsP9KQotqy5cEOEppnEh5Hqe1UpCYAgOwSIJlNb0O65fxdYcRZH3gNFQ7ZOM/2kD/R811'
-p test
You have $ in the password, see man-page of shell ...
Am 04.06.2015 um 05:29 schrieb Felix Zielcke:
> oveadm pw -t
> {SHA512-CRYP
Hi,
I use Debian jessie with Dovecot 2.2.13-11.
While writing a script for Horde to change the passwords in my passwd
file I noticed doveadm pw -t fails for SHA512-CRYPT:
# doveadm pw -s SHA1 -p test
{SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M=
# doveadm pw -t {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= -p test
reik red writes:
(I'm re-submittting after setting up a subscription, so I don't have to wait
for the moderator)
,
What happened next surprised me greatly: if I specify "-s ssha", the
resulting hashed password changes each time I invoke "doveadm pw", but
if I do
Hi there,
if you are getting different results on each invocation of the hash function,
you might have selected a salted hashing function which generates a random
salt. When you provide the same salt, you should get the same result for the
same input, but when you omit the salt, it generates a
I am absolutely dumbfounded by "doveadm pw". My understanding is that
the command should be used to create a hashed password that should in
turn be placed into /etc/dovecot/passwd
Here comes the "dumbfounded" part. I was creating a new virtual user,
running doveadm pw to
On 12.8.2014 12:23, Jon Hulatt wrote:
Hi,
Not sure if this is a PBKAC or not:-
root@ds3:/usr/share/postfixadmin# doveadm pw -s SHA512-CRYPT -p password
{SHA512-CRYPT}$6$aUgGXP0UshkMj7hY$9JV4yMRsjIe/98CzmglYrMjf.9NJ.FXzxcLE9B0v3doCRUWo2wRncc6hg6VCs0DCUHQbeC/bRDZdGCge/nB/h/
root@ds3:/usr/share
At Tuesday, 12-08-2014 on 12:23 Jon Hulatt wrote:
> Hi,
>
> Not sure if this is a PBKAC or not:-
>
> root@ds3:/usr/share/postfixadmin# doveadm pw -s SHA512-CRYPT -p password
> {SHA512-CRYPT}$6$aUgGXP0UshkMj7hY$9JV4yMRsjIe/98CzmglYrMjf.9NJ.FXzxcLE9B0v3doCRUWo2wRncc6hg6VCs0DCUHQ
At Tue, 12 Aug 2014 11:23:06 +0100,
Jon Hulatt wrote:
> root@ds3:/usr/share/postfixadmin# doveadm pw -s SHA512-CRYPT -p password
> {SHA512-CRYPT}$6$aUgGXP0UshkMj7hY$9JV4yMRsjIe/98CzmglYrMjf.9NJ.FXzxcLE9B0v3doCRUWo2wRncc6hg6VCs0DCUHQbeC/bRDZdGCge/nB/h/
>
> root@ds3:/usr/share/postfixad
Hi,
Not sure if this is a PBKAC or not:-
root@ds3:/usr/share/postfixadmin# doveadm pw -s SHA512-CRYPT -p password
{SHA512-CRYPT}$6$aUgGXP0UshkMj7hY$9JV4yMRsjIe/98CzmglYrMjf.9NJ.FXzxcLE9B0v3doCRUWo2wRncc6hg6VCs0DCUHQbeC/bRDZdGCge/nB/h/
root@ds3:/usr/share/postfixadmin# doveadm pw -t
{SHA512
On 04/01/2014 08:56 AM, Dwain Blazej wrote:
I'm writing some code for Posty, a Postfix and Dovecot Administration App.
One way to support all of dovecot's password hashes is to have "dovecot pw"
do the work, however I don't want to run the web facing Posty as root or
the same user as Dovecot.
Is
Harald wrote:
>
>
> Am 29.03.2014 22:51, schrieb Dwain Blazej:
> > dovecot --version => 2.1.7
> >
> > When I as a normal user the command:
> >
> > doveadm pw -s sha512-crypt -p example_password
> >
> > the command exit with return code 89 and the m
On 03/29/2014 06:06 PM, Reindl Harald wrote:
Am 29.03.2014 22:51, schrieb Dwain Blazej:
dovecot --version => 2.1.7
When I as a normal user the command:
doveadm pw -s sha512-crypt -p example_password
the command exit with return code 89 and the message
doveconf: Fatal: open(/etc/dove
Am 29.03.2014 22:51, schrieb Dwain Blazej:
> dovecot --version => 2.1.7
>
> When I as a normal user the command:
>
> doveadm pw -s sha512-crypt -p example_password
>
> the command exit with return code 89 and the message
>
> doveconf: Fatal: open(/etc/dovecot/do
dovecot --version => 2.1.7
When I as a normal user the command:
doveadm pw -s sha512-crypt -p example_password
the command exit with return code 89 and the message
doveconf: Fatal: open(/etc/dovecot/dovecot.conf) failed: Permission denied
If I make Dovecot's configuration files world
the verify a password hash using `doveadm
pw` via the `-V` option.
Committed, with a few changes:
http://hg.dovecot.org/dovecot-2.1/rev/fffa4d53e901
+ while ((ch = getopt(argc, argv, "lp:r:s:u:V::")) != -1) {
"::" isn't standard, so I added a separate -t parameter to give the hash.
`doveadm
pw` via the `-V` option.
$ doveadm pw -s SSHA.hex
Enter new password:
Retype new password:
{SSHA.HEX}58b910d947c60b35be3e12b0d9897c1f87dfa450e6d5a75c
$ doveadm pw -s SSHA.hex
-V{SSHA.HEX}58b910d947c60b35be3e12b0d9897c1f87dfa450e6d5a75c
Enter new password:
Retype new
40 matches
Mail list logo
