Runtime input

Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Runtime input
# 8  
Old 10-16-2013
You can find these differents informations in pgp manual:
man pgp or here (online manual)
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Read input files and merge them in given order and write them to input one param or one file

Dear Friends, I am looking for a shell script to merge input files into one file .. here is my idea: 1st paramter would be outfile file (all input files content) read all input files and merge them to input param 1 ex: if I pass 6 file names to the script then 1st file name as output file... (4 Replies)
Discussion started by: hyd1234
4 Replies

2. Shell Programming and Scripting

Script to delete files with an input for directories and an input for path/file

Hello, I'm trying to figure out how best to approach this script, and I have very little experience, so I could use all the help I can get. :wall: I regularly need to delete files from many directories. A file with the same name may exist any number of times in different subdirectories.... (3 Replies)
Discussion started by: *ShadowCat*
3 Replies

3. Shell Programming and Scripting

using read to enter the input at runtime

Hi I am stucked in the below script .I want to input with yes/no from the user and then execute the code inside if but it is not working .I just need the logic as where I am wrong so that i can use the same in my work . then echo "Hi All" fi ]. Please suugest . (4 Replies)
Discussion started by: mani_isha
4 Replies

4. Solaris

Re:How to get the path during runtime?

Thank u vgesh99 It works well.. (1 Reply)
Discussion started by: Nandagopal
1 Replies

5. Solaris

How to get the path during runtime?

Hi guys, I have commands like /solaris/opt/VRTS/bin/vxdisk /opt/VRTS/bin/vxdisk From these two commands, i need to get the directory path value before /VRTS/bin/vxdisk at runtime. e.g /solaris/opt/VRTS/bin/vxdisk as /solaris/opt /opt/VRTS/bin/vxdisk as /opt I have tried with cut... (1 Reply)
Discussion started by: Nandagopal
1 Replies

6. Shell Programming and Scripting

Reading specific contents from 1 input files and appending it to another input file

Hi guys, I am new to AWK and unix scripting. Please see below my problem and let me know if anyone you can help. I have 2 input files (example given below) Input file 2 is a standard file (it will not change) and we have to get the name (second column after comma) from it and append it... (5 Replies)
Discussion started by: sksahu
5 Replies

7. UNIX for Dummies Questions & Answers

Runtime Error...

My system did stay appears the error Run Time Library Error. What itīs? When the error appear, iīve to reboot my system and lost all I did. Is there the UNIX System problem? Please. I need help!!! (4 Replies)
Discussion started by: marpin
4 Replies

8. Solaris

Runtime error...

My interprise use a UNIX mainform for a instrumentation process control. The control use the FOXBORO INVENSYS system and they donīt gonna solve the problem the run time error. The run time error happen without logic explication. When everything itīs run perfectely and happenly appears the run time... (1 Reply)
Discussion started by: marpin
1 Replies

9. Shell Programming and Scripting

Getting Function Name At Runtime

Hi, Suppose I have a User define function get_abc in which I am using $0 to get the name of function. But when I call that function in any script, $0 will give the script name, not the function name. For example: Function: get_abc ------------------- get_abc( ){ echo $0 } Script:... (3 Replies)
Discussion started by: yeheyaansari
3 Replies
Login or Register to Ask a Question
QCATOOL(1)						Qt Cryptographic Architecture (QCA)						QCATOOL(1)

qcatool - command line tool for the Qt Cryptographic Architecture DESCRIPTION
qcatool is a command line tool for performing various cryptographic operations with the Qt Cryptographic Architecture (QCA). qcatool can also be used for testing and debugging QCA. USAGE
qcatool has a range of options and commands. You only ever get to use one command, but you may use several, one or no options. OPTIONS
As noted above, these are all optional, and may be combined. --pass=PASSWORD Specify the password to use. This is probably a bad idea except for testing, because anyone can read the arguments to a command line application. --newpass=PASSWORD Specify the new password to use for password change with the key changepass and keybundle changepass commands. This is probably a bad idea except for testing, because anyone can read the arguments to a command line application. --nonroots=CERTIFICATES Specify additional certificates, not trusted, but which may be used in the trust path if appropriate trust can be established. --roots=CERTIFICATES Specify additional certificates which can be used as trusted (root) certificates. --nosys Disable use of the standard root certificates that are provided by the operating system. --noprompt Disable prompting for passwords/passphrases. If you do not provide the passphrase on the command line (with --pass or --newpass) this will cause qcatool to abort the command if a password/passphrase is required. --ordered If outputting certificate information fields (Distinguished Name and Subject Alternative Name), show them in same the order that they are present in the certificate rather than in a friendly sorted order. --debug Enable additional output to aid debugging. --log-file=FILENAME Log to the specified file. --log-level=LEVEL Log at the specified level. The log level can be between 0 (none) and 8 (most). --nobundle When S/MIME signing, do not bundle the signer's certificate chain inside the signature. This results in a smaller signature output, but requires the recipient to have all of the necessary certificates in order to verify it. COMMANDS
help, --help, -h Output usage (help) information. version, --version, -v Output version information. plugins List available plugins. Use the --debug option to get more information on plugins which are found and which ones actually loaded. config save [provider] Save provider configuration. Use this to have the provider's default configuration written to persistent storage, which you can then edit by hand. config edit [provider] Edit provider configuration. The changes are written to persistent storage. key make rsa|dsa [bits] Create a key pair key changepass [K] Add/change/remove passphrase of a key cert makereq [K] Create certificate request (CSR) cert makeself [K] Create self-signed certificate cert makereqadv [K] Advanced version of 'makereq' cert makeselfadv [K] Advanced version of 'makeself' cert validate [C] Validate certificate keybundle make [K] [C] Create a keybundle keybundle extract [X] Extract certificate(s) and key keybundle changepass [X] Change passphrase of a keybundle keystore list-stores List all available keystores keystore list [storeName] List content of a keystore keystore monitor Monitor for keystore availability keystore export [E] Export a keystore entry's content keystore exportref [E] Export a keystore entry reference keystore addkb [storeName] [cert.p12] Add a keybundle into a keystore keystore addpgp [storeName] [key.asc] Add a PGP key into a keystore keystore remove [E] Remove an object from a keystore show cert [C] Examine a certificate show req [req.pem] Examine a certificate request (CSR) show crl [crl.pem] Examine a certificate revocation list show kb [X] Examine a keybundle show pgp [P|S] Examine a PGP key message sign pgp|pgpdetach|smime [X|S] Sign a message message encrypt pgp|smime [C|P] Encrypt a message message signencrypt [S] [P] PGP sign & encrypt a message message verify pgp|smime Verify a message message decrypt pgp|smime ((X) ...) Decrypt a message (S/MIME needs X) message exportcerts Export certs from S/MIME message ARGUMENTS
The arguments to the commands are as follows. K = private key. C = certificate. X = key bundle. P = PGP public key. S = PGP secret key. E = generic entry. These must be identified by either a filename or a keystore reference ("store:obj"). AUTHOR
qcatool was written by Justin Karneges as part of QCA. This manual page was written by Brad Hards. qcatool 1.0.0 August 2007 QCATOOL(1)