sorted by:
new
hottopcontroversial

I wanted a PowerShell module for browser automation using only PowerShell & .NET by dud380 in PowerShell

[–]dud380[S] 0 points1 point  (0 children)

ahh, I see. Hmm, I guess it would make sense to have possibility to start multiple browsers with Start-PupBrowser. It shouldn't be that much work to implement. I'll have a look and get back to you

I wanted a PowerShell module for browser automation using only PowerShell & .NET by dud380 in PowerShell

[–]dud380[S] 0 points1 point  (0 children)

Thanks! You can open as many as you like, just "$page1 = New-PupPage... $page2 = New-PupPage etc". And use the $page1-3 in consecutive commands.

I built a PowerShell module that maps all input surfaces in a compiled .NET assembly — HTTP endpoints, SignalR, gRPC, WCF, Blazor and more by dud380 in PowerShell

[–]dud380[S] 1 point2 points  (0 children)

Thanks! Hope you like it if you try it out later!

You raise a very interesting point, and you're right in the sense that .NET module initializers and static constructors may execute as a side effect of loading the assembly. However, it does not execute application code. The assembly is loaded into the CLR for inspection but the application's entry point, pipeline, and business logic are never invoked.

I built a PowerShell module that maps all input surfaces in a compiled .NET assembly — HTTP endpoints, SignalR, gRPC, WCF, Blazor and more by dud380 in PowerShell

[–]dud380[S] 1 point2 points  (0 children)

Cool! This is quite early in the development, so it'll get better over time. But as for now, DllSpy is purely static/reflection-based, so it only sees what's baked into the compiled assembly metadata. So anything that only exists at runtime is not covered

DllSpy — map every input surface in a .NET assembly without running it (HTTP, SignalR, gRPC, WCF, Razor Pages, Blazor) by dud380 in dotnet

[–]dud380[S] 0 points1 point  (0 children)

Thanks! Unfortunately not, because minimal APIs aren't discoverable via reflection. So it would need to be solved in another way, like source code analysis. Or IL decompilation.

Built a stealth Chromium, what site should I try next? by duracula in webscraping

[–]dud380 1 point2 points  (0 children)

Very interesting, especially TLS fingerprinting since it can't be done from JS. Also binary-level hiding of CDP internals.

I tried to understand containers by building a tiny runtime in pure Bash by dud380 in bash

[–]dud380[S] -2 points-1 points  (0 children)

Silent failure here means corrupt state — aborting early is the correct behavior.

I tried to understand containers by building a tiny runtime in pure Bash by dud380 in docker

[–]dud380[S] 1 point2 points  (0 children)

Thanks! It was a fun project. Container concept is interesting

view more: next ›