From: "Huber, George K CECOM RDEC STCD SRI" <George.K.Huber@us.army.mil>
To: linux-c-programming@vger.kernel.org
Subject: RE: Basic C encryption
Date: Tue, 8 Jul 2003 16:03:30 -0400 [thread overview]
Message-ID: <DDFD9B60F648D411AD670000F80822EA03FCAAB7@mail7.monmouth.army.mil> (raw)
-----Original Message-----
From: Jan-Benedict Glaw [mailto:jbglaw@lug-owl.de]
Sent: Tuesday, July 08, 2003 2:52 PM
To: linux-c-programming@vger.kernel.org
Subject: Re: Basic C encryption
Jan-Benedict Glaw wrote:
>On Tue, 2003-07-08 13:48:14 -0400, Huber, George K CECOM RDEC STCD SRI
<George.K.Huber@us.army.mil>
>wrote in message
<DDFD9B60F648D411AD670000F80822EA03FCAAB6@mail7.monmouth.army.mil>:
>> Just add one.
[...]
>Nice examples, but mostly worthless. It was asked to "encrypt" a
>function (or a class/instance), not a file. Starting with the binary,
>you'd first need to find your function/method. Note that objects per se
[...]
actually read the original post, quoted below:
"Hi, I need a small, basic way to encrypt a binary file saving a custom
class from a windoze 32 proyect.
For example, add +1 to each character that is about to be saved in the
disk. How would that be?"
The original poster wanted to encrypt a binary file. The question that he
asks is how to add a one to each characte (byte) being saved to disk -
exactly what my examples show.
George Huber
next reply other threads:[~2003-07-08 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 20:03 Huber, George K CECOM RDEC STCD SRI [this message]
2003-07-08 20:09 ` Basic C encryption Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2003-07-08 17:48 Huber, George K CECOM RDEC STCD SRI
2003-07-08 18:52 ` Jan-Benedict Glaw
2003-07-08 14:13 Fabio Miranda Hamburger
2003-07-08 14:41 ` Jan-Benedict Glaw
2003-07-08 14:33 ` Fabio Miranda Hamburger
2003-07-08 14:48 ` Jan-Benedict Glaw
2003-07-08 15:08 ` Glynn Clements
2003-07-08 15:26 ` Fabio Miranda Hamburger
2003-07-08 16:01 ` Jan-Benedict Glaw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DDFD9B60F648D411AD670000F80822EA03FCAAB7@mail7.monmouth.army.mil \
--to=george.k.huber@us.army.mil \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).