Hi Sergei,
On Thu, Feb 08, 2007 at 01:38:22PM +0300, Sergei Vyshenski wrote:
> 1) observing crypto layer policy through the whole code. That is
> remove explicit use of crypto algorithms names and features, in
> favor of calling high-level module to determine which crypto
> backends and crypto algs are actually available at the server. Fix
> webforms to determine the same at the client side.
Sounds interesting, I'm looking forward to having a look at that.
> Most affected existing files are:
> trunk/perl-modules/core/trunk/OpenXPKI/Server/Workflow/Activity/Key/Generate.pm
Please note that (to my knowledge) this file is obsolete.
> trunk/clients/perl/OpenXPKI-Client-HTML-Mason/lib/OpenXPKI/Client/HTML/Mason/Javascript.pm
While you're at it, I believe we should consider moving the
Javascript/VBScript functions into a separate file, so that each HTML
file does not always include the whole Javascript stuff.
> I would appreciate if you allow a couple of days for this job to be
> completed.
No problem on our side, I guess. I am currently working on the
notification layer and the RT integration, which is pretty much indepent
of anything else.
Regards,
Alex
--
Dipl.-Math. Alexander Klink | IT-Security Engineer
[EMAIL PROTECTED] | working @ urn:oid:1.3.6.1.4.1.11417
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel
