: : The only "mucking about" performed is that the application you've written no longer functions (or even deletes itself)... NOTHING ELSE in the system is touched. Legitimate ways do not always work, and at times when they do it can take months or even years... I've "eaten" enough time over the years to have learned this. : Irrelevant, IMHO. (Note: IANAL). If someone steals something from you and has it in his house, does that give you the right to enter and search his house to recover the stolen item? I don't think so. Do that in my house and you're likely to get shot.
If legitimate ways don't always work, tough. It's a result of living in a society in which people other than yourself also have rights. Deal with it. Nothing's perfect.
As much as this "debate" seems like pissing in the wind... you are comparing apples to oranges. Software developers have been putting time and usage locks in their products for ages. It's nothing new. As for "deal with it", obviously you're not in business for yourself and know nothing of what it's like to have to eat time ($). Time and usage locks in software are legitimate. As for "nothing's perfect", your world is what you make it... there's nothing wrong with striving for perfection.
One last note (pardon me), but what are "IMHO" and "IANAL" supposed to stand for? I'm not familiar with either of those acronyms.
: As much as this "debate" seems like pissing in the wind... you are comparing apples to oranges. Software developers have been putting time and usage locks in their products for ages. It's nothing new.
You were not talking about time and usage locks, you were talking about virii. That's comparing apples and oranges.
: As for "deal with it", obviously you're not in business for yourself and know nothing of what it's like to have to eat time ($). Time and usage locks in software are legitimate.
Agreed, but again, you were talking about solving such business problems with a virus, not time and usage locks. And I do know what it's like to 'have to eat time'; I've had my software ripped off before.
The point is that virii are [b]never[/b] acceptable solutions. Ask a lawyer about the consequences of infiltrating someone else's computer with a virus, even if it only removes unpaid-for software. Deal with such problems in legally acceptable ways or open yourself to liability. The analogy of breaking into someone's house to recover stolen property is apt. You don't have that right--have the police do it with a proper search warrant.
I understand your irritation at having to pay lawyers to deal with these problems, but that's a cost of doing business, just like insurance. If you can't handle it, perhaps you should consider a different means of earning a living. But please don't try to use this example as an excuse for writing virii. It doesn't fly.
: : One last note (pardon me), but what are "IMHO" and "IANAL" supposed to stand for? I'm not familiar with either of those acronyms. : In My Humble Opinion. I Am Not A Lawyer.
: : As much as this "debate" seems like pissing in the wind... you are comparing apples to oranges. Software developers have been putting time and usage locks in their products for ages. It's nothing new. : : You were not talking about time and usage locks, you were talking about virii. That's comparing apples and oranges.
[blue]I stand corrected. I should have made that distinction clear at the start.[/blue]
: : : : As for "deal with it", obviously you're not in business for yourself and know nothing of what it's like to have to eat time ($). Time and usage locks in software are legitimate. : : Agreed, but again, you were talking about solving such business problems with a virus, not time and usage locks. And I do know what it's like to 'have to eat time'; I've had my software ripped off before.
[blue]Again as before, I should have clarified that. As for my eating time comment, it wasn't meant to be harsh... many have no idea of the concept.[/blue]
: : The point is that virii are [b]never[/b] acceptable solutions.[blue]True[/blue] Ask a lawyer about the consequences of infiltrating someone else's computer with a virus, even if it only removes unpaid-for software.[blue]<---Personally, I'd still debate that (as I said, as long as your software is the only thing that stops... nothing else is touched... not even the data they created with it)}[/blue] Deal with such problems in legally acceptable ways or open yourself to liability. The analogy of breaking into someone's house to recover stolen property is apt. You don't have that right--have the police do it with a proper search warrant. : : I understand your irritation at having to pay lawyers to deal with these problems, but that's a cost of doing business, just like insurance.[blue]<---And in an ongoing contract, with payment in phases, I still find such lockouts a good incentive for payment}[/blue] If you can't handle it, perhaps you should consider a different means of earning a living. But please don't try to use this example as an excuse for writing virii.[blue]<---I never intended to}[/blue] It doesn't fly. : : : : : One last note (pardon me), but what are "IMHO" and "IANAL" supposed to stand for? I'm not familiar with either of those acronyms. : : : In My Humble Opinion. I Am Not A Lawyer. : : [blue] LOL... I've never have guessed! Thanks.[/blue] :
hi. dudes wan make a virus that heart someone ok..... mail me i will tell u a very unique method of virus bulding but it is top sercite [email protected]
Hello newbies, a house full of toxic waste... Give me convenience or give me death!
A virus is a program file infector, it is either resident (captures INT 21h vector) or non-resident (uses findfirst findnext). To be able to construct a binary image which could tag itself to the end of executables it must be coded in assembly, for changing its offset in the binary image will change the offsets of its variables. There is a technique around this.
To get the difference to calculate the offsets of your variables do this: call mytrick mytrick: pop bp sub bp,offset mytrick
Then to access your variables: mov dx,[bp+offset var]
Simply encode a 3-byte near jmp instruction using as a displacement the unsigned size of the host file in bytes. Copy the first three bytes of the binary image (*.com) and replace it with your jump at 100h and place the virii code at the end of the host binary image.
More complex viruses can be created that interpret the .EXE file header.
Making your virus polymorphic: Simple! Decrypt your encrypted code with a known key, execute, generate a new key, store the new key in your programs data area, re-encrypt the decrypted portion,write new encryption back where the original encryption was stored,and overwrite your own programs executable with the changes. ...
Comments
:
: The only "mucking about" performed is that the application you've written no longer functions (or even deletes itself)... NOTHING ELSE in the system is touched. Legitimate ways do not always work, and at times when they do it can take months or even years... I've "eaten" enough time over the years to have learned this.
:
Irrelevant, IMHO. (Note: IANAL). If someone steals something from you and has it in his house, does that give you the right to enter and search his house to recover the stolen item? I don't think so. Do that in my house and you're likely to get shot.
If legitimate ways don't always work, tough. It's a result of living in a society in which people other than yourself also have rights. Deal with it. Nothing's perfect.
One last note (pardon me), but what are "IMHO" and "IANAL" supposed to stand for? I'm not familiar with either of those acronyms.
You were not talking about time and usage locks, you were talking about virii. That's comparing apples and oranges.
: As for "deal with it", obviously you're not in business for yourself and know nothing of what it's like to have to eat time ($). Time and usage locks in software are legitimate.
Agreed, but again, you were talking about solving such business problems with a virus, not time and usage locks. And I do know what it's like to 'have to eat time'; I've had my software ripped off before.
The point is that virii are [b]never[/b] acceptable solutions. Ask a lawyer about the consequences of infiltrating someone else's computer with a virus, even if it only removes unpaid-for software. Deal with such problems in legally acceptable ways or open yourself to liability. The analogy of breaking into someone's house to recover stolen property is apt. You don't have that right--have the police do it with a proper search warrant.
I understand your irritation at having to pay lawyers to deal with these problems, but that's a cost of doing business, just like insurance. If you can't handle it, perhaps you should consider a different means of earning a living. But please don't try to use this example as an excuse for writing virii. It doesn't fly.
:
: One last note (pardon me), but what are "IMHO" and "IANAL" supposed to stand for? I'm not familiar with either of those acronyms.
:
In My Humble Opinion. I Am Not A Lawyer.
:
: You were not talking about time and usage locks, you were talking about virii. That's comparing apples and oranges.
[blue]I stand corrected. I should have made that distinction clear at the start.[/blue]
:
:
: : As for "deal with it", obviously you're not in business for yourself and know nothing of what it's like to have to eat time ($). Time and usage locks in software are legitimate.
:
: Agreed, but again, you were talking about solving such business problems with a virus, not time and usage locks. And I do know what it's like to 'have to eat time'; I've had my software ripped off before.
[blue]Again as before, I should have clarified that. As for my eating time comment, it wasn't meant to be harsh... many have no idea of the concept.[/blue]
:
: The point is that virii are [b]never[/b] acceptable solutions.[blue]True[/blue] Ask a lawyer about the consequences of infiltrating someone else's computer with a virus, even if it only removes unpaid-for software.[blue]<---Personally, I'd still debate that (as I said, as long as your software is the only thing that stops... nothing else is touched... not even the data they created with it)}[/blue] Deal with such problems in legally acceptable ways or open yourself to liability. The analogy of breaking into someone's house to recover stolen property is apt. You don't have that right--have the police do it with a proper search warrant.
:
: I understand your irritation at having to pay lawyers to deal with these problems, but that's a cost of doing business, just like insurance.[blue]<---And in an ongoing contract, with payment in phases, I still find such lockouts a good incentive for payment}[/blue] If you can't handle it, perhaps you should consider a different means of earning a living. But please don't try to use this example as an excuse for writing virii.[blue]<---I never intended to}[/blue] It doesn't fly.
:
: :
: : One last note (pardon me), but what are "IMHO" and "IANAL" supposed to stand for? I'm not familiar with either of those acronyms.
: :
: In My Humble Opinion. I Am Not A Lawyer.
:
: [blue] LOL... I've never have guessed! Thanks.[/blue]
:
mail me i will tell u a very unique method of virus bulding
but it is top sercite
[email protected]
a house full of toxic waste...
Give me convenience or give me death!
A virus is a program file infector, it is either resident
(captures INT 21h vector) or non-resident (uses findfirst findnext).
To be able to construct a binary image which could tag itself
to the end of executables it must be coded in assembly,
for changing its offset in the binary image will change
the offsets of its variables.
There is a technique around this.
To get the difference to calculate
the offsets of your variables do this:
call mytrick
mytrick:
pop bp
sub bp,offset mytrick
Then to access your variables:
mov dx,[bp+offset var]
Simply encode a 3-byte near jmp instruction using as a displacement
the unsigned size of the host file in bytes.
Copy the first three bytes of the binary image (*.com) and replace it
with your jump at 100h and place the virii code at the end of the
host binary image.
More complex viruses can be created that interpret the .EXE file header.
Making your virus polymorphic:
Simple! Decrypt your encrypted code with a known key, execute,
generate a new key, store the new key in your programs data area,
re-encrypt the decrypted portion,write new encryption back where
the original encryption was stored,and overwrite your own programs
executable with the changes.
...
We hate mind-control,
we are words...