Project Report on Steganography - file · Web viewSteganography is the science of hiding information in other information. Steganography is practiced from ages, and used in situations

T a b l e O f C o n t e n t s

Abstract ………………………………...................................................05

Chapter 1 Introduction

1.1 Need for the new system………………………………………………..

1.2 Detailed problem definition………………………………..

1.3 Project Scope…………………………………..

1.4 Presently Available Systems For trhe Same…………………….

1 . 4 .1 B l inds ide ………………………………….

1 . 4 .2 BMP S ec re t s ………………………..

1 . 4 .3 EZS t egno

1 . 4 .4 In The P i c tu r e s ( ITP )

1.5 Future Prospects……………………… 1.6 Organization Report……………………………….

Chapter 2 Analysis

2.1 Project Plan……………………………………………………………

2.2 Feasibility Study……………….

2.2.1 Technical Feasibility

2.2.2 Financial Feasibility

2.2.3 Resources Feasibility

2.3 Team Structure

Chapter 3 Design

3.1. Software Requirement Specification…………………………………..11

3.2 Risk Assessment

3.2.1 Performance Risk ……………………………………………...12

3.2.2 Cost Risk…………………………………………12

3.2.3 Support Risk

3.2.4 Scheduled Risk

Chapter 4 Modeling/ERP/DFD diagram (Project Work Flow)

4.1 ER Diagrams...............................................................................18

4.1.1 ER Diagram for Data Hiding

4.1.2 ER Diagram for Data Unhiding

4.2 Data Flow Diagram for Stegpro……………………………

4.2.1 Level 0 DFD

4.2.2 Level 1 DFD

4.2.3 Level 2 DFD

Chapter 5 Coding

5.1 Hardware Specification...........................................................................34

5.2 Platform...............................................................................34

5.3 Programming Language Used ..............................................................................35

5.4 Coding Style Followed

5.5 Coding

5.6 Screen Shots

Chapter 6 Testing

6.1 Formal Technical Reviews ......................................................................................45

6.2 Test Plan.........................................................................45

6.3 Test Cases And Test Result ……………………………………………….…….45

6.3.1 Unit Testing …………………………………………….…....46

6.3.2 Integration Testing………………………………….

6.3.3 Security Testing…………………………………………..

6.3.4 Peak Load Testing…………………………………………

Chapter 7 Software Cost Estimation

Chapter 8 Limitations & Scope

ABSTRACT:

S teganogr aphy i s t he s c i ence o f h id ing in f o rm a t i on in o ther

i n fo r m a t ion . S t e ganography i s p r ac t i ce d f r om ages , and u s ed in s i t ua t ions

wher e h i dden exchange o r com m un ica t ion o f i n fo r ma t ion i s r equ i r ed .

Cry p togr aphy — the s c i e nce o f wr i t i ng i n sec re t codes i s m os t l y c on fu s ed

w i th S t eganogr aphy . Cr yp togr aphy addr es se s a l l o f t he e l e me n t s neces s ary

f o r se cur e com mun i ca t i on over an in s ecur e c hanne l nam e ly p r i vacy ,

con f i den t i a l i t y , k ey exchange e t c . B u t c r yp togr aphy does no t a lways

p rov ide s a f e comm un ic a t ion . S t eganogr aphy fa r e s be t t e r s i nce i t i s t he a r t

o f conc ea led c omm un ic a t ion ; he re t he ve ry e x i s t e nce o f a m es s age i s

se c r e t . Whe reas t he goa l o f c ry p togr aphy i s t o mak e da t a unr eadab le by a

t h i r d par t y , t he goa l o f S t e ganography i s t o h i de t he da ta f rom a th i rd

par t y .

S t eganogr aphy i t s e l f has m any t y pes and var ian t s . Som e exam p le s

a re : da ta h id i ng in im ages ( t he re a r e m any i mage fo r ma t s ! ) , da t a h id ing

in aud io f i l e s , da ta h id ing in web page s , d ig i t a l wa te r m ark ing e t c .

S t eganogr aphy nowadays i s mor e soph i s t i ca t ed and m os t l y u se d in

con junc t ion w i th c r yp togr aphy and c ompr es s ion t ec hn iques .

T h i s p r o j ec t i s on t he t op i c d i s cus se d above . T h i s p r o j e c t i s a s i ncer e

e f f o r t t owar ds s tudy ing the ex i s t i ng s t eganogr aph ic t e chn ique s ; ge t

acqua in t ed w i t h var ious me t hods t o h ide t he ve r y p r e s ence o f

com mun i ca t i on f r om po t en t i a l hac ker s . I n t h i s p r o j e c t we s tudy var ious

S t eganogr aphy me thods , and im p lem en t t he m to c r ea t s t a t e -o f - t he -ar t

p roduc t . We e mphas i z e m ore on ach ie v ing the ma i n a im o f

S t eganogr aphy t o h ide t he p r e s ence o f com m un ica t i on . T he sc ope o f t h i s

p ro j ec t i s va s t , bu t we s tudy the l a t e s t r e s ear ch done i n t h i s f i e ld and

inc l ude t hose t h ings (a long w i t h t he own inpu t s , o f c ours e ! ) i n t he work ,

wh ich i s m os t r e l e van t i n t he p r e s en t wor ld o r der .

CHAPTER 1

INTRODUCTION

1.1 NEED FOR THE NEW SYSTEM :

Stegpro i s a da ta h id ing tool sa t i s fy ing above problem

def in i t ion . Users can use S tegpro to h ide any da ta in the i r

medium, and again unhide the i r da ta a t the o ther end.

This sub- topic expla ins the funct ional requi rements of

S tegpro . S tegpro requires user to do fo l lowing main th ings :

(1) Selec t the medium f i le .

(2) Selec t the f i les to be h idden.

(3) Set encrypt ion password.

(4) Set the qual i ty of the medium f i le . The qual i ty wi l l

dec ide how much da ta can be h idden in the medium.

The medium f i le may t ravel through any medium, such

as In te rnet , to the user a t the o ther end. At the o ther end,

the use r i s requi red to do fo l lowing tasks:

(1) Selec t the medium f i le ( i .e . in which the da ta i s

h idden) .

(2) Enter the requi red password.

(3) Save the ext rac ted da ta f i le .

The Hiding and Unhiding process of the Data f i les i s

