1381
What's a company secret you can share now that you no longer work there? (lemmy.world)
submitted 3 years ago by to c/asklemmy@lemmy.world
972 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 27 points 3 years ago (14 children)

cleartext usernames and passwords as the URI components of GET requests

I’m not an infrastructure person. If the receiving web server doesn’t log the URI, and supposing the communication is encrypted with TLS, which removes the credentials from the URI, are there security concerns?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 14 child comments
    •
  • [–] 35 points 3 years ago* (5 children)

    Anyone who has access to any involved network infrastructure can trace the cleartext communication and extract the credentials.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 3 points 3 years ago (3 children)

    What do you mean by any involved network infrastructure? The URI is encrypted by TLS, you would only see the host address/domain unless you had access to it after decryption on the server.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 13 points 3 years ago (2 children)

    They said clear text, I would assume it's not https.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 3 years ago* (1 child)

    The comment we are replying to is asking about a situation where there is TLS. Also using clear text values in the URI itself does not mean there wouldn't be TLS.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 12 points 3 years ago (2 children)

    I'm not 100% on this but I think GET requests are logged by default.

    POST requests, normally used for passwords, don't get logged by default.

    BUT the Uri would get logged would get logged on both, so if the URI contained @username:Password then it's likely all there in the logs

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 years ago

    Get and post requests are logged

    The difference is that the logged get requests will also include any query params

    GET /some/uri?user=Alpha&pass=bravo

    While a post request will have those same params sent as part of a form body request. Those aren’t logged and so it would look like this

    POST /some/uri

  • permalink
  • fedilink
  • source
  • parent
  • [–] 6 points 3 years ago

    I would still not sleep well; other things might log URI's to different unprotected places. Depending on how the software works, this might be client, but also middleware or proxy...

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 3 years ago

    Browser history

    Even if the destination doesn't log GET components, there could be corporate proxies that MITM that might log the URL. Corporate proxies usually present an internally trusted certificate to the client.

  • permalink
  • fedilink
  • source
  • parent