Showing posts with label Mozilla. Show all posts
Showing posts with label Mozilla. Show all posts

Saturday, 24 August 2013

Mozilla 'Plug-n-Hack' project wants browsers to play nice with security software

Mozilla is developing a protocol that aims to let security tools and Web browsers work better together.

Configuring a web browser to work with a security tool involves writing platform and browser-specific extensions, a non-trivial process that discourages people with less experience, wrote Simon Bennetts, a security automation engineer with Mozilla, on Thursday.

The proposed standard, called "Plug-n-Hack," will define how security extensions can work with a browser in a more usable way, Bennetts wrote. PnH will allow the security tool to "declare the functionality that they support which is suitable for invoking directly from the browser."

Under the current arrangement, if a user wants to, for example, intercept HTTPS traffic, a user must configure proxy connections through the tool and browser correctly and import the tool's SSL (Secure Sockets Layer) certificate, Bennetts wrote.

"If any of these steps are carried out incorrectly then the browser will typically fail to connect to any website—debugging such problems can be frustrating and time-consuming," Bennetts wrote.

Users may also have to switch often between the tool and their browser to intercept an HTTPS request.

"PnH allows security tools to declare the functionality that they support which is suitable for invoking directly from the browser," Bennets wrote. "A browser that supports PnH can then allow the user to invoke such functionality without having to switch to and from the tool."

The PnH protocol is being designed to be browser and tool independent. The implementation for Firefox has been released under the Mozilla Public License 2.0 and can be incorporated into commercial products for free, Bennetts wrote.

The next phase of the project is being planned, but it is expected it will allow browsers to "advertise their capabilities to security tools," he wrote.

"This will allow the tools to obtain information directly from the browser, and even use the browser as an extension of the tool," Bennetts wrote.


View the original article here

Following Google's lead, Mozilla considers rejecting long-lived digital certificates

Mozilla is considering the possibility of rejecting as invalid SSL certificates issued after July 1, 2012, with a validity period of more than 60 months. Google already made the decision to block such certificates in Chrome starting early next year.

“As a result of further analysis of available, publicly discoverable certificates, as well as the vibrant discussion among the CA/B Forum [Certificate Authority/Browser Forum] membership, we have decided to implement further programmatic checks in Google Chrome and the Chromium Browser in order to ensure Baseline Requirements compliance,” Ryan Sleevi, a member of the Google Chrome Team said Monday in a message to the CA/B Forum mailing list.

The checks will be added to the development and beta releases of Google Chrome at the beginning of 2014. The changes are expected in the stable release of Chrome during the first quarter of next year, Sleevi said.

The Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates, sometimes simply referred to as the Baseline Requirements, is a set of guidelines agreed upon by all certificate authorities (CAs) and browser vendors that are members of the CA/B Forum.

Version 1.0 of the Baseline Requirements went into effect on July 1, 2012, and states that “Certificates issued after the Effective Date MUST have a Validity Period no greater than 60 months.” It also says that certificates to be issued after April 1, 2015, will need to have a validity period no greater than 39 months, but there are some clearly defined exceptions to this requirement.

The shortening of certificate validity period is a proactive measure that would allow for a timely implementation of changes made to the requirements in the future. It would be hard for future requirements, especially those with a security impact, to have a practical effect if older certificates that aren’t compliant with them would remain valid for 10 more years.

Google identified 2038 certificates that were issued after July 1, 2012, and have validity periods longer than 60 months, in violation of the current Baseline Requirements.

“We encourage CAs that have engaged in this unfortunate practice, which appears to be a very limited subset of CAs, to reach out to affected customers and inform them of the upcoming changes,” Sleevi said referring to the fact that Chrome will start blocking those certificates in the beginning of 2014.

On Thursday, a discussion was started on the Mozilla bug tracker on whether the company should enforce a similar block in its products.

“Everyone agrees such certs, when newly issued, are incompatible with the Baseline Requirements,” said Gervase Markham, who deals with issues of project governance at Mozilla, on the bug tracker. “Some CAs have argued that when reissued, this is not so, but Google does not agree with them. We should consider making the same change.”

Daniel Veditz, the security lead at Mozilla said that he sees why CAs might have a problem with this from a business and legal standpoint. If a CA already sold a “product”—in this case a certificate—in the past with certain terms and would later violate those terms by deciding to reduce the certificate’s validity period, they might be in hot water, he said.

“Although it does seem as if reissuing as a 60-month cert with the promise to reissue with the balance later ought to be satisfactory,” Vediz said.

