mitzi

Well. Maybe we dont understand each other. How can I recognize that tcp client is connected to server? On client side? There’s no property except State.

I'm talking about client states, not server. Sequence is taken from TSslWSocket.OnChangeState event.

MiTeC Portable Executable Reader 2.2 has been released. It is based on TObject class and contains complete interface for reading executable file properties and structures. It is compatible with PE32 (Portable Executable), PE32+ (64bit), NE (Windows 3.x New Executable) and VxD (Windows 9x Virtual Device Driver) file types. .NET executables are supported too. It enumerates introduced classes, used units and forms for files compiled by Borland/CodeGear/Embarcadero compilers. It identifies numerous compilers and some installers, exe packers and protectors. Here are enumerated structures that are evaluated: DOS, File, Optional and CLR headers CLR Metadata streams Sections Directories Imports Exports Resources .NET Metadata Load Config Debug Thread Local Storage Exceptions Units Forms Packages Classes Package flags Version Info Compiler, installer and packer/protector identification PE Reader class capabilities are perfectly demonstrated by MiTeC EXE Explorer application. https://www.mitec.cz/

New version 13.5.0 released! + TMiTeC_SMBIOS WindowsProductKey property added - contains Windows Product Key read from ACPI.MSDM table + TMiTeC_SMBIOS UEFIGUID property added - contains UEFI GUID read from ACPI.UEFI table + TMiTeC_SMBIOS - SMBIOS 3.3 compliance * TProcMonThread handles enumeration fixed * TProcMonThread Process monitor memory leak fixed + TProcMonThread Average CPU usage added to thread record, many new properties added, DpiAwareness detection enhanced * TMiTeC_EventLog message expansion precised + TMiTeC_OperatingSystem Application theme mode and system theme mode detection added + TMiTeC_EventLog WinEvt API implemented (MiTeC_WinEvt.pas) + Library for working with certificates rewritten and greatly improved (MiTeC_Cert.pas) + TProcListMonThread new TotalProcessPrivateBytes and TotalProcessWorkingSet properties, DpiAwareness detection enhanced + TSysMonThread new PagedPool and NonPagedPool class functions + TMiTeC_CPU Physical CPU and Thread count calculation fixed For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page

Hi, can you please add this function to your components? It is tested and works and allows to load PFX/P12 certificates from memory. It is based on your LoadFromP12File function. procedure TX509Base.LoadFromP12Buffer(ABuffer: Pointer; ABufferSize: Cardinal; IncludePKey, IncludeInters: TCertReadOpt; const Password: String); var FileBio : PBIO; P12 : PPKCS12; Cert : PX509; PKey : PEVP_PKEY; Ca: PSTACK_OF_X509; PW: PAnsiChar; I: integer; begin InitializeSsl; FileBio := f_BIO_new_mem_buf(ABuffer,ABufferSize); if not Assigned(FileBio) then RaiseLastOpenSslError(EX509Exception, TRUE, 'Error reading PKCS12 certificates from buffer'); try P12 := f_d2i_PKCS12_bio(FileBio, Nil); if not Assigned(P12) then RaiseLastOpenSslError(EX509Exception, TRUE, 'Error reading PKCS12 certificates from buffer'); try Cert := Nil; Pkey := Nil; Ca := Nil; PW := Nil; if Length(Password) > 0 then PW := PAnsiChar(PasswordConvert(Password)); { V8.55 } if f_PKCS12_parse(P12, PW, Pkey, Cert, Ca) = 0 then begin if Ics_Ssl_ERR_GET_REASON(f_ERR_peek_error) = 113 then { PKCS12_R_MAC_VERIFY_FAILURE } raise EX509Exception.Create('Error PKCS12 Certificate password invalid for buffer') else RaiseLastOpenSslError(EX509Exception, TRUE, 'Error parsing PKCS12 certificates from buffer'); end; if (IncludePKey > croNo) then begin { V8.50 don't ignore croYes } if Assigned(PKey) then begin if (f_X509_check_private_key(Cert, PKey) < 1) then raise EX509Exception.Create('Certificate and private key do not match'); SetX509(Cert); SetPrivateKey(PKey); f_EVP_PKEY_free(PKey); end else begin if IncludePKey = croYes then { V8.50 require private key so error } raise EX509Exception.Create('Error reading private key from buffer'); end; end else SetX509(Cert); f_X509_free(Cert); FreeAndNilX509Inters; { intermediate certificates are optional, no error if none found } if (IncludeInters > croNo) and Assigned(Ca) then begin { V8.50 don't ignore croYes } FX509Inters := f_OPENSSL_sk_new_null; for I := 0 to f_OPENSSL_sk_num(Ca) - 1 do f_OPENSSL_sk_insert(FX509Inters, PAnsiChar(f_X509_dup (PX509(f_OPENSSL_sk_value(Ca, I)))), I); f_OPENSSL_sk_free(Ca); end; finally f_PKCS12_free(p12); end; finally f_bio_free(FileBio); end; end;

