linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: Basic C encryption
Date: Tue, 8 Jul 2003 22:09:40 +0200	[thread overview]
Message-ID: <20030708200940.GT20605@lug-owl.de> (raw)
In-Reply-To: <DDFD9B60F648D411AD670000F80822EA03FCAAB7@mail7.monmouth.army.mil>

[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]

On Tue, 2003-07-08 16:03:30 -0400, Huber, George K CECOM RDEC STCD SRI <George.K.Huber@us.army.mil>
wrote in message <DDFD9B60F648D411AD670000F80822EA03FCAAB7@mail7.monmouth.army.mil>:
> Jan-Benedict Glaw wrote:
> >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.

"custom class"?

> 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.

If it was ment that way - you're right and I claim to be unable to
read:)

However, my reading was that he wanted to hide some
functions/methods/classes from a binary executable file, which is a
non-trivial task, esp. because unencrypting it is much more easier than
encrypting it.

For the purpose of simply encrypting some random data, I'd say to
install gnupg and use one of its simple password ciphers. Then, he even
gets high-quality encryption for the price of only writing some little
wrapper (or using gpgme, which IMHO isn't really easier than writing a
wrapper for that purpose...).

If I misread the original posting - I'm really sorry for submitting TOFU
then...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-08 20:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 20:03 Basic C encryption Huber, George K CECOM RDEC STCD SRI
2003-07-08 20:09 ` Jan-Benedict Glaw [this message]
  -- 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=20030708200940.GT20605@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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).