Markham agreed. “No one is asking CAs to not give customers what they’ve paid for in terms of duration; it will just need to be 2 (or more) separate certs,” he said. “I agree that changing certs once every 5 years rather than every 10 might be a minor inconvenience for customers who use the same web server hardware and software for more than 5 years, but I’m not sure how large a group that is.”

Mozilla’s PR firm in the U.K. could not immediately provide a statement from the company regarding this issue.


View the original article here

Mozilla 'Plug-n-Hack' project wants browsers to play nice with security software

Mozilla is developing a protocol that aims to let security tools and Web browsers work better together.

Configuring a web browser to work with a security tool involves writing platform and browser-specific extensions, a non-trivial process that discourages people with less experience, wrote Simon Bennetts, a security automation engineer with Mozilla, on Thursday.

The proposed standard, called "Plug-n-Hack," will define how security extensions can work with a browser in a more usable way, Bennetts wrote. PnH will allow the security tool to "declare the functionality that they support which is suitable for invoking directly from the browser."

Under the current arrangement, if a user wants to, for example, intercept HTTPS traffic, a user must configure proxy connections through the tool and browser correctly and import the tool's SSL (Secure Sockets Layer) certificate, Bennetts wrote.

"If any of these steps are carried out incorrectly then the browser will typically fail to connect to any website—debugging such problems can be frustrating and time-consuming," Bennetts wrote.

Users may also have to switch often between the tool and their browser to intercept an HTTPS request.

"PnH allows security tools to declare the functionality that they support which is suitable for invoking directly from the browser," Bennets wrote. "A browser that supports PnH can then allow the user to invoke such functionality without having to switch to and from the tool."

The PnH protocol is being designed to be browser and tool independent. The implementation for Firefox has been released under the Mozilla Public License 2.0 and can be incorporated into commercial products for free, Bennetts wrote.

The next phase of the project is being planned, but it is expected it will allow browsers to "advertise their capabilities to security tools," he wrote.

"This will allow the tools to obtain information directly from the browser, and even use the browser as an extension of the tool," Bennetts wrote.


View the original article here

Saturday, 17 August 2013

Mozilla to ship 'Metro-ized' Firefox Dec. 10

Mozilla will launch Firefox for Microsoft’s Windows 8 “Modern” user interface in mid-December, more than a year after the operating system’s launch, according to the open-source developer’s planning documents.

Called the “Preview Release,” the touch-ready browser will be packaged with Firefox 26 for the Windows desktop. Firefox 26 is slated to ship Dec. 10.

Work on the browser—a so-called “Metro-ized” version of Firefox—will continue up until release, Mozilla said in notes from a planning meeting Wednesday published on its website.

Before the final release of Firefox 26, Mozilla will pair the Modern version with the browser’s “Aurora” and “Beta” channel builds, which are to release Sept. 16 and Oct. 28, respectively. At each step, Mozilla will quash bugs and possibly respond to user feedback with changes.

Mozilla started work on a Modern edition of Firefox, one that would run in the user interface (UI) once known as Metro, more than a year ago. The open-source developer released a rough preview in October 2012, several weeks before Microsoft shipped Windows 8.

At the time, Mozilla’s schedule claimed that the Firefox app might appear as early as January 2013. In May, the company said its developers would complete Firefox for Modern between Oct. 2, 2013, and March 20, 2014, with mid-November the likeliest date.

Third-party browser makers face unique hurdles in Windows 8. Only the default browser—which is set by the user—can run in the Modern UI; during setup, Windows 8 assigns Internet Explorer 10 (IE10) as the default browser; when Windows 8.1 ships in October, IE11 will be set as the default.

Even so, Mozilla has said it’s important that it have a Modern browser app to remain competitive. Google, for instance, has had a Windows 8 Modern version of Chrome since June 2012.

Windows RT, the touch-only spin-off designed for tablets, is a different story. Unlike Windows 8, Windows RT bars all third-party developers from accessing the limited “desktop” mode; only Microsoft’s programmers can call the APIs there, which they do to power much of the Modern version of IE on the tablet OS.

A year ago Mozilla accused Microsoft of anticompetitive behavior by purposefully blocking others from building browsers that could effectively compete with IE10 on Windows RT. That may be moot at this point, as Windows RT has struggled even more than its bigger brother, Windows 8, and increasingly looks moribund at best, a bad bet by Microsoft at worst.

Gregg Keizer covers Microsoft, security issues, Apple, Web browsers and general technology breaking news.
More by Gregg Keizer, Computerworld


View the original article here