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 FREEBSD

keylogout

KEYLOGOUT(1)						    BSD General Commands Manual 					      KEYLOGOUT(1)

NAME

     keylogout -- delete stored secret key

SYNOPSIS

     keylogout [-f]

DESCRIPTION

     The keylogout utility deletes the key stored by the key server process keyserv(8) to be used by any secure network services, such as NFS.
     Further access to the key is revoked, however current session keys may remain valid till they expire, or are refreshed.  This option will
     cause any background jobs that need secure RPC services to fail, and any scheduled at jobs that need the key to fail.  Also since only one
     copy is kept on a machine of the key, it is a bad idea to place this in your .logout file since it will affect other sessions on the same
     machine.

     The following option is available:

     -f      Forget the rootkey.  This will break secure NFS if it is done on a server.

SEE ALSO

     chkey(1), keylogin(1), login(1), publickey(5), keyserv(8), newkey(8)

BSD
								  April 15, 1989							       BSD