Archive for the ‘ Lunix ’ Category

Adobe Labs: Flash Player “Square” Preview Release

Adobe Labs – Downloads: Flash Player “Square” Preview Release.

Flash Player “Square” Preview Release

This page contains download information for the developer preview release of Adobe┬« Flash┬« Player “Square” (codename). Flash Player “Square” enables 64-bit and enhanced Internet Explorer 9 support. Release versions of Flash Player 10.1 are available from the Flash Player Download Center on Adobe.com.

Learn more about Flash Player “Square”

By downloading the software listed below, I acknowledge that I have read and agreed to the terms of the Flash Player “Square” License, the Adobe.com Terms of Use and the Adobe Online Privacy Policy.

Flash Player “Square”

Version Preview 2
Date Sep 27, 2010

The following downloads provide the Flash Player “Square” installers for Linux, Mac and Windows operating systems. This preview release is designed for evaluation purposes only. We do not recommended that this release be used on production systems or for any mission-critical work.

Important: Please note that if you install the Flash Player “Square” preview, you will need to keep this version up to date by manually installing updates from the Flash Player “Square” download page on Adobe Labs. You will not receive automatic update notifications for future final releases of Flash Player, and you will need to manually uninstall Flash Player “Square” before installing a final shipping version of Flash Player.

The Coolest Server Names – Server Fault

The Coolest Server Names – Server Fault.

The funniest server name story I have is from when I worked at the Kennedy Space Center. On our particular project, our main server was named snowwhite, and the 7 client workstations were named after the Seven Dwarves. The kicker is, one day one of our engineers ran into a Disney Imagineer who worked at Walt Disney World, and they started talking about server names. The Disney Imagineer said “that’s funny, we have a group of servers named columbia, challenger, atlantis, and discovery.”

Use MOUNTAINS!

Why?

  • There’s a TONNE of them.
  • You’ll never run out of names.
  • They’re easy to Type:
  • FUJI, MAYON, EVEREST, K2
  • Volcanoes are used for volatile servers
  • Long mountain names like KILIMANJARO are servers that you don’t want people to log onto
  • Different Mountain RAnges can serve as Clusters or a SAN. (The Rockies, Andes, Alps)
  • It’s always the user’s fault when they crash into a mountain
    • Mountains don’t crash
  • However, sometimes they explode (VESUVIUS)
  • You can rank them by Height and represent many of them pictorially in Network diagrams. (The Matterhorn, Mt. Fuji)
  • Mountains are great Security fortresses (Why do you think China wants to keep Tibet… it’s a plateau beside India!)
  • They are visible from outer space.
  • They can be classified in many different ways.
  • They can be Local (Intranet Servers) or in other countries/continents (WANs)
  • They are common to ALL people in all countries.
  • They can be named after people’s local hometown mountains. (When I was a kid I climbed to the peak of x mountain)

MOUNTAINS!!!

Apache-SSL

Apache-SSL.

Now I’ve got my server installed, how do I create a test certificate?

Step one – create the key and request:

  openssl req -new > server_cert.csr

Step two – remove the passphrase from the key (optional):

  openssl rsa -in privkey.pem -out server_cert.key

Step three – convert request into signed cert:

  openssl x509 -in server_cert.csr -out server_cert.cert -req -signkey server_cert.key -days 365

The Apache-SSL directives that you need to use the resulting cert are:

  SSLCertificateFile /path/to/certs/server_cert.cert
  SSLCertificateKeyFile /path/to/certs/server_cert.key

How do I create a client certificate?

Step one – create a CA certificate/key pair, as above (but only the first two steps)

  openssl req -new > client_cert.csr
  openssl rsa -in privkey.pem -out client_cert.key

Step two – sign the client request with the previous created CA key:

  openssl x509 -req -in client_cert.csr -out client_cert.cert -signkey server_cert.key -CA server_cert.cert -CAkey server_cert.key -CAcreateserial -days 365

Step three – issue the file ‘client_cert.cert’ to the requester.

The Apache-SSL directives that you need to validate against this cert are:

  SSLCACertificateFile /path/to/certs/server_cert.cert
  SSLVerifyClient 2
  SSLVerifyClient require

Create PKCS12 file for use in a webbrowser

  openssl pkcs12 -export -in client_cert.cert -inkey server_cert.key -out clientt.cert.p12