combined as d i f ferent modules . The user has to se lec t whe ther he

has to h ide or unhide opt ion f rom the toolbar of the working form.

1.2 DETAILED PROBLEM DEFINITION

The goal of th is projec t i s to bui ld a product tha t sa t i s f ies the

descr ip t ion of the proposed sys tem. The product should inc lude

the fea tures of any eff ic ient S teganography tool . The product

should be user -f r iendly .

The fo l lowing se t of ques t ions resemble the problems tackled

by the produc t :

What type of s teganography to be done by the product?

In case of s teganography in images , what type of f i le

formats to be suppor ted by the sof tware?

What type of double protec t ion to be provided to the data?

What combinat ion of cryptography and image compress ion

to be used?

What measures to be implemented in the sof tware to ensure

tha t the whole process i s safe over the In ternet?

What measures are implemented in the sof tware to prevent

the s teganalysis of the h idden da ta?

What innovat ive fea ture i s provided by the sof tware?

1.3 PROJECT SCOPE

In this report many relevant issues were presented, from a technical point of view.

However, little has been done to motivate these studies. A more detailed

investigation of applications, and a comparison with current techniques in

steganography would have been interesting. For example, a thorough evaluation of

the advantages natural language-based techniques can offer over image-based

techniques could have offered valuable insights. An important contribution of this

project to natural language steganography is the linguistic sophistication of the

model for word-substitution put forward. The lexical models employed in current

substitution-based systems were often criticised and their inadequate behavior

usually described with respect to language theory. These phenomena could have

been demonstrated by example, showing texts and inadequate replacements carried

out by current stegosystems. A more detailed analysis of how common these

critical situations really are in typical text could have given clues for the

construction of such systems, to decide whether the additional complexity

introduced by statistical word-sense disambiguation is worth the effort. Other

linguistic models have been studied, in addition to the lexical ones, and put in

relation to each other, and to their use for steganographic purposes. The

steganographic aspects were then covered by information-theoretic models.

However, little has been done to justify this choice. It might have been fruitful to

present other characterizations of steganography and to compare their suitability to

natural language steganography

1.4 PRESENTLY AVAILABLE SYSTEM FOR THE SAME:

1.4.1 BLINDSIDE:

Blindside is a command-line utility that hides files in BMP's and has optional

encryption. Also available are Linux, HP, Solaris, and AIX versions, with

windows-based GUI promised soon.

1.4 .2 BMP SECRETS:

BMP Secrets is a BMP-based stego product for Windows with a decent interface

and a very large hiding capacity (~65% of carrier file). It includes built-in

encryption and ability to hide data within specific sub-areas of the image.

1.4 .3 EZSTEGNO:

EZStego is a GIF-based stego application from Romana Machado, the author of

Stego for Mac. It has similar steganographic functions as its Mac-based

predecessor, but is written in the platform-independent Java language instead.

1.4 .4 IN THE PICTURES (ITP):

ITP is a Windows 95-based stego program that hides data in BMP images. It offers

multiple unique keys so you can encrypt data intended for multiple recipients into

the same file. It has a drag and drop interface and can generate a random fractal

image to use as a vessel image, if needed.

1.5 FUTURE PROSPECTS:

In this report many relevant issues were presented, from a technical point of view.

However, little has been done to motivate these studies. A more detailed

investigation of applications, and a comparison with current techniques in

steganography would have been interesting. For example, a thorough evaluation of

the advantages natural language-based techniques can offer over image-based

techniques could have offered valuable insights. An important contribution of this

project to natural language steganography is the linguistic sophistication of the

model for word-substitution put forward. The lexical models employed in current

substitution-based systems were often criticised and their inadequate behavior

usually described with respect to language theory. These phenomena could have

been demonstrated by example, showing texts and inadequate replacements carried

out by current stegosystems. A more detailed analysis of how common these

critical situations really are in typical text could have given clues for the

construction of such systems, to decide whether the additional complexity

introduced by statistical word-sense disambiguation is worth the effort. Other

linguistic models have been studied, in addition to the lexical ones, and put in

relation to each other, and to their use for steganographic purposes. The

steganographic aspects were then covered by information-theoretic models.

However, little has been done to justify this choice. It might have been fruitful to

present other characterizations of steganography and to compare their suitability to

natural language steganography

A central part of the problem motivating this report was that there are no

models formalizing the design and analysis of natural language stegosystems.

Although the present report somewhat improves the situation, by providing a

systematic investigation of the topic, there is still no system to build upon for

making formal claims about security or robustness in the natural language scenario.

CHAPTER NO.2

ANALYSIS

2.1 PROJECT PLAN

1. Initial Research

2. Project Definition Document

a. Research

b. Finished PDD

3. Further Research

4. Software Development

a. Software Architecture

i. Design Phase

ii. Coding Phase

b. Steganography

i. Design Phase

ii. Coding Phase

c. Assembling Project

5.Testing

6. Final Report

2.2 FEASIBILITY STUDY:

2.2 .1 TECNICAL FEASIBILITY:

Stegpro i s bui ld on the Microsof t .NET p la t form so i t i s

machine independent ; but i t works only in Windows

envi ronment .

Due to i t s inherent cover t na ture , the whole h id ing-

unhiding process i s sa fe-n-secure over the In te rnet .

2.2 .2 FINANCIAL FEASIBILITY:

Stegpro or for tha t mat ter any s teganographic tool i s qui te

inexpens ive and excel lent opt ion for fu l f i l l ing en terpr i se

secur i ty requi rements as compared to o ther opt ions ( l ike ,

c ryptographic tools l ike Publ ic Key Inf ras t ructure-PKIs , and

Digi ta l Cer t i f ica tes , e tc) .

2 .2 .3 RESOURCE FEASIBILTY:

The resources tha t a re used in th is projec t were eas i ly avai lable .

The informat ion re la ted to Steganography i s eas i ly ava i lable on

in terne t . And the sof tware which was used to develop the sof tware

, you can download i t f rom in ternet or you can get the sof tware

avai lable in CD.

2 .3 TEAM STRUCTURE

CHAPTER NO.3

DESIGN

Group Leader

Market survey

Development

High level design

Technical Writer

Group Member 1

Usalbility testing

Requirement Gathering

Test Plans

Group Mmeber 2

