Home All Groups Group Topic Archive Search About

How to create a pattern file package creator on spyware

Author
11 Oct 2005 3:15 PM
beginner
Greetings!

I would like to ask on how to create a pattern file package on spyware.
Using Visual Basic language. Thank you

beginner

Author
11 Oct 2005 4:16 PM
Jeff Johnson [MVP: VB]
"beginner" <junarlandi***@gmail.com> wrote in message
news:1129043743.851191.105210@g14g2000cwa.googlegroups.com...

> I would like to ask on how to create a pattern file package on spyware.
> Using Visual Basic language. Thank you

Which (anti-)spyware application are you referring to? There are several....
Author
11 Oct 2005 7:28 PM
Steven Burn
"Jeff Johnson [MVP: VB]" <i.get@enough.spam> wrote in message
news:usCgu8nzFHA.3380@TK2MSFTNGP10.phx.gbl...
>
> "beginner" <junarlandi***@gmail.com> wrote in message
> news:1129043743.851191.105210@g14g2000cwa.googlegroups.com...
>
> > I would like to ask on how to create a pattern file package on spyware.
> > Using Visual Basic language. Thank you
>
> Which (anti-)spyware application are you referring to? There are
several....

He has been given a school project that requires he write his own (or
atleast, that's the impression I got from his PM's over at Spyware Data).
He's not given as much info here, so below is the PM he sent myself
concerning it;

[QUOTE]
Thank you for your positive response on my queries about the problem. If you
don't mind again. The one I sent you is our Module A-Client. Hope you will
understand...

Module-C Pattern File Package Creator
Requirements:
Create a standalone application that accepts detection and cleanup
information for
different spyware, and outputs a pattern file package (Specification A).
This
application should perform the following actions:
.. Use the following format for command-line execution:
<program name> <raw spyware info file path>
Action: Create pattern file package containing the detection and clean
information for <spyware name> using the raw info for detection and
cleanup of a number of spyware in <raw spyware info file path>.
(<program name> and <raw spyware info file path> may vary)
Example:
myptngen.exe SPYWARE_TEST1.DATA
Module C: Pattern File Package Creator
Version 1.0 06.01.05 10
Action: the program reads the file SPYWARE_TEST1.DATA, which contains
the raw spyware info (i.e. data needed to detect and clean a number of
spyware). The program then outputs a pattern file package which can be
used with module A.
Note: SPYWARE_TEST1.DATA is not the pattern file package, but a raw
spyware info file, which is another file (with its own file format). The
format
for the raw spyware info file should be documented as part of the
documentation for this module.
.. Create a database of previous spyware information and use it in generating
a
new pattern file package for additional spyware information. This should be
made possible without having to input previous spyware information.
Note: the "database" does not have to be a relational database system. This
can be as simple as a simple text file.
.. Make this application user friendly to generate outputs at a faster pace.
.. Make the data storage location configurable - e.g. if the storage is a
relational database, make the connection information configurable; if the
storage is a file, make the filename configurable.
Additional features:
To gain extra points, add the following features:
.. Automatic spyware information extraction, given a file sample
.. Security provisions against unauthorized access of internal data storage
Outputs:
Provide the following:
1. Source code - save to "/program/src".
2. Technical Specifications - save to "/doc/techspec".
?? Overall architecture - shows how a system is being deployed over a
network. This may be presented in diagrams with label along with a brief
explanation.
?? Module specifications - explains the application's features and how these
features are implemented. This may be presented by providing a general
description as well as a detailed input, process, and output of each
feature.
3. Pre-packaged program and data: package a pre-generated raw spyware info
file that contains detection and cleanup info for the test spyware (e.g.
file
hash, filename), with the compiled program for command-line execution
testing and save to "/program/bin in .ZIP format".
Version 1.0 06.01.05 11
Note: Package the said file in such a way that the program can be executed
right after decompressing the .ZIP file.
4. Build and compile instructions - save to "/doc/techspec".
?? System requirements
?? Procedure - discusses the step-by-step instruction of building and
compiling this application.
5. Installation Guide - save to "/doc/install".
?? System requirements - if there is a software requirement, include the
trial
program and download the URL, as well as the installation instructions.
?? Installation procedure - discusses the step-by-step instruction of
installing this application.
6. Third-party libraries and programs used - if applicable, save to
"/program/3rd_party/lib or /program/3rd_party/bin".
7. Documentation of third-party code, libraries, and programs used - include
in
Technical Specifications.
?? Name of third-party programs used
?? Reference URLs
*Note: Those who fail to comply will be disqualified.
8. User's Manual - save to "/doc/user".
?? Organize in such a way that contents are presented per
section and that these sections are entitled according to their use (e.g.
"How to use the Anti-spyware Client")
[/QUOTE]

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!
Author
12 Oct 2005 12:49 PM
beginner
The anti-spyware client will check in pattern file package whether the
spyware is exist or not. It will execute the two instruction detect and
clean, it could detect only or clean only or both.
Author
12 Oct 2005 1:03 PM
beginner
The spyware application that will made a pattern file package are
drop_files, process and registry editor.