According to the CA/Browser Forum‘s new Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates (v1.0, December 2011), the first international baseline standard for the operation of Certification Authorities (CAs) issuing SSL/TLS digital certificates natively trusted in browser software, member CAs are required to warn applicants that the use of an internal IP or name is deprecated beginning July 1st 2012 (Effective Date). “Also as of the Effective Date, the CA SHALL NOT issue a certificate with an Expiry Date later than 1 November 2015 with subjectAlternativeName extension or Subject commonName field containing a Reserved IP Address or Internal
|
|
||
|
Mozilla believes that the web can displace proprietary, single-vendor stacks for application development. To that end, some time ago, Mozilla started a project called Boot to Gecko (B2G) to pursue the goal of building a complete, standalone operating system for the open web. The B2G roadmap was recently updated and shows that they are on track to to demo a product some time in mid to late 2012. This is a further step on a journey that has been happening for some time now, i.e the commoditization of the operating system. The operating system is no longer an important part Multiarch is a general solution for installing libraries of more than one architecture on a system. It was first proposed in 2004. It solves the problem which was created when Linux distributions standardized on the /lib and /lib64 directories for libaries. The core concept is to put libraries for each architecture into architecture-specif ic paths. For example, /usr/lib/libfoo (amd64) —> /usr/lib/x86_64-linux-gnu/libfoo /usr/lib/libfoo (armel) —> /usr/lib/arm-linux-gnueabi/libfoo /usr/lib/libfoo (i386) —> /usr/lib/i386-linux-gnu/libfoo GNU triplets are used for architecture paths, with some adjustment for historical cruft. While I do not particularly like the proposed names for the architecture specific directories, the general idea has Red Hat has extended the life cycle of their Red Hat Enterprise Linux (RHEL) product line from seven to ten years beginning with RHEL5 which was initially released in March 2007 March. With Extended Life Cycle Support (ELS), this now means up to 13 years of support for RHEL5 or later. Thus RHEL5 will be supported until 2017 with standard support, 2020 if you purchase ELS. Phase I support is now extended to 5.5 years. This is a change from the current 4 years for Phase 1 (It was increased from three years in mid 2008). During this period, Red |
 |
|
| Copyright © 2007-2024 Finnbarr P. Murphy. All Rights Reserved | ||