Avoid manually forward declaring BoringSSL types

Per go/cstyle#Forward_Declarations. BoringSSL already provides a forward declarations header. Also tidy up the source file's includes. It seems to only use symbols in aead.h.

PiperOrigin-RevId: 588069592
This commit is contained in:
hai007
2023-12-05 07:48:17 -08:00
committed by Copybara-Service
parent 454d24e837
commit 3a4f4cde9f
2 changed files with 3 additions and 5 deletions
+1 -2
View File
@@ -32,8 +32,7 @@
#include "absl/types/span.h"
#include "internal/crypto_cros/nearby_base.h"
#include "internal/crypto_cros/openssl_util.h"
#include <openssl/aes.h>
#include <openssl/evp.h>
#include <openssl/aead.h>
namespace crypto {
+2 -3
View File
@@ -26,8 +26,7 @@
#include "absl/types/optional.h"
#include "absl/types/span.h"
#include "internal/crypto_cros/crypto_export.h"
struct evp_aead_st;
#include <openssl/base.h>
namespace crypto {
@@ -87,7 +86,7 @@ class CRYPTO_EXPORT Aead {
size_t* output_length, size_t max_output_length) const;
absl::optional<absl::Span<const uint8_t>> key_;
const evp_aead_st* aead_;
const EVP_AEAD* aead_;
};
} // namespace crypto