A Happy Programmer

http://www.oschina.net/translate/riotjs-the-1kb-mvp-framework

https://gist.github.com/evandrix/3694955 https://github.com/dhamaniasad/HeadlessBrowsers Here are a list of headless browsers that I know about: HtmlUnit  - Java. Custom browser engine. JavaScript support/DOM emulated. Open source. Ghost  - Python only. WebKit-based. Full JavaScript support. Open source. Twill  - Python/command line. Custom browser engine. No JavaScript. Open source. PhantomJS  - Command line/all platforms. WebKit-based. Full JavaScript support. Open source. Awesomium  - C++/.Net/all platforms. Chromium-based. Full JavaScript support. Commercial/free. SimpleBrowser  - .Net 4/C#. Custom browser engine. No JavaScript support. Open source. ZombieJS  - Node.js. Custom browser engine. JavaScript support/emulated DOM. Open source. EnvJS  - JavaScript via Java/Rhino. Custom browser engine. JavaScript support/emulated DOM. Open source. Watir-webdriver  with  headless gem  - Ruby via WebDriver. Full JS Suppo...

http://www.zytrax.com/tech/survival/ssl.html http://www.zytrax.com/tech/survival/encryption.html This is a survival guide covering the mind-numbing topics of Cryptography, Encryption, Authorization and Authentication. For the mathematically challenged (and who is not) the maths involved in cryptography are gruesome in the extreme and are covered, if at all, at the level of 'stuff happens'. The guide concentrates on system functionality and consists almost exclusively of descriptions and explanations rather than specific commands or implementations.  Much of this stuff is background for SSL/TLS and X.509 certificates  in which there are commands and implementation descriptions to give you a hearty buzz for the rest of your life. Contents: Terminology Cryptographic Overview Symmetric Encryption Asymmetric Encryption Digests and Hashes Message Authentication code (MAC) Digital Signatures Terminology A non-exhaustive list of terms used in security. Many...

https://jamfnation.jamfsoftware.com/article.html?id=138 Overview If you have a private key, an SSL certificate, and a certificate bundle from a Certificate Authority (CA), you can use OpenSSL to create a certificate keystore that Tomcat can utilize. Requirements The following components are required to create a keystore for Tomcat: OpenSSL Private key with a .key file extension from CA SSL certificate file from CA Certificate bundle from CA Procedure Execute the following command to create a .p12 keystore bundle from the private key, SSL certificate, and certificate bundle: openssl pkcs12 - export - in mycert . crt - inkey mykey . key - out mycert . p12 - name tomcat - CAfile myCA . crt - caname root - chain Enter a password of “changeit” when prompted. Note: If a different password is used, it will need to be specified in the server.xml file. Once the .p12 keystore bundle is created, move it to the root of the Tomcat directory. Modify the server.xml fi...

http://chariotsolutions.com/blog/post/https-with-client-certificates-on/ http://android.stackexchange.com/questions/61540/self-signed-certificate-install-claims-success-but-android-acts-as-if-cert-isn https://jamielinux.com/docs/openssl-certificate-authority/create-the-root-pair.html https://help.github.com/enterprise/11.10.340/admin/articles/using-self-signed-ssl-certificates/ Creating Certificate Authorities and self-signed SSL certificates Following is a step-by-step guide to creating your own CA (Certificate Authority) -- and also self-signed SSL server certificates -- with openssl on Linux. Self-signing is the simpler route to take, but making one's own CA allows the signing of multiple server certificates using the same CA and involves only a few extra steps. After using openssl to generate the necessary files, you'll need to integrate them into Apache. This process differs between Linux distros and versions of Apache. Additional references exist at the en...

http://www.datanom.net/foredrag/php/soap/server/Servers-lecture.pdf TOC ● Necessary steps when constructing a simple server ● Example server ● Error handling ● Returning the WSDL to clients ● Necessary steps when constructing a complex server ● Mapping complex types ● Example server ● Concluding remarks Necessary steps when constructing a simple server 1. Write the WSDL 2. Write the service class 3. Add this class to the server:       $server- >setClass(“class”);  4. Activate the server:       $server->handle() WSDL xmlns:tns='urn:SayHello' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/' xmlns=...