If you want to know which crypto algorithms are proposed and supported then either increase the debug level in ipsec.conf
charondebug="cfg 2" or change the log level dynamically during runtime with sudo ipsec stroke loglevel cfg 2 Best regards Andreas On 07/14/2015 12:36 PM, Giulio Ambrogi wrote: > Dear community, > > is there any way to find what does strongSwan really do when > negotiating encryption and authentication algorithms (e.g.using > field/conn> *esp=encr-auth-[dh]*/*)* , expecially I would like to know > which algorithms are chosen as result of the negotiation. > The log printed out on the terminal when using "*ipsec up <conn_name>*" > doesn't show those information. > Is there any way to make this log more verbose? Or is there any useful > log file ? > Thanks , > > > Giulio > > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.strongswan.org/mailman/listinfo/dev > -- ====================================================================== Andreas Steffen [email protected] strongSwan - the Open Source VPN Solution! www.strongswan.org Institute for Internet Technologies and Applications University of Applied Sciences Rapperswil CH-8640 Rapperswil (Switzerland) ===========================================================[ITA-HSR]==
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Dev mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/dev
