cpdu

Security

Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net

0
5 .0
Description:

Cryptographic Data Utility
Cryptographic Package Distribution Utility
is a secure command line file encryption tool that allows for archiving encrypted files
with secure memory allocation, zlib and bzip compression

it currently supports the following ciphers
aes/rijndael: 256 bit key, 128 block
twofish: 256 bit key, 128 block
blowfish: 448 bit key, 64 block
cast: 128 bit key, 64 block
serpent: 256 bit key, 128 block
tripledes: 168 bit key, 64 block

aes is default cipher

it has more room for improvement and in the future will allow transferring encrypted files over the internet using a server and client implementation.
Last changelog:

discontinued note 29 days ago

im taking this off of pling and ill be working on it and making it turn up better for higher quality purposes. the main idea behind a crypto app these days either rests on mainly tangible home/work security of files that are mainly for hiding specifically as much the files hold peculiar value as in company related files like game source code or bank security. when someone is at their house and want to hide their files this sort of program only goes so far as it hold some sort of value with much to go by but simply for a particular type of reasoning behind it. in ways about how these days a program is written for a type of purpose mainly there goes without saying that there is activity and behind it is a user who needs no other sort of play but a mechanism for carnisoenistic health purpose driven scientific and a play of numeralogical sub-theoistic moronism is which in between time contingency and throttling the tenuere of base dimensed scientific work. this program is not really very important so ill be working on a new type of project.... a high entropy graphics programming library. you can check out my blog on google search 'richard enciu blogspot profile' and you might notice some theoism in my current applications for namley, sub-theoism and programming in numerlogics

C

renci

11 years ago

it is imperative that you email me if you have any problems requests or personal interests with the program. i would love to recieve your email.
it will not take long for this program to achieve its full capability. please join in developing and email me your changes so that i can upload them.
richardenciu@gmail.com
thanks very much for downloading and be careful as to not lose your encryption keys.

Report

discontinued note 29 days ago

im taking this off of pling and ill be working on it and making it turn up better for higher quality purposes. the main idea behind a crypto app these days either rests on mainly tangible home/work security of files that are mainly for hiding specifically as much the files hold peculiar value as in company related files like game source code or bank security. when someone is at their house and want to hide their files this sort of program only goes so far as it hold some sort of value with much to go by but simply for a particular type of reasoning behind it. in ways about how these days a program is written for a type of purpose mainly there goes without saying that there is activity and behind it is a user who needs no other sort of play but a mechanism for carnisoenistic health purpose driven scientific and a play of numeralogical sub-theoistic moronism is which in between time contingency and throttling the tenuere of base dimensed scientific work. this program is not really very important so ill be working on a new type of project.... a high entropy graphics programming library. you can check out my blog on google search 'richard enciu blogspot profile' and you might notice some theoism in my current applications for namley, sub-theoism and programming in numerlogics

0.49.6b 1 month ago

bugfixes. remove copy wrapper from source tree due to bugs. im working on the internet transfer part of the program soon and ill be cleaning up a lot of code and making the source neater.

0.49.6b 1 month ago

bugfixes

0.49.5b 1 month ago

i fixed some bugs in copy wrapper script for system remove command. the program now allows root access to the wrapper copy program so all root commands that use system rm have copy wrapping conditions for safe copy to /root/.cpdu/.systemremove directory.

project undergoing bugfixing 1 month ago

i have to fix a lot of bugs before i post the program source tree again... sorry

0.49.4b 1 month ago

i did some changes to the rm system command copy wrapper and its in the source tree again. the code is a little better but somethings are wrong with it because i didnt add a case to stat the .systemremove directory if the permissions are off and, the user cant enter and write to the directory otherwise being that there would be call to the script and the files would not be allowed to be copied before the remove command is called within so i guess im up to my neck if you guys change the permissions of your own .systemremove directory. im not sure what to say about it and i hope it helps insomuch and there isnt any weird things happening when calling the script and it fouls up or not. all the script does is call rm after the safe copy and the safe copy program internally checks to see if your in the user directory otherwise no action is taken. im ready to take full the responsibility to add system wide safe copies within root user priveleges but i have something i have to do before i start on that aspect like working out some things in parts of my daily activity.i know this wrapper program is helpful, noone wants accidentally deleted files....

0.49.3b 1 month ago

i removed the copy wrapper script for the system removal command because of too many bugs. i want to make it work but i need some time so i removed the code from the source tree. it has some bugs i need to work out.

0.49.3b 1 month ago

