Encrypting A File

ENCRYPTION

Edited August 29, 2008 by jibnet (see edit history)

Can i see the codes pls?

Wait... this is encryption? I clicked on the first topic I saw without reading, read the description and thought "Oh, yet another ascii shift."

Seriously, how can that even be called "encryption" anymore? At least have some xor's in there.

Someone can brute-force-check an alphanumeric sequence like that with a dictionary file in a few minutes.

Just by looking at the output of that you can tell it'd follow Zipf's Law. (see here)

Then it'd be a matter of finding out what (sub)language the author's writing this in and then the final ascii-substitute-until-we-find-dictionary-matches algorithm.

 

Anyway, following that logic...

"Well, we all know that writing an operating system in C is not a very hard task because we can do low-level programming.

Just make a kernel to handle interrupts and with a valid algorithm make sense out of them.

Example: To create a simple kernel we can make a source file that has a main() function with a self-referencing goto.

Or an infinite while loop. Or we can just have it display "hello world!\n" or any other random thing we can think of.

I have a kernel which can do things with interrupts and make lots of different results out of them.

It's at https://www.kernel.org/."

 

... needless to say, this post's making a strawman that doesn't really mean anything out of a very complex subject.

I know it's a year old, but come on, why is this type of stuff still floating around?

if you think some ascii number shifting is too low-leveled encryption, why don't you use some bitwise operation? like this example: 1001001 >> 2 = 0010010but remember to store the '01' from the end because if not it will be lost forever.I haven't made any program with this logic yet, but I guess with more advanced logic it worths some try.

if you think some ascii number shifting is too low-leveled encryption, why don't you use some bitwise operation?

like this example:

1001001 >> 2 = 0010010

Pretty simple. Because bit-shifting like that and storing the extra stuff would require more computation. It's better

off to do a cyclic shift than what you're suggesting.

 

What I'm saying here is that any one operand instruction is too simple. You can break the stuff into legible messages

faster than it'd take you to write the original message. Of course choosing one possibility out of n combinations would still

be a slight problem (hence why you'd use a dictionary attack in many cases) but still quite fast.

 

Now I'm not saying that linear bit-shifts and numerical shifts are bad. They're pretty nice actually, when they're used properly.

Simple one operation encoders that can be programmed by total newbies don't count as serious stuff.

I don't like to say that - nor am I trying to be condescending towards newbs, but it's what I've seen.

 

If I were to try to make an encryption program, I'd probably use cyclic shifts (personal preference), xors, and a lookup table with

prime numbers to start. There, code that properly and I'd start worrying about the security of the program when someone gets

a Cray supercomputer to work on this thing and the Riemann Hypothesis has been proven. Methodwise, we know that nothing

is unbreakable, but it's how long it'd take to break that matters. Since that bit shift would probably have O(n) complexity in encoding

and is reversible without serious caveats (check out the last steps in the encoding of Salsa20 if you care to see examples),

I'd say it'd have O(n) time to decode as well. That's low-level cryptography to me.

Well we all know that encrypting in C is not difficult task since we have access to low level programming.. Now to encrypt a simple text file we can have the following procedureJust read a single character from a file and then change its value with a valid algorithm and then write it to some other file which wil become the encrypted version of the file.
An Example:
a file has in it the following text "Love". Now all we need to do is get the ascii code for it and then add 7 to it and then write it to the other file. this way the file will get encrypted.
I have a code which encrypts text files into very complicated codes..
If you need the source code then please reply

you know what if all encrypting are SO easy to to crack like this
then hackers dreams became true
what you offers here is not a good encrypting
but it is good training too
if you rely like to do good encrypting
you need to find a library that can do all the work for you
since i didn't tray it i have no recommendation
only hop you find what you are looking for
good luck