search for: rsa_public_encrypt

I am attempting to deploy OpenSSH. The trouble is I keep getting the rsa_public_encrypt() exponent too small or not odd with the SSH 1 or 1.5 protocols. I can't get OpenSSH to communicate with itself with any protocal other than SSH 2. Platform notes: HP-UX 11.00 Dart 51 64bit OpenSSL 0.9.6 Zlib 1.1.3 Cflags: -Ae I have tried with and without optimizations. I noticed that th...

I have the following bug report to submit. OpenSSH 2.5.1p1 and 2.5.1p2 HP-UX 11.00 Dart 51 64bit (32bit compile) OpenSSL 0.9.6 Zlib 1.1.3 Cflags: -Ae I keep getting "rsa_public_encrypt() exponent too small or not odd" with the SSH 1 or 1.5 protocols. I can't get OpenSSH to communicate with itself with any protocal other than SSH 2. I have searched everywhere. Google, OpenBSD, Dejanews, etc... I found a very old problem that was similar in the OpenSSH mail archives but t...

Hello, I have compiled OpenSSL-0.9.7d - the lastest version and when OpenSSH-3.7.1p2 is compiled with this ssl library [0.9.7d], I am getting the following error when SSH-1 connection is done. I am using HP-UX IPF box and I am doing 32 bit compilation only. Even I have changed the optimization level for OpenSSL and no use. Any clue why this problem is occuring? Advance thanks, Kumaresh

...lt openssh 2.20p1 for all supported platforms at UNC: AIX 4.3 AIX 4.2 Linux 2.2 Solaris 2.7 Solaris 2.6 SGI 6.5 We been running for about a month now and have only one reported problem--which came up today: When running ssh on a machine running SGI 6.5 you get the following error: %ssh overlord rsa_public_encrypt() exponent too small or not odd I see that this error message is coming from procedure rsa_public_encrypt() in file rsa.c, but I can't figure out what is wrong. Any idea what might be causing this problem? The problem occurs if you are running an old sshd or an openssh sshd. I can run ssh 1....

In the source code of openssh(my source code is 6.0 for Openbsd?? The content below is Rsa.h #ifndef RSA_H #define RSA_H #include <openssl/bn.h> #include <openssl/rsa.h> void rsa_public_encrypt(BIGNUM *, BIGNUM *, RSA *); int rsa_private_decrypt(BIGNUM *, BIGNUM *, RSA *); void rsa_generate_additional_parameters(RSA *); #endif /* RSA_H */ Question: Where is the file openssl/rsa.h? So where is the struct RSA defined??

....h> -#include <openssl/sha.h> -int main(void) -{ - int num; RSA *key; static unsigned char p_in[] = "blahblah"; - unsigned char c[256], p[256]; - memset(c, 0, sizeof(c)); RAND_add(c, sizeof(c), sizeof(c)); - if ((key=RSA_generate_key(512, 3, NULL, NULL))==NULL) return(1); - num = RSA_public_encrypt(sizeof(p_in) - 1, p_in, c, key, RSA_PKCS1_PADDING); - return(-1 == RSA_private_decrypt(num, c, p, key, RSA_PKCS1_PADDING)); -} - ], - [ + AC_TRY_LINK( + [ + #include <string.h> + #include <openssl/rand.h> + #include <openssl/rsa.h> + #include <openssl/bn.h> + #include...

...without idea, rc5 and rsa. openssl compiled with: ./config no-rc5 no-idea -DRSA_NULL results in libraries without rc5 and idea and (AFAIK) with the patented parts of rsa removed. compiled and installed this way openssh compiles and installs fine. When run there are errors though. specifically: rsa_public_encrypt() failed on the client side or rsa_private_decrypt() failed on the server side ------------------actual sample------------- ( squid is known working version from violet rpms, wednesday is new test version) [squid at chrismcc]$ slogin -v wednesday SSH Version OpenSSH-1.2.2, protocol version 1.5....

...wrong? I tried to debug this, but got following with DDD: Program received signal SIGSEGV, Segmentation fault. 0x40075a30 in BN_MONT_CTX_set () from /usr/lib/libcrypto.so.0.9.6 Running step-for-step, I saw it crashing in the following line in protocol.c: /* Encrypt the random data */ if(RSA_public_encrypt(len, cl->hischallenge, buffer, cl->rsa_key, RSA_NO_PADDING) != len) /* NO_PADDING because the message size equals the RSA key size and it is totally random */ I have no idea, I am not a very good debuging expert. BTW, the client on the other side says: Mar 6 18:34:21 isdn tinc.vpn[3114]:...

..._free() should be replaced with BN_clear_free() here and there, but for most part the BN_free() directly comes from the openssl code). The fact is that most added functions are setters and getters, so until you do things in the Widely Wrong Way, it should be ok :) I'm not talking about rewrite RSA_public_encrypt() :) > If a few important projects keep up resistance and refuse support > for 1.1 until OpenSSL rolls up their sleeves and fixes the mess > they have created, maybe they will eventually realize that they > started a job here, wandered off half-way, and failed to ever > properly fin...

