March-29-2012
Filed Under (Linux) by admin

Very easy once you know how, but this is a short how to on installing an SSL certificate with NGINX

1. You should have 2 files (<<yourdomainname>>.csr and <<yourdomainname>>.key) as a result of the generation of the CSR request on the same server

2. You have received the SSL certificate from your SSL provider, containing at least the key file (<<yourdomainname>>.cer) and the intermediate file (<<yoursslprovider.cer>>).

3. For consistency reasons, rename the intermediate and the certificate file to the crt extension (instead of .cer or .pem)

3. Combine the certificates:

cat <<yoursslprovider>>.crt >><<yourdomainname>>.crt

mind the >> after the intermediate file (first part)

4. Now change your NGINX likewise; including at least this params:

ssl on;
ssl_certificate /etc/ssl/<<yourdomainname>>.crt;
ssl_certificate_key /etc/ssl/<<yourdomainname>>.key;

5. Restart Nginx

Receiving the proxy chain error? This could be because the concatenation of the certificate files are not separated with an new rule / break rule.. Look in your concatenated file and see whether the end of the first certificate does not exist on the same line as the start of the second one e.g :

WRONG:

—– END OF CERTIFICATE ———- BEGIN OF CERTIFICATE —–

CORRECT:

—– END OF CERTIFICATE —–
—– BEGIN OF CERTIFICATE —–



October-3-2011
Filed Under (Linux, Linux Enthousiasm) by martensson

So, I wanted an complete secure Moodle E-learning environment.. After completing the installation fully non-secure (HTTP) , I fiddled with al the configuration settings.. Seems there is no immediate logical / direct way for getting this done..

For reference, getting Moodle  on Nginx working completely secure (full SLL)

1) config.php –> change $CFG->wwwroot   = ‘https://yourmoodleurl’;
2) Disable HTTPS login under Administration –> Security –> HTTP
3) config.php –> add  $CFG->sslproxy=true;

And ofcourse change your nginx server/site configuration



September-6-2011
Filed Under (Mailservices with Debian Linux) by martensson

Yes, you can restrict the elements (input, styles, formats) to the users who are using the (F) CKEditor. In my case I used CKEditor for SharePoint 2010. Here’s some quick tips / howto’s regarding restriction with CKEditor:

#Delete those nasty plugins, especially the one defining the current context
config.removePlugins = ‘elementspath’;

#Force the Language
config.defaultLanguage = ‘nl’;

#Disable the option to collapse the editor, users only get lost
config.toolbarCanCollapse = false ;

#Dis or enable the resizing of the editor
config.resize_enabled = true;

#Auto Start SCAYT Spellchecker
config.scayt_autoStartup = true;

#Force spellcheck language
config.scayt_sLang = ‘nl_NL’;

#Only allow the tags P and H2 to be used
config.format_tags = ‘p;h2′;

# Remove any other Format
config.removeFormatTags = ‘b,big,code,del,dfn,em,font,i,ins,kbd’;

#Remove advanced dialogs
config.removeDialogTabs = ‘link:advanced’;

#Restrict special characters
config.specialChars =['!','"','%','&',"'",'(',')','*','+','-','.','/',':',';','','=','','?','@','^','_','`','{','|','}','~',"€", "‘", "’", "“", "”", "–", "—","©","®","À", "Á", "Â", "Ä", "È", "É", "Ê", "Ë", "Ì", "Í", "Ï","Ò", "Ó", "Ô", "Õ", "Ö",  "Ù", "Ú", "Û", "Ü","à", "á", "â", "ä", "è", "é", "ê", "ë", "ì", "í", "ï", "ò", "ó", "ô", "õ", "ö", "÷", "ù", "ú", "û", "ü", "‚", "‛", "„", "™"];