Article View: comp.lang.asm.x86
Article #79Re: Absolute addresses, relative addresses
From: Eric Minso
Date: Wed, 03 Sep 2003 16:37
Date: Wed, 03 Sep 2003 16:37
52 lines
4334 bytes
4334 bytes
"Beth" <BethStone21@hotmail.NOSPICEDHAM.com> wrote in message news:<fZi5b.138$qL6.113704@newsfep1-win.server.ntli.net>... > > You still have to be _very careful_...virus writers are in the > business of duping people into doing stupid things... > [.....] > the bullet-proof vest, we _DON'T_ want the situation of seeing you > walking around with a big bullet hole in you...the satisfaction of > being able to say "I told you so" holds none of its usual smugness in > that situation... > > Beth :) Thank you for your long answer :-) You can be sure I always have been very careful :) I just read their source to see what they do, what they read, what they write, and once I understand, I rewrite it in my own way. When I first talked about viruses, many people has reacted, but don't forget it is one possibility between several ones. At the origin, I wanted to know how programs (of which, the viruses) could "infect" an executable. The reason is beacuse I don't have the source of the executables to protect. I'm not trying to write the total protection, I know that a good hacker will always find a way to crack the software, but I want to have a protection. The company where I do my training period is a computer manufacturer : they assemble computers and install standard configurations (Windows XP + some softwares). They also give a CD-ROM with many application that the user can install. In order to lower the computer cost, the sofwares available on the CD-ROM are locked and the customer do not pay the licence for them. A serial number allows him to unlock only three or four softwares that he can choose. The interest for the customer is that he installs only softwares he wants. A few time ago, some software editors have claimed that the protection system is too easy to hack and asked to the company a better protection for their softwares. So I was asked to study a way to protect these executables. Eric.
Technical Details
Message-ID:
<7db38e60.0309030837.18c5f094@posting.google.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!feed.uncensored-news.com!sn-xit-02!sn-xit-06!sn-post-01!supernews.com!corp.supernews.com!news.crayne.org!clax86!robomod!not-for-mailReferences:
<7db38e60.0308250121.6135ebc1@posting.google.com> <bieiii$8dsqb$1@ID-165313.news.uni-berlin.de> <7db38e60.0308260511.4b9a371@posting.google.com> <bigi38$36e$1@titan.btinternet.com> <7db38e60.0308270023.1d3f4cf@posting.google.com> <bij247$3j$1@titan.btinternet.com> <7db38e60.0308280508.6205dd69@posting.google.com> <bilu4t$g7n$1@titan.btinternet.com> <7db38e60.0308290140.1817fff2@posting.google.com> <fZi5b.138$qL6.113704@newsfep1-win.server.ntli.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: feaef,44f17f79ebe31523 X-Google-Attributes: gidfeaef,public X-Google-Thread: 1093da,44f17f79ebe31523 X-Google-Attributes: gid1093da,public X-Google-Thread: 114917,44f17f79ebe31523 X-Google-Attributes: gid114917,public X-Google-Thread: f7d8d,44f17f79ebe31523 X-Google-Attributes: gidf7d8d,public X-Google-ArrivalTime: 2003-09-03 10:58:33 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!feed.uncensored-news.com!sn-xit-02!sn-xit-06!sn-post-01!supernews.com!corp.supernews.com!news.crayne.org!clax86!robomod!not-for-mail From: minso@altern.org (Eric Minso) Newsgroups: comp.lang.asm.x86,alt.lang.asm,alt.os.assembly,borland.public.tasm Subject: Re: Absolute addresses, relative addresses Approved: CLAX86 Moderators <ccrayne@crayne.org> Date: 3 Sep 2003 09:37:46 -0700 Organization: http://groups.google.com/ Message-ID: <7db38e60.0309030837.18c5f094@posting.google.com> X-CLAX86-Policy: http://www.pacificsites.com/~ccrayne/clax86.html X-CLAX86-Faq: http://www.faqs.org/faqs/by-newsgroup/comp/comp.lang.asm.x86.html X-CLAX86-Info-1: Send submissions to comp-lang-asm-x86@moderators.isc.org X-CLAX86-Info-2: Send technical complaints to ccrayne@crayne.org X-CLAX86-Info-3: Send complaints about policy to ccrayne@crayne.org X-Comment: moderators do not necessarily agree or disagree with this article. References: <7db38e60.0308250121.6135ebc1@posting.google.com> <bieiii$8dsqb$1@ID-165313.news.uni-berlin.de> <7db38e60.0308260511.4b9a371@posting.google.com> <bigi38$36e$1@titan.btinternet.com> <7db38e60.0308270023.1d3f4cf@posting.google.com> <bij247$3j$1@titan.btinternet.com> <7db38e60.0308280508.6205dd69@posting.google.com> <bilu4t$g7n$1@titan.btinternet.com> <7db38e60.0308290140.1817fff2@posting.google.com> <fZi5b.138$qL6.113704@newsfep1-win.server.ntli.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-0.6, required 4, MAILTO_TO_SPAM_ADDR 0.38, QUOTED_EMAIL_TEXT -0.48, REFERENCES -0.50) X-UIDL: N&i!!#Cb!!/4U"!HFZ"! X-Complaints-To: abuse@supernews.com Lines: 53