| 2008-01-10 22:48:04 |
Senor Hubris |
bug |
|
|
added bug |
| 2008-01-11 11:44:21 |
Pedro Villavicencio |
epiphany-browser: status |
New |
Incomplete |
|
| 2008-01-11 11:44:21 |
Pedro Villavicencio |
epiphany-browser: assignee |
|
desktop-bugs |
|
| 2008-02-04 07:32:29 |
Allison Karlitskaya |
epiphany-browser: status |
Incomplete |
New |
|
| 2008-02-04 13:15:15 |
Sebastien Bacher |
bug |
|
|
assigned to xulrunner-1.9 (Ubuntu) |
| 2008-02-04 13:16:13 |
Pedro Villavicencio |
epiphany-browser: importance |
Undecided |
Low |
|
| 2008-02-04 13:16:13 |
Pedro Villavicencio |
epiphany-browser: status |
New |
Triaged |
|
| 2008-03-20 20:34:34 |
Germán Poo-Caamaño |
bug |
|
|
added attachment 'epiphany.png' (pseudo-fancy html that only show information, no action can be taken.) |
| 2008-03-28 02:39:11 |
Mary Gardiner |
bug |
|
|
added attachment 'unnamed' (unnamed) |
| 2008-04-04 23:26:26 |
Mary Gardiner |
description |
Binary package hint: epiphany-browser
If there is a link to a site that is https, but the remote site has, say, an SSL certificate where the CN in the cert does not match the hostname for the remote site, then clicking the link will result in no action being taken by epiphany.
In the past when clicking on such a link a dialog window will popup explaining the situation and asking you if you want to continue. No such window now pops up and the browser does not continue to the linked-to site. It simply does nothing.
epiphany-gecko: 2.21.4-0ubuntu3
epiphany-browser: 2.21.4-0ubuntu3 |
Binary package hint: epiphany-browser
SUMMARY
Epiphany does not have an easy way to add a trusted certificate for an https site. Users who visit https sites with self-signed or other default untrusted certificates will see a page that looks like this screenshot: http://launchpadlibrarian.net/12764861/epiphany.png
Many legitimate websites including Free software sites such as https://bugtrack.alsa-project.org/ and https://bugs.freedesktop.org/ have certificates that are not trusted by default. Epiphany should have a method approximately as easy as Firefox 3's handling to add certificates.
Please note, you do not need to report each non-working site individually in this bug.
WORKAROUND
The current, lengthy, method of adding a certificate is:
Preliminary (these only need to be done once):
1. Install the ephiphany-extensions package if you have not already
2. If you had to install epiphany-extensions, restart epiphany
3. Go to Tools -> Extensions and make sure 'Certificates' is ticked
For every site with a problem:
1. go to Tools -> Manage Certificates
2. Press 'Add Exception'
3. At 'Location', enter the URL of the site with the problem and press 'Get Certificate'
4. Review the Certificate Status to make sure you're satisfied.
5. Make sure 'Permanently store this exception' is ticked unless you want to do this every time you visit the site
6. Press 'Confirm Security Exception'
ORIGINAL DESCRIPTION:
If there is a link to a site that is https, but the remote site has, say, an SSL certificate where the CN in the cert does not match the hostname for the remote site, then clicking the link will result in no action being taken by epiphany.
In the past when clicking on such a link a dialog window will popup explaining the situation and asking you if you want to continue. No such window now pops up and the browser does not continue to the linked-to site. It simply does nothing.
epiphany-gecko: 2.21.4-0ubuntu3
epiphany-browser: 2.21.4-0ubuntu3 |
|
| 2008-04-04 23:27:09 |
Mary Gardiner |
title |
clicking on an https link when the remote site has invalid credentials does not work |
Adding a certificate exception for non-trusted HTTPS sites is very difficult |
|
| 2008-04-04 23:27:38 |
Mary Gardiner |
description |
Binary package hint: epiphany-browser
SUMMARY
Epiphany does not have an easy way to add a trusted certificate for an https site. Users who visit https sites with self-signed or other default untrusted certificates will see a page that looks like this screenshot: http://launchpadlibrarian.net/12764861/epiphany.png
Many legitimate websites including Free software sites such as https://bugtrack.alsa-project.org/ and https://bugs.freedesktop.org/ have certificates that are not trusted by default. Epiphany should have a method approximately as easy as Firefox 3's handling to add certificates.
Please note, you do not need to report each non-working site individually in this bug.
WORKAROUND
The current, lengthy, method of adding a certificate is:
Preliminary (these only need to be done once):
1. Install the ephiphany-extensions package if you have not already
2. If you had to install epiphany-extensions, restart epiphany
3. Go to Tools -> Extensions and make sure 'Certificates' is ticked
For every site with a problem:
1. go to Tools -> Manage Certificates
2. Press 'Add Exception'
3. At 'Location', enter the URL of the site with the problem and press 'Get Certificate'
4. Review the Certificate Status to make sure you're satisfied.
5. Make sure 'Permanently store this exception' is ticked unless you want to do this every time you visit the site
6. Press 'Confirm Security Exception'
ORIGINAL DESCRIPTION:
If there is a link to a site that is https, but the remote site has, say, an SSL certificate where the CN in the cert does not match the hostname for the remote site, then clicking the link will result in no action being taken by epiphany.
In the past when clicking on such a link a dialog window will popup explaining the situation and asking you if you want to continue. No such window now pops up and the browser does not continue to the linked-to site. It simply does nothing.
epiphany-gecko: 2.21.4-0ubuntu3
epiphany-browser: 2.21.4-0ubuntu3 |
Binary package hint: epiphany-browser
SUMMARY
Epiphany does not have an easy way to add a trusted certificate for an https site. Users who visit https sites with self-signed or other default untrusted certificates will see a page that looks like this screenshot: http://launchpadlibrarian.net/12764861/epiphany.png
Many legitimate websites including Free software sites such as https://bugtrack.alsa-project.org/ and https://bugs.freedesktop.org/ have certificates that are not trusted by default. Epiphany should have a method approximately as easy as Firefox 3's handling to add certificates.
Please note, you do not need to report each non-working site individually in this bug.
WORKAROUND
The current, lengthy, method of adding a certificate is:
Preliminary (these only need to be done once):
1. Install the epiphany-extensions package if you have not already
2. If you had to install epiphany-extensions, restart epiphany
3. Go to Tools -> Extensions and make sure 'Certificates' is ticked
For every site with a problem:
1. go to Tools -> Manage Certificates
2. Press 'Add Exception'
3. At 'Location', enter the URL of the site with the problem and press 'Get Certificate'
4. Review the Certificate Status to make sure you're satisfied.
5. Make sure 'Permanently store this exception' is ticked unless you want to do this every time you visit the site
6. Press 'Confirm Security Exception'
ORIGINAL DESCRIPTION:
If there is a link to a site that is https, but the remote site has, say, an SSL certificate where the CN in the cert does not match the hostname for the remote site, then clicking the link will result in no action being taken by epiphany.
In the past when clicking on such a link a dialog window will popup explaining the situation and asking you if you want to continue. No such window now pops up and the browser does not continue to the linked-to site. It simply does nothing.
epiphany-gecko: 2.21.4-0ubuntu3
epiphany-browser: 2.21.4-0ubuntu3 |
|
| 2008-04-04 23:35:58 |
Mary Gardiner |
description |
Binary package hint: epiphany-browser
SUMMARY
Epiphany does not have an easy way to add a trusted certificate for an https site. Users who visit https sites with self-signed or other default untrusted certificates will see a page that looks like this screenshot: http://launchpadlibrarian.net/12764861/epiphany.png
Many legitimate websites including Free software sites such as https://bugtrack.alsa-project.org/ and https://bugs.freedesktop.org/ have certificates that are not trusted by default. Epiphany should have a method approximately as easy as Firefox 3's handling to add certificates.
Please note, you do not need to report each non-working site individually in this bug.
WORKAROUND
The current, lengthy, method of adding a certificate is:
Preliminary (these only need to be done once):
1. Install the epiphany-extensions package if you have not already
2. If you had to install epiphany-extensions, restart epiphany
3. Go to Tools -> Extensions and make sure 'Certificates' is ticked
For every site with a problem:
1. go to Tools -> Manage Certificates
2. Press 'Add Exception'
3. At 'Location', enter the URL of the site with the problem and press 'Get Certificate'
4. Review the Certificate Status to make sure you're satisfied.
5. Make sure 'Permanently store this exception' is ticked unless you want to do this every time you visit the site
6. Press 'Confirm Security Exception'
ORIGINAL DESCRIPTION:
If there is a link to a site that is https, but the remote site has, say, an SSL certificate where the CN in the cert does not match the hostname for the remote site, then clicking the link will result in no action being taken by epiphany.
In the past when clicking on such a link a dialog window will popup explaining the situation and asking you if you want to continue. No such window now pops up and the browser does not continue to the linked-to site. It simply does nothing.
epiphany-gecko: 2.21.4-0ubuntu3
epiphany-browser: 2.21.4-0ubuntu3 |
Binary package hint: epiphany-browser
SUMMARY
Epiphany does not have an easy way to add a trusted certificate for an https site. Users who visit https sites with self-signed or other default untrusted certificates will see a page that looks like this screenshot: http://launchpadlibrarian.net/12764861/epiphany.png
Many legitimate websites including Free software sites such as https://bugtrack.alsa-project.org/ and https://bugs.freedesktop.org/ have certificates that are not trusted by default. Epiphany should have a method approximately as easy as Firefox 3's handling to add certificates.
Problems with the current solution:
1. it requires installing epiphany-extensions, which many users need to add especially
2. it requires a lengthy sequence of steps
3. it requires re-entering the URL
4. the lengthy sequence of steps is not spelled out in the error dialog, which refers to 'advanced encryption settings', which does not appear in the menus
Please note, you do not need to report each non-working site individually in this bug.
WORKAROUND
The current, lengthy, method of adding a certificate is:
Preliminary (these only need to be done once):
1. Install the epiphany-extensions package if you have not already
2. If you had to install epiphany-extensions, restart epiphany
3. Go to Tools -> Extensions and make sure 'Certificates' is ticked
For every site with a problem:
1. go to Tools -> Manage Certificates
2. Press 'Add Exception'
3. At 'Location', enter the URL of the site with the problem and press 'Get Certificate'
4. Review the Certificate Status to make sure you're satisfied.
5. Make sure 'Permanently store this exception' is ticked unless you want to do this every time you visit the site
6. Press 'Confirm Security Exception'
ORIGINAL DESCRIPTION:
If there is a link to a site that is https, but the remote site has, say, an SSL certificate where the CN in the cert does not match the hostname for the remote site, then clicking the link will result in no action being taken by epiphany.
In the past when clicking on such a link a dialog window will popup explaining the situation and asking you if you want to continue. No such window now pops up and the browser does not continue to the linked-to site. It simply does nothing.
epiphany-gecko: 2.21.4-0ubuntu3
epiphany-browser: 2.21.4-0ubuntu3 |
|
| 2008-04-06 03:16:03 |
Mary Gardiner |
bug |
|
|
assigned to epiphany-extensions (Ubuntu) |
| 2008-04-09 12:32:13 |
Mary Gardiner |
description |
Binary package hint: epiphany-browser
SUMMARY
Epiphany does not have an easy way to add a trusted certificate for an https site. Users who visit https sites with self-signed or other default untrusted certificates will see a page that looks like this screenshot: http://launchpadlibrarian.net/12764861/epiphany.png
Many legitimate websites including Free software sites such as https://bugtrack.alsa-project.org/ and https://bugs.freedesktop.org/ have certificates that are not trusted by default. Epiphany should have a method approximately as easy as Firefox 3's handling to add certificates.
Problems with the current solution:
1. it requires installing epiphany-extensions, which many users need to add especially
2. it requires a lengthy sequence of steps
3. it requires re-entering the URL
4. the lengthy sequence of steps is not spelled out in the error dialog, which refers to 'advanced encryption settings', which does not appear in the menus
Please note, you do not need to report each non-working site individually in this bug.
WORKAROUND
The current, lengthy, method of adding a certificate is:
Preliminary (these only need to be done once):
1. Install the epiphany-extensions package if you have not already
2. If you had to install epiphany-extensions, restart epiphany
3. Go to Tools -> Extensions and make sure 'Certificates' is ticked
For every site with a problem:
1. go to Tools -> Manage Certificates
2. Press 'Add Exception'
3. At 'Location', enter the URL of the site with the problem and press 'Get Certificate'
4. Review the Certificate Status to make sure you're satisfied.
5. Make sure 'Permanently store this exception' is ticked unless you want to do this every time you visit the site
6. Press 'Confirm Security Exception'
ORIGINAL DESCRIPTION:
If there is a link to a site that is https, but the remote site has, say, an SSL certificate where the CN in the cert does not match the hostname for the remote site, then clicking the link will result in no action being taken by epiphany.
In the past when clicking on such a link a dialog window will popup explaining the situation and asking you if you want to continue. No such window now pops up and the browser does not continue to the linked-to site. It simply does nothing.
epiphany-gecko: 2.21.4-0ubuntu3
epiphany-browser: 2.21.4-0ubuntu3 |
Binary package hint: epiphany-browser
SUMMARY
Epiphany's handling of adding HTTPS certificates is not as streamlined as it could be. Presently users are presented with an error, and they then must click "Or you can add an exception…" then "Add exception..." then they must re-enter the URL with the problem, press "Get Certificate" and "Confirm Security Exception"
Problems with the current solution:
1. it requires a lengthy sequence of steps
2. some of the steps look like doing the same thing twice "I want to add an exception"... "no, I really want to add an exception!"
3. it requires re-entering the problematic URL. Not all users will really understand what this means. Some users will have clicked on a link to get to the page. They then have to copy the URL from the location bar, or realise that it can be selected for copy+paste, which is not entirely obvious.
Early comments on this bug describe earlier handling, which was far more obscure again.
Please note, you do not need to report each non-working site individually in this bug. |
|
| 2008-04-09 12:33:06 |
Mary Gardiner |
title |
Adding a certificate exception for non-trusted HTTPS sites is very difficult |
Adding a certificate exception for non-trusted HTTPS sites is difficult |
|
| 2008-04-09 22:34:42 |
Mary Gardiner |
description |
Binary package hint: epiphany-browser
SUMMARY
Epiphany's handling of adding HTTPS certificates is not as streamlined as it could be. Presently users are presented with an error, and they then must click "Or you can add an exception…" then "Add exception..." then they must re-enter the URL with the problem, press "Get Certificate" and "Confirm Security Exception"
Problems with the current solution:
1. it requires a lengthy sequence of steps
2. some of the steps look like doing the same thing twice "I want to add an exception"... "no, I really want to add an exception!"
3. it requires re-entering the problematic URL. Not all users will really understand what this means. Some users will have clicked on a link to get to the page. They then have to copy the URL from the location bar, or realise that it can be selected for copy+paste, which is not entirely obvious.
Early comments on this bug describe earlier handling, which was far more obscure again.
Please note, you do not need to report each non-working site individually in this bug. |
Binary package hint: epiphany-browser
SUMMARY
Epiphany's handling of adding HTTPS certificates is not as streamlined as it could be. Presently users are presented with an error, and they then must click "Or you can add an exception…" then "Add exception..." then they must re-enter the URL with the problem, press "Get Certificate" and "Confirm Security Exception"
Problems with the current solution:
1. it requires a lengthy sequence of steps
2. some of the steps look like doing the same thing twice "I want to add an exception"... "no, I really want to add an exception!"
3. it requires re-entering the problematic URL. Not all users will really understand what this means. Some users will have clicked on a link to get to the page. They then have to copy the URL from the location bar, or realise that it can be selected for copy+paste, which is not entirely obvious.
4. Once you press "Confirm Security Exception", you still are presented with the original error and need to reload the page
Early comments on this bug describe earlier handling, which was far more obscure again.
Please note, you do not need to report each non-working site individually in this bug. |
|
| 2008-09-20 20:26:21 |
Emilio Pozuelo Monfort |
bug |
|
|
assigned to epiphany-browser |
| 2008-09-20 20:33:49 |
Bug Watch Updater |
epiphany-browser: status |
Unknown |
New |
|
| 2008-11-28 03:59:28 |
Daniel T Chen |
xulrunner-1.9: status |
New |
Confirmed |
|
| 2008-11-28 03:59:28 |
Daniel T Chen |
xulrunner-1.9: statusexplanation |
|
|
|
| 2008-12-08 17:13:23 |
Daniel T Chen |
epiphany-extensions: status |
New |
Invalid |
|
| 2008-12-08 17:13:23 |
Daniel T Chen |
epiphany-extensions: importance |
Undecided |
Low |
|
| 2008-12-08 17:13:23 |
Daniel T Chen |
epiphany-extensions: statusexplanation |
|
|
|
| 2009-01-23 16:34:20 |
Bug Watch Updater |
epiphany-browser: status |
New |
Invalid |
|
| 2009-07-17 16:34:27 |
Bruce Cowan |
removed subscriber Bruce Cowan |
|
|
|
| 2010-09-16 18:28:37 |
Bug Watch Updater |
epiphany-browser: status |
Invalid |
Expired |
|
| 2010-09-16 18:28:37 |
Bug Watch Updater |
epiphany-browser: importance |
Unknown |
Medium |
|
| 2011-07-25 13:10:41 |
Andrea Corbellini |
epiphany-browser (Ubuntu): status |
Triaged |
Won't Fix |
|
| 2011-07-25 13:10:41 |
Andrea Corbellini |
epiphany-browser (Ubuntu): assignee |
Ubuntu Desktop Bugs (desktop-bugs) |
|
|
| 2011-07-25 13:10:49 |
Andrea Corbellini |
xulrunner-1.9 (Ubuntu): status |
Confirmed |
Won't Fix |
|
| 2011-07-25 16:39:49 |
Rolf Leggewie |
epiphany-browser (Ubuntu): status |
Won't Fix |
Confirmed |
|
| 2011-07-25 17:36:37 |
Andrea Corbellini |
epiphany-browser (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2011-09-24 04:19:26 |
Rolf Leggewie |
epiphany-browser (Ubuntu): status |
Incomplete |
Fix Released |
|
