Leaderboard

Sectigo and any Sectigo resellers supply YubiKey's Digicert supply Safenet tokens No reply from the other CA's I have contacted so far. FYI - Safenet good (can automate), YubiKey bad (password prompts cannot be avoided).

From https://quality.embarcadero.com/browse/RSP-24383 Warning/Error on record fields used without initialization

FB4D I've had no issues in VCL

The new version attached should account for that. I did think of this as a limitation, but figured it wouldn't be likely to be the case on a form that is using a menu bar. In that case the click would be on the first menu item. I thought about that last night. The new version uses Application.ActiveForm instead of Application.MainForm. This is very definitely a kludge. As I said previously, I've moved to using TMainMenu instead of TMenuBar. TMenuBarAltIssueMW2.zip

How about the pro-active approach ? This should have a huge, preventive effect against SPAM

no not at all, used to get only unusable announcements and discounts from EMB (and/or her partners). (flooded also with latest discounts from 20-30% on buying Dellphi etc, last month) Never got the mail, "YES WE ARE THERE, WE FIXED LSP ONCE AND FOR ALL" 🙂

Expect it to be discontinued at short notice when Google get bored of it

Example. Start a new VCL app, drop an Edit and a Button on a form. In the click event of the button: procedure TForm7.Button1Click(Sender: TObject); var x:TArray<Byte>; begin x := TEncoding.Unicode.GetBytes(Edit1.Text); ShowMessage(IntToStr(Length(x))); end;

Not at all. They are a perfectly valid, and still fully-supported, form of IPC. The only reason I have ever had to choose sockets over named pipes is security (or lack of) and ease-of-coding. Pipes are securable objects (from the OS's perspective), sockets are not, which can make deployments and configurations a little easier to work with. And pipes can be a little trickier to code for than sockets. But pipes work just fine when used correctly.