AngleSharp VS platform-compat

Instead, what I ended up doing is utilizing AngleSharp for transforming the existing (dynamic) websites into static files. I've stored them on disk and made them ready to be served statically.

AngleSharp

Read and understand the HTML DOM with something like this https://anglesharp.github.io/

Personally, if that script I wrote did need to be used on Core I probably would have compiled AngleSharp, loaded the HTML Parser DLL into the script, and used that.

Now, assuming you have to scrape, C# does have two decent scraping libraries: AngleSharp and Html Agility Pack. I personally prefer AngleSharp.

I would love a blog post or even a series of them about scraping local HTML files with either AngleSharp or HTMLAgilityPack.

If you want a cleaner and modern alternative to HtmlAgilityPack then I'd suggest https://github.com/AngleSharp/AngleSharp

Use anglesharp for parsing html

DotNet offers the SecureString class to keep a string encrypted in Memory, but as long as the OS does not natively support this concept, the only advantage is that it resides in memory for a shorter time, the disadvantage is that SecureStrings are easier to search for.

Note the KeePass's resistance to the attack mentioned depends on the security of .NET's secure string, which, here's what Microsoft has to say about it (https://github.com/dotnet/platform-compat/blob/master/docs/D...)

As for KeePassXC, last I checked it didn't even bother.

TIL. Looks like the deprecation note recommends MailKit.

Well of course, but it does have to be passed to the module that generates the hashes AD uses in the first place. And as I said, the standard password reset screen is bound to store the password in plain text somewhere as well.

This won’t help you with your question, but I figured I should warn against using send-mailmessage.

points you here.

Some of the reasons for not using Hashtable or other non-generic collection types are outlined here. That's why Microsoft doesn't recommend their usage in new implementations across all of its API documentation.

And if you really want to be secure you need to something better than a SecureString: https://github.com/dotnet/platform-compat/blob/master/docs/DE0001.md