"Provide a remote desktop username and password into the machine with admin privileges." Now it could be me, but exactly why would I need to provide complete and unrestricted access for valve to my servers? One of the principals of securing servers: don't give out your password. It even says so on Steam chat: "Never tell your password to anyone."
If I would set one up and have filtering on it, how would you instruct the client(s) to use that specific server? >From what I read in the past there is no way of making it do that. Also with all the requirement demands by valve... exactly what would valve be giving to us? Besides a big connection bill and 'a good feeling'?? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jake Eisenman Sent: Friday, May 07, 2010 10:43 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Mirrors Looking at that... they might get more servers if window wasn't a requirement. @Saint K: Let us know how it goes! On 5/7/2010 9:04 AM, Patrick Shelley wrote: > Becoming a Steam Content Provider: > > https://support.steampowered.com/kb_article.php?ref=3326-TDKV-4603 > > On Fri, May 7, 2010 at 9:36 AM, Saint K.<[email protected]> wrote: > > >> Isn't it a possibility that we host a private content server for anyone who >> chips in a few bucks? I would be more than willing to pay a few to have a >> private content server to be able to update my servers decently without the >> standard steam update hell. I have all the possibilities to set up a thing >> such as this. Just don't know how this is arranged with VALVe. >> >> Saint K. <SNIP> _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
