another.
> actually these 2 servers is mirrow relationship. 2. I checked the pem file
> (as attached), also is same on two servers3. I checked the error reason, but
> cannot find any description about it in the website.I am almost crazy for
> this issue, would you help to check what'
another.
> actually these 2 servers is mirrow relationship. 2. I checked the pem file
> (as attached), also is same on two servers3. I checked the error reason, but
> cannot find any description about it in the website.I am almost crazy for
> this issue, would you help to check what'
cked the pem file (as
attached), also is same on two servers3. I checked the error reason, but cannot
find any description about it in the website.I am almost crazy for this issue,
would you help to check what's the reason of this error for me? thanks a lot!
my OS: Linux version 3.7.10-1.1-desktop (geeko@
time has passed... nobody looked at this, sorry.
fixed earlier by disabling those protocol versions :)
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3580
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
Cool !
Many thanks Steve.
-Message d'origine-
De : Stephen Henson via RT [mailto:r...@openssl.org]
Envoyé : mardi 10 mai 2016 17:00
À : michel.sa...@free.fr
Cc : openssl-dev@openssl.org
Objet : [openssl.org #4173] help to check whether handshake negociates SRP or
PSK ciphersuite
This is now supported in the master branch with the SSL_CIPHER_get_auth_nid()
function.
The equivalent cannot be added to 1.0.2 as we do not add new features to stable
branches.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see:
This got committed in 6c335b0.
Closing.
Matt
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4306
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Hi,
Thanks for reply.
Pkey is not NULL, but its memory has been freed if reference decreases to 0
when the other thread don't add it to 1. Please make sure whether this will
happened.
Today I will use debug version to find this problem.
Please help check whether the other people feedback
On 31/03/16 14:00, Hejian via RT wrote:
> Hello, when upgrade openssl to 1.0.2g, If multi thread call the corba
> interface, it will cause core accidently. Please help analyze why the
> core is generated.
>
> There are two kinds of core stack list below.
>
>
>
Hello,
when upgrade openssl to 1.0.2g, If multi thread call the corba interface, it
will cause core accidently.
Please help analyze why the core is generated.
There are two kinds of core stack list below.
#0 0x7f97729ad324 in RSA_verify ()
from /opt/oss/server/3rdTools/lib/libcrypto.so
Hi,
enc:
- typo in -base64 option
- missing help opt text
ocsp/req/rsautl/s_client:
- missing help opt text
Created the following pull request with the changes.
https://github.com/openssl/openssl/pull/681
Thanks,
Mohan
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4306
commit a173a7e thanks.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4295
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Hi,
- In dgst, pkeyutl cmds, some help text was missing for some options and
in man pages.
- fixed a minor typo in openssl.pod, that fixes make install.
- digest-commands was showing ‘sha’, which is not a supported digest
anymore.
I have created the below pull request
fixed in commit 6755ff1
The github PR was done before the RT moderator :)
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4293
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
Hi,
In commands help, option valtype, 0 is to be treated same as '-', but in
apps/opt.c: valtype2param(),
case 0 was missing. Because of this, *openssl asn1parse -help* was printing
options without args wrongly.
Few cleanups are also done in asn1parse/ca/ciphers.
I have created the following
fixed in master with 0ae9e2926654657862e104a111a4e3028b0be8f6 thanks!
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
-
http://rt.openssl.org/Ticket/Display.html?id=4291
Please log in as guest with password guest if
Hi,
[-help] option in most of the commands documentation was missing and in
ciphers and rehash commands it was wrongly specified as [-h], which is not
considered as a valid option.
I have create the below pull request with the changes. Please have a look.
https://github.com/openssl/openssl/pull
kinda fixed in 1.0.2 and really fixed in 1.1
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
old release. hope you got the issue fixed by now :)
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Hi,
I believe it would be nice to have an efficient way to check if handshake
results in a SRP or PSK ciphersuite.
As I do not like to trick with OpenSSL internal structures, I suggest to add
the following to ssl_ciph.c :
int SSL_CIPHER_is_PSK(const SSL_CIPHER *c)
{
if (c != NULL &&
I am trying to compile openssl 1.0.2 SNAP 20150801
and now I get
if [ -n libcrypto.so.1.0.0 libssl.so.1.0.0 ]; then (cd ..; make
libcrypto.so.1.0.0); fi
[ -z ] || gcc -fPIC -DOPENSSL_PIC -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS
-pthread -D_THREAD_SAFE -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
Hi,
Absolutely right! Except that given context OP is more likely to have to
use --cross-compile-prefix=mips-linux-, i.e. with additional dash.
Yes, right, sorry about that..
Stefan, if it appears as nitpicking, I apologize.
No need to apologize. On the contrary, if one doesn't know the
Hi,
For other programs, after setting the environment variables according
to this guide, it is enough to run:
./configure --host=mips-linux
make
I really need your help, because it doesn't wotk with OPENSSL.
That's because OpenSSL is not using autoconf but a Configure script
variables according to
this guide, it is enough to run:
./configure --host=mips-linux
make
I really need your help, because it doesn't wotk with OPENSSL.
I tried to investigate this in a large number of different ways digging in
the Configure, config, Makefile and so on, but with no luck
Thank you
Hi,
For other programs, after setting the environment variables
according to this guide, it is enough to run:
./configure --host=mips-linux make
I really need your help, because it doesn't wotk with OPENSSL.
That's because OpenSSL is not using
We sort-of sidestepped this; the help now says
-* Any supported digest
which is reasonable for a summary. (All commands that take a message-digest or
encryption-type parameter now do this same thing.)
___
openssl-dev mailing list
To unsubscribe: https
When I try to verify a SHA-2 certificate that chains up to a SHA-1 root I get
error 20 at depth 0. If I leave the SHA-1 root off of the CAfile I get past
depth 0. Verizon support was able to replicate this issue as well.
We are trying to use OpenSSL verify to check our intermediate issuing CA
On Fri, Feb 20, 2015, W Smith wrote:
Thanks, Rich.
Does anyone know how to walk through a BIO stack that includes a BIO pair
and get to the ultimate source/sink BIO? If I can get that, I'll be in good
shape. Anybody?
Not sure I follow you. A BIO pair is the ultimate source/sink BIO.
I can deal with the HTTP side and the plethora of application-specific and
threading issues, but I'm lost on the BIO part. I'll take any pointers or
suggestions you can offer.
Only to look at SSL_set_bio.
Good luck.
--
Principal Security Engineer, Akamai Technologies
IM: rs...@jabber.me
Thanks, Rich.
Does anyone know how to walk through a BIO stack that includes a BIO pair and
get to the ultimate source/sink BIO? If I can get that, I'll be in good shape. Anybody?
On Feb 20, 2015, at 08:18 AM, Salz, Rich rs...@akamai.com wrote:
I can deal with the HTTP side and the plethora
On Fri, Feb 20, 2015, W Smith wrote:
Rich,
Yeah, I have industrial strength Tylenol standing by. I'm expecting this to
be painful, but not insurmountable for the handshake. If I'm unable to even
get at the ultimate source/sink, I can't get anywhere.
I can deal with the HTTP side and
I've been tasked with wrapping OpenSSL encrypted traffic in another protocol
(HTTP).
That's going to be a bit tricky, and require some pretty detailed knowledge of
the protocol. For example, the initial setup -- the hello messages -- will
require a couple of POST and reply messages. Even
Rich,
Yeah, I have industrial strength Tylenol standing by. I'm expecting this to be
painful, but not insurmountable for the handshake. If I'm unable to even get at
the ultimate source/sink, I can't get anywhere.
I can deal with the HTTP side and the plethora of application-specific and
Hi,
I've been tasked with wrapping OpenSSL encrypted traffic in another protocol
(HTTP).
I'm able to intrude on the data stream with the BIO callback feature
(BIO_set_callback), and have also created a BIO filter to play with. My problem
is that the BIO I have access to seems to be the BIO
From: Matthieu Crapet mcra...@gmail.com
Applies when using no-ssl2 or no-ssl3 switches to Configure.
'-ssl2' and '-ssl3' switches are correctly handled in s_client, s_server and
s_time, but help message is still mentionning it.
Signed-off-by: Matthieu Crapet mcra...@gmail.com
---
apps
I have got the reason.
It's the problem of unzip tools.
After I unzipped the files on windows, the file has some error.
But when I unzip on SUSE, it's no problem.
Thanks.
ZTE Information Security Notice: The information contained in
I have got the reason.
It's the problem of unzip tools.
After I unzipped the files on windows, the file has some error.
But when I unzip on SUSE, it's no problem.
Thanks.
ZTE Information Security Notice: The information contained in
Marcus and Andy,
thank you very much for your help so far.
I have a few more questions, see below.
Quoting Marcus Meissner meiss...@suse.de:
On Wed, Sep 24, 2014 at 01:13:51PM +0200, Michael Menge wrote:
Quoting Matt Caswell m...@openssl.org:
On 24 September 2014 10:03, Michael Menge
in that case it crashes here:
if (s-msg_callback)
s-msg_callback(0, s-version, SSL3_RT_HANDSHAKE,
s-init_buf-data, (size_t)s-init_num + 4, s, s-msg_callback_arg);
So is the pointer to the callback wrong, or is the SIGSEGV in the
called function?
What happens if
Quoting Andy Polyakov ap...@openssl.org:
in that case it crashes here:
if (s-msg_callback)
s-msg_callback(0, s-version, SSL3_RT_HANDSHAKE,
s-init_buf-data, (size_t)s-init_num + 4, s, s-msg_callback_arg);
So is the pointer to the callback wrong, or is the SIGSEGV in
On Thu, 25 Sep 2014 11:24:36 +0200, Michael Menge said:
Quoting Andy Polyakov ap...@openssl.org:
in that case it crashes here:
if (s-msg_callback)
s-msg_callback(0, s-version, SSL3_RT_HANDSHAKE,
s-init_buf-data, (size_t)s-init_num + 4, s,
Quoting Martin Simmons mar...@lispworks.com:
On Thu, 25 Sep 2014 11:24:36 +0200, Michael Menge said:
Quoting Andy Polyakov ap...@openssl.org:
in that case it crashes here:
if (s-msg_callback)
s-msg_callback(0, s-version, SSL3_RT_HANDSHAKE,
s-init_buf-data,
in that case it crashes here:
if (s-msg_callback)
s-msg_callback(0, s-version, SSL3_RT_HANDSHAKE,
s-init_buf-data, (size_t)s-init_num + 4, s, s-msg_callback_arg);
So is the pointer to the callback wrong, or is the SIGSEGV in the
called function?
What
corrupted the SSL structure.
Running under valgrind or similar might help.
Ciao, Marcus
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Result as follow:
-bash-3.00# wc -l md2test.c
0 md2test.c
-bash-3.00#
-bash-3.00# cat md2test.c
dummytest.c-bash-3.00#
-bash-3.00#
ZTE Information Security Notice: The information contained in this mail (and
any attachment
openssl-1.0.1i on Solaris 10, there are
some error, please help to check what is the reason. Thanks.
Somehow your md2test.c file is corrupted.
Line 1 should be #include stdio.h and the file has 48 lines.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
Result as follow:
-bash-3.00# wc -l md2test.c
0 md2test.c
-bash-3.00#
-bash-3.00# cat md2test.c
dummytest.c-bash-3.00#
-bash-3.00#
ZTE Information Security Notice: The information contained in this mail (and
any attachment
Somehow the file that you have is corrupted.
It is not corrupted in the tar file.
It is a local error.
I do not know what the error is but mdtest.c on your disk is WRONG.
Somehow the file that you have is corrupted.
It is not corrupted in the tar file.
It is a local error.
I do not know what the error is but mdtest.c on your disk is WRONG.
__
OpenSSL Project
this. Can you help me to debug this further?
Below is the BT of one of the core dumps
Regards
Michael Menge
#0 0x0080e130 in ?? ()
#1 0x7fe5a839334f in ssl3_get_message (s=0x80e430, st1=8347825,
stn=-1470427072, mt=optimized out, max=102400, ok=0x7fffcc974d08)
at s3_both.c
asked on the cyrus mailinglists as well, but the developer have no idea
what could cause this. Can you help me to debug this further?
Below is the BT of one of the core dumps
Regards
Michael Menge
What OS/platform is this, and what version of OpenSSL?
Matt
what could cause this. Can you help me to debug this further?
Below is the BT of one of the core dumps
Regards
Michael Menge
What OS/platform is this, and what version of OpenSSL?
Also, run 'disass ssl3_get_message' at debugger prompt, advance to
vicinity
as well, but the developer have no
idea
what could cause this. Can you help me to debug this further?
Below is the BT of one of the core dumps
Regards
Michael Menge
What OS/platform is this, and what version of OpenSSL?
Also, run 'disass ssl3_get_message' at debugger prompt
What OS/platform is this, and what version of OpenSSL?
Also, run 'disass ssl3_get_message' at debugger prompt, advance to
vicinity of address provided in back-trace, 0x7fe5a839334f in
provided example, and send that page. I mean it's lesser point to send
whole disass output, limit it to
Quoting Andy Polyakov ap...@openssl.org:
What OS/platform is this, and what version of OpenSSL?
Also, run 'disass ssl3_get_message' at debugger prompt, advance to
vicinity of address provided in back-trace, 0x7fe5a839334f in
provided example, and send that page. I mean it's lesser point
seems to be received in ssl3_get_message
or a function called by ssl3_get_message, but received no reply.
I asked on the cyrus mailinglists as well, but the developer have no idea
what could cause this. Can you help me to debug this further?
Below is the BT of one of the core dumps
Regards
(quite a lot
of) changes and improvements to documentation and online help
(according to the messages I've read on openssl-dev in the past months),
I really wonder if postponing (almost?) all of them to post-1.0.2 (i.e.
probably for another year or more) really is appropriate.
Most of them don't
I understand your frustration. We've fixed bugs and added some features in
1.0.2; 'git log apps' will show many entries. Yes, not everything. We're also
hoping to have more frequent releases so hopefully the wait won't be as long.
And once we clean up some things, my branch will get merged
Somehow your md2test.c file is corrupted.
Line 1 should be #include stdio.h and the file has 48 lines.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
__
OpenSSL Project http://www.openssl.org
The error makes no sense. The compiler is complaining about the include line?
Do wc -l md2test.c
--
Principal Security Engineer, Akamai Technologies
IM: rs...@jabber.memailto:rs...@jabber.me Twitter: RichSalz
The error makes no sense. The compiler is complaining about the include line?
Do wc -l md2test.c
--
Principal Security Engineer, Akamai Technologies
IM: rs...@jabber.memailto:rs...@jabber.me Twitter: RichSalz
__
OpenSSL Project
The OpenSSL x509 application supports additional fingerprint digests, but
the help output doesn't show them. The migration to SHA-2 signed x509
Digital Certificates has added interest in using sha2 rather than sha1.
D:\OpenSSL\openssl-1.0.1i\appsgrep -in digest to use x509.c
144: -md2/-md5
This is fixed post-1.0.2, where the message says any supported digest
See https://github.com/akamai/openssl/tree/rsalz-monolith for a preview.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
__
OpenSSL Project
Hi,
When I build openssl-1.0.1i on Solaris 10, there are some error, please
help to check what is the reason. Thanks.
making all in engines/ccgost...
make[2]: Entering directory '/ybg/openssl-1.0.1i/engines/ccgost'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/ybg/openssl
-DSHA512_ASM -DAES_ASM -DGHASH_ASM -c -o md2test.o md2test.c
md2test.c:1: error: syntax error before '.' token
md2test.c:1:12: warning: no newline at end of file
Your copy of this file is corrupted.
; wc test/md2test.c
48 148 955 test/md2test.c
;
We plan on adopting a coding style and it will address this. The style is most
likely to say put spaces around operators. I'm marking this as reject (not
resolve) because we're not gonna do this one-of fix. But a more comprehensive,
better, answer is coming.
--
Rich Salz, OpenSSL dev team;
This will be in a release after 1.0.2
commit 9aaa7be8d4be38c0a13a64a0a8cf6c4774c45a0f
Author: Nick Lewis nick.le...@usa.g4s.com
Date: Mon Aug 11 22:56:46 2014 -0400
PR 2580: dgst missing current SHA algorithms
Update the dgst.pod page to include SHA224...512 algorithms.
Update apps/progs.pl to
Fixed in the next version AFTER 1.0.2
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
__
OpenSSL Project http://www.openssl.org
Development Mailing List
This came up during testing. The entire issue is not clear, but here's
the issue filed on Github: Minor typo change in ssl/s3_enc.c,
https://github.com/openssl/openssl/issues/151:
For c/cpp syntax analysis ambiguities, is it possible to change in
int ssl3_digest_cached_records(SSL *s)
whatever the
buggy tool wants to see.
From: noloa...@gmail.com via RT [mailto:r...@openssl.org]
Sent: Monday, August 04, 2014 9:44 AM
Cc: openssl-dev@openssl.org
Subject: [openssl.org #3481] Add space to help compiler/analyzer parse
token
This came up during testing. The entire issue
I've read other messages on this topic but I am still not clear on what I need
to do to get this to work.
I need to cross-compile a FreeBSD binary on a Linux system.
I can build natively on both FreeBSD and Linux. I am using openssl-1.0.1h
and openssl-fips-2.0.5.
My problem is that fipsld wants
Please open a new ticket if this is still an issue.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
This will be fixed in a release after 1.0.2. All commands get a -help (also
--help), and the list of ciphers and digests is now consistent. It says any
supported cipher And you can find those via openssl
list-message-digest-algorithms
The verify -help output is non-standard (rest of them are a set of lines, one
per flag).
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev
No response in a decade, unsupported platform, closing this.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
- Original Message -
From: Matt Caswell via RT r...@openssl.org
To: hka...@redhat.com
Cc: openssl-dev@openssl.org
Sent: Friday, 20 June, 2014 1:12:47 AM
Subject: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
Hi Hubert
Many thanks
- Original Message -
From: Hubert Kario via RT r...@openssl.org
Cc: openssl-dev@openssl.org
Sent: Tuesday, 17 June, 2014 7:24:45 PM
Subject: Re: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
- Original Message -
From: Stephen Henson via
- Original Message -
From: Matt Caswell via RT r...@openssl.org
To: hka...@redhat.com
Cc: openssl-dev@openssl.org
Sent: Tuesday, 17 June, 2014 12:50:03 AM
Subject: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
Hi Hubert
Thanks for the patch
- Original Message -
From: Matt Caswell via RT r...@openssl.org
To: hka...@redhat.com
Cc: openssl-dev@openssl.org
Sent: Tuesday, 17 June, 2014 12:50:03 AM
Subject: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
Hi Hubert
Thanks for the patch
On Tue Jun 17 13:38:49 2014, hka...@redhat.com wrote:
Thank you, somehow missed that.
For now I just removed changes to s_time and ts from patch set.
Fixed pull request: https://github.com/openssl/openssl/pull/138
The -trusted_first option is handled through a common verify options function
- Original Message -
From: Stephen Henson via RT r...@openssl.org
To: hka...@redhat.com
Cc: openssl-dev@openssl.org
Sent: Tuesday, 17 June, 2014 2:31:07 PM
Subject: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
On Tue Jun 17 13:38:49 2014, hka
- Original Message -
From: Stephen Henson via RT r...@openssl.org
To: hka...@redhat.com
Cc: openssl-dev@openssl.org
Sent: Tuesday, 17 June, 2014 2:31:07 PM
Subject: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
On Tue Jun 17 13:38:49 2014, hka
Neither help messages nor man pages include description of
-trusted_first option. This patch fixes this issue
Pull request: https://github.com/openssl/openssl/pull/124
--
Regards,
Hubert Kario
__
OpenSSL Project
;
unsigned char * hm;
unsigned char * c;
size_t nb;
maxn = BN_num_bytes(rsa-n);
hm = mysslBN2bin(hm, hm, maxn);
c = mysslBN2bin( c, c, maxn);
nb = RSA_public_decrypt((int)maxn, c, c, rsa, RSA_PKCS1_PADDING);
}
Thanks for any help.
--Mark
(rsa-n);
hm = mysslBN2bin(hm, hm, maxn);
c = mysslBN2bin( c, c, maxn);
nb = RSA_public_decrypt((int)maxn, c, c, rsa, RSA_PKCS1_PADDING);
}
Thanks for any help.
--Mark
__
OpenSSL Project
I see. Thank you.
2014-04-28 0:48 GMT+08:00 Dr. Stephen Henson st...@openssl.org:
On Sun, Apr 27, 2014, Weibin Yao wrote:
Is it accessable for read (rt.openssl.org) ? I can't access it and
don't know where to register.
Read access is possible through the guest account:
Is it accessable for read (rt.openssl.org) ? I can't access it and
don't know where to register.
2014-04-27 5:35 GMT+08:00 Matt Caswell fr...@baggins.org:
On 25 April 2014 18:24, Kurt Roeckx k...@roeckx.be wrote:
On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote:
1. Triage RT
On Sun, Apr 27, 2014, Weibin Yao wrote:
Is it accessable for read (rt.openssl.org) ? I can't access it and
don't know where to register.
Read access is possible through the guest account:
https://www.openssl.org/support/rt.html
Steve.
--
Dr Stephen N. Henson. OpenSSL project core
your.patch
On 24 April 2014 10:06, Ben Laurie b...@links.org wrote:
Note that this is just how to help me, not a consensus view from the
whole team, though I have no doubt much of it will be helpful to the
team, too.
1. Triage RT (https://rt.openssl.org/).
RT has been neglected for a long
On 24 April 2014 18:44, Mike Bland mbl...@acm.org wrote:
On Thu, Apr 24, 2014 at 1:31 PM, Ben Laurie b...@links.org wrote:
6. Write new tests
Our test suite sucks. More tests is better.
Shall I send a pull request for this:
On 25 April 2014 00:08, Matt Caswell fr...@baggins.org wrote:
Ben - Is it possible for some of us to get RT users created? The above
assumes we can configure RT statuses - is this possible?
I think you now have RT access, right?
On 24 April 2014 19:54, Kurt Roeckx k...@roeckx.be wrote:
On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote:
Note that this is just how to help me, not a consensus view from the
whole team, though I have no doubt much of it will be helpful to the
team, too.
1. Triage RT (https
Oh, absolutely I've verified it. :-)
I'll get that turned around to you shortly.
Mike
On Sat, Apr 26, 2014 at 6:33 AM, Ben Laurie b...@links.org wrote:
On 24 April 2014 18:44, Mike Bland mbl...@acm.org wrote:
On Thu, Apr 24, 2014 at 1:31 PM, Ben Laurie b...@links.org wrote:
6. Write
On Sat, Apr 26, 2014 at 11:39:13AM +0100, Ben Laurie wrote:
On 24 April 2014 19:54, Kurt Roeckx k...@roeckx.be wrote:
On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote:
Note that this is just how to help me, not a consensus view from the
whole team, though I have no doubt much
On 25 April 2014 18:24, Kurt Roeckx k...@roeckx.be wrote:
On Thu, Apr 24, 2014 at 06:31:34PM +0100, Ben Laurie wrote:
1. Triage RT (https://rt.openssl.org/).
I think part of this means that you'll need to give some people
access to it so they can actually modify the tickets.
I now have
On 25 April 2014 01:14, Viktor Dukhovni openssl-us...@dukhovni.org wrote:
On Thu, Apr 24, 2014 at 04:56:09PM -0700, Quanah Gibson-Mount wrote:
The problem with this approach are significant requests that have languished
for years. One such example would be
On 25 April 2014 01:58, Daniel Reynolds
daniel.reyno...@providenceday.org wrote:
I am not totally sure how many people would be working on this project, but
is seems to me like it would make sense to split up into 3 groups.
I would be concerned about spreading ourselves too thinly. I hope that
On Thu, Apr 24, 2014 at 7:08 PM, Matt Caswell fr...@baggins.org wrote:
On 24 April 2014 18:31, Ben Laurie b...@links.org wrote:
Note that this is just how to help me, not a consensus view from the
whole team, though I have no doubt much of it will be helpful to the
team, too.
1. Triage
On Fri, Apr 25, 2014 at 10:03 AM, Jeff Trawick traw...@gmail.com wrote:
On Thu, Apr 24, 2014 at 7:08 PM, Matt Caswell fr...@baggins.org wrote:
On 24 April 2014 18:31, Ben Laurie b...@links.org wrote:
Note that this is just how to help me, not a consensus view from the
whole team, though I
Note that this is just how to help me, not a consensus view from the
whole team, though I have no doubt much of it will be helpful to the
team, too.
1. Triage RT (https://rt.openssl.org/).
RT has been neglected for a long time. People could usefully go
through it and identify:
a) Tickets
1 - 100 of 432 matches
Mail list logo
