HI Giovanni
Depending on the country you are located in, you may need to check the current
status of your countries regulatory legislation regarding encryption
technologies.
Participating countries : https://www.wassenaar.org/participating-states/
Dear Users,
I have released version 5.52 of stunnel.
Version 5.52, 2019.04.08, urgency: HIGH
* Bugfixes
- Fixed a transfer() loop bug introduced in stunnel 5.51.
Home page: https://www.stunnel.org/
Download: https://www.stunnel.org/downloads.html
SHA-256 hashes:
>> creation of x509 certificate with algo1 and algo2, and/or TLS and SSL
>> connection always with algo1 and algo2
Tobias Nießen wrote:
> As far as I know, you will need to have an OID assigned for each
> algorithm for x509 certificates. You can add those to OpenSSL manually,
Thank you every one for the answers and tips, really a great and active
group!
Thank you also to Teja and Tobias who has just wrote some suggestion on how
I can have a technical shortcut to prove the functionality of my
algorithms in very limited environment.
What I asked is to move a first step
1. dasync_aes128_cbc_cipher (search for this in
https://github.com/openssl/openssl/blob/master/engines/e_dasync.c) ||
replace it with your symmetric cipher, and do the same for RSA.
2. setup a server and client and hard-code the symmetric & asymmetric
ciphers to your ciphers
3. your idea is simply
creation of x509 certificate with algo1 and algo2, and/or TLS and SSL
connection always with algo1 and algo2
As far as I know, you will need to have an OID assigned for each
algorithm for x509 certificates. You can add those to OpenSSL manually,
but you won't be able to communicate with any
* Sure, I want to publish the algorithm, but not yet... waiting for
establishing a company.
This is a bit off-topic, but trying to make money from a cryptographic
algorithm isn’t really done any more. RSA was locked up by patents, and there
were some elliptic curve patents that have since
On Mon, Apr 08, 2019 at 05:48:56PM +0200, Giovanni Fontana wrote:
> my name is Giovanni Fontana. I made a new symmetric crypto algorithm (let’s
> call it *algo1*) and a new asymmetric crypto algorithm (let’s call it
> *algo2*).
Recent additions to OpenSSL include X25519, Ed25519 and ChaCha20.
Hi Clarke,
Thanks for the email.
Sure, I want to publish the algorithm, but not yet... waiting for
establishing a company.
For similar reasons no github usage at moment.
Giovanni
Il giorno lun 8 apr 2019 alle 18:06 Dennis Clarke
ha scritto:
> On 4/8/19 11:48 AM, Giovanni Fontana wrote:
> >
On 4/8/19 11:48 AM, Giovanni Fontana wrote:
> Hello everybody,
>
> my name is Giovanni Fontana. I made a new symmetric crypto algorithm
> (let’s call it *algo1*) and a new asymmetric crypto algorithm (let’s
> call it *algo2*).
>
> I use algo2 for key exchange and with that I can create a session
Hello everybody,
my name is Giovanni Fontana. I made a new symmetric crypto algorithm (let’s
call it *algo1*) and a new asymmetric crypto algorithm (let’s call it
*algo2*).
I use algo2 for key exchange and with that I can create a session key to
cipher and decipher with algo1, so Alice and Bob
On 08/04/2019 08:26, Chethan Kumar wrote:
> Dear all,
>
>
>
> We did openssl version upgrade from 1.0.2n to 1.1.1. While compiling some
> package dependent on openssl, getting errors related to M_ASN1_ D2I AND I2D
> functions.
>
> Digging deeper got to know that, in latest openssl
I provide Windows binaries for wget, which I link statically, to make
wget.exe completely self-contained, and I use OpenSSL as the crypto
backend. This worked fine for years, but when I updated OpenSSL to
1.1.1b for the latest wget release, wget is now failing on some
systems with "Disabling SSL
On 03/04/2019 22:13, Jakob Bohm via openssl-users wrote:
> As an Exim user (can already be seen in my mail headers), I always
> wondered about the weird way that Exim (according to the docs/spec)
> tries to reinit TLS for each message on a connection.
>
> It seemed very much contrary to protocol,
Dear all,
We did openssl version upgrade from 1.0.2n to 1.1.1. While compiling some
package dependent on openssl, getting errors related to M_ASN1_ D2I AND I2D
functions.
Digging deeper got to know that, in latest openssl asn1_mac.h header is
deprecated.
Can someone please help me out in
15 matches
Mail list logo