|
From: Mike N. <ta...@al...> - 2003-07-01 11:55:57
|
Dmitry Yemanov wrote: > Oh, my god. Do you suggest introducing new binaries? fbserver.exe + > fb_inet_server.exe + fbembed.dll + fbembed_with_remote_client.dll? I raised that as an option, yes. I'd prefer that fbembed stays in its little local-machine, and local-machine *only*, sandbox, unless explicitly given permission to roam the net by either the "fbembed_with_remote_client.dll" approach, or ... (more below) > Isn't it too complex to maintain and support? "Just one more macro conditional..." *ducks* Im kidding, I'm kidding! :-) > To be honest, the above issues are very selfish. But since I'm the only one > who works on the embedded server, I prefer to assign my worries the highest > priority. I understand you concerns, and I sure don't want to add more burden. Maybe the idea I had about the y-valve compiled into fbembed could load fbclient.dll (if present) and get its remote functionality from that one? Wouldn't that satisfy both the security (and possibly privacy) concerns I raised, while not adding any extra maintenance work? It would also keep down the size, and dependencies, of fbembed for running it by itself in scenarios where remote access is unwanted or unneeded. /Mike |