Yes, certificates are still useful for Intranet SSL. There’s an important difference between SSH and SSL-without-a-certificate: when you first connect to a server with SSH, your SSH stores the server’s fingerprint. If you then try to connect to what the SSH client believes to be the same machine but gets back a different fingerprint, it … Read more
Writing a comprehensive tutorial on this might not be suitable for a Q/A site, but here’s some advices. Also, this is from the perspective of managing the installation for a single client within their own intranet. For e.g. SaaS installations it’s better to use global FQDNs & PKI. As a software vendor, you SHOULD NOT: … Read more
Hey, SharePoint Services (WSS) IS free. Microsoft Office Sharepoit Services (MOSS) isn’t, but for the purpose of an intranet site, WSS should do it. This is of course if you are using Windwos Server as a base… (which is not free). Edit: Here is a good comparison between WSS and MOSS.
Yes, IANA maintains the official service and port number registry. The process for getting a port number assigned to you is documented in RFC 6335. A review process is required for any port assignment, but it is much stricter for ports < 1024; such assignments require (among other things) that your protocol is documented in … Read more
It is possible to override the compatibility mode in intranet. For IIS, just add the below code to the web.config. Worked for me with IE9. <system.webServer> <httpProtocol> <customHeaders> <clear /> <add name=”X-UA-Compatible” value=”IE=edge” /> </customHeaders> </httpProtocol> </system.webServer> Equivalent for Apache: Header set X-UA-Compatible: IE=Edge And for nginx: add_header “X-UA-Compatible” “IE=Edge”; And for express.js: res.set(‘X-UA-Compatible’, ‘IE=Edge’)