Blogs
Username: guest, 27/01/2009 07:39:00
EpsilonVPN Solution Patch:
It was noted that File transfers of huge size failed in EpsilonVPN Client transfers.
This has been investigated, and due to the nature of Sockets Programming, Asynchronous Communication and Multi-Threading, the bug appeared to persist.
Finally, the Medallion's drawn experience and talent showed through, disbanding the problem as non-existent by means of a patch and debug exercise.
Regards
EpsilonVPN Solution Team.
It was noted that File transfers of huge size failed in EpsilonVPN Client transfers.
This has been investigated, and due to the nature of Sockets Programming, Asynchronous Communication and Multi-Threading, the bug appeared to persist.
Finally, the Medallion's drawn experience and talent showed through, disbanding the problem as non-existent by means of a patch and debug exercise.
Regards
EpsilonVPN Solution Team.
Username: guest, 24/01/2009 11:57:00
Hey All,
The bug that was addressed recently on AESCryptoSystem 1.0 has been fixed. This is when you encrypt and decrypt in the same session and during this same session change key strength, the application initially went into a finite loop: meaning froze.
The Bug was addressed on launching the application and currently fixed.
Regards
Aka The Medallion
The bug that was addressed recently on AESCryptoSystem 1.0 has been fixed. This is when you encrypt and decrypt in the same session and during this same session change key strength, the application initially went into a finite loop: meaning froze.
The Bug was addressed on launching the application and currently fixed.
Regards
Aka The Medallion
Username: guest, 22/01/2009 05:52:00
I have launched AES with strengths of 128, 192 and 256 bit Keys.
On testing, there appears to be some bug that does not allow a user to do a second encryption process having changed the key strength. The program goes into a stall state.
This needs prompt analysis and rectification. Gladly the medallion is not too far away; we are certain the problem will be resolved effectively.
AESCryptoSystem 1.0
Support Team.
On testing, there appears to be some bug that does not allow a user to do a second encryption process having changed the key strength. The program goes into a stall state.
This needs prompt analysis and rectification. Gladly the medallion is not too far away; we are certain the problem will be resolved effectively.
AESCryptoSystem 1.0
Support Team.
Al Jazeera Latest News
Thailand says ‘progress made’ in border dispute talks with Cambodia
The talks come after troops from the two countries exchanged fire last month, killing one Cambodian soldier.
