| 1 |
very interesting article... |
| 2 |
hope that a solution will be found soon... |
| 3 |
O/H »Q« έγραψε: |
| 4 |
> In <news:46A70555.3020502@×××××.com>, |
| 5 |
> "b.n." <brullonulla@×××××.com> wrote: |
| 6 |
> |
| 7 |
> |
| 8 |
>> fire-eyes ha scritto: |
| 9 |
>> |
| 10 |
>>>> i just want to ask if it's ok to update to the new firefox,or if |
| 11 |
>>>> it's a serious sec problem?... :/ |
| 12 |
>>>> |
| 13 |
>>>> thx... |
| 14 |
>>>> |
| 15 |
>>> It's okay to update, as far as I know it's 2.0.0.5 and before (aka |
| 16 |
>>> everything...). |
| 17 |
>>> |
| 18 |
>>> Your best bet is to not use the password saving features, install |
| 19 |
>>> noscript (important: WIPE OUT it's whitelist, then selectively add |
| 20 |
>>> sites you trust). |
| 21 |
>>> |
| 22 |
> |
| 23 |
> At least not use the password manager for sites that essentially let |
| 24 |
> users host pages on them, e.g. social networking sites. |
| 25 |
> |
| 26 |
> |
| 27 |
>> Has the bug been fixed upstream? |
| 28 |
>> |
| 29 |
> |
| 30 |
> I don't know -- they restrict access to security-sensitive bug entries |
| 31 |
> until after an official release with a patch has been put out. It's |
| 32 |
> possible they won't fix this one at all; see the third and fourth |
| 33 |
> paragraphs at <http://www.heise-security.co.uk/news/93018>, and chase |
| 34 |
> links if you're really interested. |
| 35 |
> |
| 36 |
> |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-user@g.o mailing list |
Archives