Reliant Unix
Hallo, ich versuche openssl auf einer RM400 mit ReliantUNIX-N 5.45 A1023 zu installieren. Das config-script läuft durch und legt ein Makefile.ssl an. Der make steigt mit folgender Fehlermeldung aus: cc:[fatal]:CDR9912 thread package for -Kthread not installed Können Sie mir weiterhelfen ? Gruß SBS MPM CPI Hermann Günther Tel. 636 40060 __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Reliant Unix
Es ist ein kleines gewesen habe können wurde, da ich dies gemacht, deshalb sein meine Informationen jetzig nicht, aber es erfordert, daß Sie das DCE Klient Paket zu installieren, um erhalten, Fäden Stütze auf Siemens Nixdorf Maschinen. Ich hoffe, daß dies hilft. It's been a little while, so my information may not be current, but For Siemens Nixdorf you used to have to install a seperate package, the DCE client software, in order to get the threads libraries, headers, etc. Hope this helps. Hermann Guenther wrote: Hallo, ich versuche openssl auf einer RM400 mit ReliantUNIX-N 5.45 A1023 zu installieren. Das config-script läuft durch und legt ein Makefile.ssl an. Der make steigt mit folgender Fehlermeldung aus: cc:[fatal]:CDR9912 thread package for -Kthread not installed Können Sie mir weiterhelfen ? Gruß SBS MPM CPI Hermann Günther Tel. 636 40060 __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
.NET version of OpenSSL
Is anyone working on a .NET version of OpenSSL ? thank you
Re: .NET version of OpenSSL
Thus spake jeff roberts: Is anyone working on a .NET version of OpenSSL ? For those of us that live in non-Microsoft worlds, can you explain what this means/entails? S -- Stephen Sprunk So long as they don't get violent, I want to CCIE #3723 let everyone say what they wish, for I myself have K5SSSalways said exactly what pleased me. --Albert Einstein __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
re[2]: .NET version of OpenSSL
I will take a stab at it, but I am not going to be able to cover it all here ! A .NET port of OpenSSL would require replacing the C style DLL interface with a .NET Object DLL. The OpenSSL source code would have to be able to be compiled under the C# (pronounced c sharp) compiler. Microsoft has just released Visual Studio 7.0. Version 7.0 produces .NET dll's. exe's, etc. The new framework that is required to execute a .NET component (dll or exe) is called the common language runtime (CLR). A .NET component gets just in time compiled (JIT) when it is needed and optimized for the operating system and hardware it is running under. When future 64 bit versions of Windows arrive, .NET components will already be 64 bit when run under the new operating system. The C# language is NOT a superset of the C or C++ languages. Porting OpenSSL would be a real job! I believe that most future software development is and will be done as a .NET component and that if OpenSSL is not ported to it, then OpenSSL will die the same fate as Windows 3.1 __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: re[2]: .NET version of OpenSSL
Hi there, On Thursday 14 March 2002 10:13, Jeff Roberts wrote: A .NET port of OpenSSL would require replacing the C style DLL interface with a .NET Object DLL. The OpenSSL source code would have to be able to be compiled under the C# (pronounced c sharp) compiler. Microsoft has just released Visual Studio 7.0. Version 7.0 produces .NET dll's. exe's, etc. The new framework that is required to execute a .NET component (dll or exe) is called the common language runtime (CLR). A .NET component gets just in time compiled (JIT) when it is needed and optimized for the operating system and hardware it is running under. When future 64 bit versions of Windows arrive, .NET components will already be 64 bit when run under the new operating system. This sounds absolutely horrible. Why don't we just port OpenSSL to java which has already been doing this same thing for a while now? The C# language is NOT a superset of the C or C++ languages. Porting OpenSSL would be a real job! A real *painful* job. But by all means, go ahead. I believe that most future software development is and will be done as a .NET component and that if OpenSSL is not ported to it, then OpenSSL will die the same fate as Windows 3.1 Ah yes, I forgot; Win64/.NET - the enterprise platform of the future. We have nothing against you porting OpenSSL (or any part of it) to toy operating systems and/or half-baked enterprise-windows-beans (or windows enterprise baked beans, if you prefer) but don't expect OpenSSL itself to *move* to this new language ... the real business of computing, and *especially* security-related computing tasks, lives in a predominantly more unix/C/C++ world than you probably believe. There's no way we'll move wholesale over to Microsoft's toy language + platform, forsaking all of that on the off-chance that, contrary to all Microsoft innovation in the past, .NET and C# will actually revolutionise the industry and take us to unparalleled network bliss. If you can isolate the required changes to support C#/.NET, and provide a non-intrusive way to support that in OpenSSL's source tree, we would be happy to incorporate your contributions. Cheers, Geoff __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
RE: re[2]: .NET version of OpenSSL
I believe that most future software development is and will be done as a .NET component and that if OpenSSL is not ported to it, then OpenSSL will die the same fate as Windows 3.1 You're joking, right? You don't honestly believe that .NET is going to eliminate the need for real UNIX servers, which by the way, power the majority of commercial Internet sites, and are written in C/C++. .NET performance? Stability? Maturity? Security? M'think you've succumbed to reading way too many Microsoft Marketecture material lately. * DISCLAIMER: The information contained in this e-mail may be confidential and is intended solely for the use of the named addressee. Access, copying or re-use of the e-mail or any information contained therein by any other person is not authorized. If you are not the intended recipient please notify us immediately by returning the e-mail to the originator. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: re[2]: .NET version of OpenSSL
Maybe when Mono (the Open-Source version of .NET) is available? OpenSSL is primarily for UNIX systems, which at present have no .NET support. So making a .NET port sounds about like making a Java port, from this description. I guess Microsoft, fresh from the black eye over Java, is trying to push this on us. Since they have the market share, they'll probably get away with it too. Linux, anybody? A .NET port of OpenSSL would require replacing the C style DLL interface with a .NET Object DLL. The OpenSSL source code would have to be able to be compiled under the C# (pronounced c sharp) compiler. Microsoft has just released Visual Studio 7.0. Version 7.0 produces .NET dll's. exe's, etc. The new framework that is required to execute a .NET component (dll or exe) is called the common language runtime (CLR). A .NET component gets just in time compiled (JIT) when it is needed and optimized for the operating system and hardware it is running under. When future 64 bit versions of Windows arrive, .NET components will already be 64 bit when run under the new operating system. The C# language is NOT a superset of the C or C++ languages. Porting OpenSSL would be a real job! I believe that most future software development is and will be done as a .NET component and that if OpenSSL is not ported to it, then OpenSSL will die the same fate as Windows 3.1 __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
re[4]: .NET version of OpenSSL
I know old Unix programmers die hard ! __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
re[4]: .NET version of OpenSSL
I have heard that the reason that Microsoft bought a large part of Coral is to have them put .NET on Linux ! __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: re[4]: .NET version of OpenSSL
On Wed, 13 Mar 2002, Jeff Roberts wrote: I have heard that the reason that Microsoft bought a large part of Coral is to have them put .NET on Linux ! Yes, they also buy hotmail to prove it cant be running on nt. Could we keep on .NET please when they manage to make some code? __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: re[4]: .NET version of OpenSSL
Thus spake Jeff Roberts: I think you can create .NET components in Java too ! The point is that there are going to be a lot of .NET applications that need a .NET solution. Some companies are porting their Java code to C# because it is so similar ! C# will never have the speed that C/ASM can achieve, and you're going to have a tough time convincing us to rewrite tens of thousands of lines of code just to make Bill Gates happy. There MUST be some way to link .NET code to non-.NET DLL's, so creating a C# wrapper around OpenSSL may be a worthwhile exercise. S -- Stephen Sprunk So long as they don't get violent, I want to CCIE #3723 let everyone say what they wish, for I myself have K5SSSalways said exactly what pleased me. --Albert Einstein __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: re[4]: .NET version of OpenSSL
I think it have gone far from the questions. But in my perspective (it can be faulty) OPENSSL must be put in wrapper that make it a CSP of Windows and the application in whatever language (C, C++, C#, JAVA, next language, next ... ) will access it via the CryptoAPI this means that all the headhake will be made by the win32 layer and call under the correct component (see link). A similar architecture must be available in Unix to replace the win32 layer. http://www.microsoft.com/TechNet/itsolutions/net/evaluate/images/ITPRON03.GI F JLD - Original Message - From: Vadim Fedukovich [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 13, 2002 5:07 PM Subject: Re: re[4]: .NET version of OpenSSL On Wed, 13 Mar 2002, Jeff Roberts wrote: I have heard that the reason that Microsoft bought a large part of Coral is to have them put .NET on Linux ! Yes, they also buy hotmail to prove it cant be running on nt. Could we keep on .NET please when they manage to make some code? __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: .NET version of OpenSSL
Jeff Roberts wrote: I know old Unix programmers die hard ! You might ask yourself why that is. In fact old Unix programmers built most of the technologies on which the Internet runs. Old Unix programmers know that it is a technical error to use an OS with such obvious designed-in flaws as Windows. Old Unix programmers and young ones as well are working quite hard to make certain that software that doesn't suck is available for those who can tell the difference. Paul Allen -- Boeing Phantom Works \ Paul L. Allen, (425) 865-3297 Math Computing Technology \ [EMAIL PROTECTED] POB 3707 M/S 7L-40, Seattle, WA 98124-2207 \ Prototype Systems Group __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Reliant Unix
Sie brauchen DCE-THR V2.0 oder SIthreads. Von siemens.de: Die Betriebssystem-CD enthält das Paket SIthreads, das über cdinst installiert werden kann. Das Paket SIthreads ersetzt die frühere Version von DCE-Threads DCE-THR 2.0A von der CD-SYS-MI. Vergewissern Sie sich bitte, daß die frühere DCE-Threads-Version DCE-THR auf Ihrem System nicht installiert ist (deinstallieren Sie diese gegebenenfalls). Bemerkung: Das Paket DCE-THR 2.0A ist auch im Produkt DCE-EXEC (Reliant UNIX) 2.0 enthalten. Falls Sie das Produkt DCE-EXEC (Reliant UNIX) 2.0 auf Reliant UNIX 5.45 einsetzen, installieren Sie dieses Produkt zuerst. Deinstallieren Sie anschließend das Paket DCE-THR 2.0 und installieren Sie das Paket SIthreads. ich versuche openssl auf einer RM400 mit ReliantUNIX-N 5.45 A1023 zu installieren. Das config-script läuft durch und legt ein Makefile.ssl an. Der make steigt mit folgender Fehlermeldung aus: cc:[fatal]:CDR9912 thread package for -Kthread not installed Können Sie mir weiterhelfen ? Gruß SBS MPM CPI Hermann Günther Tel. 636 40060 __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[PATCH] Initialize cipher context in ssl/s3_(clnt|srvr).c
A ciph_ctx is declared auto, but not initialized in the SSL_kKRB5 codepath. diff -ur openssl-0.9.7-stable-SNAP-20020312-orig/ssl/s3_clnt.c openssl-0.9.7-stable-SNAP-20020312-work/ssl/s3_clnt.c --- openssl-0.9.7-stable-SNAP-20020312-orig/ssl/s3_clnt.c Mon Jan 14 18:40:23 2002 +++ openssl-0.9.7-stable-SNAP-20020312-work/ssl/s3_clnt.c Thu Mar 14 00:35:18 2002 @@ -1494,6 +1494,8 @@ + EVP_MAX_IV_LENGTH]; int padl, outl = sizeof(epms); + EVP_CIPHER_CTX_init (ciph_ctx); + #ifdef KSSL_DEBUG printf(ssl3_send_client_key_exchange(%lx %lx)\n, l, SSL_kKRB5); diff -ur openssl-0.9.7-stable-SNAP-20020312-orig/ssl/s3_srvr.c openssl-0.9.7-stable-SNAP-20020312-work/ssl/s3_srvr.c --- openssl-0.9.7-stable-SNAP-20020312-orig/ssl/s3_srvr.c Tue Mar 12 15:07:06 2002 +++ openssl-0.9.7-stable-SNAP-20020312-work/ssl/s3_srvr.c Thu Mar 14 00:35:44 2002 @@ -1559,6 +1559,8 @@ if (!kssl_ctx) kssl_ctx = kssl_ctx_new(); + EVP_CIPHER_CTX_init (ciph_ctx); + n2s(p,i); enc_ticket.length = i; enc_ticket.data = (char *)p; __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
