>Number:         8112
>Category:       misc
>Synopsis:       crypto reachover is an administrative nightmare
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    misc-bug-people (Misc Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 28 23:35:01 1999
>Last-Modified:
>Originator:     Charles M. Hannum
>Organization:
        Internetwork Hacker
>Release:        -current as of 19990719
>Environment:
        all platforms


>Description:
	It used to be the case that one could build an `exportable'
	system, and then build `domestic' separately, layering it on
	top.  Now, to build both an `exportable' system and the `secr'
	set, one has to build the entire system twice.  This is a
	major pain in the arse.

	Furthermore, Makefiles which silently DTWT if a file or
	directory isn't present are an absolutely horrible idea in
	general.

	It seems that now we have the worst possible combination: no
	direct crypto integration, *and* a painful and flaky mechanism
	for handling the unbundled tree.  Yuck.

>How-To-Repeat:
        Try to build a snapshot.

>Fix:
        Go back to making cryptosrc separately buildable, or integrate
        the crypto directly in the main source tree.

>Audit-Trail:
>Unformatted: