Repository navigation
Remove ssl context customization in Spanner #2871
Description
Specifically, ciphers should not be set to null:
Then this line can be removed, which is netty specific:
{{ message }}
Specifically, ciphers should not be set to null:
Then this line can be removed, which is netty specific:
Activity
garrettjonesgoogle commentedon Feb 6, 2018
cc @vkedia @pongad @ejona86
danoscarmike commentedon Jun 6, 2018
Removing priority label as this is not a bug. Let's triage feature requests separately and prioritize appropriately in development backlog.
garrettjonesgoogle commentedon Jun 7, 2018
This is a potential security concern. Removing the feature request label.
ejona86 commentedon Jun 13, 2018
It's also a compatibility concern. Any environment actually using one of the additional ciphers chosen here (like if running on JDK 7 with Jetty ALPN) is unsupported and can break at any time.
yihanzhen commentedon Jun 20, 2018
Migrating to Gapics would remove ssl context customization.
chingor13 commentedon Dec 4, 2018
Spanner gapic migration makes this no longer necessary.
deps: update dependency org.junit.vintage:junit-vintage-engine to v5.…
feat: add support for ExternalDatasetReference (#2871)
deps: update dependency org.junit.vintage:junit-vintage-engine to v5.…
deps: update dependency org.easymock:easymock to v5.3.0 (#2871)
chore(main): release 2.42.0 (#2847)
chore(main): release 2.48.0 (#2871)
chore: regen admin (googleapis#2871)