Hi sorry nevermind, fixed.
It was a lighttpd setting.
Thanks and have a nice week-end,
RuggedInbox team
On 2014-08-23 00:32, m...@ruggedinbox.com wrote:
Hi sorry for cross sending, we already sent this email to roundcube's
mailing list but got no answer.
We recently improved our https configu
Hi sorry for cross sending, we already sent this email to roundcube's
mailing list but got no answer.
We recently improved our https configuration on lighttpd:
https://www.ssllabs.com/ssltest/analyze.html?d=ruggedinbox.com
but something seems to have broken roundcube .. can't properly attach
f
Hi,
Another question for TLS/TCP and DTLS/SCTP...
After initially successful authentication, is it possible to disable
re-authentication such that HelloRequest/ClientHello messages are ignored?
I've looked through the documentation, and tried to track down examples, but
have not found anything
#include
#include
#include
#define ENC 1
#define DEC 0
int isDecryption(char inputFile[]);
void translate(unsigned char *dest, char *src);
int allHex(char input[]);
int main(int argc, char *argv[])
{
if (argc != 5)
{
printf("Incorrect number
2014-08-22 15:28 GMT+02:00 Brian Hassink :
> I do mean DTLS/SCTP (RFC6083).
>
> In our application, we have Diameter (RFC6733) traffic which can involve
> large messages.
OK, got it. In my case is SCTP over DTLS (WebRTC DataChannel), but the
underlying problem is the same (both UDP and SCTP are me
Hello,
I am working on a custom client/server C applications and I would like to
support:
SSLv3, and TLSv1, TLSv1.1 or TLS v1.2 on server side (because I need to support
older clients too)
and just TLSv1.1 or TLS v1.2 on client side.
Actually I am just using:
SSL_CTX_new(SSLv3_server_method())
SSL_set_bio() accepts both a read and write BIO.
We have seen example programs that allocate one BIO and use it for both read
and write, and others that allocate two BIOs.
Under what circumstances would one approach be choosen over the other, or, what
behavior results from choosing one over the
I do mean DTLS/SCTP (HYPERLINK "http://tools.ietf.org/html/rfc6083"RFC6083).
In our application, we have Diameter (HYPERLINK
"http://tools.ietf.org/html/rfc6733"RFC6733) traffic which can involve large
messages.
-Brian
-Original Message-
From: Iñaki Baz Castillo [mailto:i...@a
2014-08-22 14:43 GMT+02:00 Brian Hassink :
> We see the same problem with DTLS over SCTP.
>
> In our application, there are messages as large as 60K, so we are interested
> in knowing if there is a way to send them over DTLS.
I assume you mean "SCTP over DTLS".
That's a good point. However I do
We see the same problem with DTLS over SCTP.
In our application, there are messages as large as 60K, so we are interested in
knowing if there is a way to send them over DTLS.
-Brian
-Original Message-
From: Iñaki Baz Castillo [mailto:i...@aliax.net]
Sent: Thursday, August 21, 2014 1:3
On Wed, Aug 20, 2014, Lewis Lo wrote:
>
> I have a question on whether the following OpenSSL vulnerabilities
> described in CVE-2014-5139 affects the OpenSSL 1.0.1e-fips The affected
> platforms does not indicate if it affect the fips version. Thanks.
>
OpenSSL 1.0.1e-fips is not a separa
On Fri, Aug 22, 2014, Dalton Porter wrote:
> I have some signed files that I would like to modify and then re-sign. I need
> to recover the signed_file to the unsigned state. The files were signed like
> this:
>
> openssl smime -sign -in myfile.txt -out signed_file -signer mycert.crt -inkey
>
I have some signed files that I would like to modify and then re-sign. I need
to recover the signed_file to the unsigned state. The files were signed like
this:
openssl smime -sign -in myfile.txt -out signed_file -signer mycert.crt -inkey
mykey.key -certfile my-chain.crt -outform der -nodetach
13 matches
Mail list logo
