This is the intended way to use it:
TIdSSLVersions _SSLProtocols_;
...
_SSLProtocols_ = TIdSSLVersions();
TStringList *protoList = new TStringList('"', ':');
protoList->DelimitedText = "tlsv1:tlsv1_1:tlsv1_2";
if (protoList->IndexOf("ssl2") != -1)
_SSLProtocols_ << sslvSSLv2;
if (protoList->IndexOf("ssl3") != -1)
_SSLProtocols_ << sslvSSLv3;
if (protoList->IndexOf("tlsv1") != -1)
_SSLProtocols_ << sslvTLSv1;
if (protoList->IndexOf("tlsv1_1") != -1)
_SSLProtocols_ << sslvTLSv1_1;
if (protoList->IndexOf("tlsv1_2") != -1)
_SSLProtocols_ << sslvTLSv1_2;
SSLHandler->SSLOptions->SSLVersions = _SSLProtocols_;
@rlebeau https://en.wikipedia.org/wiki/OCSP_stapling a mechanism for checking the revocation of certificates.
@rlebeau OCSP is the replacement for CRL. The basic concept is that the user-agent looks in the certificate definition, finds a OCSP server address, and asks them if the certificate is still valid.
Now we have the problem, that these OCSP servers haven't that great uptime. Here comes OCSP Stapling to the rescue: It's basically a TLS extension in the HTTPS connection. The HTTPS web server checks it's certificates for an OCSP server. If found, then he, the web server, asks the OCSP server every now and then for the validity of the certificate (signed with a timestamp from the CA), and passes it to the user-agent when a connection is established.
If everything works well the user-agents finds that signed OCSP-response and doesn't have to query and wait for a response from a hard-to-reach 3rd party.
Btw: It also improves user privacy - the 3rd party (CA/OCSP server) can't see anymore which server is browsed.
Now we have the problem, that these OCSP servers haven't that great uptime. Here comes OCSP Stapling to the rescue: It's basically a TLS extension in the HTTPS connection. The HTTPS web server checks it's certificates for an OCSP server. If found, then he, the web server, asks the OCSP server every now and then for the validity of the certificate (signed with a timestamp from the CA), and passes it to the user-agent when a connection is established.
If everything works well the user-agents finds that signed OCSP-response and doesn't have to query and wait for a response from a hard-to-reach 3rd party.
Btw: It also improves user privacy - the 3rd party (CA/OCSP server) can't see anymore which server is browsed.
@devimplode Indy does not currently support OCSP stapling, but it might be doable, at least client-side: http://stackoverflow.com/a/11591672/65863
@jjeffman there used to be an Indy forum at http://forums2.atozed.com, but the server crashed a few months ago and the forum has not been brought back online yet. What you describe is not specific to Indy, though. Did you install the packages while another project was also open in the IDE? If so, the packages would be associated with that project. Make sure to install the packages when no other projects are open. Also check the Registry to make sure the packages are not disabled.
There was no any other project opened. I have separated the files which where placed on C6 into its file types at $(BCB)\Components\Indy10. I have put the .lib and .bpi files in Indy\Lib; the .bpl files in Indy\Bin; the .hpp files in Indy\Include; When I install the packages and after load an application which use Indy components it compiles normally. But the components are not kept on the ide if I close BCB.
@jjeffman they don't belong in the $(BCB)\bin folder, only the IDE's own files should be in there. Since you are using non-standard folders for the output, did you add your folders to the IDE's includes and library paths? See http://stackoverflow.com/questions/23674831/
is there indy documentaion for c++ builder links ? ty
Hi All, I am attempting to install Indy 10 into Delphi 2009 on a Windows 10 machine. I am able to compile all of the various DPK files with no problems, but am getting an issue when I try to install the 2 compiled BPL files into the component library. The error is, The procedure entry point @Ididn@intialization$qqrv could not be located in the dynamic link library c:\program files (x86)\codegear\ rad studio\6.0\bin\dclIndyCore120.bpl. Is anyone aware of any specific issues with Windows 10. I have successfully installed done this before in Delphi 9, but on a Windows 7 PC.
@semusta http://indyproject.org/Sockets/Docs/index.aspx, though some of it is a bit dated. There is nothing specific to C++Builder, though. Indy works the same in Delphi and C++, it is just a matter of the different code syntax between the two languages.
Hi, I think I found a small bug in indy. As I don't know were to send it, I put it here directly. When using Indy on Android with delphi seattle, timeout seems buggy : I think the problem lies here : IdGlobal.Ticks64 function never initialize the "tv" struct as gettimeofday is not called (neither USE_BASEUNIX nor KYLIXCOMPAT is defined).
Hi all, up to now, we've used Indy to send email to our sports club members using our ISP (BT Business). We would send an email containing 20 BCCs and throttle the throughput to keep in the ISPs volume limits per hour. That went out of the window when they switched to using Outlook.com to host their emailing. We've switched to using an SMTP service (AuthSMTP) who recommend sending individual emails, no BCC. The old way had a fair processing overhead, but that didn't matter as there would be a minimum of 10 secs interval between emails. Now I want to basically loop through the recipient list as fast as possible - basically Connect, loop through list clearing and building headers, Send and finally Disconnect., rather than Connect, Send one email, Disconnect and loop. Am I digging a hole for myself?
specifically at the TIdFTP component on the palette Indy Clients, Delphi XE2
I intend to to upload and download files from my ftp server, and keep the file modification date, is it possible?
I not found anything at the docsite of IndyProject, related this, but it's possible or not?
Sorry my bad english
@ntsmkfob if you are sending all of the emails using the same SMTP server, you don't need to disconnect between individual emails, you can send more than one email per login session. Connect, send send send, disconnect. The alternative is to stop using 3rd party email services altogether and just send your emails directly to each recipient's email server directly. Indy even has a TIdSMTPRelay component for that very purpose. It scans an email's recipients list and separates the recipients based on their domains, and then it uses DNS to locate each domain's receiving server, and then finally connects to each domain sending the email to all recipients within the domain. Just be careful, because this is the same thing spammers ted to do, and you might get blacklisted by some servers. This is generally why you should send emails using an ISP or intermediary service that has already been whitelisted (consider using a mailing list service, like Yahoo Groups, instead of sending emails to individual recipients, that way you only have to send 1 email on your end and let the service propegate it through the membership for you).
@marcelolx When uploading files, TIdFTP has a SetModTime() method for setting the modification time of a remote file, if the server supports the MFMT or MDTM command. When downloading a file, you have to set the modification time of the local file manually. On Windows, you can use Delphi's SysUtils.FileSetDate() function, or the Win32 SetFileTime() function directly, for that purpose.
:(
i am getting socket error 10013 on the AllocateSocket when pinging...
a bit old, but same eror...
@Mterwoord If you are pinging in code using TIdIcmpClient, then YES, you need admin rights, as TIdIcmpClient uses a RAW socket, not any OS-provided ping APIs. RAW sockets are restricted to admins on most platforms, including Windows: https://support.microsoft.com/en-us/help/195445/: "A Socket or WSASocket call that specifies the SOCK_RAW socket type fails with the following Winsock error message (10013 WSAEACCES) if the user is a non-administrator"
which translated to "i get the same red icon" :|
@mterwoord On Windows, you can send pings without admin rights using Microsoft's IcmpSendEcho() function: https://msdn.microsoft.com/en-us/library/windows/desktop/aa366050.aspx