From 6c681a409c07657bb280e6ea83f9819e84f59512 Mon Sep 17 00:00:00 2001
From: Anthony Ramine <aramine@cloudflare.com>
Date: Mon, 9 Oct 2023 15:07:13 +0200
Subject: [PATCH] Remove boring::fips::enable (fixes #150)

In boringssl, FIPS_mode_set is more or less useless, and
it doesn't even set an error stack at all on failure,
so there is no point using it instead of FIPS_mode.
---
 boring/src/fips.rs | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/boring/src/fips.rs b/boring/src/fips.rs
index 05e40a4b..e578ae75 100644
--- a/boring/src/fips.rs
+++ b/boring/src/fips.rs
@@ -3,17 +3,8 @@
 //! See [OpenSSL's documentation] for details.
 //!
 //! [OpenSSL's documentation]: https://www.openssl.org/docs/fips/UserGuide-2.0.pdf
-use crate::cvt;
-use crate::error::ErrorStack;
 use crate::ffi;
 
-/// Moves the library into or out of the FIPS 140-2 mode of operation.
-///
-/// This corresponds to `FIPS_mode_set`.
-pub fn enable(enabled: bool) -> Result<(), ErrorStack> {
-    unsafe { cvt(ffi::FIPS_mode_set(enabled as _)).map(|_| ()) }
-}
-
 /// Determines if the library is running in the FIPS 140-2 mode of operation.
 ///
 /// This corresponds to `FIPS_mode`.