Nelson B Bolyard:
> On your system, is certutil a shell script that runs a program named
> certutil-bin ?
As Eddy said about getting it from a directory server install, the
Directory/Certificate System products have been doing that for quite a
while now.
>From a system with Red Hat CS 7.1 installed:
[EMAIL PROTECTED] ~]# file `which certutil`
/opt/redhat-cs/shared/bin/certutil: Bourne shell script text
[EMAIL PROTECTED] ~]# cat /opt/redhat-cs/shared/bin/certutil
#!/bin/sh
LD_LIBRARY_PATH=/opt/redhat-cs/shared/lib
export LD_LIBRARY_PATH
/opt/redhat-cs/shared/bin/certutil-bin ${1+"$@"}
[EMAIL PROTECTED] ~]# file /opt/redhat-cs/shared/bin/certutil-bin
/opt/redhat-cs/shared/bin/certutil-bin: ELF 32-bit LSB executable, Intel
80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses
shared libs), stripped
You'll be happy to know that has changed with Red Hat CS 7.3 and Dogtag
[EMAIL PROTECTED] ~]# file `which certutil`
/usr/bin/certutil: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
I assume it is just packaging constraints. Up until 7.2 or 7.3/Dogtag,
the certificate system was packaged to install completely under the same
directory. The newer stuff is aiming to be LSB compliant IIRC and is
spread out and uses more regular system components.
Dave
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