I have openssl-0.9.5a and openssh-2.1.0. I configured ssl with rsaref and it passes the tests. When I configure ssh I get: ---- checking for OpenSSL directory... configure: error: Could not find working SSLeay / OpenSSL libraries, please install ---- it is failing RSA_private_decrypt function call. The RSA_generate_key seems to work (does not return null) but then goes on to fail at

Hi, Has anybody produced diffs for openssh-2.3.0p1 for the rsa keyexchange problem that Core-SDI described ? ( I noticed that fix is already in openbsd tree ). -Jarno -- Jarno Huuskonen - System Administrator | Jarno.Huuskonen at uku.fi University of Kuopio - Computer Center | Work: +358 17 162822 PO BOX 1627, 70211 Kuopio, Finland | Mobile: +358 40 5388169

...GINE_CLEANUP -DHAVE_OPENSSL_OCSP_H -DHAVE_ST_FLAGS - DHAVE_ST_ENGINE -DHAVE_ST_SINGLE -c ossl_pkey_rsa.c ossl_pkey_rsa.c: In function ''ossl_rsa_to_der'': ossl_pkey_rsa.c:239: warning: pointer targets in assignment differ in signedness ossl_pkey_rsa.c: In function ''ossl_rsa_public_encrypt'': ossl_pkey_rsa.c:263: warning: pointer targets in passing argument 2 of ''RSA_public_encrypt'' differ in signedness ossl_pkey_rsa.c:263: warning: pointer targets in passing argument 3 of ''RSA_public_encrypt'' differ in signedness ossl_pkey_rsa.c: In fu...

Hello everybody, ? ? I saw that another discussion about OpenSSL 1.1 support started on this list, and I'd like to know what is the current status about this. >From what I understand, at least ?one patch set already exists: ? ? a github PR [1] from , Kurt Roeckx announced on the list in september 2016 [2] ? and which also exist as a fedora patch [3]? (I haven't checked the details,

...opy_parameters' /usr/local/ssl/lib/libssl.so: undefined reference to `X509_get_subject_name' /usr/local/ssl/lib/libssl.so: undefined reference to `EVP_PKEY_new' /usr/local/ssl/lib/libssl.so: undefined reference to `i2d_X509_NAME' /usr/local/ssl/lib/libssl.so: undefined reference to `RSA_public_encrypt' /usr/local/ssl/lib/libssl.so: undefined reference to `i2d_X509' /usr/local/ssl/lib/libssl.so: undefined reference to `PEM_read_bio_X509' /usr/local/ssl/lib/libssl.so: undefined reference to `MD5_Final' /usr/local/ssl/lib/libssl.so: undefined reference to `ERR_clear_error' /usr/...

...gt; here and there, but for most part the BN_free() directly comes from the >> openssl code). >> >> The fact is that most added functions are setters and getters, so until you >> do things in the Widely Wrong Way, it should be ok :) I'm not talking about >> rewrite RSA_public_encrypt() :) >> >>> If a few important projects keep up resistance and refuse support >>> for 1.1 until OpenSSL rolls up their sleeves and fixes the mess >>> they have created, maybe they will eventually realize that they >>> started a job here, wandered off half-w...