i worked out a faily simple way to wrap the system rm command with a user space safe copy program. the script inside of the source code directory can install the the wrapper script into /usr/bin and rename the orginal /usr/bin/rm command to another working filename and put the wrapper script in its place. if you inspect the install scripts inside of the source tree the original copy of the rm command is put in /root directory for safe keeping and also copied to /usr/local/bin and /usr/bin with another filename until you want to uninstall the wrapper, the remove script inside of the source tree copys the original system remove command over the wrapper script. you might really want to inspect the code and the scripts for thinking your use with the wrapper program and i will say its a very small helpful step towards user space to get all phucked up where you accidentally use system rm in command line to remove files by either purpose or typo accidents. i used to typo rm alot so i decided to help other people with the same problem. inspect the code and try not to mess with the scripts execution internals because youll really phuck up the whole thing this thing is supposed to achieve. yeah, inspect the code and try to make it work for you as such you use the wrapper program and wrapper script for safe copying before system removal inside of user space. this wrapper program is a real deal problem solver.

0.49.2b 2 months ago

i added another fix to the removal program and its in the source directory. instead of removing the files inside the program i made it a safe copy program and in the shell script it just simple wraps the cpdu_safe_copy program to the rm script where rm is then executed. in the cpdu_safe_copy program there is a condition where only user spaces files are copied otherwise you get caught up copying tons of files to the safe copy destination.

0.49.1b 2 months ago

i certainly HAD to remove the removal replacement program i tried to cook up because it lacked proper execution exceptions for running as root or where there were maybe programs being run within user directory or as user to have needed the normal system copy to be used for the application to run correctly. so i have to find a way to give a big FIXME about that and try to find a way for proper execution for running where there are better exceptions in place. so please if you think you used the rm replacement where you downloaded the version where it was in the source tree try to be careful because it lacks the necessary exceptions. it could get a little dangerous to use also because if someone downloaded the program and edited the script where the exceptions are placed the system could accidentally screw up where applications need the system copy for use where either users run apps or root does. this program replacement that i understood to be safe was simply in a way that didnt work very well so i had to remove it and you muse try to find a way to forgive me if their was system corruption useing the removal replacement program i uploaded. i had to remove it from the cpdu source tree until i come up with a better fix. its a good idea to get this kind of program working for the user but it needs a definite FIXME so its not in the source tree for a while until i fix the script.

0.49b 2 months ago

bugfixes that are important

0.48b 2 months ago

added ncurses recovery selection menu for selecting currently deleted and copied files contained in ~/.cpdu/.systemremove to be individually selected to be copied to the current working directory. remember only root is allowed to run the regular system executable of rm as a condition in the replacement script and the replacement program is only for regular users who may accidentally delete files in their home directory with the system copy. the cpdu replacement system remove script and replacement remove program is to ensure a very practical degree of safety for the regular user and allows root to be the only one to run the regular system copy of rm.

0.47b 3 months ago

ok guys i messed up and i put the system remove replacement back online. if you run the script in the cpdu source directory to install the system remove replacement it should work fine. if you are a regular user the remove script replacement always checks if your in your home directory before the program is executed if its not then no commands are run. the /bin/rm executable from your linux/unix install is replaced with the srm script and is backed up in the /root user directory and in the /bin directory. this program is for really not stupid users and is a mock up for people that get a little frenzy when going on about useing the system remove command and accidentally delete files with typos or whatever. as i described the removal replacement program is supposed to run in the user directory and allows for copying files to ~/.cpdu/.systemremove as backup then removing the files with the c language remove(); unix system function call. be very careful because the condition in the script only allows root to run the original system executable copy due to the nature of system commands that need it for running smoothly like apt or update-grub. just really be careful that all because as root the system command is allowed to run and thats the only condition in the script for the rm command to run only if your root. i tried earlier to get a little technical in the scripts but i settled on only the whoami root condition for running and thats it you have your getting, my little take on having a user replacement for the system remove command because of problems of accidental deletion. it can get pretty devastating when you delete files accidentally.

0.46.1b 3 months ago

i removed the system remove script and the program for safe removal in the home directory. it can corrupt files when update-grub is run and got really dangerous so.... crap. no more interesting ideas out of that program for this package. youll have to try to find a way to get along without this sort of program i cooked up. it wasnt working well with system commands...... corrupting system files is definitely not good!

0.46b 3 months ago

there was some serious problems with somethings going on with my system remove replacement program so i tried the best to fix it. it works but im not sure i got all the bugs out. maybe its me drinking too much coffee and i DO know how to code accurately so i dont think theres to much of any sort of real time problem with the program at this point.

