On Monday 05 January 2015 14:33:59 Paul Eggleton wrote: > Hi Fan, > > On Friday 28 November 2014 06:05:36 Fan, Xin wrote: > > I wonder that why the ntp uses the without-openssl build option and > > disables the openssl by default. > > > > In my opinion, the ntp needs openssl to support public key cryptography > > and > > it should be enabled by default. > > I set it up this way originally because I didn't figure SSL to be that > important for a protocol like ntp for the common case. To my mind, it > depends on what you are doing with time on the system which is being > synchronised - if you are only using it to display a clock somewhere for > the user, the security of the connection to the ntp server isn't really > that important vs. avoiding the dependency on another library. If on the > other hand you are writing logs or you are using a time-sensitive protocol > such as Kerberos on the same system then you might want to consider > enabling it. > > There will always be differences in how people expect software to be > configured for whatever target and application they are building for, hence > why we make it fairly easy to adjust the configuration. In this case you > only need to set your own PACKAGECONFIG value for ntp to include "openssl" > and SSL support will be enabled.
(I should have added, my apologies for the very late reply). Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
