10 More Discussions You Might Find Interesting
1. Red Hat
I have requirement for strace utility rpm package for RHEL 5.9. I have made a google for last 1 hr. but did not find the required one. Can any one help me out to find out the compatible rpm package of strace for Redhat 5.9 version (I require 64 bit version). (7 Replies)
Discussion started by: Anjan Ganguly
7 Replies
2. UNIX for Advanced & Expert Users
Hi,
Anyone can help on applying patch "PHP Vulnerability: CVE-2015-4601" on Centos 6.8 platform.
How can I install this patch in command line using "yum" or "rpm"? Do I need to download or there is a direct command.
Thanks in advance.
Ragards,
FSPalero (4 Replies)
Discussion started by: fspalero
4 Replies
3. UNIX for Dummies Questions & Answers
I need to change Date and time stamp format from Jan 01 2015 11:00:00 PM to 01/01/2015 23.00.00
Existing Format : Mon DD YYYY hh:mi:ss AM/PM (Jan 01 2015 11:00:00 PM)
Expected Format: MM/DD/YYYY hh.mi.ss 24 hours (01/01/2015 23.00.00)
I need to update enitire file where... (3 Replies)
Discussion started by: esivaprasad
3 Replies
4. Red Hat
Does anyone know if final RHEL 7 is going to have GNOME 2 or 3?
Anyone try the beta yet? (1 Reply)
Discussion started by: Synbios
1 Replies
5. Red Hat
After checking the dependencies from below command:-
yum deplist gcc
Update:-
Now when I tried to install the very first dependency , it gave the below error, I guess something is wrong with YUM server itself :P
... (1 Reply)
Discussion started by: manish131081
1 Replies
6. Red Hat
Hi
In opensuse we have this nice version control variable I use much when designing rpm spec files:
rpm --showrc | grep suse_version
%if 0%{?suse_version} > 0 && 0%{?suse_version} < 1700
-14: suse_version 1140But I do not find anything close to this in rhel/centos
The only way... (0 Replies)
Discussion started by: mortenb
0 Replies
7. Shell Programming and Scripting
hi
i have an application which have a expect script. But now when I run application on other machines, it requires expect to be present on that system.
Now I have the binary of expect with all the libraries required.
The binary support for Rhel 5 version or later versions.
Can aneone tell... (2 Replies)
Discussion started by: tapan_kumawat
2 Replies
8. Red Hat
Hello,
Any pointers where to get an rpm for xtrlock?
Thanks,
mgb (0 Replies)
Discussion started by: mgb
0 Replies
9. Shell Programming and Scripting
I have tried thought of using instfix -ivqc | grep BIND , but this did not return the result I was looking for; it seem to list out the the different patches that had been applied to BIND. I'm actually looking for overall version, like you'd get when checking the OS level for instance. (1 Reply)
Discussion started by: sport
1 Replies
10. Cybersecurity
How do I find out my current version of BIND?
Dhall1973:D (1 Reply)
Discussion started by: dhall1973
1 Replies
SOFTHSM-KEYCONV(1) General Commands Manual SOFTHSM-KEYCONV(1)
NAME
softhsm-keyconv - converting between BIND and PKCS#8 key file formats
SYNOPSIS
softhsm-keyconv --topkcs8 --in path --out path [--pin PIN]
softhsm-keyconv --tobind --in path [--pin PIN]
--name name [--ttl ttl --ksk] --algorithm algorithm
DESCRIPTION
softhsm-keyconv can convert between BIND .private-key files and the PKCS#8 file format. This is so that you can import the PKCS#8 file
into libsofthsm using the command softhsm. If you have another file format, then openssl probably can help you to convert it into the
PKCS#8 file format.
The following files will be created when converting to BIND file format:
Kname+alg_id+key_tag.key
Public key in RR format
Kname+alg_id+key_tag.private
Private key in BIND key format
The three parts of the file name means the following:
name The owner name given by the --name argument.
alg_id A numeric representation of the --algorithm argument.
key_tag
Is a checksum of the DNSKEY RDATA.
OPTIONS
--topkcs8
Convert from BIND .private-key format to PKCS#8.
Use with --in, --out, and --pin.
--tobind
Convert from PKCS#8 to BIND .private-key format.
Use with --in, --pin, --name, --ttl, --ksk, and --algorithm.
--algorithm algorithm
Specifies which DNSSEC algorithm to use when converting to BIND format. The supported algorithms are:
RSAMD5
DSA
RSASHA1
RSASHA1-NSEC3-SHA1
DSA-NSEC3-SHA1
RSASHA256
RSASHA512
--help, -h
Shows the help screen.
--in path
The path to the input file.
--ksk This will set the flag field to 257 instead of 256 in the DNSKEY RR in the .key file. Indicating that the key is a Key Signing Key.
Can be used when converting to BIND format.
--name name
The owner name to use in the BIND file name and in the DNSKEY RR. Do not forget the trailing dot, e.g. "example.com."
--out path
The path to the output file.
--pin PIN
The PIN will be used to encrypt or decrypt the PKCS#8 file depending if we are converting to or from PKCS#8. If not given then the
PKCS#8 file is assumed to be unencrypted.
--ttl TTL
The TTL to use for the DNSKEY RR. Optional, this will default to 3600 seconds.
--version, -v
Show the version info.
EXAMPLES
To convert a BIND .private-key file to a PKCS#8 file, the following command can be used:
softhsm-keyconv --in Kexample.com.+007+05474.private
--out rsa.pem
To convert a PKCS#8 file to BIND key files, the following command can be used:
softhsm-keyconv --in rsa.pem --name example.com.
--ksk --algorithm RSASHA1-NSEC3-SHA1
AUTHOR
Written by Rickard Bellgrim.
SEE ALSO
softhsm(1), softhsm.conf(5), openssl(1), named(1), dnssec-keygen(1), dnssec-signzone(1)
SoftHSM 21 December 2009 SOFTHSM-KEYCONV(1)