The CACLS utility is now replaced by an updated version named ICACLS which ships with Vista, Windows Server 2008 and Windows Server 2003 with Service Pack 2.
You can use Icacls to reset ACLs on files and to back up ACLs. Icacls also propagates changes to inherited ACLs – something that Cacls didn’t do.
More info and a quick Google resulted in the following links:
Microsoft Technet Syntax page
Windows IT Pro Article
Techrepublic Article
Wiki page for Debian SELinux:
http://wiki.debian.org/SELinux
Security-Enhanced Linux (SELinux) is an implementation of mandatory access control using Linux Security Modules (LSM) in the Linux kernel, based on the principle of least privilege – see the SELinux Wiki page for more details http://en.wikipedia.org/wiki/SELinux
Windows Vista and Windows Server 2008 have a new TCP/IP stack which includes a new set of performance enhancements to increase throughput in networking environments. One enhancement feature is CTCP – Compound TCP CTCP, which increases the send window for connections with large receive window sizes and large bandwidth-delay.
The Cable Guy newsletter at Microsoft’s Technet site has an article detailing this which was actually written back in 2005, although has since be updated. The article is available at this link:
http://www.microsoft.com/technet/community/columns/cableguy/cg1105.mspx
By default Windows Server 2008 has CTCP enabled, however Vista does not. So far with my testing, having it switched on in Vista has no side effects, and has made transferring data quicker, so turn it on!!
Use NETSH to turn it on, you can easily turn it off with another NETSH command see below:
Enable CTCP with:
———————————————————
netsh interface tcp set global congestionprovider=ctcp
———————————————————
Disable it with:
———————————————————
netsh interface tcp set global congestionprovider=none
———————————————————
Well-known security identifiers (SIDs) in Windows operating systems – this page is handy to have as a reference.
Microsoft KB243330 which was last updated in February 2007 at the time of posting this.
http://support.microsoft.com/kb/243330
Hidden shares have always been a “Security by Obscurity” classic. I’ve always said that if you are going to hide a share make sure you still apply the appropriate security permissions (both share and NTFS). Don’t EVER create a hidden share with relaxed permissions applied, because someone will find it with the many tools out there, plus one NEW tool named “Windows Vista”.
Command Prompt in Vista with:
—————————-net view \computer /all
—————————-
I noticed Alun Jones blog has this explained in detail, check his entry:
What do those dollar signs on shares do?