Académique Documents
Professionnel Documents
Culture Documents
ON
Certificate
This is to certify that
Name of the Student
Seat No
RAHUL VICHARE
Enrollment No
1410790
187
VINAYAK KUMBHAR
1410790203
162384
AJIT JAGTAP
1100270238
162385
NIKHIL JAVHERI
1100270260
162386
162383
______________
Guide
Project Co-ordinator
_____________
______________
(Prof. P.N.Tandon)
Head of Department
______________
Internal Examiner
Principal
______________
External Examiner
ACKNOWLEDGEMENT
A project is creative work for many minds. A proper synchronization between
individuals is a must for any project to be successfully completed.Its a very difficult
task for our team, to develop software for a first time.It is our privilege to study in this
college under the leadership of our principal Prof. P.N.Tandon.
We thank our H.O.D. Prof. Ranjeet Pawar for encouraging us & giving this
opportunity to widen our knowledge by this project.We are very grateful to our
project co-ordinator Prof.Mohan Mali and project guide Prof.Ranjeet Pawar for
providing us with the essential facilities required in this project.
We hereby thank Prof.Mohan Mali ,Prof.Satish Kale Prof.Jyoti Kamble,
Prof. Shinde and for giving us knowledge & spending their valuable time in making
us understanding the concept of the same.
We also thank all the other staff members of Information Technology
department & our friends who have helped us & guided us in this project.
RAHUL VICHARE
VINAYAK KUMBHAR
AJIT JAGTAP
NIKHIL JAVHERI
INDEX
1
TITLE
Page no
1
Introduction
1.1
What is Steganography?
7
1.2
What is Authentication?
8
1.3
Methods of Authentication
8
1.4
Steganography Concept
9
1.5
Motivation
10
1.6
Objective
10
2
Problem Definition
2.1
Existing Approach
12
2.2
Purpose Approach
13
3
Requirement Specification
3.1
Software Requirement
15
3.2
Hardware Requirement
15
4
Literature Survey
4.1
Introduction
17
4.1.1
Technical Feasibility
17
4.1.2
Operational Feasibility
17
4.1.3
Economical Feasibility
18
4.2
Software Requirement and Analysis
19
General
19
4.2.1
Module Description
20
5
28
5.4
Planning
28
5.5
Gantt Chart
29
5.6
PERT Chart
31
6
System Design
6.1
Purpose
34
6.2
Project Development Approach
34
6.3
Data Flow Diagram
35
6.4
Flow Chart
36
6.5
Use Case Diagram
38
7
Advantages
40
8
Needs and Applications
42
9
Screen Shots
45
10
Conclusion
51
11
References
52
Abstract
The Internet as a whole does not use secure links, thus information in transit
may be vulnerable to interception as well. The importance of reducing a chance
of the information being detected during the transmission is being an issue now
days. Some solution to be discussed is how to pass information in a manner that
the very existence of the message is unknown in order to repel attention of the
potential attacker. Besides hiding data for confidentiality, this approach of
information hiding can be extended to copyright protection for digital media. In
this research, we clarify what steganography is, the definition, the importance as
well as the technique used in implementing steganography. We focus on the Least
Significant Bit (LSB) technique in hiding messages in an audio and video. The
system enhanced the LSB technique by randomly dispersing the bits of the
message in the image and thus making it harder for unauthorized people to
extract the original message. Audio steganography is concerned with hiding
information in a cover (host) audio signal in an imperceptible way. Hidden
information from the stego, or data-embedded audio & video signal, is retrieved
using a key similar to the one that was employed during the hiding phase. Least
Significant Bit (LSB) modification technique is the most simple and efficient
technique used for audio steganography. Proposed technique has been tested
successfully on a .wav file at a sampling frequency of 3000 samples/second with
each sample containing 8 bits. It is very important for effective and successful
embedding process to select appropriate pixels in the video frames, which are
used to store the secret data. We use video based Steganography because of large
size and memory requirements. Hiding information in a carrier file we use least
significant bit (LSB) insertion technique. In Least significant bit (LSB) insertion
technique, for hiding information we change LSB of video file with the
information bits .This paper will focus on hiding information in specific frames of
the video and in specific position of the frame by LSB substitution.
Chapter 1
Introduction
Steganography is the art and science of writing hidden messages in such a way that no
one, apart from the sender and intended recipient, suspects the existence of the
message, a form of security through obscurity. The word steganography is of Greek
origin and means "concealed writing" from the Greek words steganos meaning
"covered or protected", and graphic meaning "writing. The first recorded use of the
term was in 1499 by Johannes Trithemius in his Steganographia, a treatise on
cryptography and steganography disguised as a book on magic. Generally, messages
will appear to be something else: images, articles, shopping lists, or some other cover
text and, classically, the hidden message may be in invisible ink between the visible
lines of a private letter. The advantage of steganography, over cryptography alone, is
that messages do not attract attention to themselves. Plainly visible encrypted
messages no matter how unbreakable will arouse suspicion, and may in themselves be
incriminating in countries where encryption is illegal Therefore, whereas cryptography
protects the contents of a message, steganography can be said to protect both
messages and communicating parties. Steganography includes the concealment of
information
within
computer
files.
In
digital
steganography,
electronic
Introduction
1.2 What is Authentication?
Authentication is a process in which the credentials provided are compared to those on
file in a database of authorized users information on a local operating system or
within an authentication server. If the credentials match, the process is completed and
the user is granted authorization for access. The permissions and folders returned
define both the environment the user sees and the way he can interact with it,
including hours of access and other rights such as the amount of allocated storage
space.
The process of an administrator granting rights and the process of checking user
account permissions for access to resources are both referred to as authorization. The
privileges and preferences granted for the authorized account depend on the users
permissions, which are either stored locally or on the authentication server. The
settings defined for all these environment variables are set by an administrator.
To validate the identity of database users and prevent unauthorized use of a database
user name, you can authenticate users by using any combination of the methods
described in the following sections:
.
1.5 Motivation:
The primary reason for selecting steganography among the list of possible project
topics was due to the unfamiliarity of the word that twigged an interest in the subject.
Another motivation for researching the topic was after reading an online article in the
USA Today titled "Terror groups hide behind Web encryption" that claims terrorists
and, in particular, Osama bin Laden and the al-Qaida network, may be using
steganography to communicate with each other in planning terrorist attacks. It is
thought that images with hidden messages are placed on bulletin boards or dead drops
for other terrorists to pick up and retrieve hidden messages. Thus far, this supposition
has yet to be proven.
1.6 Objective
The goal of steganography is hide the fact that communication is taking place. So, a
fundamental requirement of this steganography system is that the hider message
carried by stego-media should not be sensible to human beings.
module of this
To extract techniques of getting secret data using decryption
module.
Providing Security.
Chapter 2
Problem Definition
PROBLEM DEFINITION
2.1 Existing System
malicious user. But, the actual content is randomized or confused and hence not
revealed. But, in Steganography the fact that the credit card details is being sent is
kept secretly (as the message or the image appears innocent). The advantage of
steganography over cryptography alone is that messages do not attract attention to
themselves, to messengers, or to recipients. An unhidden coded message, no matter
how unbreakable it is, will arouse suspicion and may in itself be incriminating, as in
some countries encryption is illegal.
Encryption software protects internet connected computers from crackers and other
online intruders. The technology is widely used to encrypt credit card information,
bank account numbers and other type of financial records so they can send safely and
securely across the internet. Protect much of the intellectual content thats marketed on
the web, such as music, Videos, articles, and software, restricting its availability to
paying customers. This system helps to hide the information while sending the
important and confidential documents in video files; it will be invisible for the third
person. This system is helpful for the defense and security departments sending and
receiving the confidential matters in emergency situations.
Encryption software protects internet connected computers from crackers and other
online intruders. The technology is widely used to encrypt credit card information,
bank account numbers and other type of financial records so they can send safely and
securely across the internet. Protect much of the intellectual content thats marketed on
the web, such as music, Videos, articles, and software, restricting its availability to
paying customers. This system helps to hide the information while sending the
important and confidential documents in video files; it will be invisible for the third
person. This system is helpful for the defense and security departments sending and
receiving the confidential matters in emergency situations.
Chapter 3
Requirement Specification
REQUIREMENT SPECIFICATION
Operating System
Windows XP /2000
Technologies
Processor
Pentium IV
RAM
512MB RAM
Hard Disk
10GB
Chapter 4
Literature Survey
LITERATURE SURVEY
4.1 Introduction
A feasibility study is a high-level capsule version of the entire System analysis and
Design Process. The study begins by classifying the problem definition. Feasibility is
to determine if its worth doing. Once an acceptance problem definition has been
generated, the analyst develops a logical model of the system. A search for alternatives
is analyzed carefully. There are 3 parts in feasibility study.
Is there sufficient support for the project from management from users? If the
current system is well liked and used to the extent that persons will not be able
to see reasons for change, there may be resistance.
Are the current business methods acceptable to the user? If they are not, Users
may welcome a change that will bring about a more operational and useful
systems.
Have the user been involved in the planning and development of the project?
Since the proposed system was to help reduce the hardships encountered. In the
existing manual system, the new system was considered to be operational feasible.
The problem statement should state what is to be done and not how it is to be
done. It should be a statement of needs, not a proposal for a solution. A user manual
for the desired system is a good problem statement. The requestor should indicate
which features are mandatory and which are optional, to avoid overly constraining
design decisions. The requestor should avoid describing system internals, as this
restricts implementation flexibility. Performance specifications and protocols for
interaction with external systems are legitimate requirements. Software engineering
standards, such as modular construction, design for testability, and provision for future
extensions, are also proper.
Many problems statements, from individuals, companies, and government
agencies, mixture requirements with design decisions. There may sometimes be a
compelling reason to require a particular computer or language; there is rarely
justification to specify the use of a particular algorithm. The analyst must separate the
true requirements from design and implementation decisions disguised as
requirements. The analyst should challenge such pseudo requirements, as they restrict
flexibility. There may be politics or organizational reasons for the pseudo
requirements, but at least the analyst should recognize that these externally imposed
design decisions are not essential features of the problem domain.
A problem statement may have more or less detail. A requirement for a
conventional product, such as a payroll program or a billing system, may have
considerable detail. A requirement for a research effort in a new area may lack many
details, but presumably the research has some objective, which should be clearly
stated.
Most problem statements are ambiguous, incomplete, or even inconsistent.
Some requirements are just plain wrong. Some requirements, although precisely
stated, have unpleasant consequences on the system behavior or impose unreasonable
implementation costs. Some requirements seem reasonable at first but do not work out
as well as the request or thought. The problem statement is just a starting point for
understanding the problem, not an immutable document. The purpose of the
subsequent analysis is to fully understand the problem and its implications. There is no
reasons to expect that a problem statement prepared without a fully analysis will be
correct.
The analyst must work with the requestor to refine the requirements so they
represent the requestors true intent. This involves challenging the requirements and
probing for missing information. The psychological, organizational, and political
considerations of doing this are beyond the scope of this book, except for the
following piece of advice: If you do exactly what the customer asked for, but the result
does not meet the customers real needs, you will probably be blamed anyway.
Encryption module
3.
Decryption module.
4.
Receiving message
1.Sending message
The sender can send a message to the destination more securely. This can be
done by attaching a video file to the message. So the third party can be unaware
the secret message. They think that a video file is sending and they not at all
know about this secret sending of the message.
2. Encryption module
In this a sender can encrypt a file by entering a key.The same key must be
entered
Same key must entered during the decryption process.
3.Decryption Module
This process can be done by entering the key that previously entered during the
Encryption process. If the entered key is wrong the message wont be received
correctly.
4.Recieving Message
In this the Receiver can receive the hidden message by the decryption process.
In This the user enter the same key as the sender sends.The receiver can receive the
message by correctly entering the key.
Chapter 5
Testing and Planning
TESTING
5.1 Testing:
Testing can demonstrate the presence of bugs, but not their absence
Debugging is the art or method of uncovering why the script /program did not
execute properly.
Black box Testing: is the testing process in which tester can perform testing
on an application without having any internal structural knowledge of
application.
Usually Test Engineers are involved in the black box testing.
White box Testing: is the testing process in which tester can perform testing
on an application with having internal structural knowledge.
Usually The Developers are involved in white box testing.
Gray Box Testing: is the process in which the combination of black box and
white box techniques are used.
Levels of Testing
Module1
Module2
Module3
Units
Units
Units
Integration o/p
i/p
total
2. Objective of testing,
3. Areas that need to be tested,
4. Areas that should not be tested,
5. Scheduling Resource Planning,
Test Development:
Test Execution:
Result Analysis:
Bug Tracing:
Reporting:
Types Of Testing:
Smoke Testing: is the process of initial testing in which tester looks for the
availability of all the functionality of the application in order to perform detailed
testing on them. (Main check is for available forms)
Regression Testing: is one of the best and important testing. Regression testing is the
process in which the functionality, which is already tested before, is once again tested
whenever some new change is added in order to check whether the existing
functionality remains same.
Static Testing: is the testing, which is performed on an application when it is not been
executed. ex: GUI, Document Testing
Compatibility testing: it is the testing process in which usually the products are
tested on the environments with different combinations of databases (application
servers, browsersetc) In order to check how far the product is compatible with all
these environments platform combination.
Installation Testing: it is the process of testing in which the tester try to install or try
to deploy the module into the corresponding environment by following the guidelines
produced in the deployment document and check whether the installation is successful
or not.
Adhoc Testing: Adhoc Testing is the process of testing in which unlike the
formal
testing where in test case document is used, with out that test case document testing
can be done of an application, to cover that testing of the future which are not covered
in that test case document. Also it is intended to perform GUI testing which may
involve the cosmetic issues.
Test Scenario
Test Procedure
Test case
This is the sample test case document for the Acadamic details of student project:
Test scope
Test coverage is provided for the screen Acadamic status entry form of a
student module of university management system application
Test Scenario
When the office personals use this screen for the marks entry, calculate the
status details, saving the information on students basis and quit the form.
Test Procedure
The procedure for testing this screen is planned in such a way that the data
entry, status calculation functionality, saving and quitting operations are tested
in terms of Gui testing, Positive testing, Negative testing using the
corresponding Gui test cases, Positive test cases, Negative test cases
respectively
5.4 Purpose
The software planning begins with a statement of the work to be performed and other
constraints and goals that define and bound the software project (those established by
the practices of the Requirements Management key process area). The software
planning process includes steps to estimate the size of the software work products and
the resources needed, produce a schedule, identify and assess software risks, Iterating
through these steps may be necessary to establish the plan for the software project
(i.e., the software development plan).
A Gantt chart can be developed for the entire project. It depicts a part of a software
project schedule that emphasizes the concept scooping task for a new software
project. All project tasks (for concept scooping) are listed in the left hand column.
The horizontal bars show the time needed to complete an activity.
A Gantt chart is a graphical representation of the duration of tasks against the
progression of time. It is a useful tool for planning and scheduling projects. It is
helpful when monitoring a projects progress.
A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts
illustrate the start and finish dates of the terminal elements and summary elements
of a project. Terminal elements and summary elements comprise the work
breakdown structure of the project. Some Gantt charts also show the dependency
relationships between activities.
Although a Gantt chart is useful and valuable for small projects that fit on a single
sheet or screen, they can become quite unwieldy for projects with more than about
30 activities. Larger Gantt charts may not be suitable for most computer displays. A
related criticism is that Gantt charts communicate relatively little information per
unit area of display. That is, projects are often considerably more complex than can
be communicated effectively with a Gantt chart.
Gantt charts only represent part of the triple constraints of projects, because they
focus primarily on schedule management. Moreover, Gantt charts do not represent
the size of a project or the relative size of work elements, therefore the magnitude of
a behind-schedule condition is miss communicated. If two projects are the same
number of days behind schedule, the larger project has a larger impact on resource
utilization, yet the Gantt does not represent this difference.
Chapter 6
System Design
SYSTEM DESIGN
6.1 Purpose
The purpose of design document is to build the project in a manner specified and
developed the project in such a way that it is able to satisfy the user requirement and
develop according the requirement of user.
problem. Process operations are represented in these boxes, and arrows connecting
them represent flow of control. Data flows are not typically represented in a
flowchart, in contrast with data flow diagrams; rather, they are implied by the
sequencing of operations.
Terms used:
Actor: Actor is an external agent that lies outside the system model but interacts
with it in some or the other way. An actor may be a person, machine or an
information system that is external to the system model. An actor is represented by a
stick figure and is not a part of the system itself. Customers, users, external devices
interacting with the system are treated as actors.
Use cases: It is initiated by the user with a particular goal in mind, and completes
success-fully when that goal is satisfied. it describes the sequence of interactions
between actors and the system necessary to deliver the services that satisfies the
goal. It also includes possible variants of this sequence. The system is represented
by the rectangular box that contains oval shaped use cases. The actors are
represented by the sticks as shown in figure above. The use case can be described
as: Figure 4.4 shows the Use Case Diagram.
Chapter 7
Advantages
Advantages:
Audio and video based Steganography has the potential to conceal more
information:
Another aspect of audio and video Steganography that makes it so attractive is its
ability to combine with existing cryptography technologies.
Users no longer have to rely on one method alone. Not only can
information be encrypted, it can be hidden altogether.
Security:
Chapter 8
Needs and Application
Especially, GTECH Hide & View program embeds data in an extremely fragile
manner.
Media data (photo picture, movie, music, etc.) have some association with other
information. A photo picture, for instance, may have the following.
(1) The title of the picture and some physical object information
(2) The date and the time when the picture was taken
(3) The camera and the photographer's information
Chapter 9
Screen Shots
Screen Shots
Here we Enter text and enter text and select carrier file to encrypt
This form is specially design for only local user (local user can decrypt file only)
Conclusion
The proposed approach in this project uses a new steganographic approach
called audio and video steganography. The application creates a stego audio and
video in which the personal data is embedded and is protected with a password
which is highly secured. The main intention of the project is to develop a
steganographic application that provides good security. The proposed approach
provides higher security and can protect the message from stego attacks. The image
resolution doesnt change much and is negligible when we embed the message into
the audio and video and the audio and video is protected with the personal
password. So, it is not possible to damage the data by unauthorized person. We used
the Least Significant Bit algorithm in this project for developing the application
which is faster and reliable and compression ratio is moderate compared to other
algorithms. The compression depends on the document size as well as the carrier
audio and video size. Steganography has its place in security. It is not intended to
replace cryptography but supplement it. Hiding a message with steganography
methods reduces the chance of a message being detected. However, if that message
is also encrypted, if discovered, it must also be cracked (yet another layer of
protection).
References
1) N.F. Johnson and S. Jajodia, Exploring steganography: Seeing the unseen 31(2)
(1998) 26- 34