#.NET Code Project  
REST API or SOAP Testing Automation with ZeroCode JSON-Based Open Source Test Framework https://t.co/ZQ3eWz6no9
Developers Keep up to date: '.NET Code Project'

Blogs

<< | < | 456|> | >>
Username: Martin Okello, 19/11/2009 10:27:00 Delete post| Update post
EpsilonVPN Communique/Solution:

File transfers are done with AES 256 bit encryption, and transfered that way. The files are transfered to any participating clients in a conversation.

Also, you should note that, as opposed to saving a transfered file individually, the file is saved automatically on any client machine transfered to (in the conversation), and the receipient notified of the location which is under the Client Application installation directory. This negates file type problems.

Another addition to the Client application is the ability for invoking a client; who then decides if they want to accept you in their converation or not. This means you can limit those you want to communicate with - giving you an advantage over unwanted guests/eavesdroppers.

Cheerio.
Martin Okello
Aka The Medallion.
Username: Martin Okello, 29/10/2009 11:01:00 Delete post| Update post
Dear Customers,

A fault existed with this site where by users found it difficult to pay for software on transfering to Paypal.

This problem has been eradicated, with the revised application currently running, plus major upgrades to Paypal's integration on regressive tests have been performed to optimise the site's functionality.

There is no need to enable pop up windows for this site (http://www.martinlayooinc.co.uk) as the revision was performed to upper most standards.

Kindest regards
Martin Okello.
Aka The Medallion
Username: Martin Okello, 18/10/2009 11:58:00 Delete post| Update post
Improvements to EpsilonVPN Solution/Communique:

As a result of thorough regression tests, I have ironed out most of the Bugs in the Printing of Communications between Clients.

At this stage all is good, and would like to hear user's improved experiences regarding this. Further on RSA encryption has been rectified, however keys and padding though effective - times exist when the old bug crops up where encrypted text is not fully obtained. This mostly happens as a result of the padding algorithm which can't be improved. You are advised to stick to 3DES, and AES in cases where you require to send Bulky Communiques, otherwise, low range rsa up to 2048 bit is deemed safe for small encryption procedures.

Regards
Martin Okello.
Aka The Medallion
<< | < | 456|> | >>