Daniel

Hi everyone, more than twenty-one years ago, I started the German-language part of this forum and could not even begin to imagine what it would become. Thanks to the tireless support of many moderators as well as your thirst for knowledge and willingness to answer other people's questions, it has become a pillar of the virtual Delphi community - even far beyond the German-speaking world. Since 2018, this English-language part of the forum has also been available, with considerable support from Lars. With an online presence of this size comes the obligation to take proper care of it. I have always been very happy to do this, but over twenty-one years is a very long time and life and its priorities change. I can't help but realize that my daily/weekly time has become less available and the time has come for me to hand over the management of the forum to someone else. Thankfully, Thomas B. ("TBx") has agreed to take over the Delphi-PRAXiS and continue it in good hands - together with Lars, of course. You know Thomas as a longtime moderator of this forum and now he will take over my previous role. I myself will of course remain part of the Delphi community - not least because I continue to work a lot with Delphi in my job. I will also remain a part of this forum. Thank you all for over 21 great years!

All new registrations are now blocked until this stops. Thanks for noticing!

Oh, relax. 😉 It's no bothering at all. In the end, there is now the information, that wibukey seems to be imcompatible to certain constellations with newer Delphi-projects. Not a Delphi-issue, but maybe an useful information for other wibukey-users.

I removed a couple of posts. Please stay on topic.

Well, yes, unrelated to your question, but a direct answser to Rollo62. Well, this is how it works sometimes. We try to stay on topic of course, but this is also not StackOverflow. So there is always a gray line ...

Next time please choose a meaningful subject for your thread.

Well, it works for me.

We clearly do not support piracy.

Peter, stop posting nonsense. The reason for an AV in RAD-studio is most likely an external plugin. Now is is up to you: If you want our help, start giving clear information. Or just shut up. It’s really that easy. Don‘t be that complicated over and over again.

As suggested I grabbed these posts and created a new topic.

There is no specific area for polls like this. "Offtopic" might be an option.

Not sure if we have a confused debugger, but for sure we do have a confused developer. Take the following code: procedure TForm1.Button1Click(Sender: TObject); var i ,j : integer; begin for i:= 0 to 1 do for j:= 1 to 2 do if i+j > 1000 then ShowMessage( 'Möp!' ); end; Just run the code and see that no message appears on the screen. Now set a breakpoint on the line with the "ShowMessage"-statement. Run the code again the see that the breakpoint will be triggered and the programs stops. Now place a "begin" and an "end" around the "ShowMessage"-statement - run the code again, the breakpoint will not be triggered anymore. for i:= 0 to 1 do for j:= 1 to 2 do if i+j > 1000 then begin ShowMessage( 'Möp!' ); // < breakpoint still here end; What is going on here? For me it looks like it has something to do with the loops, as the following breakpoint is (as expected) also not triggered: j := Random(10); if j > 1000 then ShowMessage( 'Meep' ); // <-- set breakpoint here (will not be triggered)

No, the link to the download- portal is fine. there was a deep-link to the ISO-file that I have removed.

Folks, please try to avoid posting the direct download links. Although these are not hard to guess, in the past there have been requests from Embarcadero not to publish the links.

Thanks - it is now on my ToDo-List.

Well, this is a private research-project about the EU Covid-certificates. I wanted to know how that stuff works and how the pieces are glued together. After a wild mixture of very interesting and also some nasty hours, I got it working. I also learned about new data formats that were previously unknown to me (hello "cbor"). Many different techniques come together here: decoding the data from Base45 (yes, forty-five) decompressing the result using the zlib-classes downloading external supplementary files using the http-components hopping from the formats "COSE" to "CBOR" to "JSON" using OpenSSL to extract and validate the digital signature against the official public keys All of this is now integrated in a small and fluffy Delphi program. This client reads the personal/medical data from the certificate displays the specific information for "vaccinated"-certificates "tested"-certificates "recovered"-certificates reads the digital signature from the certificate verifys that signature using the public keys from the official trust-list to detect fraud is clearly not an official application ready for production use anywhere Important: Some, but not all code ist from me. The unit "cbor.pas" comes from "https://github.com/mikerabat/DelphiCBOR", the interface to openssl comes from "https://github.com/Arvur/OpenSSL-Delphi". Just in case you're interested and want to try it: Download attached zip-archive. It contains the complete Delphi-project as well as the value-sets and trust-list (see #3). You need to get your hands on the openssl-libraries "libeay32.dll" and "ssleay32.dll" (not included in the downloads). These libraries must be located in the same directory as the executable. By default "Win32-Debug" is the output-path for this project. If you decide to switch to 64bit, you should provide the matching libraries. This program reads the trust-list and the so-called value-sets from external json-files. These files can be downloaded using the button "Download supplementary data" (button starts download, gives no feedback, you must restart the program afterwards). The trust-list contains the list of currently valid public-certificates. The value-sets contain the translations from IDs (values) to readable strings. All the json-files must be in the same directory as the executable - and that directory must be writable. The json-files from today are included in the download. You need - of course - an EU Covid-19 health certificate (vaccinated, tested or recovered). Take any barcode-scanner to translate the barcode into textual representation: You should get a string starting with "HC1:". Paste that code into the windows that opened after pressing "Scan certificate". CovDemo_06-Feb-2022.zip

I agree with you that one should be careful what information one posts about oneself. In this particular case, however, I do not feel that I have published sensitive or new data. My real name is known and I do not make a secret of the fact that I have been vaccinated. In none of the screenshots published so far was there enough information to allow misuse of the certificates - and that is of course good and right (and should stay that way).

Thanks for the support - I am a step further. Actually OpenSSL handles all these algorithm-stuff by itself. It was just my code that was writing a superfluous zero-byte to a stream. And when it comes to cryptography, a single byte can destroy everything. 😉

Thanks. Yes, this is the case for all certificates using the algorithm "ECDSA w/ SHA256" for the signature. So far I only can verify the certificates using the algorithm "RSASSA-PSS". This is a little bit tricky right now...

No known problems. I just got some emails from this forum. @AlanScottAgain Please be so kind and send me a personal message containig the email-address you want to use - and I will clean up the previous accounts.

I did not expect this - but sometimes reading the manual (aka specification) indeed helps. Hardcoding the algorithm SHA-256 while the certificates could also use SHA-384 or SHA-512 is not helpful either. I suspect that the failed examples here failed at this very point. May I ask you both to take another look at the updated code (see first post). I assume that you will see another algorithm used than "SHA-256".

Thanks - I nailed it down to the code that generates the digital signature. I am still looking for a health-certificate around me that generates this error. It is a lot easier, having one of them inside the IDE....

Interesting - thanks for the feedback. Most likely the program calculated the wrong signature to compare against the signature provided in the certificate. hm. Next week I will have access to more certificates to test with.

Well - that mistake was clearly not a highlight. *sigh* It was never the intention to approve the accounts manually, so I never expected to find a queue of accounts in that area of the admin-panel of this software. Something like this shouldn't happen - I'm honestly contrite. Maybe a free beer to everyone? 😉

The code itself works - at the moment it's the adaption to the high-dpi settings. I gave the whole project to another MVP, I will ask about the progress. Well ... I prefer not to talk about this in public. I hope for your understanding.