Channels
doorman
infrastructure
random
zercurity
community-feeds
fleet-dev
code-review
queryhub
apple-silicon
carving
tls
fim
goquery
zentral
aws
querycon
golang
zeek
file-carving
fuzzing
auditing-warroom
linen-dev
fleetosquery
plugins
jobs
arm-architecture
darkbytes
process-auditing
uptycs
android_tests
selfgroup
vendor-feeds
fleet
eclecticiq-polylogyx-extension
ebpf
website
core
general
macos
kolide
osctrl
extensions
foundation
sql
officehours
linux
windows
Title
r
Raff_B
06/19/2020, 12:40 PMCould this be related to AWS SDK being built with '-DNO_HTTP_CLIENT=1' ?
t
theopolis
06/19/2020, 11:47 PMI think the problem you are mentioning is real, and this is part of the root cause. For some context the AWS features have been implemented by the community and those using them so there’s trust that the features are working as intended. If problems arise in those features we’ll have to look to members of the community to test and suggest concrete changes.
I see where the proxy settings are being set but it’s not clear how they are used. Perhaps the expectation is the custom http client should be using some API to retrieve and use these settings?
If you make a bug report on GitHub we can ping the original authors of those proxy features and ask them.
r
Raff_B
06/22/2020, 7:40 AMThanks for the hints theopolis, I'll create a bug right away!
AWS proxy settings ignored by osqueryd #6515