Package: easy-rsa
Version: 2.2.2-2
Severity: normal
Dear Maintainer,
when using easy-rsa to create a CA (build-ca) the command fails with:
req: Error on line 198 of config file "/etc/openvpn/easy-rsa/openssl.cnf"
Generating a 2048 bit RSA private key
+++
I can also confirm that 7.0.28-4+deb7u17 works on our server again.
I can confirm that Mieks workaround works. I hit me when upgrading
grafana to the latest version in stretch. So this is not only on new
installs, but the latest update broke grafana in stretch!
Package: radicale
Version: 1.0.1-2
Severity: critical
Upstream of radicale has released a version 1.1 of radicale fixing
several security issues.
See http://radicale.org/news/
"Many improvements in this release are related to security, you should
upgrade Radicale as soon as possible:"
I updated to latest backports packages and it still works. I get the
expected TempError for amazon.com and aol.com.
So it is fixed for me. Guess you can close the bug.
Thanks for your work!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Scott Kitterman wrote:
d40c236a7b592c5a51a055c3d1456650 python-dns_2.3.3-2~0etchtest_all.deb
This one gives me:
Traceback (most recent call last):
File /usr/share/python-support/python-spf/spf.py, line 1621, in ?
print q.dns_spf(sys.argv[1])
File
I think what would be most useful now would be if you could capture port FT
both UDP and TCP with Wireshark, tcpdump, etc. when doing the above tests.
I need to see what's in the packet that's causing the crash.
I attached a file containing the raw dump for all 3 tests.
I used tcpdump with
I also get this bug in the logs. Noticed it when amazon mail stopped
coming in. So here are the log entries:
Oct 31 07:01:47 felixknecht policyd-spf[27208]: None; identity=helo;
client-ip=84.254.213.97; helo=host97.fnet2.ae21vek.ru;
[EMAIL PROTECTED]; receiver=
Oct 31 07:21:40
Today I tried to add amazon.com to my SPF domain whitelist, which
resulted in the error for each and every mail. This probably happens
because it tries to resolve the whitelist each time. So there definitely
seems to be something wrong with the results of a DNS resolve of the
amazon.com
9 matches
Mail list logo
