| GPO | |
| Office 2010 SP1 Admin Templates: | |
| Explanation: http://technet.microsoft.com/en-us/library/cc178992.aspx | |
| Download: http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=18968 | |
| # How to create custom .adm or .admx files to add search providers to the toolbar search box in IE7 | |
| http://support.microsoft.com/kb/918238 | |
| # Allowing Standard Users to Install Network Printers on Windows 7 without Prompting for Administrative Credentials |
| source: http://www.markbrilman.nl/2011/08/howto-convert-a-pfx-to-a-seperate-key-crt-file/ | |
| `openssl pkcs12 -in [yourfile.pfx] -nocerts -out [keyfile-encrypted.key]` | |
| What this command does is extract the private key from the .pfx file. Once entered you need to type in the importpassword of the .pfx file. This is the password that you used to protect your keypair when you created your .pfx file. If you cannot remember it anymore you can just throw your .pfx file away, cause you won’t be able to import it again, anywhere!. Once you entered the import password OpenSSL requests you to type in another password, twice!. This new password will protect your .key file. | |
| Now let’s extract the certificate: | |
| `openssl pkcs12 -in [yourfile.pfx] -clcerts -nokeys -out [certificate.crt]` |
| -----BEGIN PGP SIGNED MESSAGE----- | |
| Hash: SHA512 | |
| Undercover communication | |
| It should be obvious by now, that the only way to communicate | |
| stealthily and securely is to avoid raising suspicion to the | |
| level at which the authorities might consider it worthwhile | |
| to put you under active surveillance (e.g., park a van with | |
| TEMPEST equipment by your apartment). |
TCL-Expect scripts are an amazingly easy way to script out laborious tasks in the shell when you need to be interactive with the console. Think of them as a "macro" or way to programmaticly step through a process you would run by hand. They are similar to shell scripts but utilize the .tcl extension and a different #! call.
The first step, similar to writing a bash script, is to tell the script what it's executing under. For expect we use the following:
#!/usr/bin/expect
| # Modify this file accordingly for your specific requirement. | |
| # http://www.thegeekstuff.com | |
| # 1. Delete all existing rules | |
| iptables -F | |
| # 2. Set default chain policies | |
| iptables -P INPUT DROP | |
| iptables -P FORWARD DROP | |
| iptables -P OUTPUT DROP |