similar to: Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas

Displaying 20 results from an estimated 800 matches similar to: "Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas"

2019 Mar 07
2
Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas
> You could configure default scheme as CRYPT. It covers these all. Otherwise > you need to make sure passwords have {SCHEME} prefix when it differs from > default or oddities occur. --- Thank you for the tip with CRYPT. Is there any explanation for this behaviour though? Why are BCRYPT hashes accepted when default_pass_scheme is set to SHA512-CRYPT and not vice versa? Is this
2019 Mar 06
0
Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 6 March 2019 18:16 Kristijan Savic - ratiokontakt GmbH via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote:
2019 Apr 16
2
Sieve operation "send copy" not working since upgrade from dovecot 2.2.31-1 to 2.3.5.1-1
I hope that someone can help me here. Software: CentOS 7.6.1810, dovecot-2.3.5.1, dovecot-pigeonhole-2.3.5.1, exim 4.91-1 Example filter: # rule:[test] if header :contains "subject" "meow" { redirect :copy "ks at ratiokontakt.de"; } Mail log: Apr 16 11:29:02 frontend-17 dovecot: lmtp(testi at mrhoang.de)<25201><QPgZHF6gtVxxYgAARS1pjg>:
2019 Mar 07
0
Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas
On 7.3.2019 14.00, Kristijan Savic - ratiokontakt GmbH wrote: >> You could configure default scheme as CRYPT. It covers these all. Otherwise >> you need to make sure passwords have {SCHEME} prefix when it differs from >> default or oddities occur. --- > Thank you for the tip with CRYPT. > > Is there any explanation for this behaviour though? > > Why are BCRYPT
2019 Aug 21
4
sometimes no shared cipher after upgrade from 2.2 to 2.3
We recently upgraded from dovecot 2.2 to 2.3.7.1-1 Not many, but some users are experiencing difficulties. The dovecot directors log: Aug 21 14:28:49 director01 dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=redacted, lip=10.0.0.120, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher,
2019 Aug 21
2
sometimes no shared cipher after upgrade from 2.2 to 2.3
> SSL3 is no longer included in the cipher sets. Try this: > > ssl_min_protocol = SSLv3 Thanks. Unfortunately, no dice - same error. Any other tips? I was under the impression "no shared cipher" was rather the problem? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: This
2019 Apr 16
0
Sieve operation "send copy" not working since upgrade from dovecot 2.2.31-1 to 2.3.5.1-1
On 16.4.2019 13.34, Kristijan Savic - ratiokontakt GmbH via dovecot wrote: > I hope that someone can help me here. > > Software: CentOS 7.6.1810, dovecot-2.3.5.1, dovecot-pigeonhole-2.3.5.1, exim > 4.91-1 > > Example filter: > > # rule:[test] > if header :contains "subject" "meow" > { > redirect :copy "ks at ratiokontakt.de";
2019 Aug 21
0
sometimes no shared cipher after upgrade from 2.2 to 2.3
On 21/8/2019 16:12, Kristijan Savic - ratiokontakt GmbH via dovecot wrote: > We recently upgraded from dovecot 2.2 to 2.3.7.1-1 > > Not many, but some users are experiencing difficulties. The dovecot directors > log: > > Aug 21 14:28:49 director01 dovecot: pop3-login: Disconnected (no auth attempts > in 0 secs): user=<>, rip=redacted, lip=10.0.0.120, TLS handshaking:
2019 Aug 21
0
sometimes no shared cipher after upgrade from 2.2 to 2.3
On 21/8/2019 18:51, Kristijan Savic - ratiokontakt GmbH via dovecot wrote: > >> SSL3 is no longer included in the cipher sets. Try this: >> >> ssl_min_protocol = SSLv3 > > Thanks. Unfortunately, no dice - same error. > > Any other tips? I was under the impression "no shared cipher" was rather the > problem? Yes this is exactly the problem but the
2008 Apr 07
2
"\0" gives no warning "unknown escape sequence" (PR#11107)
Full_Name: Volkmar Klatt Version: 2.6.2 OS: linux Submission from: (NULL) (84.147.0.178) Hello, the documentation article ?Quotes from package:base could be improved by discussing the meaning of "\0" escape sequence. In R (currently used: R-2.6.2), a "\0" in a string will silently terminate that string, just as it would in C code. There is no warning about an unknown escape
2012 Apr 22
6
git down?
Hi, trying to compile but have problems: + /root/xen-unstable.hg-rev/tools/../scripts/git-checkout.sh git:// xenbits.xensource.com/qemu-xen-unstable.git82db8de16530f016809264d3179823999d702849 qemu-xen-traditional-dir Cloning into qemu-xen-traditional-dir-remote.tmp... fatal: read error: Connection reset by peer git down? Best Regards, Kristijan Lecnik
2013 Jun 26
4
fresh install of xen, problems booting qemu-dm
Hi, i have just install debian wheezy and xen-hypervisor-4.1-amd64 helped with http://wiki.debian.org/Xen http://wiki.xenproject.org/wiki/Xen_Beginners_Guide#Installing_Debian_Squeeze created test.cfg http://pastebin.com/D5Wsx6eB xl create test.conf Parsing config file test.conf xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->0000000000174170 TOTAL:
2011 Apr 15
2
Good by asterisk 1.4? Please not.
"Security only fixes: 2011-04-21" So in six days, no more bugfix patches will committed into 1.4-branch :( Is a prolongation possible? Because 1.4 is so reliable now. It would be a great loss. And no, 1.8 is not (yet) a replacement. Kristijan
2009 Nov 02
2
Asterisk as Outbound Proxy ?
Hello, short question: is there a possibility to use asterisk as an outbound proxy? iam open for any suggestions, use asterisk trunk, dirty patches, ugly workarounds, everything. What is want to build is: SIP Phone -> via TLS/SRTP -> Asterisk as outbound proxy -> via UDP/RTP -> VoIP-Provider So Asterisk should just forward any incoming SIP messages (INVITE, REGISTER) to the
2009 Aug 27
3
Digium Echo cancellation.
hi all, any one know, about echo cancellation with digium card, is it actually needed or it okay if we dont purchase because it increase price which half of new card, regards Dhaval -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090827/8d6c680a/attachment.htm
2017 Feb 17
3
Problem with Let's Encrypt Certificate
Hey Robert, thanks for your reply. Am 17.02.2017 um 19:28 schrieb Robert L Mathews: > Looking at your dovecot -n, you're using two different files here: > > ssl_cert = </etc/ssl/sebode-online.de/chain.pem > ssl_key = </etc/ssl/sebode-online.de/key.pem > > Are you sure these two files match, and contain the right things in the > right order? > Yes,
2012 Jan 11
5
Which SpanDSP version to play with Asterisk 10 and T.38/T.30 gatewaying ?
Hi, Maybe I missed it while checking it, but which spandsp version is recommended to play with Asterisk 10 and T.38/T.30 gatewaying ? I can see both spandsp-0.0.6pre17.tgz and spandsp-0.0.6pre18.tgz here (http://www.soft-switch.org/downloads/spandsp/) but I couldn't find a changelog documenting differences between them. So I prefer to double check ask for recommendations. Regards
2012 Apr 26
1
Call recovery feature
Hello, what about: "This feature means you can restart Asterisk after a failure (or asterisk restart itself with safe_asterisk), and keep existing calls up with only a few seconds of audio dropped." That would be a feature! there is a "other" pbx that has this feature... Anyone else would like to see that feature? just want to start some brainstorming, Kristijan
2011 May 23
3
Latest DAHDI/libpri/Asterisk 1.8 & 1x BRI port HFC based ISDN card?
Hi, I would appreciate some advice on the following: how does one use a single BRI port HFC chipset based ISDN cards with the latest DAHDI, libpri and Asterisk 1.8? For Asterisk 1.4 I would first install mISDN & mISDNuser and then build Asterisk 1.4. Now I noticed that Digium's HFC chipset based B410P is supported by the latest DAHDI & libpri but reading the source of the
2010 Jan 24
2
ReceiveFAX and SendFAX questions
Morning, Have some questions regarding receiving and sending faxes... 1:st example: exten => 101,1,Answer() exten => 101,2,Wait(3) exten => 101,3,ReceiveFAX(/var/spool/asterisk/tmp/fax.tiff) exten => 101,4,System(tiff2pdf -p A4 /var/spool/asterisk/tmp/fax.tiff > /var/spool/asterisk/tmp/fax.pdf) exten => 101,5,System(mutt -s 'New FAX for you sir' -a