Author Topic: This lisp creates itself with the dwg in the same folder  (Read 11752 times)

0 Members and 1 Guest are viewing this topic.

HasanCAD

  • Swamp Rat
  • Posts: 1422
Re: This lisp creates itself with the dwg in the same folder
« Reply #15 on: October 18, 2010, 05:56:16 AM »
GENERAL COMMENT :
...
I am less than you in the securety, may be because of my gluttony of learning
But for this file I didnt load this file but loaded automatically when open any dwg

I would have been able to solve this immediately.
I appreciate your help.

So, there is a lesson in that regard as well  :)
It is good lesson

Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: This lisp creates itself with the dwg in the same folder
« Reply #16 on: October 18, 2010, 05:58:29 AM »
GENERAL COMMENT :
...
I am less than you in the securety, may be because of my gluttony of learning
But for this file I didnt load this file but loaded automatically when open any dwg


You must have got the file from SOMEWHERE .. do you know where ?
kdub, kdub_nz in other timelines.
Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

HasanCAD

  • Swamp Rat
  • Posts: 1422
Re: This lisp creates itself with the dwg in the same folder
« Reply #17 on: October 18, 2010, 06:04:49 AM »
You must have got the file from SOMEWHERE .. do you know where ?

this is habben when we open any cad file for a project we working on
It's a bridge project comes from a consultant company located in US.

Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: This lisp creates itself with the dwg in the same folder
« Reply #18 on: October 18, 2010, 06:12:09 AM »
You must have got the file from SOMEWHERE .. do you know where ?

this is habben when we open any cad file for a project we working on
It's a bridge project comes from a consultant company located in US.

Well, you'd better tell them that they are distributing a virus.

Point them to this thread if necessary ....
kdub, kdub_nz in other timelines.
Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

HasanCAD

  • Swamp Rat
  • Posts: 1422
Re: This lisp creates itself with the dwg in the same folder
« Reply #19 on: October 18, 2010, 06:26:36 AM »
Well, you'd better tell them that they are distributing a virus.

There is no way to protect our system from coping this file
May be they dont have a solution
May be they don know that they system is infected
 
ny the way I searched for this file and found but in chines language (I think that)
see this
http://www.google.com.eg/search?q=basepath+baseacad+acaddocpath++r-acaddoc+w-basepath+rl-acaddoc++acaddoclsp++c-acaddocname&sourceid=ie7&rls=com.microsoft:en-us:IE-SearchBox&ie=&oe=&redir_esc=&ei=byC8TN_-I8q6jAeL9disDg

Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: This lisp creates itself with the dwg in the same folder
« Reply #20 on: October 18, 2010, 06:34:38 AM »
I meant search YOUR machines and server, not google , sorry for confusion :)

Quote
There is no way to protect our system from coping this file

Are you working from their server or yours ??


Quote
May be they dont have a solution

You need to DELETE the incorrect files. ... simple as that ... then add a good file to the ACAD.EXE folder.

kdub, kdub_nz in other timelines.
Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

HasanCAD

  • Swamp Rat
  • Posts: 1422
Re: This lisp creates itself with the dwg in the same folder
« Reply #21 on: October 18, 2010, 07:11:55 AM »
There was no confusion, I searched my machine and delete that file.
But while I am on net I made that search.

We working from our server,

Let me tell you from the beginning
Our system was ok,
We received cad files related to a project
Automatically this lisp file created in the same path of the opened file when we open any file related to this project,
After that the infection attack the AutoCAD itself and this lisp created at the same path of opened file.

So I am search for a solution for that

Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: This lisp creates itself with the dwg in the same folder
« Reply #22 on: October 18, 2010, 07:26:47 AM »

You already have the solution :


Quote
May be they dont have a solution

You need to DELETE the incorrect files. ... simple as that ... then add a good file to the ACAD.EXE folder.



And ensure that next time you get files from the client the "acadDoc.Lsp" file is NOT included with the files.

Don't forget to search ALL machines in your office because the code you posted copies the file from the DWG folder back to the ACAD.EXE folder.

kdub, kdub_nz in other timelines.
Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

HasanCAD

  • Swamp Rat
  • Posts: 1422
Re: This lisp creates itself with the dwg in the same folder
« Reply #23 on: October 18, 2010, 07:27:10 AM »
Kerry

Thanks for deleting the infected file

Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: This lisp creates itself with the dwg in the same folder
« Reply #24 on: October 18, 2010, 07:28:11 AM »
Kerry

Thanks for deleting the infected file

My pleasure :)
kdub, kdub_nz in other timelines.
Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

Lee Mac

  • Seagull
  • Posts: 12913
  • London, England
Re: This lisp creates itself with the dwg in the same folder
« Reply #25 on: October 18, 2010, 10:59:15 AM »
Its pretty badly written, but it does rely on you having an ACADDOC.lsp already on the system to duplicate - tbh I've seen worse code of this type specifically engineered to create multiple ACADDOC.lsp's to change Sys Vars and Registry Values  :|

Still - not nice, and I agree with Kerry's sentiment about understanding (at least partially) the code you are about to run.