[Swan-dev] exploiting DBGF

Andrew Cagney andrew.cagney at gmail.com
Mon Jun 10 13:39:25 UTC 2019


Did you mean dbg(), introduced 6 months ago(?) :-).  It merges:

/* so things don't break */
#define DBG_RAW         DBG_BASE
#define DBG_PARSING     DBG_BASE
#define DBG_EMITTING    DBG_BASE
#define DBG_CONTROL     DBG_BASE
#define DBG_LIFECYCLE   DBG_BASE
#define DBG_KERNEL      DBG_BASE
#define DBG_DNS         DBG_BASE
#define DBG_OPPO        DBG_BASE
#define DBG_CONTROLMORE DBG_BASE
#define DBG_NATT        DBG_BASE
#define DBG_X509        DBG_BASE
#define DBG_DPD         DBG_BASE
#define DBG_XAUTH       DBG_BASE
#define DBG_RETRANSMITS DBG_BASE
#define DBG_OPPOINFO    DBG_BASE

Perhaps start with files that no one is touching, such as, cough, IKEv1.


On Sun, 9 Jun 2019 at 23:32, D. Hugh Redelmeier <hugh at mimosa.com> wrote:
>
> DBGF was introduced over a year ago.  It makes code more concise and
> understandable.  I think that it is time to systematically exploit
>
> I started to make the changes but paused: since the changes are pervasive
> (but simple), I should ask if folks have large branches in flight?
>
> If so tell me.  Otherwise I will continue.
>
> | commit 1ec1c98a0926f2324761be3c1354371b786fe4ea
> | Author: D. Hugh Redelmeier <hugh at mimosa.com>
> | Date:   Sun Jun 9 23:25:23 2019 -0400
> |
> |     start systematically exploiting DBGF
> |
> |     After over a year, it's about time.
> _______________________________________________
> Swan-dev mailing list
> Swan-dev at lists.libreswan.org
> https://lists.libreswan.org/mailman/listinfo/swan-dev


More information about the Swan-dev mailing list