- Open Access
- Total Downloads : 547
- Authors : I.Syamalatha, K.N.V.S.S.K. Rajesh
- Paper ID : IJERTV1IS6398
- Volume & Issue : Volume 01, Issue 06 (August 2012)
- Published (First Online): 30-08-2012
- ISSN (Online) : 2278-0181
- Publisher Name : IJERT
- License: This work is licensed under a Creative Commons Attribution 4.0 International License
Identity-Based Security Architecture Achieving Anonymity and Traceability in Wireless Mesh Network
I.SyamaLatha1, K.N.V.S.S.K. Rajesh 2
1 PG student of CS, 2 Asst.professor
Dept of Computer Science and Engineering1, Dept of Computer Science and Engineering 2, 1 Kakinada Institute of Engineering and Technology, koragi- 533461, e.g.dt, A.P.
2 Kakinada Institute of Engineering and Technology, koragi- 533461, e.g.dt, A.P.
Abstract: A wireless mesh network is very similar to a regular wireless network. However the difference is that the former network covers a much larger area, than the later. The nodes in the WMNs can configure automatically and re-configure dynamically to maintain the mesh connectivity. One of the fundamental challenges in WMNs is how to achieve Anonymity and traceability for mobile node. In the existing architecture Domain administrator issues the Batch of tickets to the mobile client, it increases the mobile clients storage overhead and adversary attacks. To avoid this I present a new system in which the Domain administrator provides single Ticket to the client during the ticket issuance protocol based on the user profile which is included in agreement and It includes the renewal field for deposited Ticket. It increases the client connectivity with its home Domain administrator with considerable anonymity and traceability. Further this model increases the efficiency.
Index Terms- Anonymity, Misbehavior, Psedonymn, revocation, Traceability, Wireless mesh network (WMN).
-
Introduction
As various wireless networks evolve into the next generation to provide better services, a key technology, wireless mesh networks (WMNs), has emerged recently. In WMNs, nodes are comprised of mesh routers and mesh clients. Each node operates not only as a host but also as a router, forwarding packets on behalf of other nodes that may not be within direct wireless transmission range of their destinations. A WMN is dynamically self-organized and self-configured, with the nodes in the network automatically establishing and maintaining mesh connectivity among themselves (creating, in effect,
an ad hoc network). This feature brings many advantages to WMNs such as low up-front cost, easy network maintenance, robustness, and reliable service coverage.
Conventional nodes (e.g., desktops, laptops, PDAs, PocketPCs, phones, etc.) Equipped with wireless network interface cards (NICs) can connect directly to wireless mesh routers. Customers without wireless NICs can access WMNs by connecting to wireless mesh routers through, for example, Ethernet. Thus, WMNs will greatly help the users to be always-on-line anywhere anytime. Moreover, the gateway/bridge functionalities in mesh routers enable the integration of WMNs with various existing wireless networks such as cellular, wireless sensor, Wi-Fi, WiMedia networks. A device that can use Wi-Fi (such as a personal computer, video game console, Smartphone ,tablet or digital audio player) can connect to a network resource such as the Internet via a wireless network access point (or hotspot) has a range of about 20 meters (65 feet) indoors and a greater range outdoors. Hotspot coverage can comprise an area as small as a single room with walls that block radio waves or as large as many square miles. This is achieved by using multiple overlapping access points. Consequently, through an integrated WMN, the users of existing network can be provided with otherwise impossible services of these networks
A wireless mesh network (WMN) [2] is a communications network made up of radio nodes organized in a mesh topology. Wireless mesh networks often consist of mesh clients, mesh routers and gateways. The WMN is shown in Figure 1.The mesh clients are often laptops, cell phones and other
wireless devices while the mesh routers forward traffic to and from the gateways. A mesh network is reliable and offers redundancy.
When one node can no longer operate, the rest of the nodes can still communicate with each other, directly or through one or more intermediate nodes. Home and business networkers looking to buy wireless local area network gear face an array of choices. Many products conform to the 802.11a, 802.11b, 802.11g, or 802.11n wireless standards collectively known as Wi-Fi technologies. Additionally, Bluetooth and various other non Wi-Fi technologies also exist, each also designed for specific networking applications.
Fig 0. Wireless Mesh Network
Anonymity and traceability are left unattended. In WMNs the mobile node with high mobility can easily compromised by the adversary node in that network .so security is more important before the deployment of such networks. Nowadays user privacy is very important while accessing the network. For instance Anonymity is highly required for the honest user to unlink a users identity to his or her specific activities in the network. And traceability is required for the misbehaved node in the network. Conditional anonymity is required for the misbehaved mobile node to trace its activity by Domain Administrator (or TA). Several solutions have been proposed in WMNs to address the privacy issues for mobile users.
-
Related Works
Sensor networks are typically characterized by limited power supplies, low bandwidth, small memory sizes and limited energy. This leads to a very demanding environment to provide security.
Majority of security issues have not been addressed and surveyed in I.F. Akyildiz, X. Wang, and W. Wang [2].Universal pass model [3] proposed for WMNs, addressing countermeasures to wide range of attacks in WMNs. In J. Sun, Chi Zhang, Yanchao Zhang and Yuguang Fang [1]the TA provides free Internet access but requires the clients (CLs) to be authorized and affiliated members generally for a long term so that Ticket based security architecture was developed which includes Ticket issuance, Ticket deposit, .Design of a ticket-based anonymity system with traceability property; bind of the ticket and pseudonym which guarantees anonymous access control (i.e., anonymously authenticating a user at the access point and simplified revocation process
,revocation of Tickets, adoption of the hierarchical identity-based cryptography (HIBC) for interdomain authentication avoiding domain parameter certification are illustrated in[1].the following figure[fig 1] explains the Ticket issuance and Deposit phase[1].
Ticket Issuance
Here Ticket issuance occurs when the client initially attempts to access the network or when all previously issued tickets are depleted. The client needs to reveal his real ID to the TA(Trusted Authority) in order to obtain a ticket since the TA has to ensure the authenticity of this client. After some process TA issues batch of Tickets to MN (mobile Node) . The ticket generation algorithm[1], which can be any restrictive partially blind signature scheme in the literature, takes as input the clients and TAs secret numbers, the common agreement c, and some public parameters, and generates a valid ticket . A design issue to be pointed out is the commonly agreed information c negotiated at the beginning of the ticket generation algorithm. We define C as (Ticket Value, Expiry Date, and Misbehavior)
Ticket Value -The total amount of traffic that the client is allowed to generate and receive before the expiry date of the ticket Misbehavior-Ticket reuse and multiple deposits
Expiry Date-Ticket expiry date (validity period) After obtaining a valid ticket, the client may deposit it Anytime the network service is desired before the ticket expires, using the ticket deposit protocol.
p>Misbehavior It is totally different from noncompliant behavior.
Stora
Tic D ge
ket G D
dep W B
osit
reques
e-cash systems where it is used for detecting and tracing double-spenders.
Each client can get the batch of Tickets during the Ticket issuance phase, so that client memory will be increased. And it place extra overhead in revocation process of unused Tickets. Here Ticket
Cli ent
t
M R
Initiall y
Depos it
G W
T D
A B
Client ID
TAs
Secret
value is assigned based on past misbehavior history of mobile node (client), there is no possible decision making function during the Ticket generation process for the mobile node who want to be a permanent user within that trust domain.
IV Proposed System
access memb er
Registr Tic
Ticket generat ion
Numbe r
Public
Commo n Agreem ent
Blind Signature
In general, a blind signature scheme allows a receiver to obtain a signature on a message such that both the message and the resulting signature remain unknown to the signer. We refer the readers for a formal definition of a blind signature scheme, which
Paramet
Fig 1. Ticket issuance and deposit
Limitations
Each client can get the batch of Tickets during the Ticket issuance phase, so that client memory will be increased. And it place extra overhead in revocation process of unused Tickets. Here Ticket value is assigned based on past misbehavior history of mobile node (client), there is no possible decision making function during the Ticket generation process for the mobile node who want to be a permanent user within that trust domain.
III Existing System
In wireless communication systems, it is easier for a global observer to mount traffic analysis attacks by following the packet forwarding path than in wired networks. Thus, routing anonymity is indispensable, which conceals the confidential communication relationship of two parties by building an anonymous path between them. Nevertheless, unconditional anonymity may incur insider attacks since misbehaving users are no longer traceable. Therefore, traceability is highly desirable such as in
should bear the properties of verifiability, unlink ability, and unforge – ability.
Restrictiveness: This property restricts the user in the blind signature scheme to embed some account- related secret information into what is being signed by the bank (otherwise, the signing will be unsuccessful) such that this secret can be recovered by the bank to identify a user if and only if he double-spends. The restrictiveness property is essentially the guarantee for traceability in the restrictive blind signature systems.
Partial Blindness: A signature scheme is partially blind if all probabilistic polynomial time algorithms win the game in the signature issuing protocol with probability.
Ticket Generation based on user profile
In order to maintain security of the network against attacks and the fairness among clients, the home TA may control the access of each client by issuing tickets based on the misbehaviour history of the client, which reflects the TAs confidence about the client to act properly. Ticket issuance occurs when the client initially attempts to access the network [1][fig 2]
The proposed system includes the common agreement c ( Val, exp , Mis , User Profile) for obtaining ticket from Domain Administrator(i.e. TA).
User Profile consists of 1) Long Term User with less anonymity 2) Short Term User with high anonymity based on this the client can get the suitable ticket value (Min or Max).restrictive Partially blind signature scheme is used for achieving anonymity for user [1] which borrows the blind signature technique [5][6][7] to achieve anonymity.ID based cryptography used for authentication purpose.
TA
Trusted Authority
Long Term User with less anonymity
If the client initially entered into the network, he or she can request Ticket from the TA to access the internet with free of cost .first the TA authenticates the client then it issues the Ticket to achieve anonymity and traceability of client. If the clients want to be a permanent user in particular domain, he or she uses this field. During the ticket generation protocol if the client sends this common agreement ( c )
C (Val, exp, Mis, Long Term User)
Then the TA does the following steps
checks the past misbehavior history of the corresponding client
If (mis=0) then
checks the client anonymity requirement Status
If (anonymity=not strict)
Short Term User
The common agreement( c ) , C(Val, exp, Mis, short Term user) is used to get the Ticket with lower value. Normally TA sets the lower value for the misbehaved clients to punish the clients. In addition if the mobile client having high mobility and it needs strict anonymity scheme, this field is used. The TA checks the user profile field in the C and assigns the value based on user requirements.
Note: The user profile can be varied for each time
Gateway
Mesh Router
Mesh Client ID
GW
M
C
User Profile
based on anonymity requirement of corresponding user.
Deposited Ticket Renewal Process
After depositing a Ticket on a GW, the client can access the services until the Ticket expired, in the following cases the client can request Renewal process. The record generated by GW to the deposited ticked and forwarded to TA. This includes Renewal request.
Case 1: deposited ticket value is depleted before the expiry time.
Figure 3: profile based ticket request
The mobile client can enter its ID and related information along with User profile to TA to get the Ticket [Fig 3].
Renewal request processing steps 1 .DGW informs the Client
(i.e. c(val=0,mis=0,exp=not expired)) 2 If the Client wants renewal then Renewal (ticket)
Else
Revocation (ticket)
-
DGW sends the request to TA
-
DGW and TA databases are updated
Case 2: The client wants to access the internet under the same ticket. i.e. the following condition
C (Val=0,mis=0,exp=expired)
Renewal process applicable only for the deposited Ticket (mis=0), and renewal process doesnt give fresh Ticket, it will increase the Ticket value for few seconds only .computation complexity increased for GWs in which renewal process is carried out.
Security Analysis
Simplicity in Wireless Sensor Network with resource constrained nodes makes them extremely vulnerable to variety of attacks. Attackers can eavesdrop on our radio transmissions, inject bits in the channel, replay previously heard packets and many more. Securing the Wireless Sensor Network needs to make the network support all security properties: confidentiality, integrity, authenticity and availability. Attackers may deploy a few malicious nodes with similar hardware capabilities as the legitimate nodes that might collude to attack the system cooperatively. The attacker may come upon these malicious nodes by purchasing them separately, or by "turning" a few legitimate nodes by capturing them and physically overwriting their memory. Also, in some cases colluding nodes might have high-quality communications links available for coordinating their attack.
Framing Resistance
If the client is honest with over-whelming probability the representation is different from that the malicious TA falsely generated.
Fundamental Security Objective
It is trivial to show that the security requirement for authentication, data integrity and confidentiality which follows directly from the employment of the standard cryptographic primitives namely digital signature, message authentication code and encryption.
Traceability
It is also called as conditional anonymity. According to this definition this requirement is twofold.
-
Anonymiy for honest clients is unconditional.
-
A misbehaving client is traceable where the identity can be revealed.
Unforgeability
The proof of unforgeability adopted restrictive partially blind signature scheme is existentially unforgeable against adaptively chosen message and ID attacks under the assumption of the intractability of CDHP in G1 and the random oracle.
We conclude that the proposed security architecture satisfies the security requirements for anonymity, traceability, framing resistance, and unforge ability, in addition to the fundamental objectives including authentication, data integrity, confidentiality, and non repudiation, under the assumption that CDHP in G1 is hard and the random oracle.
Efficiency Analysis
In existing a batch of Tickets is assigned to requested clients, but in this proposed model restriction applied for client requested message i.e. a client can get single Ticket during the ticket generation process. It decreases the clients storage overhead. The renewal process decreases the computation overhead of client. Revocation processes of unused tickets are eliminated. If the client wants another Ticket, it must initiate the revocation process for the old.
The inter domain access is enabled by the hierarchical ID-based cryptosystem, the implementation of which largely determines the efficiency of the inter domain access. The communication and computation efficiency is best achieved using the Dual-HIDS
The client transmits approximately 148 bytes and 446 bytes respectively, for a new ticket request and a ticket deposit request. They correspond to the transmission time of 1.18 and 3.57 ms, respectively, assuming a 1 Mbps communication link between the client and the gateway. In the new ticket request, the client needs to perform an HIDS signing and verification, a symmetric-key encryption, and an HMAC, among which the HIDS operations dominate the computation costs. The signing involves only four point multiplications (three for HIDS and one for deriving the symmetric key), one point addition, and one hash evaluation, and can be
efficiently carried out160bit HMAC output), respectively, for a new ticket request and a ticket deposit request.
Communication
Our ticket-based security architecture consists of four intradomain protocols in which ticket deposit involves only clients and gateways. This protocol is distributed in nature, and thus, the communication cost incurred is more affordable. In contrast, protocols involving interactions with the centralized TA contribute largely to the expensive communication costs in the system. In the fraud detection protocol, gateways report accumulated ticket records to the TA periodically instead of in real time. Reports from gateways can be scheduled at different time intervals, avoiding a sudden increase in the communication overhead caused by simultaneous transmissions.
Ticket issuance and revocation may take place in real time. The associated communication overhead depends on how frequent 1) the clients use up issued tickets and 2) the clients misbehave. One can expect minimal real-time interaction with the TA for systems where ticket issuance is based on the clients usage trend (such that ticket requests other than scheduled will be infrequent) and there is a well behaving majority. Since multiple tickets are issued to the client at each scheduled interval, the average communication cost can be further reduced because some parameters need only be transmitted once. In a single ticket issuance, the client sends roughly 60 bytes (i.e., three 160-bit elements) to the TA. The TA sends to the client approximately 128 bytes (i.e., four G1 elements and two 160-bit HMACs).
Storage
The TA may consist of several servers to store necessary information from all clients during protocol executions. The storage capability of these high end servers is usually not a concern, and therefore, we focus on the storage overhead encountered at the low-end client side.
Fortunately, many pairing operations in the protocols can be computed once and stored for future use. Furthermore, some stored information remains unchanged for all instances of protocol execution (e.g., all tickets issued in the ticket
issuance protocol). As a result, we need merely take into account the effective storage overhead (i.e., information that is changed and has to be stored at each protocol instance).
In ticket issuance, the client stores for each protocol Instance 621 bytes pre computed information and 43 bytes after-protocol information for future use.
Computation
In ticket issuance, the client only computes two basic pairings in real time for each protocol instance. The remaining pairing operations can either be computed once or be pre computed and stored for all protocol instances.
Several HMAC operations also need to be performed in real time, which is considered computationally efficient. In ticket deposit, one signing, one verification, and two HMAC operations are performed in real time by the client for each ticket deposited. All pairings involved in this protocol can be pre computed except one for the verification. A finite field exponentiation is needed for the signing. Similarly, in ticket revocation, a client has to compute one signature in real time for each revoked
V. Conclusion
An Identity-Based security architecture mainly consisting of the ticket based protocols, which resolves the conflicting security requirements of unconditional anonymity for honest users and traceability of misbehaving users. If the network ID of a clients device is fixed and exposed in packet forwarding, the packets sent by a same client can be linked, which will enable the attackers to profile the client through traffic analysis attacks. By utilizing the tickets, self-generated pseudonyms, and the hierarchical identity-based cryptography, the proposed architecture is demonstrated to achieve security objectives and efficiency.
REFERENCES
-
IEEE transactions on Depentable and Secure computing vol 8, NO.2 march-april 2011 SAT: A Security Architecture Achieving Anonymity and Traceability in Wireless Mesh Networks Jinyuan Sun, Chi Zhang, Yanchao Zhang, and Yuguang Fang,
-
I.F. Akyildiz, X. Wang, and W. Wang, Wireless Mesh Networks: A Survey, Computer Networks, vol. 47, no. 4, pp. 445- 487, Mar. 2005.
-
Y. Zhang and Y. Fang, ARSA: An Attack- Resilient Security Architecture for Multihop Wireless Mesh Networks, IEEE J. Selected Areas Comm., vol. 24, no. 10, pp. 1916- 1928, Oct. 2006.
-
X. Chen, F. Zhang, and S. Liu, ID-Based Restrictive Partially Blind Signatures and Applications, J. Systems and Software, vol. 80, no. 2, pp. 164-171, Feb. 2007.
-
S. Brands, Untraceable Off-Line Cash in Wallets with Observers,Proc. 13th Ann. Intl Cryptology Conf. Advances in Cyptology (CRYPTO 93), pp. 302-318, Aug. 1993.
-
K. Wei, Y.R. Chen, A.J. Smith, and B. Vo,
Whopay: A Scalableand Anonymous Payment System for Peer-to-Peer Environments, Proc. IEEE Intl Conf. Distributed Computing Systems (ICDCS), July 2006.
-
D. Chaum, Blind Signatures for Untraceable Payments, Advancesin CryptologyCrypto 82, pp. 199-203, Springer-Verlag, 1982.
-
D. Boneh and M. Franklin, Identity-Based Encryption from the WeilPairings, Advances in Cryptology-Asiacrypt 2001, pp. 514-532, 2001.
-
J. Sun, C. Zhang, and Y. Fang, A Security Architecture Achieving Anonymity and Traceability in Wireless Mesh Networks, Proc. IEEE INFOCOM, pp. 1687-1695, Apr. 2008.
-
Y. Zhang, W. Liu, W. Lou, and Y. Fang,
Securing Mobile Ad Hoc Networks with Certificateless Public Keys, IEEE Trans.
Dependable and Secure Computing, vol. 3, no. 4,pp. 386-399, Oct. 2006.
Ms.I.Syamalatha, received the B.Tech degree in Computer Science Information Technology from J N T University. She is pursuing M.Tech in Computer Science from J.N.T.U, Kakinada.
p>Mr.K.N.V.S.S.K.Rajesh received his M.Tech degree from JNT University Kakinada in Computer Science and Engineering and currently working as Asst. Professor in the department of CSE of Kakinada Institute of Engineering and Technology.