On 03/08/2011 04:30 PM, Marc-André Moreau wrote: > I have a suggestion regarding certificate validation: > > Looking at mstsc.exe, it appears to me that the certificate validation > is delegated to a module dedicated just to that. If we let the UI handle > it with a callback, maybe we could provide the UI with a library that > can handle it? This way, for instance, a system with both xfreerdp and > dfbfreerdp wouldn't need to have separate certificate validation. > Information could be stored in ~/.freerdp
We have to be wire-compatible with MS, but I'm not sure how much we should learn from MS when it comes to architecture. However, except for "is the certificate valid with regard to these CAs" question (which should be answered by the crypto library that already is encapsulated in libfreerdp) there isn't much code that could be reused. It is mostly policy and user interfacing, and that is closely related to how the GUI choose to do it. I also don't think it would make much sense if for example remmina looked in .freerdp. It should use its own configuration and UI. When it comes to FreeRDPs own simple UIs I think they should be built from the same source with a sufficient number of compile options, and branded as freerdp on all platforms. Exactly just like for example firefox is firefox on all platforms even though it differs and is platform specific in some points. That way they will all share the same command line options and configuration file parsers and so on - and they would all use ~/.freerdp. /Mads ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