Task Indentification

Configuration Testing

Low Level Design

Group Member 3

Analysis

Modelling

Compatibilty Testing

3.1 SOFTWARE REQUIREMENT SPECIFICATION:

The sof tware tools used by us to develop S tegpro a re g iven

below, wi th the i r uses :

(1) Microsoft Visual Studio .NET 2008 Redis tr ibutable

Package:

This i s used to wri te and compi le the

implementa t ion code of Stegpro . We use the

VisualC#.NET programming language of the VS.NET

pla t form to wri te the code .

(2) Microsoft HTML Help Workshop:

This sof tware tool was used to c rea te the ‘Help’

module of S tegpro .

3.2 RISK ASSESSMENT:

An Important aspect of project management is to assess the difficulties that could

arise during the development of the project. I have outlined the risks and

probability that they will occur here.

Risk Factor Impact Probability

Scope too large Serious 30%

Loss/Corruption of

data

Medium 5%

Choosing the wrong

development

environment

Serious 20%

Inability to meet

requirements

Critical 20%

Insufficient internet

access at home

Serious 40%

Scope creep Medium 10%

Learning curve of new

technology too steep

Serious 30%

Illness Serious 10%

Improper Testing Serious 15%

Overlooking

Requirements

Critical 10%

Time spent on

secondary functions

impacting development

of key functions

Serious 2%

Failure at Demo Stage Critical 20%

3.2 .1 PERFORMANCE RISKS:

The c lass ica l approach to r i sk assessment i s to f i r s t ident i fy the

threa t and then assess the threa t , then determine vulnerabi l i ty to

threa t , and f ina l ly de termine the impact i f the vulnerabi l i ty i s

exploi ted .

3.2 .2 COST RISKS:

This may be v iewed as the cos t tha t agents have to pay in order to

benef i t f rom the t rus ted envi ronment . In some cases there i s a

poss ib i l i ty to use only appl ica t ion layer Steganography i .e . image

and audio h id ing methods. Another secur i ty r i sk in Steganography

i s the use of sof tware program to h ide the data , p ic tures , or text

wi th in another document i .e . image or audio f i le . For eg . The

Mi2g worm cost US $950 mi l l ion to US $150 bi l l ion in los t

produc t iv i ty in only 5 days .

3.2 .3 SUPPORT RISKS:

I t was conjec tured tha t , g iven covers of uni form capaci ty and a

quant i ta t ive s teganalys is method sa t i s fy ing cer ta in assumpt ion,

“secure” s teganogrphy capaci ty i s proport ional only to the square

root of the number of covers . We now prove tha t , wi th respect a

na tura l def in i t ion of secure capaci ty , and in a su i tably asymptot ic

sense , th is conjec ture is t rue . This is in sharp cont ras t to

capaci ty resul t s to noisy channels .

3.2 .4 SCHEDULE RISKS:

The sof tware program f r idr ich has developed may help determine

who i s us ing s teganography to communicate secre t messages

about 40 DragonEyes a l ready exis t wi th fu l l product ion schedule

for the end of 2002. The prac t ice of h id ing a message or a f i le

wi th in a la rger f i le or an image or an audio f i le in such a way

tha t , the tape recycl ing process i s overwr i t ing tapes wi th new

data , usual ly on a f ix schedule involving the tape ro ta t ion .

CHAPTER NO.4

MODELLING (PROJECT FLOW)

4.1 ER-DIAGRAMS:

One of the key techniques in ER model ing i s to document the

ent i t ies and re la t ionships types in graphica l forms ca l led ENTITY

RELATIONSHIPS ER-DIAGRAM.

Start

Select medium

file.

Set quality.

Select data files.

Save the medium

file.

Want to add

more data

files?

Hide.

End.

Capacity of

medium file >0 ?

No more files can be added.

4.1.1 ER-DIAGRAM FOR HIDING DATA:

Start.

Select the file from which data is to be

extracted.

Unhide.

Enter Password.

Enter path at which data files are to be

stored.

End.

4.1.2 ER-DIAGRAM FOR UNHIDING DATA:

4.2 DATA-FLOW DIAGRAM FOR STEGPRO:

4.2 .1 LEVEL-0 DFD:

The L eve l -0 DF D fo r S t egp ro c an be s how n a s b e l ow. Th i s show s

the c on tex t - l eve l DF D fo r t h i s app l i ca t i on .

4.2 .2 LEVEL-1 DFD:

The L eve l -1 DF D fo r S t egp ro c an be show n a s be l ow.

4.2 .3 LEVEL-2 DFD FOR STEGPRO:

The L eve l -2 DF D fo r S t egp ro ma y be show n a s be l ow.

CHAPTER NO:5

CODING

5.1 HARDWARE SPECIFICATION:

The p ro j ec t , S t egp ro i s a s o f tw a re p ro j ec t a nd hence ha s a ve ry

nomina l ha rdw are r e qu i r em en t s ( a P C! ! ! ) .

We ha ve u se d a P C wi th f o l l owi ng con f igu ra t i on :

In t e l Pe n t ium IV 1 . 8G H z p roces s o r

256 MB D D R-RAM

Mi c ros o f t Wi ndows 7 P ro fe s s i ona l

5.2 PLATFORM :

VISUAL STUDIO 2008:

Microsof t Visual Studio 2008 del ivers on Microsof t v is ion of

smar t c lent appl ica t ions by enabl ing developers to rapidly

crea te connected appl ica t ions tha t de l ivers the h ighest qual i ty ,

r ich user exper iences . With Visual S tudio 2008, organiza t ion

wi l l f ind i t eas ier than ever before to capture and analyze

informat ion to he lp to make them ef fec t ive business dec is ion .

5.3 PROGRAMMING LANGUAGE USED:

C#.NET:

C# is pronounced as "C sharp". It is a new programming language that enables

programmers in quickly building solutions for the Microsoft .NET platform.

The first component in the c /c++ family is C#. Here every thing really is

an object it is basically used for preservation of investment.

Component concepts are first class :

1. Properties, methods, events.

2. Design time and run time attributes.

3. Integrated documentation using XML.

Enables one-stock programming:

1. No header files, ideal, etc.

2. Can be embedded in web pages.

5.4 CODING STYLE FOLLOWED:

IMAGE FILE HIDING MODULE :

This module handles the ta sk of da ta h id ing in image

f i les . This module consis t s of two main procedures :

Hide , Reveal . These two procedures per form fo l lowing

func t ions :

Hide : Hides the da ta f i les provided by the

user in the image medium f i le , which i s a l so

provided by the user .

Hide module i s fur ther d iv ided in to

severa l funct ional i t ies as descr ibed below.

publ ic in t checkdatas ize(s t r ing datafname, in t opt)

{

/ / re turn -1 ;

/ / i f da ts ize i s la rger to be h ide than

/ / the capaci ty of the image f i le

/ / re turn 1 ;

/ / i f da ta can de h idden

}

This funct ion takes the input f i les to be h idden in the image and

checks whether i t can be h idden in the source image suppl ied by

the user .

I f there i s enough space remaining in the image f i le to h ide

the da ta f i le then th is funct ion re turns 1 or e l se i t re turns -1

indica t ing not enough space .

This funct ion takes input as the f i lename and the 2nd

argument ‘opt ’ indica tes whether user wants to add f i les or

remove f i les .

publ ic in t h idedata(s t r ing s rc image,s t r ing[]

h idef i le , in t count , in t

encrypt req ,s t r ing password,

s t r ing path )

{

/ / / / / / / / / / / / / / / / / /

/ / Encode MAIN HEADER

// / / / / / / / / / / / / / / / /

for ( in t i=0; i<nooff i les ; i++)

{

/ / / / / / / / / / / / / / / /

/ /Encode f i lename&size

/ / / / / / / / / / / / / / / /

/ / / / / / / / / / / / / / / /

/ /Encode ac tual f i le

/ / ( f i le may be encrypted)

/ / / / / / / / / / / / / / / /

}

}

This funct ion ac tual ly does the process of h id ing

data .Severa l parameters i t t akes consis t s of the source image in

which da ta i s to be h idden, the password by which the f i le is to be

protec ted , the locat ion of the f i les to be h idden, opt ion of whether

encrypt ion is need or not .

Encoding process involves f i r s t the encoding of the MAIN

HEADER of sof tware projec t in which a l l above ment ioned

informat ion i s s tored and encrypted .

Afte r encoding header the ac tual f i les are h ided.

Reveal : Ext rac ts the h idden da ta f i les f rom the medium

f i le provided by the user .

The revea lmodule i s fur ther d iv ided in to d i f ferent sub

modules . They are as fo l lows .

publ ic s t r ing char form(byte[ ] inbyte , in t noofbi t s)

{

/ / / / / / / / /

/ / / /de f in ig var iables

/ / in i t i lasa t ion var iables

for ( i=0; i<loop; i++)

{

x=inbyte[ i ]&val ;

for ( j=0; j<7; j++)

asc iof img[ j]=0;

j=0;

whi le(x>=2)

{

asc iof img[ j]=x%2;

x=x/2;

j++;

}

asc iof img[ j]=x;

for ( j=noofbi t s-1 ; j>=0; j - - )

{

asc iofmain[k]=asciof img[ j ] ;

k-- ;

}

}

k=0;

x=0;

for (k=0;k<8;k++)

{

x+=asciofmain[k]*( in t )System.Math .Pow(2,k) ;

}

re turn ( (char)x) .ToStr ing() ;

}

This funct ion whi le performing decoding of the data makes

one byte of the h idden f i le f rom many bytes of the medium/image

f i le .

publ ic in t unhide(s t r ing s rc image , s t r ing path ,

s t r ing password)

{

/ / / / / / / / / / / / / / / / / / / / / / / / /

/ /Check for header in the speci f ied f i le

/ / / / / / / / / / / / / / / / / / / / / / / / /

/ / / / / / / / / / / / / / / / / / / / / / / / /

/ /Check for correc t password

/ / / / / / / / / / / / / / / / / / / / / / / / /

for ( i=0; i<nooff i les ; i++)

{

/ / / / / / / / / / / / / / / / / / / / / / / / / /

/ /Sta r t decoding f i le

/ / / / / / / / / / / / / / / / / / / / / / / / /

/ / / / / / / / / / / / / / / / / / / / / / / / / /

/ / I f f i le i s encrypted than decrypt i t .

/ / / / / / / / / / / / / / / / / / / / / / / / /

}

}

The decoding process takes the input f i le f ro the user and

f i r s t checks i t for va l id i ty whether i t i s the correc t f i le in which

data i s h idden.

For the cor rec t f i le password i s checked i .e the password

entered by the user i s checked wi th tha t of s tored in the f i le .

Afte r ver i fy ing only the a lgor i thm fur ther proceeds .

Af ter decoding f i les i f they are in encrypted form then they

are decrypted .

SOUND DATA HIDING MODULE :

This module handles the da ta h id ing in sound f i les . This

modules cons is t s of fo l lowing main procedures : Hide and

Reveal . These procedures a re expla ined be low in de ta i l .

Hide :

T h e i m p l e m e n t a t i o n o f t h e H i d e p r o c e d u r e c o n s i s t s o f f o l l o w i n g c o d i n g

s t e p s :

(1) Accept the sound( .wav) f i le f rom the user .

(2) Check i f th is sound f i le i s a va l id .wav

f i le .This i s done by checking the header of

the f i le whether i t matches wi th the

s tandard .wav header .

I f f i le i s va l id then the f i le i s checked for

any unknown coding technique . I t i s checked,

whether 8-bi t or 16-bi t i s used for a sample .

From th is i t i s inferred whether the qual i ty

of sound de ter iora tes a f ter h id ing da ta . For

example , i f in any par t icular sound f i le 8-b i t

i s used for a sample , then the qual i ty wi l l

badly de ter iora te a f ter da ta h id ing. I f such i s

the case , then a message is f i red to the

user , warning of th is resul t .

I f f i le i s not va l id , then d isplay a message

to the user s ta t ing th is .

(3) Next s tep is to accept the da ta f i les

provided by the user , tha t a re to be h idden in

the sound medium f i le .

The da ta f i le which can of any type , a re

checked for the i r s ize . Also the ir o ther

proper t ies a re ca lcula ted . Depending on the

maximum amount of da ta tha t can be h idden

in the provide medium f i le , the progress ba r

i s updated .

(4) Now, f i r s t copy the ent i re .wav header

