Re: [twsocket] Android
> Means if there would be some sort of AnsiString support say for > Linux one could continue to work on it because the amount of work > needed would be way less? Yes, if a new version of Delphi restored base1 AnsiStrings, life would be much easier, avoiding our own AnsiString units and changes everywhere to use them. OS-X was supported by Arno which is effectively Linux already, however I don't have any Apple Macs without which the mobile version can not be built. I do have Android but I have too many other things to do than learn Linux from scratch, at my age! Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Android
> >> Now my other topic: what became of the idea to support Android >> which came up lately? > > Effort on mobile platforms and Linux stalled due the massive changes > needed to replace missing AnsiStrings. Also little demand. Means if there would be some sort of AnsiString support say for Linux one could continue to work on it because the amount of work needed would be way less? > >> The issue is, that since Android 6 Google switched from OpenSSL >> to its own BoringSSL implementation and Indy still cannot use >> that one. > > Indy still uses OpenSSL 1.0.2 for which all support will be > discontinued at the end of 2019. > > ICS supports 1.0.2, 1.1.0 and 1.1.1, the latter is needed for TLSv1.3. > > > BoringSSL is based on OpenSSL 1.1.0 with similar API exports, but I > believe is simplified removing a lot of legacy OpenSSL stuff, looked at > it a while ago, not closely. > > ICS uses an API exports table to load different exports from different > OpenSSL DLL versions, so adding BoringSSL would be relatively easy, > provided nothing we need is actually missing, and that the behaviour of > the API is mostly the same. > >> Maybe it could be helpful for both sides if forces would be joined >> on the TLS matter (requires of course implementing the other >> stuff), means if a cooperation between Remy Lebeau from Indy and >> folks from ICS working on Android formed some sort of sub project >> to do some of the work requiredto interface BoringSSL in a joint >> manner. > > It would be possible for Indy to replace it's OpenSSL interface unit > with our version, although we rename all exports which would either > mean separate versions for Indy renaming other units to match. > > I could assist in a Windows migration to Indy, but would not get > involved in Android testing, I don't have the time for new development > environments. Thanks, I'll rely this to remy Lebeau. Best regards Markus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Android
> Now my other topic: what became of the idea to support Android > which came up lately? Effort on mobile platforms and Linux stalled due the massive changes needed to replace missing AnsiStrings. Also little demand. > The issue is, that since Android 6 Google switched from OpenSSL > to its own BoringSSL implementation and Indy still cannot use > that one. Indy still uses OpenSSL 1.0.2 for which all support will be discontinued at the end of 2019. ICS supports 1.0.2, 1.1.0 and 1.1.1, the latter is needed for TLSv1.3. BoringSSL is based on OpenSSL 1.1.0 with similar API exports, but I believe is simplified removing a lot of legacy OpenSSL stuff, looked at it a while ago, not closely. ICS uses an API exports table to load different exports from different OpenSSL DLL versions, so adding BoringSSL would be relatively easy, provided nothing we need is actually missing, and that the behaviour of the API is mostly the same. > Maybe it could be helpful for both sides if forces would be joined > on the TLS matter (requires of course implementing the other > stuff), means if a cooperation between Remy Lebeau from Indy and > folks from ICS working on Android formed some sort of sub project > to do some of the work requiredto interface BoringSSL in a joint > manner. It would be possible for Indy to replace it's OpenSSL interface unit with our version, although we rename all exports which would either mean separate versions for Indy renaming other units to match. I could assist in a Windows migration to Indy, but would not get involved in Android testing, I don't have the time for new development environments. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