0.45b 3 months ago

try to frantically fix the cpdu system remove placement code because of some fixing and buggy things going on. i hope it works better now.

0.43b 3 months ago

fixed script and lrm cpdu replacement to catch any usage of rm command as root and report as 'unusual execution' and exits without actions. also the replacement program catches if files are too small or calling from main home directory or that any files are called in the program that are hidden. they might be passwords or config files so that the program is just within the right sort of niche for safety. in the execution script and the remove program replacement all usage of root is caught unless mainly within the script the condition still stands for the system copy to be used if a normal system program is using the system removal copy for regular safe and usual execution. (asin if sudo system commands are used that have usual conditions for file removal the idea is to allow system remove to be used for proper removal)

0.41b 3 months ago

fixed srm shell script for system removal replacement to check to see if apt or apt-get is running from home or else where so that regular system copy of remove is to be used. the shell script contains a function (for editing) to allow to determine if any system command is running so that it can use the proper removal file.

simply, the cpdu removal script runs if no specified (in shell script) programs are running that need the system copy of remove. the only way the removal program for cpdu is ran is if it is simply in the usr home directory and thats all. you can edit the shell script all you want in the examples to specify which program should be checked out as much it currently is running so that the system rm command is ran as a shell script condition.

0.4b update 3 months ago

i added some system rm utiliity scripts for my safe copy safe remove application in the cpdu directory. when you make youll get a 'lrm' executable. in the srm_shell_script directory is a install script and remove script to install a shell script wrapper for the system remove utility. what this does is backup system /bin/rm executable and replace it with a shell script that determines if your in your usr home directory. if you are the lrm executable is executed if not the regular system command is executed. this makes sure when optionally when you want to install lrm for safe removing and copying you dont accidenctally delete your files all the way. its a start but you have to be carefull not to delete any files you dont want to thats why i wrote this utility.

0.4b 4 months ago

added a simple system rm command replacement that backs up files that can be deleted from command line into {HOME}/.cpdu/.systemremove directory. Its not altogther replacing the 'rm' command because when you make install-rm it copys the cpdu remove utility to '/usr/local/bin/srm' and is known globally as 'srm' on command line. all directory entities remain the same and all files are copied exactly how they are deleted with directory hierarchy intact. it allows recursive search and shows prompt before removing and allows no prompt as an option. STILL IN DEVELOPMENT.

0.3.99b 2 years ago

bugfixes

0.9.38b 2 years ago

added backup file option. this allows files to backed up in an archive without any compression or encryption and it is stored and named automatically (with current time and date) into the {HOME}/.cpdu/.recoverdb directory
bugfix: fixed key file generation code finally and also fixed commit and crunch_key functions so really now as much as i was getting to the point to do it the functions work securely now
bugfix: got rid of mmap secmem allocation code but the source file remains. the primitive to use mmap is at a certain reality based point mlockall completes the same idea so the notion is also then is that you need root priveleges within the given terminal to lock the memory space into real memory. you might as much term this as a little paranoid but kind of to me remains tactful whereas it remains at a point tactfullness to me at least is certain the main idea to lock the memory to the ram memory instead of the page area (hard drive mapped memory allocation)

0.3.97b 2 years ago

bugfixes
added purge hot track list option

0.3.97b 2 years ago

bugfixes
added purge hot track list option

0.3.96b 3 years ago

bugfixes
added reseal hottrack list option so that when all tracked files are termed encrypted over previous sessions and they are (supposedly) decrypted with the -H option in decrypt mode, the files can be tracked over and reencrypted (previous session files in hottrack list) so that pure hottracking can be further addeuced with the programs capability

0.3.96b 3 years ago

bugfixes
added reseal hottrack list option so that when all tracked files are termed encrypted over previous sessions and they are (supposedly) decrypted with the -H option in decrypt mode, the files can be tracked over and reencrypted (previous session files in hottrack list) so that pure hottracking can be further addeuced with the programs capability

0.3.95b 3 years ago

minor bugfix in recovery database entry creation

0.3.94b 3 years ago

directory tree menu selection fixes

0.3.94b 3 years ago

directory tree menu selection fixes

0.3.92b 3 years ago

menu bugfix,directory tree menu works correctly now (i hope)

0.3.91b 3 years ago

menu bugfix

0.3.90b 3 years ago

bugfixes for hot track file menu selection
added menu for encrypting over directory tree

10 years ago