in to the targe t f i le ;as th is th ing wi l l remain

same.

(5) Now a funct ion Encode() i s def ined. This

func t ion f i rs t embeds the ‘marc’ header in

the s tar t of da ta por t ion of the ta rget f i le .

(6) Afte r th is Encode() embeds the o ther da ta

f i les in the da ta pot ion of ta rget f i le , fo l lowing

the ‘marc’ header .

Reveal :

T h e i m p l e m e n t a t i o n o f t h e R e v e a l p r o c e d u r e c o n s i s t s o f f o l l o w i n g c o d i n g

s t e p s :

(1) A c c e p t t h e . w a v m e d i u m p r o v i d e d b y t h e u s e r . S k i p h e a d e r a n d

m o v e t o t h e d a t a p o r t i o n o f t h e f i l e .

(2) C h e c k w h e t h e r t h e ‘ m a r c ’ h e a d e r i s p r e s e n t a t t h e s t a r t o f d a t a

p o r t i o n o f t h e f i l e .

I f t h e ‘ m a r c ’ h e a d e r i s n o t p r e s e n t , t h e t h e u s e r i s n o t i f i e d a n d t h e

a l l t h i n g s a r e r e f r e s h e d .

I f t h e ‘ m a r c ’ h e a d e r i s p r e s e n t , t h e n t h e m e d i u m f i l e i s g e n u i n e .

Once, the medium file is authenticated, move on to decode and extract the

hidden data files and save those files. The extracted files are displayed in the

data file list.

5.5 CODING:

Mainform::

using System;

using System.Drawing;

using System.Collections;

using System.ComponentModel;

using System.Windows.Forms;

namespace MarcStegPro

