Eibriel

Emesene Server (EServer)

“[...] will be possible for a business man in New York to dictate instructions, and have them instantly appear in type at his office in London or elsewhere. He will be able to call up, from his desk, and talk to any telephone subscriber on the globe, without any change whatever in the existing equipment. An inexpensive instrument, not bigger than a watch, will enable its bearer to hear anywhere, on sea or land, music or song, the speech of a political leader, the address of an eminent man of science, or the sermon of an eloquent clergyman, delivered in some other place, however distant. In the same manner any picture, character, drawing, or print can be transferred from one to another place. Millions of such instruments can be operated from but one plant of this kind. [...]“
Nikola Tesla (1908)
[On the Wardenclyffe Tower, in "The Future of the Wireless Art" in Wireless Telegraphy and Telephony (1908) ]

About:

Emesene Server (Eserver) is an Open Protocol for instant messaging. Now under heavy modifications, more information on Git Wiki

thanks:

• Steven Roddis

Resources:

• PePE Git
  
• Emesene2 Client – Ubuntu Deb Package
• Emesene Server Main Page

Currently Working:

Server:

• Nothing

Client:

• Nothing

Screeshots:

Goals:

Make a secure, strong instant messaging protocol. Based on P2P and capable to easily transmit and stream data. The main target users are people interested on social and entertain chat.

Inspiration:

Basis: Microsoft Live Messenger
Operation mode: Skype
Other: Neuronal systems

Tecnology:

• XMPP
• P2P
• Distributed hash table
• OTR (Off the Record) – Socialist Millionaire
• OpenPGP
• OpenID

Description:

When switch from Node to Supernode?:

If the node can Receive connections from a Supernode on port 80, 443 and another one.
And accept and make TCP and UDP connections.
And have more than 1Gb ram (or two).

When switch from Supernode to Node?:

If the Supernode don’t receive connections or fail on create.
Or have less than 1Gb ram.

Server-Client:

Proposed scheme based on Layers. Every layer could be set on the fly to stablish communication.

The client have 6 layers: Authentication layer, that set the Authentication Type required to stablish communication (the number on the Phone). Input Layer, that set the input of the Object to transmit (Mic). The Listen Layer set the communication port that is always opened and waiting information (Line In). The Process Layer take the information and redirect it to the proper location to process and generate an answer (Integrated Circuit). The Security Layer encrypt the answer message properly (? on cell phones). The Output Layer send the message (Line Out).

The server have 5 layers, basically the same as Client but not the Input one: The Listen Layer set the communication port that is always opened and waiting information (Line In). Authentication layer, that set the Authentication Type required to stablish communication (the number of the line on the Phone). The Security Layer decrypt the message (? on cell phones). The Process Layer take the information and redirect it to the proper location to process and generate an answer (Central). The Output Layer send the message (Line Out).

Client:

Authentication Layer:

1. None
2. UserName
3. UserName – Password
4. UserName – Passphrase
5. ClientName – Passphrase | UserName – Passphrase

Input Layer:

1. Generation
2. Stdinput
3. Parameter (From outside)

Listen Layer:

1. HTTP
2. Port UDP/TPC

Process Layer:

1. Function
2. Authentication

Security Layer

1. Plain
2. Simple encriptation

Output Layer

1. Stdout
2. Return
3. HTTP POST/GET
4. HTTPS POST/GET

Server:

Listen Layer:

1. HTTP POST/GET (web server)
2. HTTPS POST/GET (web server)
3. Port UDP/TPC

Authentication Layer:

1. None
2. UserName
3. UserName – Password
4. UserName – Passphrase
5. ClientName – Passphrase | UserName – Passphrase

Security Layer:

1. Plain
2. Simple encriptation

Process Layer:

1. Function
2. Authentication

Output Layer:

1. HTTP
2. HTTPS
3. Port UDP/TPC

Example:

Client ->
Hi Server!
Server ->
Hi Client!

Client:

Authentication:
None ->
No Action

Input Layer:
Parameter ->
Object=”Hi Server!”
Type=”text”

Security Layer:
Plain ->
No Action

Output Layer:
HTTP POST ->
www.server.com?erequest=<erequest type=”text”>Hi Server!</erequest>

Server:

Listen Layer:
HTTP POST->
<erequest type=”text”>Hi Server!</erequest>

Security Layer:
Plain ->
No Action

Process Layer:
Function ->
Object=”Hi Server!”
Type=”text”

Function:
always return “Hi Client!”.

Output Layer:
HTTP ->
echo “<erequest type=”text”>Hi Client!</erequest>”

Client:

Autentication:
Direct Response ->
No Action

Listen Layer:
HTTP->
<erequest type=”text”>Hi Client!</erequest>

Input Layer:
Parameter ->
Object=”Hi Server!”
Type=”text”

Process Layer:
Function ->
Object=”Hi Server!” Type=”text