These are chat archives for IndySockets/Indy

5th
Sep 2017
treyko
@treyko
Sep 05 2017 14:43
??
Remy Lebeau
@rlebeau
Sep 05 2017 16:53
@treyko AFAIK, X25519 is not implemented in OpenSSL 1.0.2, it was added in 1.1.0.
treyko
@treyko
Sep 05 2017 19:11

but last lib on https://indy.fulgan.com/SSL/ is OpenSSL 1.0.2. Where i can find 1.1.0?
I try used this lib https://slproweb.com/products/Win32OpenSSL.html
(with rename to

libeay32.dll
ssleay32.dll )
but i have error message : Could not load SSL library.
Can you help ?

Remy Lebeau
@rlebeau
Sep 05 2017 19:27
@treyko Indy doesn't support 1.1.0 yet. You can't just rename the 1.1.0 DLLs to 1.0.2 filenames, the OpenSSL API in general has changed in fundamantal ways that are not backwards compatible with 1.0.2
treyko
@treyko
Sep 05 2017 20:37
Since then, Curve25519 has become the de facto alternative to P-256, and is used in a wide variety of applications.Starting in 2014, OpenSSH defaults to Curve25519-based ECDH. But indy not support this in 2017. Cool! Thx for answer
Valmeras
@Valmeras
Sep 05 2017 22:36
I am trying to copy an image using Indy TIdHttp component. The image source require credentials: username and password. If I set TidHttp.Request Username and Password, they are ignored by the image source. I am obliged to include them in the image link. The problem is that if they look like: http://username:password@, it is rejected by the browsers. So, how can I set the username and the password in TidHttp so that they will be accepted by the image source?
Remy Lebeau
@rlebeau
Sep 05 2017 22:43
@Valmeras You already know the answrer to that: TIdHTTP.Request.Username and Request.Password. What you have to take into account is that the WWW uses many different kinds of authentication schemes (Basic, NTLM, OAuth, etc), but TIdHTTP only supports Basic by default (when TIdHTTP.Request.BasicAuthentication=True). If the server in question requires a different scheme (use the TIdHTTP.OnSelectAuthorization event to find out), you will have to enable/implement it manually, depending on what it actually is. Indy has a few IdAuthentication... units you can add to your uses clause to enable things like Digest and NTLM, but other schemes have to be implemented manually in your own code. As for username:password@, it is not part of an HTTP URL itself, a browser will extract such credentials from the URL before sending the HTTP request, and then use the credentials when requested by the HTTP server, prompting the user for new credentials if none are provided or they fail (the TIdHTTP.OnAuthorization event). What kind of URL are you trying to access?
Valmeras
@Valmeras
Sep 05 2017 22:55
Remy Lebeau
@rlebeau
Sep 05 2017 23:07
@Valmeras What is running at 192.168.3.104:30000 exactly? I'm guessing a webcam maybe? What kind of HTTP authentication does it actually require (what is being reported in the TIdHTTP.OnSelectAuthoriation event)? The actual URL is http://192.168.3.104:30000/mjpeg/stream.cgi?chn=1, username:password@ is handled separately by a web browser (and by TIdHTTP, for that matter).