Debug using "Remote GDB server" without "Could not verify ST device"?

[SKled.1]

I mentioned this in my other recent thread: https://community.st.com/t5/stm32cubeide-mcus/start-3rd-party-gdb-server-or-any-script-from-debug-config/m-p/734462#M31799 

and I thought I did have this working in the past, by perhaps I only used printf-style debugging via the Renode USART emulation - I don't recall for sure.

If one uses a remote GDB server connection, it would seem to stand to reason that ST debugger hardware should not be expected or enforced to be present?
The reason that this option is even there suggests one should be able to make this work - or is it an oversight / Eclipse CDT leftover?

Can this be made to work? I.e. debug a firmware running on the Renode emulator (which starts a GDB server, but no ST-link or other debugger Hardware is involved), from CubeIDE.

---

EDIT: ok, so this is not about the ST-Link, but actually checking it's an ST MCU, because auf counterfeit chips?
How unfortunate then that this wrecks debugging in an emulator with this IDE, especially in times where availability of chips can become poor.
https://community.st.com/t5/stm32-mcus-products/stm32f407zet6-could-not-verify-st-device/td-p/620036/page/2 

[SKled.1]

Ah, that applies to the usually created "STM32 C/C++ Application" type debug configurations.

One can instead also create those configurations of the type "GDB Hardware debugging", and those do not have the problem described above.

I wonder why the specialised STM32 type debug config then has the "GDB remote server" option.
Can you actually start a STM32 debug session on one computer where an ST-Link is connected, then debug, over network, on another computer? How would that work? It could be an interesting option.