Goodbye, EdgeHTML - The Mozilla Blog
Microsoft is officially giving up on an independent shared platform for the internet. By adopting Chromium, Microsoft hands over control of even more of online life to Google. This may sound melodramatic, but it’s not. The “browser engines” — Chromium from Google and Gecko Quantum from Mozilla — are “inside baseball” pieces of software that actually determine a great deal of what each of us can do
Mitigations landing for new class of timing attack – Mozilla Security Blog
Several recently-published research articles have demonstrated a new class of timing attacks (Meltdown and Spectre) that work on modern CPUs. Our internal experiments confirm that it is possible to use similar techniques from Web content to read private information between different origins. The full extent of this class of attack is still under investigation and we are working with security res
Distrusting New WoSign and StartCom Certificates – Mozilla Security Blog
Mozilla has discovered that a Certificate Authority (CA) called WoSign has had a number of technical and management failures. Most seriously, we discovered they were backdating SSL certificates in order to get around the deadline that CAs stop issuing SHA-1 SSL certificates by January 1, 2016. Additionally, Mozilla discovered that WoSign had acquired full ownership of another CA called StartCom an
Distrusting New CNNIC Certificates – Mozilla Security Blog
Last week, Mozilla was notified that a Certificate Authority (CA) called CNNIC had issued an unconstrained intermediate certificate, which was subsequently used by the recipient to issue certificates for domain names the holder did not own or control (i.e., for MitM). We added the intermediate certificate in question to Firefox’s direct revocation system, called OneCRL, and have been further inves
Microsoft announces asm.js optimizations | Luke Wagner's Blog
The Microsoft Chakra team has announced on the IE blog that asm.js optimizations are In Development. We at Mozilla are very excited for IE to join Firefox in providing predictable, top-tier performance on asm.js code and from my discussions with the Chakra team, I expect this will be the case. What does “asm.js optimizations” mean? Given this announcement, it’s natural to ask what exactly “asm.js
Mozilla Supports LGBT Equality | The Mozilla Blog
Over the past few days we have been asked a number of questions about Brendan Eich’s appointment as CEO. This post is to clarify Mozilla’s official support of equality and inclusion for LGBT people. Mozilla’s mission is to make the Web more open so that humanity is stronger, more inclusive and more just. This is why BOTH Mozilla Corporation and Mozilla Foundation support equality for all, includin
Mozilla and Samsung Collaborate on Next Generation Web Browser Engine | The Mozilla Blog
Mozilla and Samsung Collaborate on Next Generation Web Browser Engine Mozilla’s mission is about advancing the Web as a platform for all. At Mozilla Research, we’re supporting this mission by experimenting with what’s next when it comes to the core technology powering the Web browser. We need to be prepared to take advantage of tomorrow’s faster, multi-core, heterogeneous computing architectures.
IonMonkey in Firefox 18
Today we enabled IonMonkey, our newest JavaScript JIT, in Firefox 18. IonMonkey is a huge step forward for our JavaScript performance and our compiler architecture. But also, it’s been a highly focused, year-long project on behalf of the IonMonkey team, and we’re super excited to see it land. SpiderMonkey has a storied history of just-in-time compilers. Throughout all of them, however, we’ve been
Rolling Out HTTPS Google search – Open Policy & Advocacy
Now in Aurora: Secure Google Searches are default. In Aurora when you search using the location bar, search box, or the right-click menu, your search will be sent to Google through a secure (HTTPS) connection. You won’t notice a difference in how you search, but your Google search suggestions and search results will be presented through a secure web site. Enabling HTTPS for these searches shields
SpiderMonkey is on a diet – Nicholas Nethercote
One thing I’ve learnt while working for Mozilla is that a web browser can be characterized as a JavaScript execution environment that happens to have some multimedia capabilities. In particular, if you look at Firefox’s about:memory page, the JS engine is very often the component responsible for consuming the most memory. Consider the following snapshot from about:memory of the memory used by a s
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
The MCS Incident and Its Consequences for CNNIC