Sponsored Content
Full Discussion: Cryptography
Top Forums Shell Programming and Scripting Cryptography Post 302182080 by era on Saturday 5th of April 2008 10:25:19 AM
Old 04-05-2008
It would probably be a good idea to take a brief moment to explain "why" and "do you know what you are doing", as usually one or the other of these two often turns out to be a problem when dealing with encryption.

You can of course encrypt anything you like, but it would help to know: do you need to be able to get it back (really!) and should it still be text-only.

Passwords are usually encrypted in such a way that they cannot be recovered -- all you can (or ever need to) do is encrypt another input string and compare; if they are the same, the user had the right password.

Should all the information be encrypted using a single passphrase, or do they need to be individual?

Have you been thinking about whether symmetric, secret-key encryption would suit your needs better, or asymmetric public-key encryption? Do you have a preference for any particular encryption algorithm or software?
 

4 More Discussions You Might Find Interesting

1. Cybersecurity

Firewalls and cryptography

As we know, firewall is designed to keep unauthorized outsiders from tampering with a computer system or network. We don't talk about computer security without cryptography. In this case, may I know,How does cryptographic protection (at the TCP/IP layers or at the application layer) affect a... (1 Reply)
Discussion started by: heroine
1 Replies

2. What is on Your Mind?

How To Analyze This (Cryptography Random?) Permutation...?

Hi to all of you guys, I'm new here... May this thread fits on this section. A friend of mine gave me this enigma to do, written in excel. I attach the file below, name New.xls. Enigma: There are 10^20 possibilities of tables (Table1, Table 2, Table 3, Table 4, Table 5,...), with ten rows (row... (3 Replies)
Discussion started by: lucky7
3 Replies

3. Red Hat

Need help in allowing symmetric cryptography[2]

I have encountered some problems in my school work. Here is the question: The server that provides the time synchronization must be configured to allow its clients to verify its authenticity using symmetric cryptography. Much Appreciated!:) (1 Reply)
Discussion started by: wilsonljx
1 Replies

4. Homework & Coursework Questions

Need help in allowing symmetric cryptography[2]

The server that provides the time synchronization must be configured to allow its clients to verify its authenticity using symmetric cryptography. 4. Singapore Polytechnic, Dover, Singapore,Mr Kam, and Computer Engineering I don't think there is any coding since it is just configuring... (3 Replies)
Discussion started by: wilsonljx
3 Replies
EVP_SealInit(3) 						      OpenSSL							   EVP_SealInit(3)

NAME
EVP_SealInit, EVP_SealUpdate, EVP_SealFinal - EVP envelope encryption SYNOPSIS
#include <openssl/evp.h> int EVP_SealInit(EVP_CIPHER_CTX *ctx, EVP_CIPHER *type, unsigned char **ek, int *ekl, unsigned char *iv,EVP_PKEY **pubk, int npubk); int EVP_SealUpdate(EVP_CIPHER_CTX *ctx, unsigned char *out, int *outl, unsigned char *in, int inl); int EVP_SealFinal(EVP_CIPHER_CTX *ctx, unsigned char *out, int *outl); DESCRIPTION
The EVP envelope routines are a high level interface to envelope encryption. They generate a random key and IV (if required) then "enve- lope" it by using public key encryption. Data can then be encrypted using this key. EVP_SealInit() initializes a cipher context ctx for encryption with cipher type using a random secret key and IV. type is normally supplied by a function such as EVP_des_cbc(). The secret key is encrypted using one or more public keys, this allows the same encrypted data to be decrypted using any of the corresponding private keys. ek is an array of buffers where the public key encrypted secret key will be written, each buffer must contain enough room for the corresponding encrypted key: that is ek[i] must have room for EVP_PKEY_size(pubk[i]) bytes. The actual size of each encrypted secret key is written to the array ekl. pubk is an array of npubk public keys. The iv parameter is a buffer where the generated IV is written to. It must contain enough room for the corresponding cipher's IV, as deter- mined by (for example) EVP_CIPHER_iv_length(type). If the cipher does not require an IV then the iv parameter is ignored and can be NULL. EVP_SealUpdate() and EVP_SealFinal() have exactly the same properties as the EVP_EncryptUpdate() and EVP_EncryptFinal() routines, as docu- mented on the EVP_EncryptInit(3) manual page. RETURN VALUES
EVP_SealInit() returns 0 on error or npubk if successful. EVP_SealUpdate() and EVP_SealFinal() return 1 for success and 0 for failure. NOTES
Because a random secret key is generated the random number generator must be seeded before calling EVP_SealInit(). The public key must be RSA because it is the only OpenSSL public key algorithm that supports key transport. Envelope encryption is the usual method of using public key encryption on large amounts of data, this is because public key encryption is slow but symmetric encryption is fast. So symmetric encryption is used for bulk encryption and the small random symmetric key used is transferred using public key encryption. It is possible to call EVP_SealInit() twice in the same way as EVP_EncryptInit(). The first call should have npubk set to 0 and (after set- ting any cipher parameters) it should be called again with type set to NULL. SEE ALSO
evp(3), rand(3), EVP_EncryptInit(3), EVP_OpenInit(3) HISTORY
EVP_SealFinal() did not return a value before OpenSSL 0.9.7. 0.9.7a 2003-01-26 EVP_SealInit(3)
All times are GMT -4. The time now is 08:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy