AFAIR even Google does not recommend using it in non-Google projects. "BoringSSL is a fork of OpenSSL that is designed to meet Google's needs. Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability." So I doubt Indy support would be a good idea. On the other hand, Windows Schannel native support may be a better idea for Indy.
The problem is that not all devices can deploy the openSSL libraries, in some cases boringSSL is always the default library and should migrate to other libraries all Android applications
AFAIR even Google does not recommend using it in non-Google projects. "BoringSSL is a fork of OpenSSL that is designed to meet Google's needs. Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability." So I doubt Indy support would be a good idea. On the other hand, Windows Schannel native support may be a better idea for Indy.
ReplyDeleteThe problem is that not all devices can deploy the openSSL libraries, in some cases boringSSL is always the default library and should migrate to other libraries all Android applications
ReplyDeleteIIRC Google states that BoringSSL is used by the system, but should not to be used by regular Android applications.
ReplyDeleteI read that but how can we use Indy on Android?
ReplyDelete