I see suggestions like following but not sure if/how that can be done when using Ktor/Netty https://stackoverflow.com/questions/65680170/how-to-exclude-weak-protocols-ciphers-suits-from-the-netty-sslcontext

I think I can get access to

connector

and extract some of the code in

NettyChannelInitializer

for example.....

(btw still have to use 1.6.x here....and running on Android fwiw)

I built ktor locally here and included following in

NettyChannelInitializer

protocols("TLSv1.3", "TLSv1.2")

but for some reason following still working

openssl s_client -connect <ip address>:443 -tls1

ah, it did actually work....I had initially put that

protocols

call inside the

if (alpnProvider != null)

block but that is actually null!

sslContext = SslContextBuilder.forServer(pk, *certs).apply {
    protocols("TLSv1.3", "TLSv1.2")
    if (alpnProvider != null) {
        sslProvider(alpnProvider)

Just need to see now if there's any way to set this without custom build of ktor

@Aleksei Tirman [JB] just in case you might know if this is possible....or would it be worth creating PR to allow this to be customised?

I've created fork/branch off 1.6.3 (version we're currently on) that has the TLS fix. If I run

./gradlew publishToMavenLocal

and use

mavenLocal()

in project using ktor (using custom version we're using) then it works fine. However, when I try to publish to gitlab maven repo I'm running in to some issues with symbols not found for a few of the artifacts (have updated

publish.gradle

locally to point to our repo). Is there particular publication task I should run (have tried a few)? Screenshot shows example....

ktor-server-core

seems fine but having issues resolving symbols from `ktor-server-host-common`` for some reason

hmm, I've no idea what cause of issue was but I changed version number and did fresh publication and seems to be ok now.....perhaps something had gone wrong with previous publication or perhaps some caching issue.....

@Aleksei Tirman [JB] I can try and create PR for this....do you have any particular preference for where/how this should be configured?

(fixed url)

seeing several failures in CI tests so far for the PR but haven't been able to link them yet to my changes.....but I could be missing something

I had run

jvmTest

here locally fwiw and they had passed