can substitute boringssl with openssl?
In general, it's not advised to do so. `boringssl` is a safer version of `openssl`, with none of the design choices that resulted in the `openssl` vulnerabilities that are famous (Hearthbleed) or not I know boringssl may have better security and performance, but our service not for public, so security may not so important to us. for we must use brpc, so we must use openssl, from you answer, I guess I can modify tensorflow to use openssl thanks a lot for anyone has same demand, use repo_mapping = { "@boringssl": "@openssl",} is the fastest sustitution way Are you satisfied with the resolution of your issue?
<a href="https://docs.google.com/forms/d/e/1FAIpQLSfaP12TRhd9xSxjXZjcZFNXPGk4kc1-qMdv3gc6bEP90vY1ew/viewform?entry.85265664=Yes&entry.2137816233=https://github.com/tensorflow/tensorflow/issues/60009">Yes</a>
<a href="https://docs.google.com/forms/d/e/1FAIpQLSfaP12TRhd9xSxjXZjcZFNXPGk4kc1-qMdv3gc6bEP90vY1ew/viewform?entry.85265664=No&entry.2137816233=https://github.com/tensorflow/tensorflow/issues/60009">No</a>
 > for anyone has same demand, use repo_mapping = { "@boringssl": "@openssl",} is the fastest sustitution way对于任何有相同需求的人，使用 repo_mapping = { “”： “”，} 是最快的 sustitution 方式

there?please
![image](https://github.com/tensorflow/tensorflow/assets/15188456/2acb73d0-56d0-4be7-a123-cff067ca4526)

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Build/Install

### Have you reproduced the bug with TF nightly?

Yes

### Source

source

### Tensorflow Version

tf 2.8.4

### Custom Code

No

### OS Platform and Distribution

ubuntu22.04

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current Behaviour?

```shell
my project import brpc and tf both, brpc must use openssl, tf use boringssl, so build will fail, can I modify tf use openssl?
```


### Standalone code to reproduce the issue

```shell
build conflict
```


### Relevant log output

_No response_</details>