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)
Regards.
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
ENIGMA(1)						    BSD General Commands Manual 						 ENIGMA(1)

NAME
enigma, crypt -- very simple file encryption SYNOPSIS
enigma [-s] [-k] [password] crypt [-s] [-k] [password] DESCRIPTION
The enigma utility, also known as crypt is a very simple encryption program, working on a ``secret-key'' basis. It operates as a filter, i.e., it encrypts or decrypts a stream of data from standard input, and writes the result to standard output. Since its operation is fully symmetrical, feeding the encrypted data stream again through the engine (using the same secret key) will decrypt it. There are several ways to provide the secret key to the program. By default, the program prompts the user on the controlling terminal for the key, using getpass(3). This is the only safe way of providing it. Alternatively, the key can be provided as the sole command-line argument password when starting the program. Obviously, this way the key can easily be spotted by other users running ps(1). As yet another alternative, enigma can be given the option -k, and it will take the key from the environment variable CrYpTkEy. While this at a first glance seems to be more secure than the previous option, it actually is not since environment variables can also be examined with ps(1). Thus this option is mainly provided for compatibility with other implementations of enigma. When specifying the option -s, enigma modifies the encryption engine in a way that is supposed to make it a little more secure, but incompat- ible with other implementations. Warning The cryptographic value of enigma is rather small. This program is only provided here for compatibility with other operating systems that also provide an implementation (usually called crypt(1) there). For real encryption, refer to bdes(1), openssl(1), pgp(1) (ports/security/pgp), or gpg(1) (ports/security/gnupg). However, restrictions for exporting, importing or using such tools might exist in some countries, so those stronger programs are not being shipped as part of the operating system by default. ENVIRONMENT
CrYpTkEy used to obtain the secret key when option -k has been given EXAMPLES
man enigma | enigma > encrypted Enter key: (XXX -- key not echoed) This will create an encrypted form of this man page, and store it in the file encrypted. enigma XXX < encrypted This displays the previously created file on the terminal. SEE ALSO
bdes(1), gpg(1), openssl(1), pgp(1), ps(1), getpass(3) HISTORY
Implementations of crypt are very common among UNIX operating systems. This implementation has been taken from the Cryptbreakers Workbench which is in the public domain. BSD
May 14, 2004 BSD