Is ccrypt AES 256 bit crypto secure enough? Post: 302887059

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

encrypting file system using AES 256 bit

Experts, I am trying to encrypt my filesystem using the AES 256 bit type of encryption. I am using FreeBSD 5.4 and need to encrypt one of the mounted points. Does anybody have any good idea of how to do it? Is there any documentation about encrypting the disk partition as this method is more...

2. Programming

AES encryption

Hi, Any body can please point me to source code for implementing AES encryption in CTR mode i.e RFC 3686 (AES-CTR).I did googling but no good results.

3. Programming

JAVA AES keylength exception

I am developing a JAVA application that must encrypt its data. On my development machine, I can use a 256 bit key with no problem. A test machine throws an exception complaining about an illegal key length. The test machine is using JRE 1.6u21. Does anyone know where I can get a version of the JRE...

4. UNIX for Dummies Questions & Answers

Using sed with special characters produced from crypto

Hey there, I'm facing some weird issues with sed when trying to do substitution in a text file with the content of some environment variables. Those variables are used to store crypted (3DES) info with much special characters and that's where the problem starts. I've already tried to use both...

5. Programming

Publish and Subscribe to AES-256 Encrypted MQTT Messages to Node-RED from PHP Scripts

Various Node-Red crypto modules do not work with PHP, so to send an encrypted message from a PHP script (in this case from a Ubuntu server) to Node-RED we need our own code. After a few hours of searching, testing various libs, more testing and debugging, I got this PHP to Node-RED code...

LEARN ABOUT HPUX

chkey

chkey(1)						      General Commands Manual							  chkey(1)

NAME

       chkey - change user's secure RPC key pair

SYNOPSIS

       [ ] [

DESCRIPTION

       is used to change a user's secure RPC public key and secret key pair.  prompts for the old secure-rpc password and verifies that it is cor-
       rect by decrypting the secret key.

       If the user has not already used to decrypt and store the secret key with registers the secret key with the local daemon.  If  the  secure-
       rpc  password  does  not  match	the  login password, prompts for the login password.  uses the login password to encrypt the user's secret
       Diffie-Hellman (192 bit) cryptographic key.

       ensures that the login password and the secure-rpc password are kept the same.

       The key pair can be stored in the file (see publickey(4)), the NIS map, or entries in the LDAP directory.  If a new secret  key	is  gener-
       ated, it will be registered with the local daemon.

       If  the	source	of  the  is  not  specified  with  the	option, consults the entry in the name service switch configuration file (see nss-
       witch.conf(4)).	If the entry specifies one and only one source, then will change the key in the specified name service.  However, if  mul-
       tiple name services are listed, cannot decide which source to update and will display an error message.	The user should specify the source
       explicitly with the option.

       Non root users are not allowed to change their key pair in the file.

   Options
       Re-encrypt the existing secret key with the user's
		   login password.

       Update the  NIS database.

       Update the  database.

       Update the  LDAP database.

WARNINGS

       HP-UX 11i Version 2 is the last HP-UX release on which NIS+ is supported.  LDAP is the recommended replacement for NIS+.  HP fully supports
       the industry standard naming services based on LDAP.

AUTHOR

       was developed by Sun Microsystems, Inc.

FILES

SEE ALSO

       keylogin(1), keylogout(1), keyserv(1M), newkey(1M), nsswitch.conf(4), publickey(4).

																	  chkey(1)