Firstly, i apologise if i have posted in a wrong section of the forum. Please let me know which is the correct section my post should go to.
I have to SCP a file from one server(server A) to another (server B). I read around that a secure way is to use public and private keys.
Assuming my... (2 Replies)
Hello*! I have problems with public keys. On one side i have Solaris 10, and on other side is HP UNIX. I created public keys on Solaris with "ssh-keygen -t rsa", append id_rsa.pub key to ~user/.ssh/authorized_keys on remote machine, and tried to connect with ssh without password. But for some... (1 Reply)
I'm hoping someone can help get me moving in the right direction here, so bear with me.
I've got 2 RedHat Linux servers, let's call them A & B.
- A receives "sensitive" files, which are PGP encrypted, and immediately sends them off to B for decryption/processing/deletion
- B needs to make... (1 Reply)
Hello here is what I've seen
inside some public pgp keys.
gAIAAAAAAAkBAAAAAAoAAAAFAAoArwFI/gkAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA... (1 Reply)
Hi All,
I am having knowledge on some basics of ssh and wanted to know what are the public keys and how can we create and implement it in connecting server.
Please provide the information for the above, it would be helpful for me.
Thanks,
Ravindra (1 Reply)
Hi,
I need to export an existing PGP key and import it into GnuPG on a different machine.
This is how I did the export:
pgp -kx myuser _myuser_public
pgp -kx myuser _myuser_private secring.skr
(this is from the pgp installation directory that contains secring.skr).
This produced two... (0 Replies)
Hi,
I need to export an existing PGP key and import it into GnuPG on a different machine.
This is how I did the export:
pgp -kx myuser _myuser_public
pgp -kx myuser _myuser_private secring.skr
(this is from the pgp installation directory that contains secring.skr).
This produced two... (0 Replies)
Hi Guys,
Am facing issue in generating PGP keys. Can you please help me to figure this out??
I fired the below command to generate keys. The log say keys successfully created. But when i tried to list it doesnt shows me the keys created.
pgp --gen-key "pgptest<ram@gmail.com>"... (3 Replies)
Hi Guys,
I am trying to import the public of vendor to my system. I am getting below error while importing public key. can anyone please help me with this??
laranakejt4:/u/raja/.pgp $ pgp --import secure.asc
0x1545A56A52:import key (4007:key failed signature check)
secure.asc:import key... (0 Replies)
Discussion started by: Vinoth Kumar G
0 Replies
LEARN ABOUT FREEBSD
enigma
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