Thank you for pointing out. That is not what I expect, but very important
point for fix.
Sincerely,
Yuchi Tian
On Mon, Feb 6, 2017 at 4:59 PM, Lars Nordin wrote:
> On 2017-02-05 07:54, yuchi tian wrote:
>
> Dear OpenSSL developers,
>
> We are software engineering researchers at University of Vi
On 2017-02-05 07:54, yuchi tian wrote:
Dear OpenSSL developers,
We are software engineering researchers at University of Virginia. As
part of a research project, we have built a tool for automatically
finding and fixing error handling bugs and are testing it on
various cryptographic libraries
> Guidance for how to correctly submit patches is given in the
> CONTRIBUTING file here:
> https://github.com/openssl/openssl/blob/master/CONTRIBUTING
> Please could you submit your fixes as a github pull request? One pull
> request for all of these issues should be fine.
Thank you for the infor
> Will you make the tool and the corresponding scientific publication
> public?
Yes. We are currently in the step of evaluating our tools. We will submit
our work and share our tools when the project is done.
Sincerely,
Yuchi Tian
On Sun, Feb 5, 2017 at 6:16 AM, Hanno Böck wrote:
> On Sun, 5 F
On 05/02/17 06:54, yuchi tian wrote:
> Dear OpenSSL developers,
>
> We are software engineering researchers at University of Virginia. As
> part of a research project, we have built a tool for automatically
> finding and fixing error handling bugs and are testing it on
> various cryptographic li
On Sun, 5 Feb 2017 01:54:06 -0500
yuchi tian wrote:
> We are software engineering researchers at University of Virginia. As
> part of a research project, we have built a tool for automatically
> finding and fixing error handling bugs and are testing it on
> various cryptographic libraries and app
Dear OpenSSL developers,
We are software engineering researchers at University of Virginia. As part
of a research project, we have built a tool for automatically finding and
fixing error handling bugs and are testing it on
various cryptographic libraries and applications that use them.
In the mos
Too late for 1.0.1 and too much work for 1.0.2 :)
We fixed it in master (1.1) by saying "any supported digest" which isn't ideal,
admittedly.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.opens
Hi. openssl 1.0.1c and its man pages don't tell the full story about
support for secure hash algorithms, especially the SHA family. The
attached patch fixes this. Though it's a bit clunky.
FWIW "openssl dss1" seems to be an alias for sha1 and the output is
reported as DSA. But we can't have
Bodo Moeller wrote:
> > Do you prefer the patch against the pre-patched version or against the
> > patched version of the ca.pod file ?
>
> I'd prefer one for the patched version (but it shouldn't really matter
> if you use a context or unified diff).
Here it is. I think it should be "error" fr
Harald Koch wrote:
> There's a configuration option in the openssl.conf file that lets you
> either copy or move the email address from the X509 subject to the
> subjectAltName extension.
The problem was that if you did not wanted the EMAIL field in the subject
while having the extensions correc
> This patch adds the possibility to not include the EMAIL field in the
> DN of the issued certificate when issuing a new certificate. This was
> needed as the inclusion of the EMAIL is actually deprecated by RFCs.
This functionality already exists, at least in the 0.9.7 branch.
There's a config
Hi,
It's been some time since I wrote last time on the mailing lists (:-D),
anyway I have some patches for the ca.c command. This time them should be
complete (the ca.pod patch is present also).
To patch simply copy the ca.patch in the apps/ dir and the ca.pod.patch
in the docs/apps and do:
Attached is the patches for OpenSSL 0.9.6 to enable the AES
winner:Rijndael. Also attached is the files that is not included in the
patch and is new.
Nine files:
1. rijndael.diff - The diff file to use with "patch -p3 -u"
2. cmd - The command executed to create the diff file.
3. exc
Bodo Moeller wrote:
>
> On Fri, Oct 27, 2000 at 10:52:16AM +0200, Robert Sandilands wrote:
>
> > Attached is the patches for OpenSSL 0.9.6 to enable the AES
> > winner:Rijndael.
>
> Your patch doesn't seem to include any of your new files, such as the
> o
On Fri, Oct 27, 2000 at 10:52:16AM +0200, Robert Sandilands wrote:
> Attached is the patches for OpenSSL 0.9.6 to enable the AES
> winner:Rijndael.
Your patch doesn't seem to include any of your new files, such as the
one actually containing the Rijndael implementation ...
Anyw
Attached is the patches for OpenSSL 0.9.6 to enable the AES
winner:Rijndael.
Three files:
1. rijndael.diff - The diff file to use with "patch -p3 -u"
2. cmd - The command executed to create the diff file.
3. exclude - The files that were excluded.
Procedure for using patch:
Attached is the patches for OpenSSL 0.9.6 to enable the AES
winner:Rijndael.
Three files:
1. rijndael.diff - The diff file to use with "patch -p3 -u"
2. cmd - The command executed to create the diff file.
3. exclude - The files that were excluded.
Procedure for using patch:
Hello everyone...
I'm relatively new to these lists, so this may have been hashed
out in the past or may be in some FAQ somewhere I can't find. If so,
I appologize in advance.
In the OpenCA bundle, there are some patches for OpenSSL that are
recommended in the INSTAL
ftp://ftp.stacken.kth.se/pub/random/levitte/openssl-0.9.4-dev-VMS.diffs
contains the changes needed to get a working OpenSSL 0.9.4 on VMS. The
changes are relative to the latest rsync done here, which was about 10
hours ago (and I've seen no changes being done since).
--
Richard Levitte \ Spa
20 matches
Mail list logo
