To detect if your HPUX 11.11 system is running in 64-bit mode, you simply
have to do the following:
# /usr/bin/file /stand/vmunix
You should get the following response if you are 64-bit.
/stand/vmunix: ELF-64 executable object file - PA-RISC 2.0 (LP64)
And you'll get the following if you
Now, the really cool thing would be if someone (you?) could provide us
with some sh code that identifies 64bit HP/UX so we could set that up
in the script 'config'.
??? 'config' tells apart 32- and 64-bit HP/UX kernels since long time
ago. Look for 'getconf KERNEL_BITS'.
# /usr/bin/file
In message [EMAIL PROTECTED] on Wed, 19 Nov 2003 09:38:04 +0100 (MET), Andy
Polyakov via RT [EMAIL PROTECTED] said:
rt
rt Now, the really cool thing would be if someone (you?) could provide us
rt with some sh code that identifies 64bit HP/UX so we could set that up
rt in the script
On Wed, Nov 19, 2003 at 09:50:41AM +0100, Richard Levitte - VMS Whacker via RT wrote:
In message [EMAIL PROTECTED] on Wed, 19 Nov 2003 09:38:04 +0100 (MET), Andy
Polyakov via RT [EMAIL PROTECTED] said:
rt
rt Now, the really cool thing would be if someone (you?) could provide us
rt
rt Now, the really cool thing would be if someone (you?) could provide us
rt with some sh code that identifies 64bit HP/UX so we could set that up
rt in the script 'config'.
rt
rt ??? 'config' tells apart 32- and 64-bit HP/UX kernels since long time
rt ago. Look for 'getconf KERNEL_BITS'.
rt Now, the really cool thing would be if someone (you?) could provide us
rt with some sh code that identifies 64bit HP/UX so we could set that up
rt in the script 'config'.
rt
rt ??? 'config' tells apart 32- and 64-bit HP/UX kernels since long time
rt ago. Look for 'getconf
rt Now, the really cool thing would be if someone (you?) could provide us
rt with some sh code that identifies 64bit HP/UX so we could set that up
rt in the script 'config'.
rt
rt ??? 'config' tells apart 32- and 64-bit HP/UX kernels since long time
rt ago. Look for 'getconf
We have this working on HPUX ia64 in both 32 and 64 bit modes.
You'll have to manually Configure anyway, there are three supported
modes, 32 bit , 64 bit, and pa_risc, all of which are supported by the base
OS. Autodetection is going to give the wrong answer 2 times in 3.
The IBM patch with
Hi,
Is there a table that references all the known/declared ASN1_TEMPLATE ?
The goal is to use OpenSSL for dynamic ASN1_TEMPLATE declaration, but to do
this I need to set the ASN1_ITEM_EXP member.
Frédéric Giudicelli
http://www.newpki.org
We have this working on HPUX ia64 in both 32 and 64 bit modes.
You'll have to manually Configure anyway, there are three supported
modes, 32 bit , 64 bit, and pa_risc, all of which are supported by the base
OS.
./config tells apart IA-64 and PA-RISCs as well, and then it consciously
defaults
On Wed, Nov 19, 2003, Frédéric Giudicelli wrote:
Hi,
Is there a table that references all the known/declared ASN1_TEMPLATE ?
The goal is to use OpenSSL for dynamic ASN1_TEMPLATE declaration, but to do
this I need to set the ASN1_ITEM_EXP member.
Not sure what you mean. Do you want all
Oh? So how come 64-bit people get a build that tries to go for
32-bit? What have we missed? I haven't looked yet, but I might
tonight, if I remember...
Yes, during media installation of the OS (11.00, 11.11, etc), you can
choose 64 or 32 bit operating system installation.
11.11 (11i)
??? 'config' tells apart 32- and 64-bit HP/UX kernels since long time
ago. Look for 'getconf KERNEL_BITS'.
That may be the case, but it didnt detect my 64-bit kernel (thus the root
of my emails)...
As clarified by Lutz the issue is that kernel 64-bitness is not checked
at all, whenever gcc
Since the OpenSSL libraries are used by many other applications, it might
be appropriate for the Configure to build both 32 and 64 bit version of the libs.
This applies to more then just HP and more then just OPenSSL.
The configure should use the local systems naming/location conventions
for
The relevant question is of requestor can
confirm that gcc can *now* generate *both* 32- and 64-bit code?
What's
the switch? -m64 as on most of other plaforms or something else? Does
'./Configure hpux64-parisc-gcc -m64' work? Note the commentary
section
above hpux64-parisc-gcc...
snip
Since the OpenSSL libraries are used by many other applications, it might
be appropriate for the Configure to build both 32 and 64 bit version of the libs.
Yes, it's indeed appropriate and support might be implemented at some
point (starting with unification of .h files), but it's not the case
Andy Polyakov wrote:
Since the OpenSSL libraries are used by many other applications, it might
be appropriate for the Configure to build both 32 and 64 bit version of the libs.
Yes, it's indeed appropriate and support might be implemented at some
point (starting with unification of .h
'./Configure hpux64-parisc-gcc -m64' work?
snip
nmcmadam:/opt/patches/openssl-0.9.7c ./Configure hpux64-parisc-gcc -m64
...
Configured for hpux64-parisc-gcc.
nmcmadam:/opt/patches/openssl-0.9.7c
/snip
Does that help?
Not really:-) What happens if you actually run 'make'?
Since the OpenSSL libraries are used by many other applications, it might
be appropriate for the Configure to build both 32 and 64 bit version of the libs.
Yes, it's indeed appropriate and support might be implemented at some
point (starting with unification of .h files), but it's not
It should be changed to detect 10.X systems separate from 11.X systems.
Why?
11.X systems break down to three different categories:
11.00
11.11
11.22
Why? What's so different between 11.x?
Each which you can check to see if it is running 32 or 64bit mode.
If the only difference is
Hi
OpenSSL does not support OAEP for S/MIME mails. I think should be enabled in
further version. One easy (may be not elegant) way is to do a simple
fallback in EVP_PKEY_decypt().
Thanks,
Thorsten
__
OpenSSL Project
On Wed, Nov 19, 2003 at 12:28:18PM +0100, Andy Polyakov wrote:
The IBM patch with the code in it is available, but it's too big to post to
this list.
Post it to openssl-team then:-) A.
Even better: do post it to [EMAIL PROTECTED] RT will forward the message to
the list but will strip the
If you can really confirm that './config -t' fails to print
configuring
for hpux64-parisc-gcc on your system,
nmcmadam:/opt/patches/openssl-0.9.7c ./config -t
Operating system: 9000/800-hp-hpux10
^^ Well, HP-UX 11.x user might find
this inappropriate, but
[EMAIL PROTECTED] - Wed Nov 19 18:10:06 2003]:
Hi
OpenSSL does not support OAEP for S/MIME mails. I think should be
enabled in
further version. One easy (may be not elegant) way is to do a simple
fallback in EVP_PKEY_decypt().
That could be done but it would be none standard. The
Configuring for hpux-parisc-gcc
/usr/contrib/bin/perl ./Configure hpux-parisc-gcc -D_REENTRANT
then submit output from 'gcc -v -E -x c /dev/null' command.
nmcmadam:/opt/InCharge6 gcc -v -E -x c /dev/null
/usr/local/pa20_64/lib/gcc-lib/hppa64-hp-hpux11.11/3.3.2/cc1 -E
-quiet -v
Hi,
when i run ./config i get:
Operating system: sun4u-sun-solaris2
./config: test: unknown operator (GCC)
then on running make i get:
making all in crypto...
( echo #ifndef MK1MF_BUILD; \
echo /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */; \
echo #define CFLAGS \cc
I have a question anout the use of sequence number as a part of the
input to the hash function during the MAC calculation. Does that security
concerns? Would the security aspects of theSSL be affected if the sequence
number is not used as a part of the input to the hash funtion for MAC
hi,
thanks for your quick reply.
So if I can include the sequence number as a part of the protocol(may be
another field added by the SSL) data, I still solve the problem of replay
attacks and I can get rid of sequence number from the MAC calculation. So
my MAC wouldnt depend on the sequence number
Swaminathan P wrote:
hi,
thanks for your quick reply.
So if I can include the sequence number as a part of the protocol(may be
another field added by the SSL) data, I still solve the problem of replay
attacks and I can get rid of sequence number from the MAC calculation. So
my MAC wouldnt depend
On November 19, 2003 07:16 pm, Swaminathan P wrote:
I have a question anout the use of sequence number as a part of the
input to the hash function during the MAC calculation. Does that
security concerns? Would the security aspects of theSSL be affected if
the sequence number is not used as a
Those were great replies. Thanks Lev and Geoff.
Guess I'll have to put more thought into this.
Thanks again,
swami
On Wed, 19 Nov 2003, Geoff Thorpe wrote:
On November 19, 2003 07:16 pm, Swaminathan P wrote:
I have a question anout the use of sequence number as a part of the
input to the
31 matches
Mail list logo
