1 / 3
Caption Text
2 / 3
Caption Two
3 / 3
Caption Three margin testing

Showing posts with label how-to. Show all posts
Showing posts with label how-to. Show all posts

Monday, May 14, 2012

10 Spelling Checker Secrets for Microsoft Word

http://www.computerworld.com/s/article/9225180/10_Spelling_Checker_Secrets_for_Microsoft_Word?source=rss_latest_content&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+computerworld%2Fnews%2Ffeed+%28Latest+from+Computerworld%29&utm_content=Google+Feedfetcher
 - Computerworld

10 Spelling Checker Secrets for Microsoft Word

These tips can prevent you from confusing 'advice' with 'advise,' stop Word from flagging acronyms, and make you look more literate.

Helen Bradley

March 14, 2012 (PC World)
You use Word's spelling checker every day, and probably just as often encounter some of the tool's puzzling behavior. Do you know how to get rid of a word that you mistakenly added to its dictionary, for instance, or how to hide the red wiggly lines that appear all over your document?
The following ten tricks will help you to work more efficiently in Word 2010, and they will even make you and your documents look smarter.
1. Control the 'Check Spelling as You Type' Feature
This default feature reviews spelling within your document as you work, indicating with a red wiggly line any words that are missing from the spelling checker's dictionary. The feature can be distracting, but it's easy to disable. To do so, choose File, Options, Proofing, click the Check spelling as you type checkbox to clear it and reverse the current setting, and then click OK.
2. Check Foreign-Language Spelling
Word isn't naturally bilingual, but you can train it to process more than one language at a time. Ordinarily, when you're working on a document that includes text in, say, French, Word likely won't recognize the other language if you've set your primary language to U.S. English; in this case, Word will add wiggly lines under the assorted foreign words, suggesting that they are all misspellings.
You can avoid that situation by setting Word to check the French text using a French word list. To arrange this, select the text in French (or whatever foreign language you're using), and click the Review tab on the Ribbon toolbar. Then click Language and choose Set Language in the Proofing group of buttons. The Language dialog box will appear. Here you should click the language to use for the selected text; the listed languages displaying checkmark icons are available for use in checking spelling. Click OK to finish.
3. Add Unusual Words to the Dictionary
If you know ahead of time that you will be using some unusual words, and if you do not want Word to report them as possible misspellings, you can add them to the dictionary.
Choose File, Options, Proofing, and click Custom Dictionaries. Click the custom.dic file--or the name of the dictionary to add the words to, if you are using a special dictionary--and click Edit Word List. Type a word, and click Add. When you're done, click OK to exit the dictionary.
Adding words one at a time is sensible if you have only a few. But if you have a long list of words to add, it's best to do so by editing the dictionary file itself.
First, from the Custom Dictionaries dialog box, make a note of the file-path entry that shows where the custom.dic file is located. Then launch a plain-text editor such as Notepad or WordPad, and use it to open the custom.dic file. Type or paste your words, one word per line, into the document and then save it. Word will automatically sort the items into alphabetical order when it next uses the file.
4. Remove Misspellings in the Spelling Checker
If you add a misspelled word to the dictionary by accident, Word won't identify it as misspelled until you remove it.
Choose File, Options, Proofing, and click Custom Dictionaries. Select the default dictionary in the list; typically this is the custom.dic file. Click Edit Word List to open the custom.dic dialog box, which contains a list of words you have added to Word's custom dictionary. Scroll down the list, click the errant word, and then click Delete and Close. In the future, if you use this misspelling in a document, Word will properly flag it as a mistake.
5. Determine What the Spelling Checker Checks
Depending on the type of work you do, you may discover that Word either finds errors where none exist, or fails to catch the embarrassing errors you do make. For some terms, such as email addresses, URLs, or items containing numbers, you can decide whether Word checks their spelling or leaves them alone.
To see the preferences that Word is currently configured to use, choose File, Options, Proofing. Here you can set preferences, such as 'Ignore words in UPPERCASE' and 'Ignore words that contain numbers'. If you don't want Word to report email addresses and URLs as misspellings, for example, click to enable the Ignore Internet and file addresses checkbox.
You can also disable Flag repeated words if you find Word's highlighting of repeated words annoying. When you are done, click OK to return to editing the document. These changes apply instantly, and will remain in place even after you shut down and restart Word.
6. Hide the Wiggly Underlines, Just This Once
If you like to work with 'Check spelling as you type' enabled, but wish to hide the wiggly underlines for one document only to reduce distractions, you can do so. This feature lets you control the visibility of the wiggly lines on a document-by-document basis, without disabling the spelling checker itself.
Choose File, Options, Proofing. Within the 'Exceptions for:' group of options, make sure the current document name appears in the box, and click Hide spelling errors in this document only. Click OK, and the document will stop showing wiggly underlines. You can still spelling-check the document, of course, by clicking the Review tab on the Ribbon toolbar and selecting Spelling & Grammar, or by pressing the shortcut key, F7.
7. Configure Text So That Word Doesn't Check It
Computer programming code, scientific data, and other specialized text often includes words that don't live in Word's dictionary, so the spelling checker frequently flags them. To disable spelling checks for such situations, first select the text in question. Then click the Review tab on the Ribbon toolbar, and choose Language, Set Proofing Language. Click the Do not check spelling or grammar checkbox, and click OK. Word will no longer proof the selected text, now or at any time in the future.
8. Use Multiple Dictionaries for Different Projects
Many businesses have their own language. For example, a doctor's office uses medical terminology, and a mining office uses mining jargon. If your business uses certain industry terms, it's convenient to have a dictionary of those terms on hand, to prevent Word from flagging them as misspellings.
You can either add the special terminology to your own custom.dic file or create a second dictionary file of the specialized terms. Maintaining a second file can be beneficial, as you can share it with other users without sharing your own personal custom.dic or needing to overwrite the other user's custom.dic file with your version.
To create a second dictionary, choose File, Options, Proofing, and click Custom Dictionaries. Click New, type a name for your dictionary file, and click Save. Now you can add words to the dictionary as detailed in Tip 3 above.
If you are using two dictionaries--both custom.dic and a second one of specialized words--you'll want Word to use words from both files when it makes suggestions for correcting the items it has flagged as spelling errors. To make sure that Word is configured to do this, click File, Options, Proofing, and confirm that the option Suggest from main dictionary only is disabled. If not, disable it and click OK.
9. Share a Custom Dictionary With Other Users
Once you've created a dictionary file, you can share it with other users so that they can employ it in their version of Word. To do so, in Windows Explorer, locate the .dic file you created, and then send the recipient a copy. The other person, on their computer, will need to place the file in the same folder as their own custom.dic file.
Then, to add the file to Word, the recipient should launch Word and choose File, Options, Proofing, Custom Dictionaries and click Add. The user should then locate and select the new .dic file, which will be in the folder that the dialog box points to, and click Open to add it to Word's Dictionary list.
10. Flag Words Misspelled in Context Only
In some situations you may find yourself using a word that's correctly spelled but incorrect in the context. Homophones, such as stationary and stationery, or advice and advise, can be confusing--all the more so because the spelling checker won't always flag their misuse. In addition, if you tend to overuse a word, you may want Word to alert you so that you can change it on certain occasions. A solution to both issues is to exclude the problematic words so that the tool will flag them.
To exclude one or more words, you must add them to the Word exclusion file, which is already created for you and installed with Word 2007 and 2010.
Start by searching for ExcludeDictionaryEN*.lex using Windows Search. In the search results, you will find multiple files, one for each English variant. The four-digit code in each filename tells you which .lex file belongs to which language variant. For example, 0409 is for the United States, and 0809 is for the United Kingdom. See Microsoft's site for the IDs for each locale; look for the number in the LCID Hex column to identify the files for the language variants you use.
In Windows Explorer, open the folder containing the exclusion files, right-click the ExcludeDictionaryEN*.lex file for the first language variant you use, and choose Open With, then WordPad. Type the words to exclude, one per line, and click Save. Repeat for any other language variants that you use. Close and reopen Word.
In the future, when you type any word that's in the exclude dictionary file, Word will flag it as a spelling error. Take care to click only 'Ignore Once'--not 'Ignore All' or 'Add To Dictionary'--to move past the word when you're using the 'Spelling and Grammar' dialog box. Otherwise, the spelling checker won't flag the word as a misspelling in the future.

Sunday, March 4, 2012

10 Apache Security and Hardening Tips

http://www.kyplex.com/docs/apache-security.html
 | Kyplex cloud security

The Apache web server is a crucial part of the website infrastructure. It has a number of built in features that can improve your website resistance to attacks. The following document covers a number of steps that will help you to achieve this goal. This document is largely based on the knowledge gathered by our security team and by statistics information revealed by our security scanner.

Tip No. 1: Disable Apache Signature and/or Apache Banner

Apache Signature or Apache Banner is basically the same thing. It is an application name together with version name that is printed when performing a web request. Nobody actually needs this information at all, but it is enabled by default. You need to alter the Apache configuration file to disable it.
In Ubuntu, you need to change the following file: /etc/apache2/apache2.conf
Double check that ServerSignature and ServerTokens configuration settings are not enabled in some other parts of the configuration file.

Tip No. 2: The Trace HTTP Request

HTTP TRACE request is used to echo back all received information. It can be tricked to print HTTP cookies and as a result steal HTTP session. Basically this request can be used as part of the Cross Site Scripting attack, or XSS. It is recommended to disable it as a security precaution.
Add the following to the web-server's configuration file. For example alter the following file in Ubuntu: /etc/apache2/apache2.conf .

Tip 3: Remove PHP scripts that print debug info using phpinfo()

The built-in PHP function phpinfo() prints a lot of interesting internal information about the PHP environment. It can include list of which PHP modules are enabled, and the location of various files on the web-server and other sensitive information. Our web security scanner finds a lot of such files. It is recommended to remove these test files from a production website.
Here is a tip hpw to find such files. Look for the files with the following name: test.php,info.phpi.php and phpinfo.php in your website directory and remove them.

Tip 4: Disable directory indexing

Directory indexing is a features found in every web-server by default. When directory indexing is enabled, the web-site prints a list of files found in the website directories when the default page does not exists (for example index.php). Directories reported can be viewed by any visitor. It is vulnerable in the sense that these directories can contain configuration, private and backup files which can be used by the attackers to take your server under control.
You can fix this problem by disabling the Apache autoindex module. In some Apache installations it is called mod_autoindex.so. In Ubuntu, you just need to remove the following files:
So you can do it running the following commands:

Tip 5: Disable WebDAV

WebDAV is a file access protocol created over HTTP protocol. It allows you to upload and download files, and change file contents from the website. This service is required only in very rare cases. From our experience, this feature was only required to run SVN server (link). Make sure that WebDAV is disabled in production websites. When WebDAV is enabled, the following commands are supported by Apache: OPTIONS, PROPFIND, etc. These commands are sensitive from computer security point of view.
You can fix this problem by disabling Apache dav, dav_fs and dav_lock modules. In Ubuntu you just need to remove the following files:
So you can do it running the following commands:

Tip 6: Create a chroot'ed Apache environment

Chroot is a kind of virtual environment supported operating systems such as Linux and FreeBSD. When an application is executed in chrooted environment it has no access to the parent disk and to other recources.
This is a good solution if you want to protect your website from malicious users. The action steps required to create chroot Apache was already covered in a number of websites. For example: http://www.linux.com/archive/feed/36331
The main hidden issue with chrooted environment is that this environment protects the websites from accessing the operating system's files. It does not protect one site from another. In other words, if a malicious script located in one site it can access files located on other site because they are located on the same chrooted environment.
A solution to this problem is the following. Create a number of apache instances, each one hosting one website running each one if different chrooted directory. These apache instances will not be able to share IP addresses. You will have to configure different IP for each Apache instance you run.

Tip 7: Enable PHP basedir

PHP has built in a kind of chroot environment. It is called "basedir". You can configure PHP scripts to access files only in specific directory similar to chroot. Basically you can configure each site to access only files located in that site directory which is a very good idea from the security point of view.
You can add the following lines to the website configuration file or to .htaccess file to enable PHP basedir:
This will specify that your PHP scripts can access only specified directories.

Tip 8: Web Stats

Some webmasters install open source tools on their website that analyze web requests and create statistical reports. Access to these webstat scrips is almost never secured with a password. So any visitor can basically view such reports. For example some webmasters install in in the /stats directory accessible by http://www.my-site.com/stats .
Statistical reports contain a lot of sensitive information. For example it can contain hidden file names and directory names, full web requests, search engine keywords, etc... All this information can be used by the malicious users and/or your competitors.
Instead of running a statistics script on your website we recommend that you use Google Analytics. It is a free-of-charge and quality service.

Tip 9: Use Google

Most of the webmasters use common web scripts and CMS or blog software. We recommend you to frequently search for security updates using Google and register for security news at your blog/CMS website.

Tip 10: Additional Steps

If your webserver runs together with MySQL server it brings additional potential security problem. MySQL can read any files located on you server including the one located in different chrooted environments. It happens because of the FILE permission. By default only MySQL root has it. For more info about MySQL security take a look at this article ( link to GreenSQL) .
Install a Database Firewall
Download GreenSQL Express which is a free version of the GreenSQL database firewall.
Install a Web Firewall
Mod_security is a good open source product.
Additional links

Sunday, January 29, 2012

10 Apache Security and Hardening Tips

http://www.kyplex.com/docs/apache-security.html
 | Kyplex cloud security

The Apache web server is a crucial part of the website infrastructure. It has a number of built in features that can improve your website resistance to attacks. The following document covers a number of steps that will help you to achieve this goal. This document is largely based on the knowledge gathered by our security team and by statistics information revealed by our security scanner.

Tip No. 1: Disable Apache Signature and/or Apache Banner

Apache Signature or Apache Banner is basically the same thing. It is an application name together with version name that is printed when performing a web request. Nobody actually needs this information at all, but it is enabled by default. You need to alter the Apache configuration file to disable it.
In Ubuntu, you need to change the following file: /etc/apache2/apache2.conf
Double check that ServerSignature and ServerTokens configuration settings are not enabled in some other parts of the configuration file.

Tip No. 2: The Trace HTTP Request

HTTP TRACE request is used to echo back all received information. It can be tricked to print HTTP cookies and as a result steal HTTP session. Basically this request can be used as part of the Cross Site Scripting attack, or XSS. It is recommended to disable it as a security precaution.
Add the following to the web-server's configuration file. For example alter the following file in Ubuntu: /etc/apache2/apache2.conf .

Tip 3: Remove PHP scripts that print debug info using phpinfo()

The built-in PHP function phpinfo() prints a lot of interesting internal information about the PHP environment. It can include list of which PHP modules are enabled, and the location of various files on the web-server and other sensitive information. Our web security scanner finds a lot of such files. It is recommended to remove these test files from a production website.
Here is a tip hpw to find such files. Look for the files with the following name: test.php,info.phpi.php and phpinfo.php in your website directory and remove them.

Tip 4: Disable directory indexing

Directory indexing is a features found in every web-server by default. When directory indexing is enabled, the web-site prints a list of files found in the website directories when the default page does not exists (for example index.php). Directories reported can be viewed by any visitor. It is vulnerable in the sense that these directories can contain configuration, private and backup files which can be used by the attackers to take your server under control.
You can fix this problem by disabling the Apache autoindex module. In some Apache installations it is called mod_autoindex.so. In Ubuntu, you just need to remove the following files:
So you can do it running the following commands:

Tip 5: Disable WebDAV

WebDAV is a file access protocol created over HTTP protocol. It allows you to upload and download files, and change file contents from the website. This service is required only in very rare cases. From our experience, this feature was only required to run SVN server (link). Make sure that WebDAV is disabled in production websites. When WebDAV is enabled, the following commands are supported by Apache: OPTIONS, PROPFIND, etc. These commands are sensitive from computer security point of view.
You can fix this problem by disabling Apache dav, dav_fs and dav_lock modules. In Ubuntu you just need to remove the following files:
So you can do it running the following commands:

Tip 6: Create a chroot'ed Apache environment

Chroot is a kind of virtual environment supported operating systems such as Linux and FreeBSD. When an application is executed in chrooted environment it has no access to the parent disk and to other recources.
This is a good solution if you want to protect your website from malicious users. The action steps required to create chroot Apache was already covered in a number of websites. For example: http://www.linux.com/archive/feed/36331
The main hidden issue with chrooted environment is that this environment protects the websites from accessing the operating system's files. It does not protect one site from another. In other words, if a malicious script located in one site it can access files located on other site because they are located on the same chrooted environment.
A solution to this problem is the following. Create a number of apache instances, each one hosting one website running each one if different chrooted directory. These apache instances will not be able to share IP addresses. You will have to configure different IP for each Apache instance you run.

Tip 7: Enable PHP basedir

PHP has built in a kind of chroot environment. It is called "basedir". You can configure PHP scripts to access files only in specific directory similar to chroot. Basically you can configure each site to access only files located in that site directory which is a very good idea from the security point of view.
You can add the following lines to the website configuration file or to .htaccess file to enable PHP basedir:
This will specify that your PHP scripts can access only specified directories.

Tip 8: Web Stats

Some webmasters install open source tools on their website that analyze web requests and create statistical reports. Access to these webstat scrips is almost never secured with a password. So any visitor can basically view such reports. For example some webmasters install in in the /stats directory accessible by http://www.my-site.com/stats .
Statistical reports contain a lot of sensitive information. For example it can contain hidden file names and directory names, full web requests, search engine keywords, etc... All this information can be used by the malicious users and/or your competitors.
Instead of running a statistics script on your website we recommend that you use Google Analytics. It is a free-of-charge and quality service.

Tip 9: Use Google

Most of the webmasters use common web scripts and CMS or blog software. We recommend you to frequently search for security updates using Google and register for security news at your blog/CMS website.

Tip 10: Additional Steps

If your webserver runs together with MySQL server it brings additional potential security problem. MySQL can read any files located on you server including the one located in different chrooted environments. It happens because of the FILE permission. By default only MySQL root has it. For more info about MySQL security take a look at this article ( link to GreenSQL) .
Install a Database Firewall
Download GreenSQL Express which is a free version of the GreenSQL database firewall.
Install a Web Firewall
Mod_security is a good open source product.
Additional links

Featured Post

Windows和Ubuntu双系统完全独立的安装方法

http://www.ubuntuhome.com/windows-and-ubuntu-install.html  | Ubuntu Home Posted by Snow on 2012/06/25 安装Windows和Ubuntu双系统时,很多人喜欢先安装windows,然...