Due to globalization, global trade is strongly growing nowadays. The use of containers has significantly increased and bringing the change on the shape of the world economy. Thus, monitoring every single container is a big challenge for port industries. Furthermore, rapid development in embedded computing systems has led to the emergence of Wireless Sensor Network (WSN) technology which enabled us to envision the intelligent containers. This represents the next evolutionary development in logistics industry to increase the efficiency, productivity, security of containerized cargo shipping. In this paper, we present a comprehensive containerized cargo monitoring system based on WSNs. We incorporated tilt/motion sensor to improve the network convergence time of container networks. Moreover, we periodically switch the nodes into sleeping mode to save energy and extend the lifetime of the network. Based on the technical implementation on a real container vessel, we strongly believed that our design which employed WSN technology is viable to be implemented in container logistics to improve port services and provide safe transport of containerized cargo.

Key agreement protocol is of fundamental importance in providing data confidentiality and integrity between two or more parties over an insecure network. In 2004, Popescu [14] proposed an authenticated key agreement protocol in which its security is claimed. However, Yoon and Yoo [19] discovered its vulnerabilities two years later and proposed an improved variant of it. In this paper, we highlight the vulnerability of this improved variant under the LaMacchia et al.'s extended Canetti-Krawczyk security model [12]. With this, we propose another enhanced version of Popescu's protocol which offers stronger security features and appears to be significantly more efficient than Yoon-Yoo's scheme. In order to justify our claims, we present a thorough heuristic security analysis on our scheme and compare the computational cost and security attributes with the surveyed schemes.

No abstract

No abstract

The goal of the Linuxe Standard Base (LSB) is to develop and promote a set of standards that will increase compatibility among Linux distributions and enable software applications to run on any compliant Linux system. There are currently LSB specifications available for the Intel Architecture IA-32e processors and for the 32and 64-bit PowerPCe, Itaniume, 31-and 64-bit zSeriese, and AMD64e architectures. This paper describes the process of building LSB-compliant applications, and covers the use of the LSB development environments, testing of binaries, and packaging. Development of the Linux** kernel was started by Linus Torvalds in 1991. By 1992, some early Linux distributions such as MCC (a Linux distribution from the Manchester Computing Centre), TAMU (a distribution from Texas A&M University) and SLS (Softlanding Linux System) were easily available over the Internet. Distrowatch.com, a comprehensive Web site following Linux distributions, has over 350 distributions in its database. 1 Standards for operating systems can reduce the incompatibilities between various implementations. The POSIX** standard is an example of an API (application programming interface) standard which has helped keep a certain level of commonality among UNIX** implementations. Where there are large numbers of implementations, as is the case with Linux, widespread core compatibility makes it possible to have applications that work correctly on many implementations. The Linux Standard Base (LSB) is a set of operatingsystem standards with the goal of increasing compatibility among Linux distributions and enabling software applications to run on any Linuxcompliant system. 2 The LSB is developed and promoted by the LSB workgroup of the Free Standards Group (FSG), an independent, non-profit organization dedicated to accelerating the use of free and open-source software by developing and promoting standards. 3 Other examples of standardization workgroups of the FSG are OpenI18n (which addresses issues of internationalization), Open-Printing, and the Open Cluster Framework (which defines standard clustering APIs). The LSB workgroup is divided into several subprojects, each of which is responsible for a major component of the project; such as, its specification, futures, testing, sample implementation, example