On 18/03/2015 10:14, Matt Caswell wrote:
On 18/03/15 07:59, Jakob Bohm wrote:
(Resend due to MUA bug sending this to -announce)
On 16/03/2015 20:05, Matt Caswell wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming
On 18/03/15 07:59, Jakob Bohm wrote:
(Resend due to MUA bug sending this to -announce)
On 16/03/2015 20:05, Matt Caswell wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming release
of OpenSSL versions 1.0.2a,
(Resend due to MUA bug sending this to -announce)
On 16/03/2015 20:05, Matt Caswell wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming release
of OpenSSL versions 1.0.2a, 1.0.1m, 1.0.0r and 0.9.8zf.
These releases
On 18/03/15 10:45, Jakob Bohm wrote:
However the patch rebasing instructions are *completely
useless* for those of us whomaintain private patches
against releases tarballs. We *don't* have any of this
in a clone of your gitand we *have no way* to access
intermediary git steps from your
We maintain our own derivative of OpenSSL and haven't had any
significant issues due to the code reformat. We simply run the reformat
script on our downstream derivative. We can then generate patch files
of our changes and reapply them to new OpenSSL releases. It was fairly
straight forward.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/03/15 19:05, Matt Caswell wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming
release of OpenSSL versions 1.0.2a, 1.0.1m, 1.0.0r and 0.9.8zf.
These releases
Nice, so the extra work is minimal for complete forks of
OpenSSL.
The extra work is also documented (in a place not linked from
the wiki) for those who maintain a git fork of the OpenSSL
repository.
But I have not yet seen a meaningful recipe for those of us
who maintain a traditional set of
I have BMC BladeLogic and recently downloaded a password change script that
uses openssl and I am seeing an error message of the script unable for
openssl to generate hash for password. Can I attach the script for someone
to help me?
Thank you,
Respectfully
//SIGNED//
Andy Magaña
UNIX
Hi,
before calling this function,
remove any whitespace;
Walter
smime.p7s
Description: S/MIME Cryptographic Signature
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
The extra work is also documented (in a place not linked from the wiki) for
those who maintain a git fork of the OpenSSL repository.
I just tossed together https://wiki.openssl.org/index.php/Code_reformatting
Found off the main page,
Hi Dave and Walter,
Thanks for our reply.
I'm not doing anything different for the ssh pubkey. I'm able to decode it
using the openssl enc -base64 -d -A command. But not using the C program.
Attaching my entire code here. After getting the base64 decoded I'm
calculating the MD5 sum and printing
Please refer to Dave Thompson's answer, it describes your problem.
On 18/03/2015 16:08, Prashant Bapat wrote:
Hi Dave and Walter,
Thanks for our reply.
I'm not doing anything different for the ssh pubkey. I'm able to
decode it using the openssl enc -base64 -d -A command. But not using
the C
Thanks for the three line upgracde recipe in
https://wiki.openssl.org/index.php/Code_reformatting
It's as simple as you stated, indeed.
The reformatting was a good thing to do. Also, it makes sense to me to apply it
to all
stable branches uniformly, in order to simplify cross-branch merging.
I believe the SSH pubkey is binary data, not ASCII, so strlen() will not work
on it if it has embedded NUL chars.
As Dave Thompson suggested, instead of strlen(), use the length returned from
BIO_read.
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Prashant Bapat
Hi,
Most likely this has been answered before, please bear with me.
I'm trying to use the base64 decode function in C. Below is the function.
char *b64_decode(unsigned char *input, int length)
{
BIO *b64, *bmem;
char *buffer = (char *)malloc(length);
memset(buffer, 0, length);
Hello,
Here is a recipe to guide you through the reformatting.
It worked nicely for me. I wrote a small bash shell script
which helped me do the bulk conversion, see attachment
Hope you'll find this information helpful.
In following I briefly describe the steps how you can
1) get your patches
As always, if you don't know or care what FIPS 140-2 is then count
yourself lucky and move on (in this case, count yourself *very* lucky).
We have -- we think -- a workaround for the hostage issue that was
blocking the addition of new platforms to the OpenSSL FIPS module
validation via change
On 18.03.2015 16:08, Prashant Bapat wrote:
printf(Base64 decoded string is : %s\n, b64_decode(str, strlen(str))); //
This should print binary for a ssh key.
not really, because the return of b64_decode is not a C string; and the
format specfier %s expects a C string;
smime.p7s
Description:
18 matches
Mail list logo
