Research Electronics International
Research Electronics International specializes in the design and manufacture of electronic countermeasure equipment.

SSL Tunneling
SSL stands for Secure Socket Layer. The 'Secure' implies an encryption, while Socket Layer denotes an addition to the Window Socket system, Winsock. For those that don't know, a Socket is an attachment to a port on a system. You can have many sockets on one port, providing they are non-blocking (allowing control to pass through to another socket aware application which wishes to connect to that port).

A Secure Socket Layer means that any sockets under it, are both secure and safe. The idea behind SSL was to provide an encrypted, and thus, secure route for traffic along a socket based system, such as TCP/IP (the internet protocol). Doing this allows security in credit card transactions on the Internet, encrypted and protected communiqué along a data line, and overall peace of mind.

Secure Sockets Layer or SSL Torn Apart
Secure Sockets Layer or SSL is a secure protocol, which is the reason why secure E-Commerce and E-Banking is possible. It has become the de facto standard for secure and safe only transactions. When Netscape first developed SSL, the main aim or motive behind it was to ensure that the client and host can communicate or transfer data and information securely.

What SSL does in short would be, encrypt data at the sender’s end and decrypt data at the receiver’s end. This encrypted data cannot be picked up or hijacked in between and any tampering would not only be very difficult, it would easily be detected. Not only that, SSL also provides for two-way authentication i.e. verification of the client’s and the server’s identity.

Introduction to Denial of Serivice
In this paper I have tried to answer the following questions:

- What is a denial of service attack?
- Why would someone crash a system?
- How can someone crash a system.
- How do I protect a system against denial of service attacks?

Next-Generation Win32 exploits: fundamental API flaws
This paper presents a new generation of attacks against Microsoft Windows, and possibly other message-based windowing systems. The flaws presented in this paper are, at the time of writing, unfixable. The only reliable solution to these attacks requires functionality that is not present in Windows, as well as efforts on the part of every single Windows software vendor. Microsoft has known about these flaws for some time; when I alerted them to this attack, their response was that they do not class it as a flaw - the email can be found here. This research was sparked by comments made by Microsoft VP Jim Allchin who stated, under oath, that there were flaws in Windows so great that they would threaten national security if the Windows source code were to be disclosed. He mentioned Message Queueing, and immediately regretted it. However, given the quantity of research currently taking place around the world after Mr Allchin's comments, it is about time the white hat community saw what is actually possible.

This paper is a step-by-step walkthrough of how to exploit one example of this class of flaw. Several other attack methods are discussed, although examples are not given. There are many ways to exploit these flaws, and many variations on each of the stages presented. This is just one example.

Security pros develop flaw database
A broad group of hackers and security experts have banded together to create a new service that assembles information on vulnerabilities, security tools and bug-related discussions.

Snort on Windows 98/ME/NT4/2000
This documentation will hopefully help you to install Snort on your Win32 box. It will also help you install Snort as a service (Only available on NT4 and 2000), install MySQL as a database, and Acid to view your alert file that Snort will create.

Wireless Security & Hacking
This article deals with WLAN security, explains the most common attack techniques and introduces some useful tools.

Network security niche technologies
Alright this article is going to be concentrating on some of the more niche and what some people may consider obscure topics within the concept of network security, and giving you a basic synopsis of what they are, how they work, and how they’re implemented. Most of what is covered in articles about network security covers some of the more popular (and equally important) topics such as encryption (a topic I covered myself), proxies, firewalls, IP spoofing, VPNs, NetBIOS, etc. These are all good topics to cover and interesting and vitally important to discuss and understand. But with the growing trend of technological obscurity, I decided I'd try and write an article that covered the basics of some of the more obscure but still important topics in network security.Specifically those topics are DMZs (commonly known as de-militarized zones), vulnerability scanners (which are at this point are mostly not perfected, but have been gaining speed, and many people have been lending their expertise to the development of this technology), intrusion detection systems (a technology that’s been around for a long while, but is only now becoming a particularly trusted and more perfected technology), side-channel attacks as they are commonly known (something which has been gaining more and more popularity since the famous attacks against RSA in 1995), and finally steganography (the art of hiding messages, i.e. encrypting them so to speak in images, videos, etc. something