For a better formatted document, download http://files.1t-s.com/gaf/LinuxSrv.pdf

Maximum project budget $5,000

You MUST
Have great experience in Linux, Perl, creating security certificates & keys (PKI) and creating secure connections. I am looking for a team with a strong security background to help me deliver a very secure system.

Do NOT
Post generic or standard bids – they will be ignored. No time wasters. Bid only if you have strong skill sets that are relevant to this project.

Timescale
Once the project has been awarded, the project must be completed to a beta testing stage in 60 days or less.

Introduction
The aim is to set up is secure private electronic mail service network that clients can connect to and send each other messages and files as attachments. The server application (this project) will run on multiple Linux systems to provide a network of servers that will form the backbone of the secure electronic mail service.

Individual mailboxes are hosted on user PCs (personal mail server, WIMS). Clients will contact a designated system server to get authorisation and attempt to send the message directly to the destination mailbox, bypassing the system servers. If the destination mailbox is offline, then the message will be delivered to one of the system servers, designated as a backup host server (BHS). The server does not relay the message. Instead, the message is stored till the client system connects to collect waiting messages. In essence, the system is a secure, direct delivery or store till collected electronic mail system.

Within the group of Linux servers, one will be nominated as the master / index server (IS) and will provide additional functionality including support for a secure web-portal which will act as the front-end to managing customer, domain names, email account and other related details.

This project is to develop the Linux server functionality only. Other components (WIMS server and secure web portal) will be developed separately as different projects. Overall project description and further details will be provided to suitable bidders.

Some of the features required include:
. Admin panel.
. Initially support 32-bit Linux OS but must be scalable to 64-bit Linux OS.
. Support for high volume of concurrent connections (20k+).
. Connections are both secure (SSL / TLS) and non-secure.
. User account, partnerships details and other system data are automatically distributed / shared between the Linux servers.
. Security Keys (PKI). Create, manage and issue security certificates & keys for servers (BHS and WIMS) and mailbox accounts.

Support for Secure Web-portal (HTTPS):
. Create and manage user login accounts (IS).
. Create, register and manage our own Domains and sub-domains (private to our service and not issued by Nominet, Internic or any domain registrar) (IS).
. Manage and maintain user transactions (save payments related details, record payment transactions etc..) on IS.
. Product pricing for a small list of products (20 approximately) (IS).
. Payment Gateway including automated ability to take money from user credit card when payments for services are due (IS).
. Create and manage mailbox accounts (email addresses) on free or registered domains (IS). New account details are sent to all backup servers.
. Domain & mailbox assignment. When new domains are created they are assigned (based on set criteria) to two or more Linux servers, which act as the mailbox backup host servers.
. Create and manage mailbox account details (profiles).
. Manage potential partner lists for each account (users will upload their contacts details from personal address books to see if they are also using this service).
. Manage user templates. The web-portal will be based on a templating engine and users may define / associate different templates with their accounts.
. Manage promotion agent details and commission earned on service sales.

Support for WIMS (Destination Mailbox Server):
. Handle and manage secure account logins (inbound connections).
. Time synchronisation. All servers time is synchronised to GMT and WIMS will get their date and time from the Linux servers.
. Register WIMS
. Cache WIMS last connection details.
. Send, receive and manage partnerships between accounts (only established partners can send messages to each other).
. Partnership profiles (account details that are exchanged) uploads / downloads.
. Part or full messages (these may be large, 4GB+ and are sent in small data chunks) may be sent or collected by WIMS, as binary data, for logged in account.
. Authorisations. WIMS must obtain authorisation before it can send a message.
. Support for direct end-to-end TCP/IP connections. Clients try to deliver mail directly to the destination WIMS. To allow this direct connection through firewalls, support will be required for UDP hole punching or something better.
. Download system files. System files (e.g. application software updates, details of network Linux servers and other service related files etc..).

Support for Linux Server - Linux Server:
. Copy / backup data between servers, over secure connections, for backup / safeguarding.
. Account details queries. Any mailbox backup-hosting servers may query the service index server about mailbox account details.

At the end:
· You will provide all source code and full documentation.
· Intellectual property passes to me.

Payment in milestones.