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 18:01:28 +0200	[thread overview]
Message-ID: <20030708160128.GM20605@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0307080924450.28267-100000@ns.isi.ulatina.ac.cr>

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

On Tue, 2003-07-08 09:26:44 -0600, Fabio Miranda Hamburger <fabmirha@ns.isi.ulatina.ac.cr>
wrote in message <Pine.LNX.4.44.0307080924450.28267-100000@ns.isi.ulatina.ac.cr>:

> C'mon guys. I just need a basic encrypt from project of a subject of my
> bachelor.
> It's not big deal. I am out of time also.
> How can I add 1 to the ascii value of a char and write it to disc. Then,
> When am I going to read it, I have to reduce to 1 the ascii value.

So you want no compile your program, modify the binary and after
startup, you want the binary to "cure" itself?

Some systems won't even allow that (sometimes, you can either execute
_or_ modify code, but not both). Further more, you'd have to localize
your target function. Even that's a hard part (maybe you can play with
explicitely named sections), but you'll need in-depth knowledge of the
binary format your binary uses (most probably ELF or ELF64) or you need
to use the libbfd.

So - there's on "simple" way to achieve this.

Or this one - compile your function into a separate .o file and
dynamically link it with dlopen()/dlsym()/dlclose(). But then, the
reader is presented with a single object of interest:)

Again - easy to de"crypt".

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 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 14:13 Basic C encryption 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 [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 20:03 Huber, George K CECOM RDEC STCD SRI
2003-07-08 20:09 ` 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=20030708160128.GM20605@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).