cancel
Showing results for 
Search instead for 
Did you mean: 

What is the timeline for TLS 1.1 or 1.2 support in firefox?

Highlighted
New User

What is the timeline for TLS 1.1 or 1.2 support in firefox?

My employer wants to deploy a webapp that only supports TLS 1.0 and above. Is there a timeline for TLS 1.1 or 1.2 support in Firefox?

IE and others already do.

12 REPLIES
Site Moderator

Re: What is the timeline for TLS 1.1 or 1.2 support in firefox?

Probably not known.

  • Bug 565047 – Implement TLS 1.1 (RFC 4346)
  • Bug 480514 – Implement support for TLS 1.2 (RFC 5246)

(please do not comment in bug reports; you can vote instead)

New User

Re: What is the timeline for TLS 1.1 or 1.2 support in firefox?

Time to fix this issue, and fast... https://blog.torproject.org/blog/tor-and-beast-ssl-attack

New User

Re: What is the timeline for TLS 1.1 or 1.2 support in firefox?

I would like to be able to remove Timeline from my FB account. Google Chrome has the facility to do this. Can you do it for Firefox?...I do hope so, I do not like it.....thanks...

New User

Re: What is the timeline for TLS 1.1 or 1.2 support in firefox?

I receove Time Line;.I would like to be able to remove Timeline from my FB account. Google Chrome has the facility to do this. Can you do it for Firefox?...I do hope so, I do not like it.....thanks... Help to remove it thank you

SUMO Contributor

Re: What is the timeline for TLS 1.1 or 1.2 support in firefox?

Hi joycendavid and chenzee, this thread is not about Facebook timeline. To change how a website works, consider finding an add-on or a userscript:

https://addons.mozilla.org/

http://userscripts.org/

New User

Re: What is the timeline for TLS 1.1 or 1.2 support in firefox?

I can't believe this is still not fixed! Just because you are too lazy to move away from NSS, even though it's been nearly a year since BEAST broke the TLS1.0 protocol!

FIX IT!

Site Moderator

Re: What is the timeline for TLS 1.1 or 1.2 support in firefox?

syragon, all you did was SPAM that 565047 bug as your comment there was no help at all and can actually have a negative affect in making people who could fix it to decided to spend their valuable time on other bug reports instead in meantime. Also bugzilla is not a discussion forum.

https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

New User

Re: What is the timeline for TLS 1.1 or 1.2 support in firefox?

If you think using the word "SPAM" in uppercase will negatively defer attention to the TRUTH of the fact that Firefox ONLY supports NSS (Netscape related) security framework layer security, after being breached for nearly a year, you are self-illusioned. SPAM by nature means the spammer has something to market. What am I marketing here? What is in this for me? Nothing other than the honest truth about what is going on in this situation. Therefore I am not a SPAMMER. You fail to see that, and you therefore fall into the same category as the people who fail to do anything about it! What is at risk here is people's identities, financial security and personal information. Firefox claims to be ahead of M$, however IE9 already supports TLS1.1 and yet Mozilla is making excuses. Your best comeback falls short of reality - Mozilla is reliant on outdated framework code. Take it from a Fortune 100 software engineer. And what real-world experience do YOU have? Only when the public makes the truth uncomfortable with Mozilla act, and that is what I am doing. So what do you care about, image, or content?

Site Moderator

Re: What is the timeline for TLS 1.1 or 1.2 support in firefox?

It was indeed essentially spam because it was not useful, you called them lazy and you caused everybody on CC list to get email spammed (unless they set it otherwise) due to your pointless comment.

I understand there are risks with not fixing this, just that your comment could make things worse in progress of that bug and not better as you may think. You obviously have not used Bugzilla before or followed bugs that have been ignored for a time by those (or one person) who could have provided a patch or such because of comments like your "FIX IT" or demands or attacks or such.

The quickest way to get it fixed is to provide a patch yourself or at least something constructive that can either fix it or help move it much closer to being fixed.

https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

1. No pointless comments. Unless you have something constructive and helpful to say, do not add a comment to a bug. In bugs where there is a heated debate going on, you should be even more inclined not to add a comment. Unless you have something new to contribute, then the bug owner is aware of all the issues, and will make a judgement as to what to do. If you agree the bug should be fixed, vote for it. Additional "I see this too" or "It works for me" comments are unnecessary unless they are on a different platform or a significantly different build. Constructive and helpful thoughts unrelated to the topic of the bug should go in the appropriate newsgroup.

2. No obligation. "Open Source" is not the same as "the developers must do my bidding." Everyone here wants to help, but the only person who has any obligation to fix the bugs you want fixed is you. Therefore, you should not act as if you expect someone to fix a bug by a particular date or release. Aggressive or repeated demands will not be received well and will almost certainly diminish the impact and interest in your suggestions.