> B. The commands will be provided, with requirements that > > 1. "Non-FIPS" disclaimer text will be added to required > manual pages. > > 2. Code/functionality duplication accepted, as these > implementations are common across a variety of platforms > and downstream deviation presents an ongoing maintenance > cost. > > (shred is already en route to handling similar to B. su is being > omitted based on an assessment that the cost of steps similar to A > would be uneconomic.) >
Isn't it the case that schred does not work on ZFS so why provide it at all? Casper