Yes but when i want to compare Subject of one certificate with subject of another one, then I need whole Subject line in right order and filled fields. I don't know what fields are filled in certificate so I can't successfully compose whole subject line for comparison. So it would be nice to have SubjectOneLine (and IssuerOneLine) in mentioned form. I get this info in correct form from another certificate with no problem via WinCrypt API and need to compare it with data returned by ICS in TX509Base.

Another question: How to convert TX509Base.SubjectOneLine to readable normalized form? I get e.g. /C=CZ/postalCode=00000/ST=\x00L\x00i\x00b\x00e\x00r\x00e\x00c\x00k\x00\xFD/L=SomeCity/street=SomeStreet/O=SomeName/OU=IT/CN=SomeName but need C=CZ, PostalCode=00000, S=Liberecký, L=SomeCity, STREET=SomeStreet, O=SomeName, OU=IT, CN=SomeName

What kind of certificates? PEM,DER,PFX? If you are able to get certificate context then adding to windows store is simple: (it uses WinCrypt API functions) function AddCertContextToStore(ACertContext: PCCERT_CONTEXT; const AStoreName: string = 'MY'): boolean; // other store names are e.g CA or ROOT var cs: HCERTSTORE; begin cs:=CertOpenStore(CERT_STORE_PROV_SYSTEM,0,0,CERT_SYSTEM_STORE_CURRENT_USER,PChar(AStoreName)); try Result:=Assigned(cs) and CertAddCertificateContextToStore(cs,ACertContext,CERT_STORE_ADD_REPLACE_EXISTING,nil); finally CertCloseStore(cs,0); end; end; But obtaining the certificate contexts from different file(certificate) types is more complicated. Following function gets first certificate context from PEM,P7C,P7B,CER,CRT,DER certificate files, PFX/P12 and combined PEM files are more difficult. function GetCertContext(const AFilename: string; out ACertContext: PCCERT_CONTEXT): boolean; var cs: HCERTSTORE; begin Result:=False; ACertContext:=nil; cs:=CertOpenStore(CERT_STORE_PROV_FILENAME,X509_ASN_ENCODING or PKCS_7_ASN_ENCODING,0,CERT_STORE_OPEN_EXISTING_FLAG or CERT_STORE_READONLY_FLAG,PChar(AFilename)); if Assigned(cs) then begin ACertContext:=CertEnumCertificatesInStore(cs,nil); Result:=Assigned(ACertContext); CertCloseStore(cs,0); end; end;

Eh, not sure what do you mean.

MiTeC Portable Executable Reader 2.1 has been released. It is based on TObject class and contains complete interface for reading executable file properties and structures. It is compatible with PE32 (Portable Executable), PE32+ (64bit), NE (Windows 3.x New Executable) and VxD (Windows 9x Virtual Device Driver) file types. .NET executables are supported too. It enumerates introduced classes, used units and forms for files compiled by Borland/CodeGear/Embarcadero compilers. It identifies numerous compilers and some installers, exe packers and protectors. Here are enumerated structures that are evaluated: DOS, File, Optional and CLR headers CLR Metadata streams Sections Directories Imports Exports Resources .NET Metadata Load Config Debug Thread Local Storage Exceptions Units Forms Packages Classes Package flags Version Info Compiler, installer and packer/protector identification PE Reader class capabilities are perfectly demonstrated by MiTeC EXE Explorer application. https://www.mitec.cz/

I wanted to emphasize that it is not based on TComponent, because many users in the past thought it is component. It means it is a direct successor of TObject.

New version 13.4.0 released! * TMiTeC_SMBIOS detection fixed * TMiTeC_OperatingSystem VMWare/VirtualPC/VirtualBox session identification fixed * TProcMonThread handles enumeration fixed + TProcMonThread file handle file position evaluated in handles detection * TMiTeC_TCPIP adapter detection fixed For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page

MiTeC Portable Executable Reader is based on TObject class and contains complete interface for reading executable file properties and structures. It is compatible with PE32 (Portable Executable), PE32+ (64bit), NE (Windows 3.x New Executable) and VxD (Windows 9x Virtual Device Driver) file types. .NET executables are supported too. It enumerates introduced classes, used units and forms for files compiled by Borland/CodeGear/Embarcadero compilers. Here are enumerated structures that are evaluated: DOS, File, Optional and CLR headers CLR Metadata streams Sections Directories Imports Exports Resources .NET Metadata Load Config Debug Thread Local Storage Exceptions Units Forms Packages Classes Package flags Version Info Compiler and packer/protector identification PE Reader class capabilities are perfectly demonstrated by MiTeC EXE Explorer application.

New version 13.3.0 released! + TMiTeC_Startup entries extended to full version info + TMiTeC_SMBIOS tables 16,22,39,41,43,204,219,221 detection added + SMBIOS 3.2 compliance added + TProcListMonThread process priority class and affinity added + TProcMonThread process priority class and affinity added + ROM BIOS Explorer enhanced (version 2.0) + Device monitor volume connect/disconnect event now correctly returns multiple drives For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page

MiTeC System Information Component Suite is the most complex system information probe in Delphi and FPC/Lazarus world. For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page