{

/// <summary>

/// Summary description for Form1.

/// </summary>

public class frmmain : System.Windows.Forms.Form

{

private System.Windows.Forms.MainMenu mainMenu1;

private System.Windows.Forms.MenuItem menumainselect;

private System.Windows.Forms.MenuItem menuimage;

private System.Windows.Forms.MenuItem menusound;

private System.Windows.Forms.MenuItem menuItem4;

private System.Windows.Forms.MenuItem menuexit;

private System.Windows.Forms.MenuItem menulist;

public frmimage imagefrm;

public wav.frmwave soundfrm;

public MenuItem mn;

private System.Windows.Forms.StatusBar statusBar1;

private System.Windows.Forms.MenuItem menuItem1;

/// <summary>

/// Required designer variable.

/// </summary>

private System.ComponentModel.Container components = null;

public frmmain()

{

//

// Required for Windows Form Designer support

//

InitializeComponent();

//

// TODO: Add any constructor code after InitializeComponent

call

//

}

/// <summary>

/// Clean up any resources being used.

/// </summary>

protected override void Dispose( bool disposing )

{

if( disposing )

{

if(components != null)

{

components.Dispose();

}

}

base.Dispose( disposing );

Application.Exit();

}

#region Windows Form Designer generated code

/// <summary>

/// Required method for Designer support - do not modify

/// the contents of this method with the code editor.

/// </summary>

private void InitializeComponent()

{

this.mainMenu1 = new System.Windows.Forms.MainMenu();

this.menumainselect = new

System.Windows.Forms.MenuItem();

this.menuimage = new System.Windows.Forms.MenuItem();

this.menusound = new System.Windows.Forms.MenuItem();

this.menuItem4 = new System.Windows.Forms.MenuItem();

this.menuexit = new System.Windows.Forms.MenuItem();

this.menulist = new System.Windows.Forms.MenuItem();

this.menuItem1 = new System.Windows.Forms.MenuItem();

this.statusBar1 = new System.Windows.Forms.StatusBar();

this.SuspendLayout();

//

// mainMenu1

//

this.mainMenu1.MenuItems.AddRange(new

System.Windows.Forms.MenuItem[] {

this.menumainselect,

this.menulist,

this.menuItem1});

//

// menumainselect

//

this.menumainselect.Index = 0;

this.menumainselect.MenuItems.AddRange(new

System.Windows.Forms.MenuItem[] {

this.menuimage,

this.menusound,

this.menuItem4,

this.menuexit});

this.menumainselect.Text = "Main_Select ";

//

// menuimage

//

this.menuimage.Index = 0;

this.menuimage.Shortcut =

System.Windows.Forms.Shortcut.CtrlI;

this.menuimage.Text = "IMAGE";

this.menuimage.Click += new

System.EventHandler(this.menuimage_Click);

//

// menusound

//

this.menusound.Index = 1;

this.menusound.Shortcut =

System.Windows.Forms.Shortcut.CtrlW;

this.menusound.Text = "SOUND";

this.menusound.Click += new

System.EventHandler(this.menusound_Click);

//

// menuItem4

//

this.menuItem4.Index = 2;

this.menuItem4.Text = "-";

//

// menuexit

//

this.menuexit.Index = 3;

this.menuexit.Text = "EXIT";

this.menuexit.Click += new

System.EventHandler(this.menuexit_Click);

//

// menulist

//

this.menulist.Index = 1;

this.menulist.MdiList = true;

this.menulist.Text = "List";

//

// menuItem1

//

this.menuItem1.Index = 2;

this.menuItem1.Text = "";

//

// statusBar1

//

this.statusBar1.Font = new System.Drawing.Font("Microsoft

Sans Serif", 9F, System.Drawing.FontStyle.Bold,

System.Drawing.GraphicsUnit.Point, ((System.Byte)(0)));

this.statusBar1.Location = new System.Drawing.Point(0, 471);

this.statusBar1.Name = "statusBar1";

this.statusBar1.Size = new System.Drawing.Size(494, 16);

this.statusBar1.TabIndex = 1;

this.statusBar1.Text = "For Help Click here...";

this.statusBar1.Click += new

System.EventHandler(this.statusBar1_Click);

this.statusBar1.PanelClick += new

System.Windows.Forms.StatusBarPanelClickEventHandler(this.statusBar1_Panel

Click_1);

//

// frmmain

//

this.AutoScaleBaseSize = new System.Drawing.Size(5, 13);

this.ClientSize = new System.Drawing.Size(494, 487);

this.Controls.Add(this.statusBar1);

this.FormBorderStyle =

System.Windows.Forms.FormBorderStyle.Fixed3D;

this.IsMdiContainer = true;

this.MaximizeBox = false;

this.Menu = this.mainMenu1;

this.Name = "frmmain";

this.StartPosition =

System.Windows.Forms.FormStartPosition.CenterScreen;

this.Text = "MARC Stegpro";

this.Load += new System.EventHandler(this.frmmain_Load);

this.ResumeLayout(false);

}

#endregion

private void frmmain_Load(object sender, System.EventArgs e)

{

statusBar1.Cursor=Cursors.Hand;

}

private void menuimage_Click(object sender, System.EventArgs e)

{

bool present=false;

foreach(Form frm in this.MdiChildren)

{

if(frm.Text=="Image ")

present=true;

}

if(!present)

{

imagefrm=new frmimage();

imagefrm.MdiParent =this;

imagefrm.Show();

}

else

{

MessageBox.Show("Form is already open","Image");

}

}

private void menuexit_Click(object sender, System.EventArgs e)

{

Application.Exit();

}

private void statusBar1_PanelClick(object sender,

System.Windows.Forms.StatusBarPanelClickEventArgs e)

{

}

private void statusBar1_Click(object sender, System.EventArgs e)

{

if(System.IO.File.Exists(Application.StartupPath+@"\help\

stegpro.chm")==false)

MessageBox.Show("Help not present!","Help not

Found",MessageBoxButtons.OK,MessageBoxIcon.Error);

else

{

Help.ShowHelp(this,Application.StartupPath+@"\help\

stegpro.chm");

}

}

private void menusound_Click(object sender, System.EventArgs e)

{

bool present=false;

foreach(Form frm in this.MdiChildren)

{

if(frm.Text=="Wave Main Form")

present=true;

}

if(!present)

{

soundfrm=new wav.frmwave();

soundfrm.MdiParent=this;

soundfrm.Show();

}

else

{

MessageBox.Show("Form is already open","Sound");

}

}

private void statusBar1_PanelClick_1(object sender,

System.Windows.Forms.StatusBarPanelClickEventArgs e)

{

}

}

}

Encrypt Decrypt::

using System;

using System.IO;

public class Encrypt

{

public string app_path;

public Encrypt(string path)

{

//

// TODO: Add constructor logic here

//

app_path=path;

}

public void encryptfile(string filename,string password)

{

FileInfo sfinfo=new FileInfo (filename);

Stream sf=sfinfo.OpenRead();

string dfname=app_path+@"\marc_e.abu";

FileInfo dfinfo=new FileInfo(dfname);

Stream df=dfinfo.OpenWrite();

int pl=password.Length;

int cnt=0;

int ch;

while((ch=sf.ReadByte())!=-1 )

{

char chchar=(char)ch;

ch=ch+(int)password[cnt];

char t=password[cnt];

chchar=(char)ch;

df.WriteByte((byte)chchar);

cnt++;

if(cnt>=pl)

cnt=0;

}

sf.Close();

df.Close();

//return 1;

}

/// <summary>

/// For decrypting file

/// </summary>

/// <param name="srcname"></param>

/// <param name="destname"></param>

/// <param name="password"></param>

public void decryptfile(string srcname,string destname,string

password)

{

FileInfo sfinfo=new FileInfo(srcname);

Stream sf=sfinfo.OpenRead();

string dfname=app_path+@"\"+destname;

FileInfo dfinfo=new FileInfo(dfname);

Stream df=dfinfo.OpenWrite();

int pl=password.Length;

int cnt=0;

int ch;

while((ch=sf.ReadByte())!=-1 )

{

char chchar=(char)ch;

ch=ch-(int)password[cnt];

char t=password[cnt];

chchar=(char)ch;

df.WriteByte((byte)chchar);

cnt++;

if(cnt>=pl)

cnt=0;

}

sf.Close();

df.Close();

}

}

Password

using System;

using System.Drawing;

using System.Collections;

using System.ComponentModel;

using System.Windows.Forms;

/// <summary>

/// Summary description for password.

/// </summary>

public class frmpassword : System.Windows.Forms.Form

{

private System.Windows.Forms.Button buttonok;

private System.Windows.Forms.Button buttoncancel;

public string pass;

private System.Windows.Forms.Label label1;

private System.Windows.Forms.Label label2;

private System.Windows.Forms.TextBox textBoxpass;

private System.Windows.Forms.TextBox textBoxrepass;

/// <summary>

/// Required designer variable.

/// </summary>

private System.ComponentModel.Container components = null;

public frmpassword()

{

//

// Required for Windows Form Designer support

//

InitializeComponent();

//

// TODO: Add any constructor code after InitializeComponent

call

//

}

/// <summary>

/// Clean up any resources being used.

/// </summary>

protected override void Dispose( bool disposing )

{

if( disposing )

{

if(components != null)

{

components.Dispose();

}

}

base.Dispose( disposing );

}

#region Windows Form Designer generated code

/// <summary>

/// Required method for Designer support - do not modify

/// the contents of this method with the code editor.

/// </summary>

private void InitializeComponent()

{

System.Resources.ResourceManager resources = new

System.Resources.ResourceManager(typeof(frmpassword));

this.textBoxpass = new System.Windows.Forms.TextBox();

this.buttonok = new System.Windows.Forms.Button();

this.buttoncancel = new System.Windows.Forms.Button();

this.textBoxrepass = new System.Windows.Forms.TextBox();

this.label1 = new System.Windows.Forms.Label();

this.label2 = new System.Windows.Forms.Label();

this.SuspendLayout();

//

// textBoxpass

//

this.textBoxpass.Font = new System.Drawing.Font("Arial",

12F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point,

((System.Byte)(0)));

this.textBoxpass.Location = new System.Drawing.Point(128,

16);

this.textBoxpass.MaxLength = 9;

this.textBoxpass.Name = "textBoxpass";

this.textBoxpass.PasswordChar = '*';

this.textBoxpass.Size = new System.Drawing.Size(176, 26);

this.textBoxpass.TabIndex = 0;

this.textBoxpass.Text = "";

this.textBoxpass.TextChanged += new

System.EventHandler(this.textBox1_TextChanged);

//

// buttonok

//

this.buttonok.Font = new System.Drawing.Font("Microsoft

Sans Serif", 8.25F, System.Drawing.FontStyle.Bold,

System.Drawing.GraphicsUnit.Point, ((System.Byte)(0)));

this.buttonok.Location = new System.Drawing.Point(48, 88);

this.buttonok.Name = "buttonok";

this.buttonok.Size = new System.Drawing.Size(80, 24);

this.buttonok.TabIndex = 2;

this.buttonok.Text = "Ok";

this.buttonok.Click += new

System.EventHandler(this.buttonok_Click);

//

// buttoncancel

//

this.buttoncancel.DialogResult =

System.Windows.Forms.DialogResult.Cancel;

this.buttoncancel.Font = new System.Drawing.Font("Microsoft

Sans Serif", 8.25F, System.Drawing.FontStyle.Bold,

System.Drawing.GraphicsUnit.Point, ((System.Byte)(0)));

this.buttoncancel.Location = new System.Drawing.Point(176,

88);

this.buttoncancel.Name = "buttoncancel";

this.buttoncancel.Size = new System.Drawing.Size(80, 24);

this.buttoncancel.TabIndex = 3;

this.buttoncancel.Text = "Cancel";

this.buttoncancel.Click += new

System.EventHandler(this.buttoncancel_Click);

//

// textBoxrepass

//

this.textBoxrepass.Font = new System.Drawing.Font("Arial",

12F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point,

((System.Byte)(0)));

this.textBoxrepass.Location = new System.Drawing.Point(128,

48);

this.textBoxrepass.MaxLength = 9;

this.textBoxrepass.Name = "textBoxrepass";

this.textBoxrepass.PasswordChar = '*';

this.textBoxrepass.Size = new System.Drawing.Size(176, 26);

this.textBoxrepass.TabIndex = 1;

this.textBoxrepass.Text = "";

this.textBoxrepass.TextChanged += new

System.EventHandler(this.textBoxrepass_TextChanged);

//

// label1

//

this.label1.AutoSize = true;

this.label1.Font = new System.Drawing.Font("Microsoft Sans

Serif", 8.25F, System.Drawing.FontStyle.Bold,

System.Drawing.GraphicsUnit.Point, ((System.Byte)(0)));

this.label1.Location = new System.Drawing.Point(8, 16);

this.label1.Name = "label1";

this.label1.Size = new System.Drawing.Size(56, 16);

this.label1.TabIndex = 4;

this.label1.Text = "Password";

//

// label2

//

this.label2.AutoSize = true;

this.label2.Font = new System.Drawing.Font("Microsoft Sans

Serif", 8.25F, System.Drawing.FontStyle.Bold,

System.Drawing.GraphicsUnit.Point, ((System.Byte)(0)));

this.label2.Location = new System.Drawing.Point(8, 48);

this.label2.Name = "label2";

this.label2.Size = new System.Drawing.Size(103, 16);

this.label2.TabIndex = 5;

this.label2.Text = "Confirm Password";

//

// frmpassword

//

this.AutoScaleBaseSize = new System.Drawing.Size(5, 13);

this.CancelButton = this.buttoncancel;

this.ClientSize = new System.Drawing.Size(326, 124);

this.ControlBox = false;

this.Controls.Add(this.label2);

this.Controls.Add(this.label1);

this.Controls.Add(this.textBoxrepass);

this.Controls.Add(this.textBoxpass);

this.Controls.Add(this.buttoncancel);

this.Controls.Add(this.buttonok);

this.FormBorderStyle =

System.Windows.Forms.FormBorderStyle.Fixed3D;

this.Icon = ((System.Drawing.Icon)

(resources.GetObject("$this.Icon")));

this.Name = "frmpassword";

this.StartPosition =

System.Windows.Forms.FormStartPosition.CenterScreen;

this.Text = "Password";

this.Load += new

System.EventHandler(this.frmpassword_Load);

this.ResumeLayout(false);

}

#endregion

private void buttonok_Click(object sender, System.EventArgs e)

{

if(textBoxpass.Text ==textBoxrepass.Text )

{

pass=textBoxpass.Text;

textBoxpass.Text ="";

textBoxrepass.Text ="";

Dispose();

}

else

{

MessageBox.Show("Both the passwords do not

match!","Incorrect match");

textBoxpass.Text="";

textBoxrepass.Text="";

}

}

private void frmpassword_Load(object sender, System.EventArgs e)

{

pass="";

buttonok.Enabled=false;

}

private void textBox1_TextChanged(object sender, System.EventArgs

e)

{

makeenable();

}

private void makeenable()

{

if(textBoxpass.Text!="" && textBoxrepass.Text!="")

buttonok.Enabled=true;

else

buttonok.Enabled=false;

}

private void textBoxrepass_TextChanged(object sender,

System.EventArgs e)

{

makeenable();

}

private void buttoncancel_Click(object sender, System.EventArgs e)

{

}

}

5.6 SCREEN SHOTS:

MAINFORM

SETTING PASSWORD

ENCODING OF IMAGE

DECODING OF FILE

CHAPTER 6

TESTING

6.1 FORMAL TECHNICAL REVIEW

The FTR (Formal Technica l Review) is a sof tware qual i ty

assurance ac t iv i ty wi th the objec t ives to uncover er rors in

func t ion , logic or implementa t ion for any representa t ion of the

sof tware ; to ver i fy tha t the sof tware under review meets i t s

requirements ; to ensure tha t the sof tware has been represented

according to predef ined s tandards ; to achieve sof tware tha t is

developed in a uni form manner and to make projec ts more

manageable .

FTR (Formal Technica l Review) i s a l so a learning ground for

junior developers to know moreabout d i f ferent approaches to

sof tware analys is , des ign and implementa t ion . I t a l so serves as a

backup and cont inui ty for the people who are not exposed to the

sof tware deve lopment so far . FTR (Formal Technica l Review)

ac t iv i t ies inc lude walkthroughs , inspect ion and round robin

reviews and other technica l assessments . The above-ment ioned

methods are d i f ferent FTR (Formal Technica l Review) formats .

6.2 TEST PLAN

• Avai labi l i ty of necessary hardware and sof twares(Visual

S tudio 2008, Microsof t Windows XP) .

• Conf igura t ion Test ing .

• Compat ib i l i ty Tes t ing .

• Loading of Image and Sound Tes t ing .

• Adding the Data Test ing .

• Ver i fy ing password Test ing .

• Encrypyt ion and Decrypt ion Test ing .

6.3 TEST CASES AND TEST RESULTS:

Sr. No

To be test Specification says Actual Result Status

1 Availability of necessary software and Hardware

1. Visual Studio 2008 that includes c# language

All requirement available

Pass

2 Configuration Testing 1. 32 bit operating system

2. Minimum 32 MB RAM

3. Minimum 54MB free hard disk space

All requirement available

Pass

3 Compatibility 1. Visual Studio 2008 to be worked on 32-bit Operating System

All softwares are compatible

Pass

4 Adding of Data Testing 1. Data should not exceed the limit.

2. Password should be encrypted

3. Password and retype password should be matched

4. Path should

Pass

be specified for decryption of information.

6.3 .1 Unit test ing :

Unit tes t ing examines the programming logic . For th is

purpose we deve lop tes t cases tha t resul t s in execut ing

every ins t ruct ion in the program or module tha t i s t es ted .

In th is projec t we have taken every poss ib le types of input ,

That caused every ins t ruct ion in the code to execute such as :

For opening an correc t and incorrec t source image.

Adding and removing data f i les .

Set t ing qual i ty for encoding.

Set t ing opt ion of encrypt ing f i les or not .

6.3 .2 Integrat ion tes t ing :

In in tegra t ion tes t ing , we examine the in tegra t ions s ta t ing

what the programs should do and how should i t perform

under var ious condi t ions when a l l the modules are in tegra ted .

Afte r tha t t es t cases a re cases a re developed for each

condi t ion or combinat ion of condi t ions and submit ted for

process ing.

In th is projec t a l l requi rements speci f ied in problem

def in i t ion are wel l exmined and successful ly tes ted .

6.3 .3 Securi ty tes t ing :

Any computer-based sys tem tha t manages sensi t ive

informat ion or causes ac t ions tha t can improper ly harm(or

benef i t ) individua ls i s a ta rget for improper or i l legal

penet ra t ion . Penet ra t ion spans a broad range of ac t iv i t ies :

hackers who a t tempt to penet ra te sys tems for spor t ;

d isgrunt led employees who t ry to penet ra te for revenge;

d ishones t individuals who a t tempt to penet ra te for i l l ic i t

personal ga ins .

Secur i ty tes t ing a t tempts to ver i fy tha t protec t ion

mechanisms bui l t in to a sys tem wi l l , in fac t , pro tec t i t

f rom improper penet ra t ion . The sys tem’s secur i ty must , of

course , be tes ted for invulnerabi l i ty f rom f ronta l a t tack ,

but must a l so be tes ted for invulnerabi l i ty f rom f lank or

rear a t tack .

During secur i ty tes t ing , the tes ter p lays the ro le of

the individuals who des i res to penet ra te the sys tem. The

tes ter may a t tempt to acqui re passwords through external

c ler ica l means ; may a t tack the sys tem wi th custom

sof tware des igned to breakdown any defenses tha t have been

const ructed; may purposely cause sys tem e rrors , hoping to

f ind the key to sys tem ent ry .

Given enough t ime and resources , good secur i ty tes t ing

wi l l u l t imate ly penet ra te a sys tem. The ro le of the sys tem

designer i s to make penet ra t ion cos t more than the va lue

of the informat ion tha t wi l l be obta ined.

In th is projec t secur i ty i s provided in te rms of password.

Even i f any one gets the medium f i le in which is encoded and the

sof tware , he wil l not be able to ge t the h idden informat ion unt i l

cor rec t password i s been provided.

6.3 .4 Peak load test ing :

This tes t ing de termines whether the sys tem can handle

volume of ac t iv i t ies tha t occur when sys tem i s a t the peak

of process ing demand.

In th is projec t maximum number of da ta f i les

tha t can be h idden a re suppl ied as input .The resul t we got i s tha t

i t requi res more t ime for encoding and decoding depending on the

computer ’s conf igura t ion

CHAPTER NO:7

SOFTWARE COST ESTIMATION

C H A P T E R N O : 8

L I M I T A T I O N S A N D S C O P E

LIMITATIONS:

1. The f i le can be embedded by making changes to

b inary code tha t does not af fec t the execut ion of f i le .To

decode and ext rac t the f i le ,you wi l l need to have the or ig inal

b inary code.By compar ing the marked and or ig ina l f i les ,you

can then spot the s ta tement swi tches and ext rac t the

embedded f i le .This method i s very s imple but i s not res is tant

to a t tacks . I f the a t tacker has many di f ferent vers ions of the

marked f i les than he may detec t the marked f i le and thus he

may be able to remove i t .

2 . By taking advantage of the l imi ta t ions of the human

percept ion i t i s poss ib le to enbed data with in a f i le .For

example ,wi th audio f i les f requency masking occurs when two

tones wi th s imi la r f requencies a re p layed a t the same

t ime.The l i s tener only hears the louder tone whi le the quie te r

tone i s masked.Simi lar ly , temporal masking occurs when a

low-leve l s ignal occurs immedia te ly before or af ter a s t ronger

one as i t t akes us t ime to adjus t hear ing the new

f requency.This provides c lear point in the f i le in which to

embed the mark.

3 . Changes in the s tegno objec t mjus t have no e ffec t on

the marked objec t . Imagine i f u have a legal copy of an image

tha t you would l ike to manipula te in var ious ways .These

manipula t ions can be s imple process such as

res iz ing, t r imming or ro ta t ing the image .The marked image

must survive these manipula t ions ,o therwise the a t tackers can

very eas i l t remove the marked image and the point of

S teganography wi l l be broken.Final ly ,we a lways assume tha t

the a t tacker knows tha t the re i s h idden informat ion ins ide the

s tego objec t .

4 . The s tego objec t must reamin unchanged or a lmost

unchanged to the naked eye . I f the s tego objec t changes

cont inuosly and can be not iced ,a th i rd paty may see tha t the

informat ion i s h idden and therefore could a t tempt to ext rac t

or des t roy i t .

SCOPE:

The scope of th is projec t i s as fo l low:

1. Implementa t ion of s teganographic tools for h id ing

informat ion inc ludes sound and image f i les .

2 .Three d i f ferent approaches being explored which are leas t

s igni f icant b i t ,masking and f i l te r ing and a lgor i thms and

t ransformat ion.