0.3.1b:
added aes/rijndael cipher
bugfixes
0.3.2b:
minor feature enhancements
important bugfixes
0.3.32b-bf#1:
important bugfixes
added new ciphers
bf#1:another important bugfix
0.3.4b:
important bugfixes
added recovery directory/database:
all files specified for encryption are stored in a recovery database as plaintext for now, the permissions on the recover directory are set to 0(zero) and recoverydb files will not be able to modified or read unless permissions are changed by the user explicitely
added security mode: for encryption,
the '--secure, -f' flag specifies to not store encrypted plaintext files in the recovery database for the session
0.3.4b-bf#1:
important bugfix
0.3.5b:
important bugfixes
added new option ' --masterkey, -m':
all encryption keys are written in a master key list in the '~/.cpdu/.keystore' directory. any encryption key used can be used as a session key in a decryption session simply by using the ' --masterkey, -m' flag. the program searches for the appropriate key based on hash data in the encrypted file.
it is not encrypted internally but to make it a point, it is "exportable" so you can save it when you leave for a while to an external media/disk to keep files safe. this way you will never lose your encryption keys as well as making the program much more useful.

an example is when we encrypt the file 'hackermeeting.mpg' with:
cpdu -ep hackermeeting.mpg -f
afterwards we can use the -m flag to decrypt with the proper key without having to type it in:
cpdu -dmp hackermeeting.mpg
then you can cut/move the key list to an external media for security.

remember to read the README-0.3.5b in the source directory

0.3.5b-bf#1:
important bugfix

0.3.6b:
very important decryption bugfix
added generate random keyfile
added use file/keyfile for session key
bugfix

0.3.7b:
header information is now encrypted so margin of security for cpdu is now high level in tandem with compression primitive
base64 is disabled until bug is fixed

0.3.8b:
bzip compression added
bzip works but sometimes there is zero byte truncation of files so i added a simple loop into the decompression routine again. is there randomization in bzip ? probably not...

bf-1: serious bugfix sorry but i didnt know about somthing that could hurt alot of encrypted files, its actually not that bad if you have encrypted files without the compression flag and you get the error truncation detected just do the following:
add // in front of line 665,
if ( vencrypt[0] > 0 ) decompress = 1; else decompress = 0;
and make it
// if ( vencrypt[0] > 0 ) decompress = 1; else decompress = 0;

then decrypt the files and then change the line back to,
if ( vencrypt[0] > 0 ) decompress = 1; else decompress = 0;

bf-2: improved encryption/decryption routine to handle crypt blocks correctly

bf-3: improved progress info code

0.3.81b:
permission bugfix
progress update fix
client/server code in progress...

0.3.82b:
added create volatile key...
this option enables making low length/entropy keys to full keyspace keys with secure random (volatile) key data and commits the new volatile key to the key database... this is dangerous if you accidentally missplace the keydb or delete it but accordingly makes all low entropy keys full entropy and allows them not to be lost...
this is good key security/management practice and makes the program much more secure

client/server code in progress... need coder help if anyone wants to help me with it....

0.3.83b-cygwin:
latest version for cygwin and hopefully linux due to not being able to utilize a linux machine. ive been using windows for a while becuase my computer had gotten stolen. archiveing updates have been made like an auto naming feature for naming archives with the first specified file specified on the command line or the directory specified to be archived if a directory is specified. also there is a -A archive feature to manually specify an archive name and if an extension is not specified the ext. '.cpdu.ar' will be used. so -a is for autonaming archives with first file entry name and -A is for direct specification of an archive name. also i added a wipearchdir, -W flag for wiping encrypted archive directories after archive creation. the entries are secure wiped....
progress updates have been made also as well as program status updates iterating program status while running

0.3.84b:
added functional log capability and edited progress update to make it to a state in compliance

0.3.85b: added file transfer capabilities without public key encryption support and its functionality. you can send encrypted files over the net using a client server notation but considering the point to have said, you need to transfer keys with a contrived escrow method for now. logging is not included with this version.
bugfixes
progress update fixes

12345678910
product-maker Base: 4 x 5.0 Ratings
Be the first to comment
File (click to download) Version Description PackagetypeArchitectureRelease Channel Downloads Date Filesize DL OCS-Install MD5SUM
*Needs pling-store or ocs-url to install things
Pling
0 Affiliates
Details
license
version
0.49.6b-linux-unix (discontinued)
updated Jul 13 2020
added Oct 28 2008
downloads 24h
0
mediaviews 24h 0
pageviews 24h 2
System Tags app software