Hi,
No, unfortunately not. I just suffered it again aswell over the
Christmas break. Let me know if you find any fix.
Regards,
Mark
On Sun, Dec 26, 2010 at 12:50:26PM +0100, Moritz Muehlenhoff wrote:
On Wed, Oct 06, 2010 at 12:05:18PM +0100, Mark Adams wrote:
As this is when the clock
, 2011 at 04:56:00PM +, Mark Adams wrote:
Hi,
No, unfortunately not. I just suffered it again aswell over the
Christmas break. Let me know if you find any fix.
Regards,
Mark
On Sun, Dec 26, 2010 at 12:50:26PM +0100, Moritz Muehlenhoff wrote:
On Wed, Oct 06, 2010 at 12:05:18PM +0100
Please close this bug report. The issue was found to be with a script
that had overrun the server. I have noted that the bug regarding time
Hi Ben, Thanks for your response. See my responses inline.
On Wed, Oct 06, 2010 at 03:35:23AM +0100, Ben Hutchings wrote:
On Tue, 2010-10-05 at 09:31 +0100, Mark Adams wrote:
Package: xen-linux-system-2.6.32-5-xen-amd64
Version: 2.6.32-21
Severity: important
Hi, Did you receive
On Wed, Oct 06, 2010 at 11:47:05AM +0100, Ian Campbell wrote:
On Wed, 2010-10-06 at 09:33 +0100, Mark Adams wrote:
Hi Ben, Thanks for your response. See my responses inline.
On Wed, Oct 06, 2010 at 03:35:23AM +0100, Ben Hutchings wrote:
On Tue, 2010-10-05 at 09:31 +0100, Mark Adams
Package: xen-linux-system-2.6.32-5-xen-amd64
Version: 2.6.32-21
Severity: important
Hi, Did you receive this bug report? I hadn't received a bug ID even
though receiving the copy of the original report. Likely because the
address it was sent from originally was invalid.
-
Hi
Hi Ian,
Thanks for your response. The kernel is linux-image-2.6.26-2-xen-amd64,
installed via the xen-linux-system-2.6.26-2-xen-amd4 package. The issue
occurred inside of a PV domU.
Best Regards,
Mark
On Wed, Aug 11, 2010 at 04:13:11PM +0100, Ian Campbell wrote:
Thanks for your report.
Hi, Sorry, It's 2.6.26-19lenny2.
Regards,
Mark
On Wed, Aug 11, 2010 at 04:25:28PM +0100, Ian Campbell wrote:
On Wed, 2010-08-11 at 16:21 +0100, Mark Adams wrote:
Hi Ian,
Thanks for your response. The kernel is linux-image-2.6.26-2-xen-amd64,
installed via the xen-linux-system-2.6.26-2
Excellent, thank you. Could you also cut'n'paste your current exim
(MAIN_TLS_*) configuration?
Which exim version are you using? Still 4.63-17? It would help if you
could post a short snippet of an updated error message, with the new
filenames and so on.
When do the problem actually
On Mon, Mar 03, 2008 at 06:41:05PM +0100, Marc Haber wrote:
On Mon, Mar 03, 2008 at 01:44:35PM +, Mark Adams wrote:
All, This is now working as desired. I am using exactly the same
configuration as I detailed in my first post (it was commented, I
uncommented it.)
MAIN_TLS_ENABLE
On Wed, Feb 27, 2008 at 11:07:02PM +0200, Nikos Mavrogiannopoulos wrote:
Mark Adams wrote:
On Jan 3, 2008 2:36 AM, Marc Haber [EMAIL PROTECTED] wrote:
I'm using gnutls 2.0.4 at present (this is the current debian testing
version). Is it possibly a known issue with this version? I can
On Fri, Jan 04, 2008 at 12:22:51PM +0100, Simon Josefsson wrote:
Hi Mark! I'm trying to help debug this problem. Could you please post
the output from running:
certtool -i /etc/exim4/certificates/newserver_co_uk.crt
Could you also check that
certtool -k
On Thu, Feb 28, 2008 at 12:51:46PM +, Mark Adams wrote:
On Wed, Feb 27, 2008 at 11:07:02PM +0200, Nikos Mavrogiannopoulos wrote:
Mark Adams wrote:
On Jan 3, 2008 2:36 AM, Marc Haber [EMAIL PROTECTED] wrote:
I'm using gnutls 2.0.4 at present (this is the current debian testing
]
(cert/key set up: cert=/etc/exim4/certificates/newserver_co_uk.crt
key=/etc/exim4/certificates/newserver_co_uk.pem) : Base64 decoding error.
/Simon
Mark Adams [EMAIL PROTECTED] writes:
Hi Simon,
Apologies for the very late reply.
certool works fine on the .crt file
On Jan 3, 2008 2:36 AM, Marc Haber [EMAIL PROTECTED] wrote:
Hi,
Simon writes:
Appears to be an unreprodicible problem with a specific
certificate/key which the user cannot reveal. Another
certificate/key
from the same CA works fine. Theory: could it be CRLF problems?
Other
Hi Simon,
Apologies for the very late reply.
certool works fine on the .crt file, but not on the .key - I get the
Base64 decoding error.
certtool: Import error: Base64 decoding error.
The file appears to be in the correct format.
Regards,
Mark
On Fri, Jan 04, 2008 at 12:22:51PM +0100, Simon
No, permissions are correct. This seems to be a problem with wildcard
SSL certs.
Mark.
On 24 Dec 2007, at 20:20, Florian Weimer [EMAIL PROTECTED] wrote:
* Mark Adams:
I this might sound daft, but are you really running these tests with
the cert/key pair exim seems to have trouble
Hello,
I have tried this again with the reissued certificate. Unfortunately the
same error still occurs.
It appears this must be something to do with the fact that this is a
wildcard certificate (*.domain.co.uk) as the exact configuration works
fine on other servers with single host
Hello,
I have checked this, they are ASCII only with unix line endings.
Could it be something to do with the * ? (wildcard certificate)
Mark
On Tue, Dec 11, 2007 at 12:41:13PM +0100, Marc Haber wrote:
On Tue, Dec 11, 2007 at 11:16:43AM +, Mark Adams wrote:
I have tried this again
Hi Marc,
You can obtain a free 90 day trial certificate from this company, see
http://www.instantssl.com/ssl-certificate-products/free-ssl-certificate.html
This is the company that I purchased my cert from, they are comodo
resellers
I would be very greatful if you would be interested in
On Sat, Jun 30, 2007 at 08:43:19AM +0200, Marc Haber wrote:
I still do not see the exact command lines that were used to obtain
this output on both sides.
For server;
gnutls-serv --debug 5 --x509keyfile myhost_net.key --x509certfile myhost_net.crt
And for Client;
gnutls-cli -p 5556
+0100, Mark Adams wrote:
Hi There,
When using gnutls-cli to connect to the client whilst running the
gnutls-server command I get the following response
- Peer's certificate issuer is unknown
- Peer's certificate is NOT trusted
- Version: TLS 1.0
- Key Exchange: DHE RSA
- Cipher: AES 256
On Thu, Jun 28, 2007 at 01:15:33PM +0200, Marc Haber wrote:
On Wed, Jun 20, 2007 at 04:47:27PM +0100, Mark Adams wrote:
When using gnutls-cli to connect to the client whilst running the
gnutls-server command I get the following response
- Peer's certificate issuer is unknown
- Peer's
: DEFLATE
- Handshake was completed
- Simple Client Mode:
Is it failing because of the first 2 responses? this doesn't seem to
relate to any base64 decoding error?
Thanks,
Mark
On Thu, Jun 07, 2007 at 09:39:52PM +0200, Marc Haber wrote:
On Wed, May 30, 2007 at 08:37:04PM +0100, Mark Adams wrote
...
On Sun, May 27, 2007 at 10:43:45AM +0200, Andreas Metzler wrote:
On 2007-05-26 Mark Adams [EMAIL PROTECTED] wrote:
[...]
Does
openssl s_server -debug -key exim.key -cert exim.crt
work?
And how about
gnutls-serv --debug 5 --x509keyfile exim.key --x509certfile exim.crt
Both
if more information is required.
--
Mark Adams
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
26 matches
Mail list logo
