Re: CaCert root certificates not in SeaMonkey distribution

[Yamo']

Hi,

Dirk Munk a tapoté le 22/01/2020 12:55:
> Updated to 2.53.2 beta 1, seems to be fine. I guess 2.57 is a bit too 
> adventurous ?

Yes :


I quote :
> not very usable at the moment.



-- 
Stéphane
Sorry for possible mistakes in English!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: CaCert root certificates not in SeaMonkey distribution

[Dirk Munk via support-seamonkey]

Frank-Rainer Grahl wrote:



Dirk Munk wrote:

Frank-Rainer Grahl wrote:

Which version?

2.53, 64 bit, build 20190917130005




Dirk Munk wrote:
The CaCert root certificates are not in the SeaMonkey distribution. 
That's a bit sad if you want to use their mail certificates for 
instance, or if web sites use CaCert certifcates. Can the 
developers add these root certificates please?




> 2.53, 64 bit, build 20190917130005

Ancient. Please update to 2.53.1 beta 1 or the unofficial 2.53.2 pre. 
These have the latest NSS Releases included.


FRG

Updated to 2.53.2 beta 1, seems to be fine. I guess 2.57 is a bit too 
adventurous ?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: CaCert root certificates not in SeaMonkey distribution

[Frank-Rainer Grahl]

Dirk Munk wrote:

Frank-Rainer Grahl wrote:

Which version?

2.53, 64 bit, build 20190917130005




Dirk Munk wrote:
The CaCert root certificates are not in the SeaMonkey distribution. That's 
a bit sad if you want to use their mail certificates for instance, or if 
web sites use CaCert certifcates. Can the developers add these root 
certificates please?




> 2.53, 64 bit, build 20190917130005

Ancient. Please update to 2.53.1 beta 1 or the unofficial 2.53.2 pre. These 
have the latest NSS Releases included.


FRG

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: CaCert root certificates not in SeaMonkey distribution

[Dirk Munk via support-seamonkey]

Frank-Rainer Grahl wrote:

Which version?

2.53, 64 bit, build 20190917130005




Dirk Munk wrote:
The CaCert root certificates are not in the SeaMonkey distribution. 
That's a bit sad if you want to use their mail certificates for 
instance, or if web sites use CaCert certifcates. Can the developers 
add these root certificates please?


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: CaCert root certificates not in SeaMonkey distribution

[Frank-Rainer Grahl]

Which version?

Dirk Munk wrote:
The CaCert root certificates are not in the SeaMonkey distribution. That's a 
bit sad if you want to use their mail certificates for instance, or if web 
sites use CaCert certifcates. Can the developers add these root certificates 
please?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

CaCert root certificates not in SeaMonkey distribution

[Dirk Munk via support-seamonkey]

The CaCert root certificates are not in the SeaMonkey distribution. 
That's a bit sad if you want to use their mail certificates for 
instance, or if web sites use CaCert certifcates. Can the developers add 
these root certificates please?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey email and certificates

[cyberzen]

stap...@gmail.com a écrit :

I have been using Seamonkey for years and love it. But recently I have been 
having trouble with using mail.  I keep getting time out errors.  My email 
works on my phones with out any troubles.  This keeps occurring from time to 
time.  The other issue is I keep getting untrusted  security certificate errors 
from certain websites. Is there going to be an update to fix these problems?


in this case I suggest to verify the time and date
a battery problem maybe the origin of a wrong time in the bios

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey email and certificates

[WaltS48]

On 12/3/18 10:48 PM, stap...@gmail.com wrote:

I have been using Seamonkey for years and love it. But recently I have been 
having trouble with using mail.  I keep getting time out errors.  My email 
works on my phones with out any troubles.  This keeps occurring from time to 
time.  The other issue is I keep getting untrusted  security certificate errors 
from certain websites. Is there going to be an update to fix these problems?



You don't indicate what version of SeaMonkey you are having the problem 
with or on what operating system it is running.


I suggest installing the latest 2.49.4 version if you are not already 
using it




Then we need a link to a site you are getting the certificate errors so 
we can test them.


More information about the email account. POP3 or IMAP, provider?



--
OS: Linux Mint 19 - Cinnamon Desktop
https://www.thunderbird.net/en-US/get-involved/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Seamonkey email and certificates

[stapcon]

I have been using Seamonkey for years and love it. But recently I have been 
having trouble with using mail.  I keep getting time out errors.  My email 
works on my phones with out any troubles.  This keeps occurring from time to 
time.  The other issue is I keep getting untrusted  security certificate errors 
from certain websites. Is there going to be an update to fix these problems? 
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[Frank-Rainer Grahl]

In 99% of all cases always the same. Virus scanner acts as a man in the middle 
and intercepts https traffic. You need to disable it or install the virus 
scanner certificate(s) in SeaMonkey. There were enough cases discussed here. 
Just use search or ask for support wrt. your virus scanner.


FRG

w.wij...@gmail.com wrote:

Op zondag 27 augustus 2017 06:42:59 UTC+2 schreef David E. Ross:

On 8/26/2017 9:17 PM, David Guymer wrote:

David Guymer wrote:

David E. Ross wrote:

On 8/26/2017 12:34 AM, David Guymer wrote:

There is something wrong with SeaMonkey 2.48.Every page I go to I get a
certificate warning.

I have aspersky Total Security 18.0. I have imported the Certificate
from this program with the same warning afterwards.

All other browswers are unaffected. News and mail are unaffected in
SeaMonkey.

David Guymer



Give us a link to an affected Web page, a page that does not require a
login to an account that I do not have.



https://www.foxtel.com.au/my-account


Another important site that won't load is
https://my.gov.au/LoginServices/main/login?execution=e1s1

David Guymer



Windows 7
SeaMonkey 2.48

That one loaded okay.  The site certificate for www.my.gov.au is owned
by the Australian Department of Human Services.  It and the intermediate
certificate were properly installed on the www.my.gov.au server.  Both
successfully chained to the DigiCert High Assurance EV Root CA
certificate, which was installed on my PC with SeaMonkey.

It is possible that your file of root certificates has become corrupted.
  To restore it, I suggest the following:

1.  On the SeaMonkey menu bar, select [Help > Troubleshooting
Information].

2.  Under "Application Basics", select the Open Folder button to the
right of Profile Folder.

3.  Terminate all instances of SeaMonkey.

4.  In the profile folder opened in #2, locate the file cert8.db and
delete it.

5.  Relaunch SeaMonkey (which re-creates cert8.db) and try your problem
Web sites again.

If you truly trust the Australian government's Web sites (why not?), you
might also try disabling Kaspersky just before attempting to access
those sites.  Remember to enable Kaspersky afterwards.

--
David E. Ross
<http://www.rossde.com/>




I use 2.49.3 and Bullguard, and I have the EXAT same issues as descrbed by OP, 
so I tried these steps (locate the file cert8.db and delete it, reboot SM), 
same issues persists

IS THERE A SOLUTION OR NOT??


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[w . wijmer]

Op zondag 27 augustus 2017 06:42:59 UTC+2 schreef David E. Ross:
> On 8/26/2017 9:17 PM, David Guymer wrote:
> > David Guymer wrote:
> >> David E. Ross wrote:
> >>> On 8/26/2017 12:34 AM, David Guymer wrote:
> >>>> There is something wrong with SeaMonkey 2.48.Every page I go to I get a
> >>>> certificate warning.
> >>>>
> >>>> I have aspersky Total Security 18.0. I have imported the Certificate
> >>>> from this program with the same warning afterwards.
> >>>>
> >>>> All other browswers are unaffected. News and mail are unaffected in
> >>>> SeaMonkey.
> >>>>
> >>>> David Guymer
> >>>>
> >>>
> >>> Give us a link to an affected Web page, a page that does not require a
> >>> login to an account that I do not have.
> >>>
> >>
> >> https://www.foxtel.com.au/my-account
> > 
> > Another important site that won't load is 
> > https://my.gov.au/LoginServices/main/login?execution=e1s1
> > 
> > David Guymer
> > 
> 
> Windows 7
> SeaMonkey 2.48
> 
> That one loaded okay.  The site certificate for www.my.gov.au is owned
> by the Australian Department of Human Services.  It and the intermediate
> certificate were properly installed on the www.my.gov.au server.  Both
> successfully chained to the DigiCert High Assurance EV Root CA
> certificate, which was installed on my PC with SeaMonkey.
> 
> It is possible that your file of root certificates has become corrupted.
>  To restore it, I suggest the following:
> 
> 1.  On the SeaMonkey menu bar, select [Help > Troubleshooting
> Information].
> 
> 2.  Under "Application Basics", select the Open Folder button to the
> right of Profile Folder.
> 
> 3.  Terminate all instances of SeaMonkey.
> 
> 4.  In the profile folder opened in #2, locate the file cert8.db and
> delete it.
> 
> 5.  Relaunch SeaMonkey (which re-creates cert8.db) and try your problem
> Web sites again.
> 
> If you truly trust the Australian government's Web sites (why not?), you
> might also try disabling Kaspersky just before attempting to access
> those sites.  Remember to enable Kaspersky afterwards.
> 
> -- 
> David E. Ross
> <http://www.rossde.com/>



I use 2.49.3 and Bullguard, and I have the EXAT same issues as descrbed by OP, 
so I tried these steps (locate the file cert8.db and delete it, reboot SM), 
same issues persists 

IS THERE A SOLUTION OR NOT?? 
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Expired certificates in the Builtin Object Token

[Mason83]

On 25/01/2018 13:41, Andrey Shcheglov wrote:

> I see a number of expired certificates under Builtin Object Token
> (vanilla SeaMonkey 2.46 and 2.49.1, fresh user profile):
> 
> https://habrastorage.org/webt/5d/ay/ch/5daychmswvrkawglzjk68bp7vfa.png
> 
> If I delete those, they reappear under the "Others" tab:
> 
> https://habrastorage.org/webt/xa/2q/is/xa2qisg6arve5xwmc6tmpcmwrqw.png
> 
> The certificates are expired (expiration year is 2014, below is an
> example for https://addons.mozilla.org):
> 
> https://habrastorage.org/webt/5f/ry/ox/5fryoxyqavfrl6hcibhnsbzjxuw.png
> 
> They, naturally, differ from their effective counterparts of the said
> web sites:
> 
> https://habrastorage.org/webt/rs/rq/we/rsrqwev0r-wnaujxrpacyf-s0s4.png
> 
> What's the need for those?

These are all "fake" certificates, dating back to 2011, wrongly issued
by Comodo.

https://www.wired.com/2011/03/comodo-compromise/
https://en.wikipedia.org/wiki/Comodo_Group#Certificate_hacking

In SM, I think they store the fact that they should NOT be trusted.

However, since they are now expired, I'm not sure they are needed anymore;
or maybe it is to flag the use of the fake certs. Maybe a cert specialist
can explain that better :-)

Regards.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Expired certificates in the Builtin Object Token

[Andrey ``Bass'' Shcheglov]

Thanks Lee.

Regards,
Andrey.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Expired certificates in the Builtin Object Token

[Lee]

On 1/25/18, Andrey ``Bass'' Shcheglov <andrewb...@gmail.com> wrote:
> Hello,
>
> I see a number of expired certificates under Builtin Object Token
> (vanilla SeaMonkey 2.46 and 2.49.1, fresh user profile):
>
> https://habrastorage.org/webt/5d/ay/ch/5daychmswvrkawglzjk68bp7vfa.png
>
> If I delete those, they reappear under the "Others" tab:
>
> https://habrastorage.org/webt/xa/2q/is/xa2qisg6arve5xwmc6tmpcmwrqw.png
>
> The certificates are expired (expiration year is 2014, below is an
> example for https://addons.mozilla.org):
>
> https://habrastorage.org/webt/5f/ry/ox/5fryoxyqavfrl6hcibhnsbzjxuw.png
>
> They, naturally, differ from their effective counterparts of the said
> web sites:
>
> https://habrastorage.org/webt/rs/rq/we/rsrqwev0r-wnaujxrpacyf-s0s4.png
>
> What's the need for those?

https://askubuntu.com/questions/497923/fake-usertrust-com-certificates-in-chrome

which links to
https://www.eff.org/deeplinks/2011/03/iranian-hackers-obtain-fraudulent-https
  March 23, 2011

  On March 15th, an HTTPS/TLS Certificate Authority (CA) was tricked
into issuing fraudulent certificates that posed a dire risk to
Internet security.


As to why they're marked as expired - maybe to make sure those certs
can't be used even if your clock is off by years?  i dunno...

Regards,
Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Expired certificates in the Builtin Object Token

[Andrey ``Bass'' Shcheglov]

Hello,

I see a number of expired certificates under Builtin Object Token
(vanilla SeaMonkey 2.46 and 2.49.1, fresh user profile):

https://habrastorage.org/webt/5d/ay/ch/5daychmswvrkawglzjk68bp7vfa.png

If I delete those, they reappear under the "Others" tab:

https://habrastorage.org/webt/xa/2q/is/xa2qisg6arve5xwmc6tmpcmwrqw.png

The certificates are expired (expiration year is 2014, below is an
example for https://addons.mozilla.org):

https://habrastorage.org/webt/5f/ry/ox/5fryoxyqavfrl6hcibhnsbzjxuw.png

They, naturally, differ from their effective counterparts of the said
web sites:

https://habrastorage.org/webt/rs/rq/we/rsrqwev0r-wnaujxrpacyf-s0s4.png

What's the need for those?

Regards,
Andrey.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[David E. Ross]

On 9/10/2017 2:03 AM, David Guymer wrote:
> Another site that SeaMonkey 2.48 won't let me gp tp is 
> https://www.seamonkey-project.org/start/
> 
> That version is rediculas tide up.
> 
> When will the next version be releast? I wonder if SeaMonkey 2.48 will 
> allow updates?
> 
> Very frustrated.
> 
> David Guymer
> 

gp??  tp??

-- 
David E. Ross


Yes, George Washington, Thomas Jefferson, and other
"founding fathers" owned slaves.  However, they created
a nation.  Robert E. Lee, Jefferson Davis, Thomas
"Stonewall" Jackson and other "heroes" of the
Confederacy tried to tear the nation apart.  Statues
and other monuments to those "heroes" of the
Confederacy actually celebrate traitors and treason.

See my .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[David Guymer]

Daniel wrote:

On 28/08/2017 1:26 AM, Lee wrote:

On 8/27/17, Daniel <dan...@albury.net.spam.au> wrote:

On 27/08/2017 2:17 PM, David Guymer wrote:

David Guymer wrote:

David E. Ross wrote:

On 8/26/2017 12:34 AM, David Guymer wrote:

There is something wrong with SeaMonkey 2.48.Every page I go to I
get
a
certificate warning.

I have aspersky Total Security 18.0. I have imported the Certificate
from this program with the same warning afterwards.

All other browswers are unaffected. News and mail are unaffected in
SeaMonkey.

David Guymer



Give us a link to an affected Web page, a page that does not
require a
login to an account that I do not have.



https://www.foxtel.com.au/my-account


Another important site that won't load is
https://my.gov.au/LoginServices/main/login?execution=e1s1

David Guymer


My SM 2.48 gets me to the my.gov.au "Secret Question" page  just
like it has done for years!!


Unless you've got Kaspersky installed on your machine & configured to
check all web traffic your situation is totally different.

see, for example,
https://bugs.chromium.org/p/project-zero/issues/detail?id=978
  Kasperky installs a WFP driver to intercept all outgoing HTTPS
connections. They effectively proxy SSL connections, inserting their
own certificate as a trusted authority in the system store and then
replace all leaf certificates on-the-fly. This is why if you examine a
certificate when using Kaspersky Antivirus, the issuer appears to be
"Kaspersky Anti-Virus Personal Root".

Lee


Ah!! No Kasperky, so Sorry for distracting you.

Daniel

Another site that SeaMonkey 2.48 won't let me gp tp is 
https://www.seamonkey-project.org/start/


That version is rediculas tide up.

When will the next version be releast? I wonder if SeaMonkey 2.48 will 
allow updates?


Very frustrated.

David Guymer
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[Daniel]

On 28/08/2017 1:26 AM, Lee wrote:

On 8/27/17, Daniel <dan...@albury.net.spam.au> wrote:

On 27/08/2017 2:17 PM, David Guymer wrote:

David Guymer wrote:

David E. Ross wrote:

On 8/26/2017 12:34 AM, David Guymer wrote:

There is something wrong with SeaMonkey 2.48.Every page I go to I get
a
certificate warning.

I have aspersky Total Security 18.0. I have imported the Certificate
from this program with the same warning afterwards.

All other browswers are unaffected. News and mail are unaffected in
SeaMonkey.

David Guymer



Give us a link to an affected Web page, a page that does not require a
login to an account that I do not have.



https://www.foxtel.com.au/my-account


Another important site that won't load is
https://my.gov.au/LoginServices/main/login?execution=e1s1

David Guymer


My SM 2.48 gets me to the my.gov.au "Secret Question" page  just
like it has done for years!!


Unless you've got Kaspersky installed on your machine & configured to
check all web traffic your situation is totally different.

see, for example,  https://bugs.chromium.org/p/project-zero/issues/detail?id=978
  Kasperky installs a WFP driver to intercept all outgoing HTTPS
connections. They effectively proxy SSL connections, inserting their
own certificate as a trusted authority in the system store and then
replace all leaf certificates on-the-fly. This is why if you examine a
certificate when using Kaspersky Antivirus, the issuer appears to be
"Kaspersky Anti-Virus Personal Root".

Lee


Ah!! No Kasperky, so Sorry for distracting you.

Daniel

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 
SeaMonkey/2.48 Build identifier: 20170329183526

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[Lee]

On 8/27/17, Daniel <dan...@albury.net.spam.au> wrote:
> On 27/08/2017 2:17 PM, David Guymer wrote:
>> David Guymer wrote:
>>> David E. Ross wrote:
>>>> On 8/26/2017 12:34 AM, David Guymer wrote:
>>>>> There is something wrong with SeaMonkey 2.48.Every page I go to I get
>>>>> a
>>>>> certificate warning.
>>>>>
>>>>> I have aspersky Total Security 18.0. I have imported the Certificate
>>>>> from this program with the same warning afterwards.
>>>>>
>>>>> All other browswers are unaffected. News and mail are unaffected in
>>>>> SeaMonkey.
>>>>>
>>>>> David Guymer
>>>>>
>>>>
>>>> Give us a link to an affected Web page, a page that does not require a
>>>> login to an account that I do not have.
>>>>
>>>
>>> https://www.foxtel.com.au/my-account
>>
>> Another important site that won't load is
>> https://my.gov.au/LoginServices/main/login?execution=e1s1
>>
>> David Guymer
>
> My SM 2.48 gets me to the my.gov.au "Secret Question" page  just
> like it has done for years!!

Unless you've got Kaspersky installed on your machine & configured to
check all web traffic your situation is totally different.

see, for example,  https://bugs.chromium.org/p/project-zero/issues/detail?id=978
  Kasperky installs a WFP driver to intercept all outgoing HTTPS
connections. They effectively proxy SSL connections, inserting their
own certificate as a trusted authority in the system store and then
replace all leaf certificates on-the-fly. This is why if you examine a
certificate when using Kaspersky Antivirus, the issuer appears to be
"Kaspersky Anti-Virus Personal Root".

Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[Daniel]

On 27/08/2017 2:17 PM, David Guymer wrote:

David Guymer wrote:

David E. Ross wrote:

On 8/26/2017 12:34 AM, David Guymer wrote:

There is something wrong with SeaMonkey 2.48.Every page I go to I get a
certificate warning.

I have aspersky Total Security 18.0. I have imported the Certificate
from this program with the same warning afterwards.

All other browswers are unaffected. News and mail are unaffected in
SeaMonkey.

David Guymer



Give us a link to an affected Web page, a page that does not require a
login to an account that I do not have.



https://www.foxtel.com.au/my-account


Another important site that won't load is
https://my.gov.au/LoginServices/main/login?execution=e1s1

David Guymer


My SM 2.48 gets me to the my.gov.au "Secret Question" page  just 
like it has done for years!!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 
SeaMonkey/2.48 Build identifier: 20170329183526

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[Lee]

On 8/27/17, David Guymer  wrote:
> Paul B. Gallagher wrote:
>> David Guymer wrote:
>>
>>> Another important site that won't load is
>>> 
>>
>> Works fine here in the Untied States.
>>
> Strange. I didn't think it was acessible outside of Australia.
>
> It still is reported as having an invalid certificate for me.

Can you look at the certificate?  If the issuer is "Kaspersky
Anti-Virus Personal Root" and you've already tried reinstalling their
root cert your best bet might be opening a support ticket w/ kaspersky

Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[David Guymer]

Paul B. Gallagher wrote:

David Guymer wrote:


Another important site that won't load is



Works fine here in the Untied States.


Strange. I didn't think it was acessible outside of Australia.

It still is reported as having an invalid certificate for me.

Windows 10 Insider Preveiw Build 16275

David Guymer
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[Paul B. Gallagher]

David Guymer wrote:


Another important site that won't load is



Works fine here in the Untied States.

--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[David E. Ross]

On 8/26/2017 9:17 PM, David Guymer wrote:
> David Guymer wrote:
>> David E. Ross wrote:
>>> On 8/26/2017 12:34 AM, David Guymer wrote:
>>>> There is something wrong with SeaMonkey 2.48.Every page I go to I get a
>>>> certificate warning.
>>>>
>>>> I have aspersky Total Security 18.0. I have imported the Certificate
>>>> from this program with the same warning afterwards.
>>>>
>>>> All other browswers are unaffected. News and mail are unaffected in
>>>> SeaMonkey.
>>>>
>>>> David Guymer
>>>>
>>>
>>> Give us a link to an affected Web page, a page that does not require a
>>> login to an account that I do not have.
>>>
>>
>> https://www.foxtel.com.au/my-account
> 
> Another important site that won't load is 
> https://my.gov.au/LoginServices/main/login?execution=e1s1
> 
> David Guymer
> 

Windows 7
SeaMonkey 2.48

That one loaded okay.  The site certificate for www.my.gov.au is owned
by the Australian Department of Human Services.  It and the intermediate
certificate were properly installed on the www.my.gov.au server.  Both
successfully chained to the DigiCert High Assurance EV Root CA
certificate, which was installed on my PC with SeaMonkey.

It is possible that your file of root certificates has become corrupted.
 To restore it, I suggest the following:

1.  On the SeaMonkey menu bar, select [Help > Troubleshooting
Information].

2.  Under "Application Basics", select the Open Folder button to the
right of Profile Folder.

3.  Terminate all instances of SeaMonkey.

4.  In the profile folder opened in #2, locate the file cert8.db and
delete it.

5.  Relaunch SeaMonkey (which re-creates cert8.db) and try your problem
Web sites again.

If you truly trust the Australian government's Web sites (why not?), you
might also try disabling Kaspersky just before attempting to access
those sites.  Remember to enable Kaspersky afterwards.

-- 
David E. Ross
<http://www.rossde.com/>

Yes, George Washington, Thomas Jefferson, and other
"founding fathers" owned slaves.  However, they created
a nation.  Robert E. Lee, Jefferson Davis, Thomas
"Stonewall" Jackson and other "heroes" of the
Confederacy tried to tear the nation apart.  Statues
and other monuments to those "heroes" of the
Confederacy actually celebrate traitors and treason.

See my <http://www.rossde.com/editorials/edtl_conf_flag.html>.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[David E. Ross]

On 8/26/2017 8:01 PM, David Guymer wrote:
> David E. Ross wrote:
>> On 8/26/2017 12:34 AM, David Guymer wrote:
>>> There is something wrong with SeaMonkey 2.48.Every page I go to I get a
>>> certificate warning.
>>>
>>> I have aspersky Total Security 18.0. I have imported the Certificate
>>> from this program with the same warning afterwards.
>>>
>>> All other browswers are unaffected. News and mail are unaffected in
>>> SeaMonkey.
>>>
>>> David Guymer
>>>
>>
>> Give us a link to an affected Web page, a page that does not require a
>> login to an account that I do not have.
>>
> 
> https://www.foxtel.com.au/my-account
> 

I get: "Access to My Account is not currently available outside
Australia."  This was via a redirect to
, which --
being an HTTP page and not HTTPS -- does not have a certificate.

-- 
David E. Ross


Yes, George Washington, Thomas Jefferson, and other
"founding fathers" owned slaves.  However, they created
a nation.  Robert E. Lee, Jefferson Davis, Thomas
"Stonewall" Jackson and other "heroes" of the
Confederacy tried to tear the nation apart.  Statues
and other monuments to those "heroes" of the
Confederacy actually celebrate traitors and treason.

See my .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[David Guymer]

David Guymer wrote:

David E. Ross wrote:

On 8/26/2017 12:34 AM, David Guymer wrote:

There is something wrong with SeaMonkey 2.48.Every page I go to I get a
certificate warning.

I have aspersky Total Security 18.0. I have imported the Certificate
from this program with the same warning afterwards.

All other browswers are unaffected. News and mail are unaffected in
SeaMonkey.

David Guymer



Give us a link to an affected Web page, a page that does not require a
login to an account that I do not have.



https://www.foxtel.com.au/my-account


Another important site that won't load is 
https://my.gov.au/LoginServices/main/login?execution=e1s1


David Guymer
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[David Guymer]

David E. Ross wrote:

On 8/26/2017 12:34 AM, David Guymer wrote:

There is something wrong with SeaMonkey 2.48.Every page I go to I get a
certificate warning.

I have aspersky Total Security 18.0. I have imported the Certificate
from this program with the same warning afterwards.

All other browswers are unaffected. News and mail are unaffected in
SeaMonkey.

David Guymer



Give us a link to an affected Web page, a page that does not require a
login to an account that I do not have.



https://www.foxtel.com.au/my-account
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[PhillipJones]

Lee wrote:

On 8/26/17, David Guymer <david.guy...@optusnet.com.au> wrote:

There is something wrong with SeaMonkey 2.48.Every page I go to I get a
certificate warning.

I have aspersky Total Security 18.0. I have imported the Certificate
from this program with the same warning afterwards.


It sounds like the cert wasn't imported - or maybe it wasn't imported
into the right place?
edit / preferences
privacy & security / certificates / manage certificates
authorities

do you see the Kaspersky cert there?

but before clicking on import take a look at
  https://www.us-cert.gov/ncas/alerts/TA17-075A
Allowing your a/v program to inspect traffic from https sites might be
desirable but be aware of the trade-offs.

Lee




All other browswers are unaffected. News and mail are unaffected in
SeaMonkey.

David Guymer
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey



I can't even get 2.48 to work MacBook Pro Bought in Feb 2017 16 GB RAM 
SSD Drive OSX12.6 After updating from 2.46 to 2.48. Crashed hard. 
Fortunately I  went back to 2.46 using time Machine. Works Perfect.  The 
last couple of updates for Mac have been Stinkers.


--
Phillip M. Jones, C.E.T.  "If it's Fixed, Don't Break it"
http://www.phillipmjones.netmailto:pjones...@comcast.net
http://phillipjones-cet.net/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[Lee]

On 8/26/17, David Guymer <david.guy...@optusnet.com.au> wrote:
> There is something wrong with SeaMonkey 2.48.Every page I go to I get a
> certificate warning.
>
> I have aspersky Total Security 18.0. I have imported the Certificate
> from this program with the same warning afterwards.

It sounds like the cert wasn't imported - or maybe it wasn't imported
into the right place?
edit / preferences
privacy & security / certificates / manage certificates
authorities

do you see the Kaspersky cert there?

but before clicking on import take a look at
  https://www.us-cert.gov/ncas/alerts/TA17-075A
Allowing your a/v program to inspect traffic from https sites might be
desirable but be aware of the trade-offs.

Lee


>
> All other browswers are unaffected. News and mail are unaffected in
> SeaMonkey.
>
> David Guymer
> ___
> support-seamonkey mailing list
> support-seamonkey@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-seamonkey
>
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.48 Certificates

[David E. Ross]

On 8/26/2017 12:34 AM, David Guymer wrote:
> There is something wrong with SeaMonkey 2.48.Every page I go to I get a 
> certificate warning.
> 
> I have aspersky Total Security 18.0. I have imported the Certificate 
> from this program with the same warning afterwards.
> 
> All other browswers are unaffected. News and mail are unaffected in 
> SeaMonkey.
> 
> David Guymer
> 

Give us a link to an affected Web page, a page that does not require a
login to an account that I do not have.

-- 
David E. Ross


Yes, George Washington, Thomas Jefferson, and other
"founding fathers" owned slaves.  However, they created
a nation.  Robert E. Lee, Jefferson Davis, Thomas
"Stonewall" Jackson and other "heroes" of the
Confederacy tried to tear the nation apart.  Statues
and other monuments to those "heroes" of the
Confederacy actually celebrate traitors and treason.

See my .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

SeaMonkey 2.48 Certificates

[David Guymer]

There is something wrong with SeaMonkey 2.48.Every page I go to I get a 
certificate warning.


I have aspersky Total Security 18.0. I have imported the Certificate 
from this program with the same warning afterwards.


All other browswers are unaffected. News and mail are unaffected in 
SeaMonkey.


David Guymer
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.46 keeps asking for security certificates

[David Guymer]

Lemuel Johnson wrote:

On 7/30/2017 5:16 AM, David Guymer wrote:

SeaMonkey has started asking for security certificates or not displaying
pages for all websites.

I have tried uninstalling and reinstalling SeaMonkey with the same
result.

I am running Windows 10 Insider preview 16251.

Is the a known SeaMonkey problem or is it more likely related to the
Insider Preview?

David G


I had a similar problem where my Kaspersky program interfered with
display of all sites with "https" URL's.

https://groups.google.com/forum/#!topic/mozilla.support.seamonkey/K6gMNd17lwQ


Lem Johnson

Adding a certificate for Kaspersky fixed the problem.

Thanks

David Guymer
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.46 keeps asking for security certificates

[Lemuel Johnson]

On 7/30/2017 5:16 AM, David Guymer wrote:

SeaMonkey has started asking for security certificates or not displaying
pages for all websites.

I have tried uninstalling and reinstalling SeaMonkey with the same result.

I am running Windows 10 Insider preview 16251.

Is the a known SeaMonkey problem or is it more likely related to the
Insider Preview?

David G


I had a similar problem where my Kaspersky program interfered with 
display of all sites with "https" URL's.


https://groups.google.com/forum/#!topic/mozilla.support.seamonkey/K6gMNd17lwQ

Lem Johnson
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.46 keeps asking for security certificates

[Ed Mullen]

On 7/30/17 at 6:16 AM, David Guymer created this epitome of digital genius:
SeaMonkey has started asking for security certificates or not displaying 
pages for all websites.


I have tried uninstalling and reinstalling SeaMonkey with the same result.

I am running Windows 10 Insider preview 16251.

Is the a known SeaMonkey problem or is it more likely related to the 
Insider Preview?


David G


Try Safe Mode and/or a new profile.

--
Ed Mullen
http://edmullen.net/
Too many freaks, not enough circuses.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

SeaMonkey 2.46 keeps asking for security certificates

[David Guymer]

SeaMonkey has started asking for security certificates or not displaying 
pages for all websites.


I have tried uninstalling and reinstalling SeaMonkey with the same result.

I am running Windows 10 Insider preview 16251.

Is the a known SeaMonkey problem or is it more likely related to the 
Insider Preview?


David G
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Handling of security certificates

[NoOp]

On 11/20/2014 03:42 PM, NoOp wrote:
 On 11/20/2014 07:01 AM, Paul Marwick wrote:
 NoOp wrote:
 On 11/18/2014 01:50 PM, Paul Marwick wrote:
 I've just hit a new problem with Seamonkey 2.30.

 Just finished installing a new small Linux server. I needed to access
 the web page on the server. Fired up Seamonkey, entered https:IP and
 the port number. And got this message:

 An error occurred during a connection to test1:1. The key does not
 support the requested operation. (Error code: sec_error_invalid_key)

 The page you are trying to view cannot be shown because the authenticity
 of the received data could not be verified.

 Please contact the web site owners to inform them of this problem.

 And it won't let me log on. Wonderful I know the key is not offical.
 And I don't care - its on my internal network. At least in older
 versions I was given a warning and allowed to make an exception. Seems
 that I'm now to be protected, even when I do know exactly what I'm doing!

 Firefox exhibits exactly the same over protective nonsense. In the end,
 I had to use Chromium to access the setup page.

 Is this expected behaviour, or is it something I've (yet again) got
 messed up in my profile?

 I've used Seamonkey since the old Mozilla suite. But if this is about to
 become standard, it is about to get dropped. Permanently!

 User agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101
 Firefox/33.0 SeaMonkey/2.30

 Paul.


 These might be of interest:

 https://bugzilla.mozilla.org/show_bug.cgi?id=1084606
 (Allow overrides for MOZILLA_PKIX_ERROR_INADEQUATE_KEY_SIZE (some cases
 of SEC_ERROR_INVALID_KEY in Fx33))
 https://stackoverflow.com/questions/26389964/firefox-33-0-wont-open-a-specific-local-application-error-code-sec-error-inva/26520093#26520093
 https://superuser.com/questions/826232/how-to-bypass-the-secure-connection-failed-warning-in-firefox-33
 
 Thanks. That last link allowed me to fix it. I've got a number of small 
 servers out there that use Webmin, which was the main problem. 
 
 Excellent!
 
 Generating a new key from within Webmin has fixed those that I can reach 
 - I'll have to go onsite for the rest, but it does work.
 
 You might try elinks  see if that will work.
 
 Also see:
 https://bugs.launchpad.net/ubuntu/+source/elinks/+bug/769354
 (elinks accepts self-signed ssl certificates without warning)
 may work in your favor :-)
...

Paul, I used https://localhost:631 to test.

SeaMonkey, FireFox, Opera,  Chromium barf w/cert warning unless you
make an certificate exception for 'localhost:631' (CUPS admin interface).
elinks (terminal text browser - https://en.wikipedia.org/wiki/ELinks)
works with:
https://localhost:631/
If you prefer a GUI based browser that will also work, give epiphany
(https://wiki.gnome.org/Apps/Web) a go - it also works
w/https://localhost:631.

Those both should allow you to remotely log into your Webmin's without
having to go on site. Also, I'm not so sure that the key length is the
entire problem. My localhost (Ubuntu 14.04) has a key that is 2048:

ubuntu
Identity: ubuntu
Verified by: ubuntu
Expires: 06/03/2024

Subject Name
CN (Common Name):   ubuntu
Issuer Name
CN (Common Name):   ubuntu
Issued Certificate
Version:3
Serial Number:  00 93 B8 19 5E 6D 3E 8E 29
Not Valid Before:   2014-06-06
Not Valid After:2024-06-03
Certificate Fingerprints
SHA1:   6B 77 1D 27 2C 80 D6 71 3A 08 05 75 ED 68 CA 53 A6 20 E7 FA
MD5:1F D5 5B 53 11 92 39 B9 BC F5 4B E8 D8 F2 F3 B4
Public Key Info
Key Algorithm:  RSA
Key Parameters: 05 00
Key Size:   2048




___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Handling of security certificates

[Paul Marwick]

NoOp wrote:

On 11/18/2014 01:50 PM, Paul Marwick wrote:

I've just hit a new problem with Seamonkey 2.30.

Just finished installing a new small Linux server. I needed to access
the web page on the server. Fired up Seamonkey, entered https:IP and
the port number. And got this message:

An error occurred during a connection to test1:1. The key does not
support the requested operation. (Error code: sec_error_invalid_key)

The page you are trying to view cannot be shown because the authenticity
of the received data could not be verified.

Please contact the web site owners to inform them of this problem.

And it won't let me log on. Wonderful I know the key is not offical.
And I don't care - its on my internal network. At least in older
versions I was given a warning and allowed to make an exception. Seems
that I'm now to be protected, even when I do know exactly what I'm doing!

Firefox exhibits exactly the same over protective nonsense. In the end,
I had to use Chromium to access the setup page.

Is this expected behaviour, or is it something I've (yet again) got
messed up in my profile?

I've used Seamonkey since the old Mozilla suite. But if this is about to
become standard, it is about to get dropped. Permanently!

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101
Firefox/33.0 SeaMonkey/2.30

Paul.



These might be of interest:

https://bugzilla.mozilla.org/show_bug.cgi?id=1084606
(Allow overrides for MOZILLA_PKIX_ERROR_INADEQUATE_KEY_SIZE (some cases
of SEC_ERROR_INVALID_KEY in Fx33))
https://stackoverflow.com/questions/26389964/firefox-33-0-wont-open-a-specific-local-application-error-code-sec-error-inva/26520093#26520093
https://superuser.com/questions/826232/how-to-bypass-the-secure-connection-failed-warning-in-firefox-33


Thanks. That last link allowed me to fix it. I've got a number of small 
servers out there that use Webmin, which was the main problem. 
Generating a new key from within Webmin has fixed those that I can reach 
- I'll have to go onsite for the rest, but it does work.




You still should be able to set an exception via
Edit|Preferences|PrivacySecurity|Certificates|Manage Certificates




I may have to try that if I find any sites in the wild that have the 
same problem.


Paul.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Handling of security certificates

[Paul Marwick]

Thee Chicago Wolf [MVP] wrote:

I've just hit a new problem with Seamonkey 2.30.

Just finished installing a new small Linux server. I needed to access
the web page on the server. Fired up Seamonkey, entered https:IP and
the port number. And got this message:

An error occurred during a connection to test1:1. The key does not
support the requested operation. (Error code: sec_error_invalid_key)

The page you are trying to view cannot be shown because the authenticity
of the received data could not be verified.

Please contact the web site owners to inform them of this problem.

And it won't let me log on. Wonderful I know the key is not offical.
And I don't care - its on my internal network. At least in older
versions I was given a warning and allowed to make an exception. Seems
that I'm now to be protected, even when I do know exactly what I'm doing!

Firefox exhibits exactly the same over protective nonsense. In the end,
I had to use Chromium to access the setup page.

Is this expected behaviour, or is it something I've (yet again) got
messed up in my profile?

I've used Seamonkey since the old Mozilla suite. But if this is about to
become standard, it is about to get dropped. Permanently!

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101
Firefox/33.0 SeaMonkey/2.30

Paul.

Is it a self-signed key? If so, no more self signed keys are allowed
if I am not mistaken.




Yes, its a self-signed key. Fortunately, its the key length that is a 
problem, not the fact that it is self-signed. If they try to prevent 
self-signed keys, there are a lot of sites that will suddenly be out of 
reach...


In my case, the page I had the initial problem with was a Webmin page on 
an internal server. This allowed me to fix it so that I can use 
Seamonkey to access it again:


https://superuser.com/questions/826232/how-to-bypass-the-secure-connection-failed-warning-in-firefox-33

Paul.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Handling of security certificates

[NoOp]

On 11/20/2014 07:01 AM, Paul Marwick wrote:
 NoOp wrote:
 On 11/18/2014 01:50 PM, Paul Marwick wrote:
 I've just hit a new problem with Seamonkey 2.30.

 Just finished installing a new small Linux server. I needed to access
 the web page on the server. Fired up Seamonkey, entered https:IP and
 the port number. And got this message:

 An error occurred during a connection to test1:1. The key does not
 support the requested operation. (Error code: sec_error_invalid_key)

 The page you are trying to view cannot be shown because the authenticity
 of the received data could not be verified.

 Please contact the web site owners to inform them of this problem.

 And it won't let me log on. Wonderful I know the key is not offical.
 And I don't care - its on my internal network. At least in older
 versions I was given a warning and allowed to make an exception. Seems
 that I'm now to be protected, even when I do know exactly what I'm doing!

 Firefox exhibits exactly the same over protective nonsense. In the end,
 I had to use Chromium to access the setup page.

 Is this expected behaviour, or is it something I've (yet again) got
 messed up in my profile?

 I've used Seamonkey since the old Mozilla suite. But if this is about to
 become standard, it is about to get dropped. Permanently!

 User agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101
 Firefox/33.0 SeaMonkey/2.30

 Paul.


 These might be of interest:

 https://bugzilla.mozilla.org/show_bug.cgi?id=1084606
 (Allow overrides for MOZILLA_PKIX_ERROR_INADEQUATE_KEY_SIZE (some cases
 of SEC_ERROR_INVALID_KEY in Fx33))
 https://stackoverflow.com/questions/26389964/firefox-33-0-wont-open-a-specific-local-application-error-code-sec-error-inva/26520093#26520093
 https://superuser.com/questions/826232/how-to-bypass-the-secure-connection-failed-warning-in-firefox-33
 
 Thanks. That last link allowed me to fix it. I've got a number of small 
 servers out there that use Webmin, which was the main problem. 

Excellent!

 Generating a new key from within Webmin has fixed those that I can reach 
 - I'll have to go onsite for the rest, but it does work.

You might try elinks  see if that will work.

Also see:
https://bugs.launchpad.net/ubuntu/+source/elinks/+bug/769354
(elinks accepts self-signed ssl certificates without warning)
may work in your favor :-)


 

 You still should be able to set an exception via
 Edit|Preferences|PrivacySecurity|Certificates|Manage Certificates


 
 I may have to try that if I find any sites in the wild that have the 
 same problem.
 
 Paul.
 

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Handling of security certificates

[Paul Marwick]

I've just hit a new problem with Seamonkey 2.30.

Just finished installing a new small Linux server. I needed to access 
the web page on the server. Fired up Seamonkey, entered https:IP and 
the port number. And got this message:


An error occurred during a connection to test1:1. The key does not 
support the requested operation. (Error code: sec_error_invalid_key)


The page you are trying to view cannot be shown because the authenticity 
of the received data could not be verified.


Please contact the web site owners to inform them of this problem.

And it won't let me log on. Wonderful I know the key is not offical. 
And I don't care - its on my internal network. At least in older 
versions I was given a warning and allowed to make an exception. Seems 
that I'm now to be protected, even when I do know exactly what I'm doing!


Firefox exhibits exactly the same over protective nonsense. In the end, 
I had to use Chromium to access the setup page.


Is this expected behaviour, or is it something I've (yet again) got 
messed up in my profile?


I've used Seamonkey since the old Mozilla suite. But if this is about to 
become standard, it is about to get dropped. Permanently!


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 
Firefox/33.0 SeaMonkey/2.30


Paul.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Handling of security certificates

[NoOp]

On 11/18/2014 01:50 PM, Paul Marwick wrote:
 I've just hit a new problem with Seamonkey 2.30.
 
 Just finished installing a new small Linux server. I needed to access 
 the web page on the server. Fired up Seamonkey, entered https:IP and 
 the port number. And got this message:
 
 An error occurred during a connection to test1:1. The key does not 
 support the requested operation. (Error code: sec_error_invalid_key)
 
 The page you are trying to view cannot be shown because the authenticity 
 of the received data could not be verified.
 
 Please contact the web site owners to inform them of this problem.
 
 And it won't let me log on. Wonderful I know the key is not offical. 
 And I don't care - its on my internal network. At least in older 
 versions I was given a warning and allowed to make an exception. Seems 
 that I'm now to be protected, even when I do know exactly what I'm doing!
 
 Firefox exhibits exactly the same over protective nonsense. In the end, 
 I had to use Chromium to access the setup page.
 
 Is this expected behaviour, or is it something I've (yet again) got 
 messed up in my profile?
 
 I've used Seamonkey since the old Mozilla suite. But if this is about to 
 become standard, it is about to get dropped. Permanently!
 
 User agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 
 Firefox/33.0 SeaMonkey/2.30
 
 Paul.
 


These might be of interest:

https://bugzilla.mozilla.org/show_bug.cgi?id=1084606
(Allow overrides for MOZILLA_PKIX_ERROR_INADEQUATE_KEY_SIZE (some cases
of SEC_ERROR_INVALID_KEY in Fx33))
https://stackoverflow.com/questions/26389964/firefox-33-0-wont-open-a-specific-local-application-error-code-sec-error-inva/26520093#26520093
https://superuser.com/questions/826232/how-to-bypass-the-secure-connection-failed-warning-in-firefox-33

You still should be able to set an exception via
Edit|Preferences|PrivacySecurity|Certificates|Manage Certificates

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Problems w/ certificates after last update 2.22.1

[Ulf Starke]

since the last update, sea monkey has problems with accepting some 
certificates. Even from web sites that are o.k. The worst part is, if 
sea monkey thinks that a web site is not good, one cannot access the 
respective site at all.


There are also some problems with certificates of email providers, such 
as AOL.




___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

personal digital certificates impossibile to use with SM 2.21

[Gabriel]

Hello,

I noticed right now that the menu Security in the composition window 
does not show any checkmark when I select Encrypt or Digitally Sign.

I do have valid personal certificates installed in SM.

I'm using:
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) 
Gecko/20100101 Firefox/24.0 SeaMonkey/2.21

Build identifier: 20130908221205


I'm also sure it worked until some times ago.

Gabriel
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Upgrade to 2.12.1 changed all my permissions on security certificates!

[Daniel]

Rufus wrote:

Daniel wrote:

Desiree wrote:

I have had all Comodo and Comodo related certs as Untrusted (in all
browsers) since Eddy Nig was able to buy a cert for mozilla.com back in
December 2008 from a Comodo reseller. I also have Go Daddy certs as
Untrusted.  This is quite a few certs.

At the very least, SeaMonkey should warn me that it will revert all cert
settings to default when I upgrade but there has been no warning that SM
reset my settings for certificates. I only realized it when I didn't
get a
popup warning when I went to a site that uses Comodo related certs.
(Here is
where I prefer Opera as it handles this in an elegant, no fuss, clean,
and
quick manner but Mozilla browsers do it in a clumsy and irritating
manner
although in the past Mozilla handled the certs in a much superior manner
than now).

I avoid sites that use Comodo/Comodo related or Go Daddy certs as
much as
possible so I want to be warned anytime I am about to go to one of these
sites.

I have gone through every cert's settings now and Untrusted all the
ones I
want to be Untrusted.  I'd like to avoid this with future updates.



Where does one look up one's cert settings??



Preferences/Privacy and Security/Certificates/Manage Certificates/Edit
Trust



Deselected several Comodo certs and several Go-Daddy certs (as I've 
heard they are suspect as well)


Ta to Rufus and David for directions.
--
Daniel
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Upgrade to 2.12.1 changed all my permissions on security certificates!

[Desiree]

I have had all Comodo and Comodo related certs as Untrusted (in all 
browsers) since Eddy Nig was able to buy a cert for mozilla.com back in 
December 2008 from a Comodo reseller. I also have Go Daddy certs as 
Untrusted.  This is quite a few certs.

At the very least, SeaMonkey should warn me that it will revert all cert 
settings to default when I upgrade but there has been no warning that SM 
reset my settings for certificates. I only realized it when I didn't get a 
popup warning when I went to a site that uses Comodo related certs. (Here is 
where I prefer Opera as it handles this in an elegant, no fuss, clean, and 
quick manner but Mozilla browsers do it in a clumsy and irritating manner 
although in the past Mozilla handled the certs in a much superior manner 
than now).

I avoid sites that use Comodo/Comodo related or Go Daddy certs as much as 
possible so I want to be warned anytime I am about to go to one of these 
sites.

I have gone through every cert's settings now and Untrusted all the ones I 
want to be Untrusted.  I'd like to avoid this with future updates. 


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Upgrade to 2.12.1 changed all my permissions on security certificates!

[Daniel]

Desiree wrote:

I have had all Comodo and Comodo related certs as Untrusted (in all
browsers) since Eddy Nig was able to buy a cert for mozilla.com back in
December 2008 from a Comodo reseller. I also have Go Daddy certs as
Untrusted.  This is quite a few certs.

At the very least, SeaMonkey should warn me that it will revert all cert
settings to default when I upgrade but there has been no warning that SM
reset my settings for certificates. I only realized it when I didn't get a
popup warning when I went to a site that uses Comodo related certs. (Here is
where I prefer Opera as it handles this in an elegant, no fuss, clean, and
quick manner but Mozilla browsers do it in a clumsy and irritating manner
although in the past Mozilla handled the certs in a much superior manner
than now).

I avoid sites that use Comodo/Comodo related or Go Daddy certs as much as
possible so I want to be warned anytime I am about to go to one of these
sites.

I have gone through every cert's settings now and Untrusted all the ones I
want to be Untrusted.  I'd like to avoid this with future updates.



Where does one look up one cert settings??

--
Daniel
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Upgrade to 2.12.1 changed all my permissions on security certificates!

[David E. Ross]

On 9/17/12 1:08 AM, Desiree wrote:
 I have had all Comodo and Comodo related certs as Untrusted (in all 
 browsers) since Eddy Nig was able to buy a cert for mozilla.com back in 
 December 2008 from a Comodo reseller. I also have Go Daddy certs as 
 Untrusted.  This is quite a few certs.
 
 At the very least, SeaMonkey should warn me that it will revert all cert 
 settings to default when I upgrade but there has been no warning that SM 
 reset my settings for certificates. I only realized it when I didn't get a 
 popup warning when I went to a site that uses Comodo related certs. (Here is 
 where I prefer Opera as it handles this in an elegant, no fuss, clean, and 
 quick manner but Mozilla browsers do it in a clumsy and irritating manner 
 although in the past Mozilla handled the certs in a much superior manner 
 than now).
 
 I avoid sites that use Comodo/Comodo related or Go Daddy certs as much as 
 possible so I want to be warned anytime I am about to go to one of these 
 sites.
 
 I have gone through every cert's settings now and Untrusted all the ones I 
 want to be Untrusted.  I'd like to avoid this with future updates. 
 
 

Some time ago, I untrusted CNNIC.  This did not change with 2.12 or
2.12.1.

-- 

David E. Ross
http://www.rossde.com/

Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation.
© 1997 by David E. Ross
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Upgrade to 2.12.1 changed all my permissions on security certificates!

[David E. Ross]

On 9/17/12 6:06 AM, Daniel wrote:
 Desiree wrote:
 I have had all Comodo and Comodo related certs as Untrusted (in all
 browsers) since Eddy Nig was able to buy a cert for mozilla.com back in
 December 2008 from a Comodo reseller. I also have Go Daddy certs as
 Untrusted.  This is quite a few certs.

 At the very least, SeaMonkey should warn me that it will revert all cert
 settings to default when I upgrade but there has been no warning that SM
 reset my settings for certificates. I only realized it when I didn't get a
 popup warning when I went to a site that uses Comodo related certs. (Here is
 where I prefer Opera as it handles this in an elegant, no fuss, clean, and
 quick manner but Mozilla browsers do it in a clumsy and irritating manner
 although in the past Mozilla handled the certs in a much superior manner
 than now).

 I avoid sites that use Comodo/Comodo related or Go Daddy certs as much as
 possible so I want to be warned anytime I am about to go to one of these
 sites.

 I have gone through every cert's settings now and Untrusted all the ones I
 want to be Untrusted.  I'd like to avoid this with future updates.

 
 Where does one look up one cert settings??
 

1.  On the SeaMonkey menu bar, select [Edit  Preferences].

2.  On the Preferences window, select [Privacy  Security  Certificates].

3.  On the Certificates pane, select the Manage Certificates button.

4.  On the Certificate Manager window, select the Authorities tab.

5.  Under any listed certification authority (CA) listed, select a
certificate.  (If the CA has a + in the box to the right, you will first
have to select that box to get a - and display the CA's certificates.)

6.  Select the Edit Trust button.  Check marks will appear in the
checkboxes for those certificate uses where the certificate is trusted.

No, step #6 is NOT intuitive.  You might think that the View button
would show the status of a certificate, but it does not.

-- 

David E. Ross
http://www.rossde.com/

Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation.
© 1997 by David E. Ross
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Upgrade to 2.12.1 changed all my permissions on security certificates!

[Rufus]

Daniel wrote:

Desiree wrote:

I have had all Comodo and Comodo related certs as Untrusted (in all
browsers) since Eddy Nig was able to buy a cert for mozilla.com back in
December 2008 from a Comodo reseller. I also have Go Daddy certs as
Untrusted.  This is quite a few certs.

At the very least, SeaMonkey should warn me that it will revert all cert
settings to default when I upgrade but there has been no warning that SM
reset my settings for certificates. I only realized it when I didn't
get a
popup warning when I went to a site that uses Comodo related certs.
(Here is
where I prefer Opera as it handles this in an elegant, no fuss, clean,
and
quick manner but Mozilla browsers do it in a clumsy and irritating manner
although in the past Mozilla handled the certs in a much superior manner
than now).

I avoid sites that use Comodo/Comodo related or Go Daddy certs as much as
possible so I want to be warned anytime I am about to go to one of these
sites.

I have gone through every cert's settings now and Untrusted all the
ones I
want to be Untrusted.  I'd like to avoid this with future updates.



Where does one look up one cert settings??



Preferences/Privacy and Security/Certificates/Manage Certificates/Edit Trust

--
 - Rufus
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Upgrade to 2.12.1 changed all my permissions on security certificates!

[Desiree]

David E. Ross nobody@nowhere.invalid wrote in message 
news:avidnqu_zd1p3srnnz2dnuvz_gcdn...@mozilla.org...
 On 9/17/12 1:08 AM, Desiree wrote:
 I have had all Comodo and Comodo related certs as Untrusted (in all
 browsers) since Eddy Nig was able to buy a cert for mozilla.com back in
 December 2008 from a Comodo reseller. I also have Go Daddy certs as
 Untrusted.  This is quite a few certs.

 At the very least, SeaMonkey should warn me that it will revert all cert
 settings to default when I upgrade but there has been no warning that SM
 reset my settings for certificates. I only realized it when I didn't get 
 a
 popup warning when I went to a site that uses Comodo related certs. (Here 
 is
 where I prefer Opera as it handles this in an elegant, no fuss, clean, 
 and
 quick manner but Mozilla browsers do it in a clumsy and irritating manner
 although in the past Mozilla handled the certs in a much superior manner
 than now).

 I avoid sites that use Comodo/Comodo related or Go Daddy certs as much as
 possible so I want to be warned anytime I am about to go to one of these
 sites.

 I have gone through every cert's settings now and Untrusted all the ones 
 I
 want to be Untrusted.  I'd like to avoid this with future updates.



 Some time ago, I untrusted CNNIC.  This did not change with 2.12 or
 2.12.1.

 -- 

 David E. Ross
 http://www.rossde.com/

 Anyone who thinks government owns a monopoly on inefficient, obstructive
 bureaucracy has obviously never worked for a large corporation.
 © 1997 by David E. Ross

I don't recall this happening with past updates...just this last one. I 
wonder if it could be because I had to do a full upgrade...not the small one 
from internal update (which had the wrong files when I tried to update that 
way)? 


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates disappeared from Seamonkey 2.0.x - Fixed

[Frank J Nagy]

user@domain.invalid wrote:

Mac OS X 10.6.7
Seamonkey 2.0.14, problem first noticed under 2.0.13

My personal certificates and the CA certificates which
authenticate them have disappeared from Seamonkey.
This used to all work prior to 2.0.13 but not neither
my personal certificates nor the CA Authority ceriticates
shows up in the Certificate manager.

However, if I try to re-install (at least one of) the
CA certificates I get a dialog bot saying that the
certificate is already installed but I cannot see it!



Fixed this.  After a bit of googling I decided that my
certificate store was probably corrupted and followed
instructions to stop Seamonkey, delete the cert8.db file
in my profile and restart.  I was then able to reload
my personal certificates and their CA certificates.
All is good again.

--
= Dr. Frank J. Nagy[Applied Scientist]
= Fermilab Computing Division/Lab and Scientific Core Services
= Service Operations Support Dept/Engineering Support Group
= n...@fnal.gov (Alt: f.n...@clear.net)
= Web page: http://home.fnal.gov/~nagy/
= Feynman Computing FCC394   630-840-4935  FAX 840-6345
= USnail: Fermilab POB 500 MS/369 Batavia, IL 60510
= ICBM: 40d 51m 34s N, 88d 12d 29d W, 651 ft ASL
+ This seat. It warms your ass. Wonderful. -- Dr. Bishop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Certificates disappeared from Seamonkey 2.0.x

[user]

Mac OS X 10.6.7
Seamonkey 2.0.14, problem first noticed under 2.0.13

My personal certificates and the CA certificates which
authenticate them have disappeared from Seamonkey.
This used to all work prior to 2.0.13 but not neither
my personal certificates nor the CA Authority ceriticates
shows up in the Certificate manager.

However, if I try to re-install (at least one of) the
CA certificates I get a dialog bot saying that the
certificate is already installed but I cannot see it!

--
= Dr. Frank J. Nagy[Applied Scientist]
= Fermilab Computing Division/Lab and Scientific Core Services
= Service Operations Support Dept/Engineering Support Group
= n...@fnal.gov (Alt: f.n...@clear.net)
= Web page: http://home.fnal.gov/~nagy/
= Feynman Computing FCC394   630-840-4935  FAX 840-6345
= USnail: Fermilab POB 500 MS/369 Batavia, IL 60510
= ICBM: 40d 51m 34s N, 88d 12d 29d W, 651 ft ASL
+ This seat. It warms your ass. Wonderful. -- Dr. Bishop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Disappearing certificates in SeaMoneky 2.0 under Mac OS X

[Frank J. Nagy]

The 2.0.13 upgrade to SeaMonkey has apparrently destroyed
my personal certificates.  Both the long term (1+ year)
and short term certificates no longer appear nor do their
CA certificates appear under the Authorites tab.
This was all working as of 2.0.12, does anyone else
see this?  Have a solution?


--
= Dr. Frank J. Nagy[Applied Scientist]
= Fermilab Computing Division/Central Services and Infrastructure
= Authentication, Directory and Messaging Services
= n...@fnal.gov (Alt: f.n...@sbcglobal.net)
= Web page: http://home.fnal.gov/~nagy/
= Feynman Computing FCC358   630-840-4935  FAX 840-6345
= USnail: Fermilab POB 500 MS/369 Batavia, IL 60510
= ICBM: 40d 51m 34s N, 88d 12d 29d W, 651 ft ASL
+ This seat. It warms your ass. Wonderful. -- Dr. Bishop

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Disappearing certificates in SeaMoneky 2.0 under Mac OS X

[Joe32065]

Frank J. Nagy wrote:

The 2.0.13 upgrade to SeaMonkey has apparrently destroyed
my personal certificates. Both the long term (1+ year)
and short term certificates no longer appear nor do their
CA certificates appear under the Authorites tab.
This was all working as of 2.0.12, does anyone else
see this? Have a solution?


Frank, I think you replied to the wrong post.  Or should have started a 
new post.


So far I have found no solution on my question.  If you need to go 
through hundreds of posts marking threads as read, moving the thread as 
read button to the main menu should make sense.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey nightly (SM2.1.b2pre) web site authentication with certificates broken

[dominique]

dominique wrote, On 1/7/2011 4:18 PM:

Hello all,

I am using the Seamonkey nightlies to access a web site which requires
certificates for authentication.
I see it is broken since a few days
I have not narrowed down the exact date where this happens, but it looks
like it happened between 20101223 and 20110106
Dominique


I have now narrowed down the problem to both Firefox and Seamonkey 
nightlies (must be trunk issue) and at a starting date of 20110106


Jan 5th 2011: both SM2.1b2pre and FF4.0b9pre are OK
Jan 6th 2011: both SM2.1b2pre and FF4.0b9pre present the problem.

Any problem already logged in bugzilla ?
any regression ?

I no news from anyone, I'll log a new bug

Dominique
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey nightly (SM2.1.b2pre) web site authentication with certificates broken

[dominique]

dominique wrote, On 1/9/2011 4:42 PM:

dominique wrote, On 1/7/2011 4:18 PM:

Hello all,

I am using the Seamonkey nightlies to access a web site which requires
certificates for authentication.
I see it is broken since a few days
I have not narrowed down the exact date where this happens, but it looks
like it happened between 20101223 and 20110106
Dominique


I have now narrowed down the problem to both Firefox and Seamonkey
nightlies (must be trunk issue) and at a starting date of 20110106

Jan 5th 2011: both SM2.1b2pre and FF4.0b9pre are OK
Jan 6th 2011: both SM2.1b2pre and FF4.0b9pre present the problem.

Any problem already logged in bugzilla ?
any regression ?

I no news from anyone, I'll log a new bug

Dominique


Seems logged as: https://bugzilla.mozilla.org/show_bug.cgi?id=624075

Dominique
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Seamonkey nightly (SM2.1.b2pre) web site authentication with certificates broken

[dominique]

Hello all,

I am using the Seamonkey nightlies to access a web site which requires 
certificates for authentication.

I see it is broken since a few days
I have not narrowed down the exact date where this happens, but it looks 
like it happened between 20101223 and 20110106


Anyone else seeing this problem too ?
Is there a bug already opened for that ?

Thanks for any pointer here.

Dominique
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Phillip Jones wrote:

James wrote:

James wrote:

Phillip Jones wrote:

James wrote:

Rick Merrill wrote:

James wrote:

Phillip Jones wrote:

James wrote:

Phillip Jones wrote:

James wrote:
I set up SeaMonkey with certificates for each email account. 
The major problem is to get the certificates recognized in 
Thunderbird and vice versa. I keep getting the broken key 
symbol. Something similar happens on the other end.


The certificates are functional between the accounts I 
manage, but I do not have any external correspondents with 
other certificate enabled email clients to extend my range 
of testing.


Unless I get a solution soon, I must abandon SeaMonkey. Has 
anyone compiled a list of email certificate problems, with 
or without solutions?


The same certificates will work just as good SeaMonkey as in 
Thunderbird. export your personal certificates (from Versign 
or thawte) to folder (directory) on your hard drive. you will 
have to supply your password used to create the certificate. 
and in some cases if you have password protected Thunderbird 
you'll have to supply that as well. When you import into SM 
you have to supply those password(s) again. Certificate meant 
for MS products will not work on Mozilla Products. The 
certificate have to be customized by the company (Thawte / 
Versign) for the email Client and the OS. But any customized 
for Mozilla (or Netscape) works on any Mozilla Product.
You misunderstand. The certificates are properly installed and 
working, but a recipient that is using Thunderbird can not 
read encrypted email sent to him and I can not read encrypted 
email received from him. SeaMonkey to SeaMonkey works fine. 
SeaMonkey to or from Thunderbird does not work at all.


Oh you and he is supposed to send you public key to each other. 
The public key that each other receives works with the private 
keys if they fit you can talk. Go to Versign and look up 
Private key and Public key also look in SeaMonkey's help.


We each have traded certificate and public key data, yet it does 
not function. No help here. I am not a novice as I have been 
using email certificates for years without problems until I 
migrated to SeaMonkey. Unless I get a solution, SeaMonkey is 
history as far as I am concerned.


Excuse me, but did you address the issue Certificates meant for 
MS products will not work on Mozilla Products?


The certificates worked in Thunderbird without problems. They do 
not work in SeaMonkey. I presume my initial inquiry was too 
complex. *Certificate encrypted emails from SeaMonkey to 
Thunderbird do not decrypt. Certificate encrypted emails from 
Thunderbird to SeaMonkey do not decrypt.* That is as simple as I 
can explain the problem. Does anyone have a solution?


Since both SeaMonkey and Thunderbird are both Mozilla products, I 
do not see how your reference applies. I do not use Micro$oft 
products unless I require a function found there that is not 
available elsewhere. For instance, I use Micro$oft Internet 
Explorer for those web pages that do not function using any other 
browser. Another example is that I only use Micro$oft Word when I 
must manipulate lists where tabs and paragraph marks must be used 
in 'search and replace' operations as Open Office does not support 
that function.
  How did you migrate the certificates did you do and export and 
then an import?


Yes, I exported the certificates from Thunderbird and imported them 
into SeaMonkey when I decided to migrate. The more I look at it, the 
more of a mistake that seems to be.
SeaMonkey to SeaMonkey test completed. Both SeaMonkey email clients 
had certificate authority issued certificates. After trading signed 
emails, encryption was successful in both directions.


Unfortunately, that does not help explain why it fails with 
Thunderbird. Without a fix, migrating back to Thunderbird will be 
necessary.


My thanks to everyone that has contributed to this thread.


 Have you tried importing your SeaMonkey Cert to Thunderbird?

It originally came from ThunderBird, so I do not anticipate any problems 
there.


Further investigation shows that for some reason the public key is not 
being sent with the certificate, so when I look into the certificate 
file, there is nothing there from the Thunderbird client. I wonder if 
the Thunderbird client has correctly stored my certificate. I presume 
SeaMonkey automatically sends the public key with the signature, but I 
have been unable to verify that other than with a new correspondent (as 
per the latest test). I must remember to ask if the Thunderbird client 
has a copy of my certificate and public key.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Ray_Net wrote:

James wrote:

Ray_Net wrote:

James wrote:

Mark Hansen wrote:

On 10/25/2010 12:46 PM, James wrote:

You make it seem as if you never sent or received an encrypted
email using your method. If you had, you would know what each
participant is required to have. Still, when I have time, I will
continue to research Enigmail. So far it seems it will only work
with Mozilla email client programs.

Actually, I sent encrypted/signed message to and received from many
people. However, I don't know what they were using.

Reading the documentation makes it seem that it is a certificate
creator and manager. There is nothing that presumes the certificates
will not work anywhere a certificate is used. I do not think this
will solve the problem in sending certificate encrypted emails to
Thunderbird and receiving certificate encrypted emails from 
Thunderbird.


I tried again to encrypt to Thunderbird and again failed. All the
other attempts succeeded. Without a definitive answer to the
SeaMonkey email certificate problem, I must migrate back to 
Thunderbird.


Personally, I believe that all internet traffic should be encrypted.
Unfortunately, the majority say, I keep myself vulnerable because I
want to be abused, here is my banking information. I do not wish the
hackers to know that I am saying things like, Hello, how are you?
in the emails I send. Let them try to decrypt it to find out there is
no personal info there.


So you need to sent the public key to everyone in the world - because
you don't know to which person the destination of the next mail will
be...

Is that not how Enigmail works? You trade public keys (certificates)
then you may encrypt? I have zero experience with Enigmail,

Me too :-)
I think that you must send public key but you should encrypt with your 
personal key.
I never use encrypted mail to not force the recipent to install 
decryption software, etc ... let the people stay simple and reserve 
encrypted mail if you want to sent sensible data in a mail.
It seems to me that Enigmail makes certificates easier to create and 
manage, but the signed and encrypted emails themselves are handled the 
same with or without Enigmail. If you would like to practice, you may 
send me a signed email. I will then reply signed. Then we may attempt 
sending each other encrypted emails. You with Enigmail and me without. 
It should work as we are both using SeaMonkey. I would like to test it 
out with someone that is using Thunderbird as I have only one 
correspondent that uses Thunderbird for encryption and it would be 
useful to find out if it works or the problem is with SeaMonkey or with 
Thunderbird. One point on a chart does not make a graph.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

James wrote:

Phillip Jones wrote:

James wrote:

Rick Merrill wrote:

James wrote:

Phillip Jones wrote:

James wrote:

Phillip Jones wrote:

James wrote:
I set up SeaMonkey with certificates for each email account. 
The major problem is to get the certificates recognized in 
Thunderbird and vice versa. I keep getting the broken key 
symbol. Something similar happens on the other end.


The certificates are functional between the accounts I manage, 
but I do not have any external correspondents with other 
certificate enabled email clients to extend my range of testing.


Unless I get a solution soon, I must abandon SeaMonkey. Has 
anyone compiled a list of email certificate problems, with or 
without solutions?


The same certificates will work just as good SeaMonkey as in 
Thunderbird. export your personal certificates (from Versign or 
thawte) to folder (directory) on your hard drive. you will have 
to supply your password used to create the certificate. and in 
some cases if you have password protected Thunderbird you'll 
have to supply that as well. When you import into SM you have 
to supply those password(s) again. Certificate meant for MS 
products will not work on Mozilla Products. The certificate 
have to be customized by the company (Thawte / Versign) for the 
email Client and the OS. But any customized for Mozilla (or 
Netscape) works on any Mozilla Product.
You misunderstand. The certificates are properly installed and 
working, but a recipient that is using Thunderbird can not read 
encrypted email sent to him and I can not read encrypted email 
received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey 
to or from Thunderbird does not work at all.


Oh you and he is supposed to send you public key to each other. 
The public key that each other receives works with the private 
keys if they fit you can talk. Go to Versign and look up Private 
key and Public key also look in SeaMonkey's help.


We each have traded certificate and public key data, yet it does 
not function. No help here. I am not a novice as I have been using 
email certificates for years without problems until I migrated to 
SeaMonkey. Unless I get a solution, SeaMonkey is history as far as 
I am concerned.


Excuse me, but did you address the issue Certificates meant for MS 
products will not work on Mozilla Products?


The certificates worked in Thunderbird without problems. They do not 
work in SeaMonkey. I presume my initial inquiry was too complex. 
*Certificate encrypted emails from SeaMonkey to Thunderbird do not 
decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey 
do not decrypt.* That is as simple as I can explain the problem. 
Does anyone have a solution?


Since both SeaMonkey and Thunderbird are both Mozilla products, I do 
not see how your reference applies. I do not use Micro$oft products 
unless I require a function found there that is not available 
elsewhere. For instance, I use Micro$oft Internet Explorer for those 
web pages that do not function using any other browser. Another 
example is that I only use Micro$oft Word when I must manipulate 
lists where tabs and paragraph marks must be used in 'search and 
replace' operations as Open Office does not support that function.
 How did you migrate the certificates did you do and export and then 
an import?


Yes, I exported the certificates from Thunderbird and imported them 
into SeaMonkey when I decided to migrate. The more I look at it, the 
more of a mistake that seems to be.
SeaMonkey to SeaMonkey test completed. Both SeaMonkey email clients had 
certificate authority issued certificates. After trading signed emails, 
encryption was successful in both directions.


Unfortunately, that does not help explain why it fails with Thunderbird. 
Without a fix, migrating back to Thunderbird will be necessary.


My thanks to everyone that has contributed to this thread.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

James wrote:

Ray_Net wrote:

James wrote:

Ray_Net wrote:

James wrote:

Mark Hansen wrote:

On 10/25/2010 12:46 PM, James wrote:
You make it seem as if you never sent or received an encrypted 
email using your method. If you had, you would know what each 
participant is required to have. Still, when I have time, I will 
continue to research Enigmail. So far it seems it will only work 
with Mozilla email client programs.
Actually, I sent encrypted/signed message to and received from 
many people. However, I don't know what they were using.
Reading the documentation makes it seem that it is a certificate 
creator and manager. There is nothing that presumes the 
certificates will not work anywhere a certificate is used. I do 
not think this will solve the problem in sending certificate 
encrypted emails to Thunderbird and receiving certificate 
encrypted emails from Thunderbird.


I tried again to encrypt to Thunderbird and again failed. All the 
other attempts succeeded. Without a definitive answer to the 
SeaMonkey email certificate problem, I must migrate back to 
Thunderbird.


Personally, I believe that all internet traffic should be 
encrypted. Unfortunately, the majority say, I keep myself 
vulnerable because I want to be abused, here is my banking 
information. I do not wish the hackers to know that I am saying 
things like, Hello, how are you? in the emails I send. Let them 
try to decrypt it to find out there is no personal info there.


So you need to sent the public key to everyone in the world - 
because you don't know to which person the destination of the next 
mail will be...
Is that not how Enigmail works? You trade public keys (certificates) 
then you may encrypt? I have zero experience with Enigmail,
Me too :-) I think that you must send public key but you should 
encrypt with your personal key. I never use encrypted mail to not 
force the recipent to install decryption software, etc ... let the 
people stay simple and reserve encrypted mail if you want to sent 
sensible data in a mail.
It seems to me that Enigmail makes certificates easier to create and 
manage, but the signed and encrypted emails themselves are handled the 
same with or without Enigmail. If you would like to practice, you may 
send me a signed email. I will then reply signed. Then we may attempt 
sending each other encrypted emails. You with Enigmail and me without. 
It should work as we are both using SeaMonkey. I would like to test it 
out with someone that is using Thunderbird as I have only one 
correspondent that uses Thunderbird for encryption and it would be 
useful to find out if it works or the problem is with SeaMonkey or 
with Thunderbird. One point on a chart does not make a graph.
SeaMonkey to SeaMonkey test completed. Both SeaMonkey email clients had 
certificate authority issued certificates. After trading signed emails, 
encryption was successful in both directions.


Unfortunately, that does not help explain why it fails with Thunderbird. 
Without a fix, migrating back to Thunderbird will be necessary.


My thanks to everyone that has contributed to this thread.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Phillip Jones]

James wrote:

James wrote:

Phillip Jones wrote:

James wrote:

Rick Merrill wrote:

James wrote:

Phillip Jones wrote:

James wrote:

Phillip Jones wrote:

James wrote:

I set up SeaMonkey with certificates for each email account.
The major problem is to get the certificates recognized in
Thunderbird and vice versa. I keep getting the broken key
symbol. Something similar happens on the other end.

The certificates are functional between the accounts I manage,
but I do not have any external correspondents with other
certificate enabled email clients to extend my range of testing.

Unless I get a solution soon, I must abandon SeaMonkey. Has
anyone compiled a list of email certificate problems, with or
without solutions?


The same certificates will work just as good SeaMonkey as in
Thunderbird. export your personal certificates (from Versign or
thawte) to folder (directory) on your hard drive. you will have
to supply your password used to create the certificate. and in
some cases if you have password protected Thunderbird you'll
have to supply that as well. When you import into SM you have
to supply those password(s) again. Certificate meant for MS
products will not work on Mozilla Products. The certificate
have to be customized by the company (Thawte / Versign) for the
email Client and the OS. But any customized for Mozilla (or
Netscape) works on any Mozilla Product.

You misunderstand. The certificates are properly installed and
working, but a recipient that is using Thunderbird can not read
encrypted email sent to him and I can not read encrypted email
received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey
to or from Thunderbird does not work at all.


Oh you and he is supposed to send you public key to each other.
The public key that each other receives works with the private
keys if they fit you can talk. Go to Versign and look up Private
key and Public key also look in SeaMonkey's help.


We each have traded certificate and public key data, yet it does
not function. No help here. I am not a novice as I have been using
email certificates for years without problems until I migrated to
SeaMonkey. Unless I get a solution, SeaMonkey is history as far as
I am concerned.


Excuse me, but did you address the issue Certificates meant for MS
products will not work on Mozilla Products?


The certificates worked in Thunderbird without problems. They do not
work in SeaMonkey. I presume my initial inquiry was too complex.
*Certificate encrypted emails from SeaMonkey to Thunderbird do not
decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey
do not decrypt.* That is as simple as I can explain the problem.
Does anyone have a solution?

Since both SeaMonkey and Thunderbird are both Mozilla products, I do
not see how your reference applies. I do not use Micro$oft products
unless I require a function found there that is not available
elsewhere. For instance, I use Micro$oft Internet Explorer for those
web pages that do not function using any other browser. Another
example is that I only use Micro$oft Word when I must manipulate
lists where tabs and paragraph marks must be used in 'search and
replace' operations as Open Office does not support that function.

  How did you migrate the certificates did you do and export and then
an import?


Yes, I exported the certificates from Thunderbird and imported them
into SeaMonkey when I decided to migrate. The more I look at it, the
more of a mistake that seems to be.

SeaMonkey to SeaMonkey test completed. Both SeaMonkey email clients had
certificate authority issued certificates. After trading signed emails,
encryption was successful in both directions.

Unfortunately, that does not help explain why it fails with Thunderbird.
Without a fix, migrating back to Thunderbird will be necessary.

My thanks to everyone that has contributed to this thread.


 Have you tried importing your SeaMonkey Cert to Thunderbird?

--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.net/   mailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Ray_Net]

James wrote:

Ray_Net wrote:

James wrote:

Mark Hansen wrote:

On 10/25/2010 12:46 PM, James wrote:

You make it seem as if you never sent or received an encrypted
email using your method. If you had, you would know what each
participant is required to have. Still, when I have time, I will
continue to research Enigmail. So far it seems it will only work
with Mozilla email client programs.

Actually, I sent encrypted/signed message to and received from many
people. However, I don't know what they were using.

Reading the documentation makes it seem that it is a certificate
creator and manager. There is nothing that presumes the certificates
will not work anywhere a certificate is used. I do not think this
will solve the problem in sending certificate encrypted emails to
Thunderbird and receiving certificate encrypted emails from Thunderbird.

I tried again to encrypt to Thunderbird and again failed. All the
other attempts succeeded. Without a definitive answer to the
SeaMonkey email certificate problem, I must migrate back to Thunderbird.

Personally, I believe that all internet traffic should be encrypted.
Unfortunately, the majority say, I keep myself vulnerable because I
want to be abused, here is my banking information. I do not wish the
hackers to know that I am saying things like, Hello, how are you?
in the emails I send. Let them try to decrypt it to find out there is
no personal info there.


So you need to sent the public key to everyone in the world - because
you don't know to which person the destination of the next mail will
be...

Is that not how Enigmail works? You trade public keys (certificates)
then you may encrypt? I have zero experience with Enigmail,

Me too :-)
I think that you must send public key but you should encrypt with your 
personal key.
I never use encrypted mail to not force the recipent to install 
decryption software, etc ... let the people stay simple and reserve 
encrypted mail if you want to sent sensible data in a mail.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Ray_Net]

James wrote:

Mark Hansen wrote:

On 10/25/2010 12:46 PM, James wrote:

You make it seem as if you never sent or received an encrypted email
using your method. If you had, you would know what each participant is
required to have. Still, when I have time, I will continue to research
Enigmail. So far it seems it will only work with Mozilla email client
programs.

Actually, I sent encrypted/signed message to and received from many
people. However, I don't know what they were using.

Reading the documentation makes it seem that it is a certificate creator
and manager. There is nothing that presumes the certificates will not
work anywhere a certificate is used. I do not think this will solve the
problem in sending certificate encrypted emails to Thunderbird and
receiving certificate encrypted emails from Thunderbird.

I tried again to encrypt to Thunderbird and again failed. All the other
attempts succeeded. Without a definitive answer to the SeaMonkey email
certificate problem, I must migrate back to Thunderbird.

Personally, I believe that all internet traffic should be encrypted.
Unfortunately, the majority say, I keep myself vulnerable because I
want to be abused, here is my banking information. I do not wish the
hackers to know that I am saying things like, Hello, how are you? in
the emails I send. Let them try to decrypt it to find out there is no
personal info there.


So you need to sent the public key to everyone in the world - because 
you don't know to which person the destination of the next mail will be...

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Ray_Net wrote:

James wrote:

Mark Hansen wrote:

On 10/25/2010 12:46 PM, James wrote:
You make it seem as if you never sent or received an encrypted 
email using your method. If you had, you would know what each 
participant is required to have. Still, when I have time, I will 
continue to research Enigmail. So far it seems it will only work 
with Mozilla email client programs.
Actually, I sent encrypted/signed message to and received from many 
people. However, I don't know what they were using.
Reading the documentation makes it seem that it is a certificate 
creator and manager. There is nothing that presumes the certificates 
will not work anywhere a certificate is used. I do not think this 
will solve the problem in sending certificate encrypted emails to 
Thunderbird and receiving certificate encrypted emails from Thunderbird.


I tried again to encrypt to Thunderbird and again failed. All the 
other attempts succeeded. Without a definitive answer to the 
SeaMonkey email certificate problem, I must migrate back to Thunderbird.


Personally, I believe that all internet traffic should be encrypted. 
Unfortunately, the majority say, I keep myself vulnerable because I 
want to be abused, here is my banking information. I do not wish the 
hackers to know that I am saying things like, Hello, how are you? 
in the emails I send. Let them try to decrypt it to find out there is 
no personal info there.


So you need to sent the public key to everyone in the world - because 
you don't know to which person the destination of the next mail will 
be...
Is that not how Enigmail works? You trade public keys (certificates) 
then you may encrypt? I have zero experience with Enigmail, but the 
documentation suggests it is a certificate generator and certificate 
manager add-on for Mozilla email client programs.


Certificates issued by certificate authorities work to enable you to 
sign emails that can be sent to anyone, but both sender and recipient 
need each other's public keys for encryption. Trading certificates with 
an initial email and reply using signed emails is about as convenient as 
it gets before you can start sending encrypted emails.


Before secure emails, you had to encrypt a file and send it as an 
attachment. Self-extracting files were executable (.exe) and all the 
emails I tried to send with an executable file were stopped. This means 
both need the same encryption software. Trading passwords securely may 
be a problem using stand alone encryption. In my experience, the 
majority have no idea that their emails are being routinely scanned by 
hackers looking for a quick profit. I keep hearing stories about people 
sending credit card info to a family member to make a purchase and the 
credit card or bank account being raided for all it is worth by a hacker 
even before the family member can use it. I do not even like sending 
unencrypted emails that have no personal information, but convincing the 
drooling mouth breather with a mind of a gnat that encryption is good is 
as harder than teaching people to breathe under water. They argue, I 
have nothing to hide.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Phillip Jones wrote:

James wrote:

Rick Merrill wrote:

James wrote:

Phillip Jones wrote:

James wrote:

Phillip Jones wrote:

James wrote:

I set up SeaMonkey with certificates for each email account. The
major
problem is to get the certificates recognized in Thunderbird and
vice
versa. I keep getting the broken key symbol. Something similar
happens
on the other end.

The certificates are functional between the accounts I manage, but
I do
not have any external correspondents with other certificate 
enabled

email clients to extend my range of testing.

Unless I get a solution soon, I must abandon SeaMonkey. Has anyone
compiled a list of email certificate problems, with or without
solutions?


The same certificates will work just as good SeaMonkey as in
Thunderbird.
export your personal certificates (from Versign or thawte) to 
folder
(directory) on your hard drive. you will have to supply your 
password

used to create the certificate. and in some cases if you have
password
protected Thunderbird you'll have to supply that as well. When you
import into SM you have to supply those password(s) again.
Certificate meant for MS products will not work on Mozilla 
Products.

The certificate have to be customized by the company (Thawte /
Versign) for the email Client and the OS. But any customized for
Mozilla (or Netscape) works on any Mozilla Product.

You misunderstand. The certificates are properly installed and
working,
but a recipient that is using Thunderbird can not read encrypted 
email

sent to him and I can not read encrypted email received from him.
SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird
does
not work at all.


Oh you and he is supposed to send you public key to each other. The
public key that each other receives works with the private keys if
they fit you can talk. Go to Versign and look up Private key and
Public key also look in SeaMonkey's help.


We each have traded certificate and public key data, yet it does not
function. No help here. I am not a novice as I have been using email
certificates for years without problems until I migrated to SeaMonkey.
Unless I get a solution, SeaMonkey is history as far as I am 
concerned.


Excuse me, but did you address the issue Certificates meant for MS
products will not work on Mozilla Products?


The certificates worked in Thunderbird without problems. They do not
work in SeaMonkey. I presume my initial inquiry was too complex.
*Certificate encrypted emails from SeaMonkey to Thunderbird do not
decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey do
not decrypt.* That is as simple as I can explain the problem. Does
anyone have a solution?

Since both SeaMonkey and Thunderbird are both Mozilla products, I do not
see how your reference applies. I do not use Micro$oft products unless I
require a function found there that is not available elsewhere. For
instance, I use Micro$oft Internet Explorer for those web pages that do
not function using any other browser. Another example is that I only use
Micro$oft Word when I must manipulate lists where tabs and paragraph
marks must be used in 'search and replace' operations as Open Office
does not support that function.
 How did you migrate the certificates did you do and export and then 
an import?


Yes, I exported the certificates from Thunderbird and imported them into 
SeaMonkey when I decided to migrate. The more I look at it, the more of 
a mistake that seems to be.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Mark Hansen wrote:

On 10/24/2010 1:43 PM, James wrote:
   

Mark Hansen wrote:
 

On 10/23/2010 6:24 PM, James wrote:

   

I have been using email certificates for years. The only time I had
email certificate problems is when I started using SeaMonkey.

 

Have you considered using Enigmail? To be honest, I didn't even know
SeaMonkey had a built-in way to send/receive encrypted e-mail messages.

Enigmail provides this and has been working for me for years.

   

I have been looking at the documentation and found no reference to how
the other user would be able to use anything I sent to them encrypted.
Does each party need the same program? If so, then this application will
be severely limited as most of my correspondents that use certificate
encryption use Outlook, Outlook Express, or some other email client
program. My problem is with the Thunderbird user.

I will continue to look into this and I thank you for your suggestion.
 

 From what I understand, the encrypted e-mail message is done in an
industry-standard way, so anyone (with the correct public pgp key)
should be able to read it.

However, I don't know for sure. You might want to check with the author's
site. I'm sure he has an FAQ or is willing to answer questions, etc.

Good luck.
   
You make it seem as if you never sent or received an encrypted email 
using your method. If you had, you would know what each participant is 
required to have. Still, when I have time, I will continue to research 
Enigmail. So far it seems it will only work with Mozilla email client 
programs.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Mark Hansen]

On 10/25/2010 12:46 PM, James wrote:
 You make it seem as if you never sent or received an encrypted email 
 using your method. If you had, you would know what each participant is 
 required to have. Still, when I have time, I will continue to research 
 Enigmail. So far it seems it will only work with Mozilla email client 
 programs.

Actually, I sent encrypted/signed message to and received from many
people. However, I don't know what they were using.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Mark Hansen]

On 10/23/2010 6:24 PM, James wrote:
 I have been using email certificates for years. The only time I had 
 email certificate problems is when I started using SeaMonkey.

Have you considered using Enigmail? To be honest, I didn't even know
SeaMonkey had a built-in way to send/receive encrypted e-mail messages.

Enigmail provides this and has been working for me for years.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Phillip Jones wrote:

James wrote:

Phillip Jones wrote:

James wrote:

I set up SeaMonkey with certificates for each email account. The major
problem is to get the certificates recognized in Thunderbird and vice
versa. I keep getting the broken key symbol. Something similar happens
on the other end.

The certificates are functional between the accounts I manage, but 
I do

not have any external correspondents with other certificate enabled
email clients to extend my range of testing.

Unless I get a solution soon, I must abandon SeaMonkey. Has anyone
compiled a list of email certificate problems, with or without
solutions?


The same certificates will work just as good SeaMonkey as in 
Thunderbird.

export your personal certificates (from Versign or thawte) to folder
(directory) on your hard drive. you will have to supply your password
used to create the certificate. and in some cases if you have password
protected Thunderbird you'll have to supply that as well.  When you
import into SM you have to supply those  password(s) again.
Certificate meant for MS products will not work on Mozilla Products.
The certificate have to be customized by the company (Thawte /
Versign) for the email Client and the OS. But any customized for
Mozilla (or Netscape) works on any Mozilla Product.

You misunderstand. The certificates are properly installed and working,
but a recipient that is using Thunderbird can not read encrypted email
sent to him and I can not read encrypted email received from him.
SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does
not work at all.


Oh you and he is supposed to send you public key to each other. The 
public key that each other receives works with the private keys if 
they fit you can talk.  Go to Versign and look up Private key and 
Public key also look in SeaMonkey's help.


We each have traded certificate and public key data, yet it does not 
function. No help here. I am not a novice as I have been using email 
certificates for years without problems until I migrated to SeaMonkey. 
Unless I get a solution, SeaMonkey is history as far as I am concerned.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Rick Merrill]

James wrote:

Phillip Jones wrote:

James wrote:

Phillip Jones wrote:

James wrote:

I set up SeaMonkey with certificates for each email account. The major
problem is to get the certificates recognized in Thunderbird and vice
versa. I keep getting the broken key symbol. Something similar happens
on the other end.

The certificates are functional between the accounts I manage, but
I do
not have any external correspondents with other certificate enabled
email clients to extend my range of testing.

Unless I get a solution soon, I must abandon SeaMonkey. Has anyone
compiled a list of email certificate problems, with or without
solutions?


The same certificates will work just as good SeaMonkey as in
Thunderbird.
export your personal certificates (from Versign or thawte) to folder
(directory) on your hard drive. you will have to supply your password
used to create the certificate. and in some cases if you have password
protected Thunderbird you'll have to supply that as well. When you
import into SM you have to supply those password(s) again.
Certificate meant for MS products will not work on Mozilla Products.
The certificate have to be customized by the company (Thawte /
Versign) for the email Client and the OS. But any customized for
Mozilla (or Netscape) works on any Mozilla Product.

You misunderstand. The certificates are properly installed and working,
but a recipient that is using Thunderbird can not read encrypted email
sent to him and I can not read encrypted email received from him.
SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does
not work at all.


Oh you and he is supposed to send you public key to each other. The
public key that each other receives works with the private keys if
they fit you can talk. Go to Versign and look up Private key and
Public key also look in SeaMonkey's help.


We each have traded certificate and public key data, yet it does not
function. No help here. I am not a novice as I have been using email
certificates for years without problems until I migrated to SeaMonkey.
Unless I get a solution, SeaMonkey is history as far as I am concerned.


Excuse me, but did you address the issue Certificates meant for MS products will not 
work on Mozilla Products?


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Rick Merrill wrote:
James wrote:
  
  Phillip Jones wrote:

James wrote:
  
  Phillip Jones wrote:

James wrote:
  
  I set up SeaMonkey with certificates
for each email account. The major

problem is to get the certificates recognized in Thunderbird and vice

versa. I keep getting the broken key symbol. Something similar happens

on the other end.


The certificates are functional between the accounts I manage, but

I do

not have any external correspondents with other certificate enabled

email clients to extend my range of testing.


Unless I get a solution soon, I must abandon SeaMonkey. Has anyone

compiled a list of email certificate problems, with or without

solutions?

  
  
The same certificates will work just as good SeaMonkey as in
  
Thunderbird.
  
export your personal certificates (from Versign or thawte) to folder
  
(directory) on your hard drive. you will have to supply your password
  
used to create the certificate. and in some cases if you have password
  
protected Thunderbird you'll have to supply that as well. When you
  
import into SM you have to supply those password(s) again.
  
Certificate meant for MS products will not work on Mozilla Products.
  
The certificate have to be customized by the company (Thawte /
  
Versign) for the email Client and the OS. But any customized for
  
Mozilla (or Netscape) works on any Mozilla Product.
  

You misunderstand. The certificates are properly installed and working,

but a recipient that is using Thunderbird can not read encrypted email

sent to him and I can not read encrypted email received from him.

SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird
does

not work at all.

  
  
Oh you and he is supposed to send you public key to each other. The
  
public key that each other receives works with the private keys if
  
they fit you can talk. Go to Versign and look up Private key and
  
Public key also look in SeaMonkey's help.
  
  

We each have traded certificate and public key data, yet it does not

function. No help here. I am not a novice as I have been using email

certificates for years without problems until I migrated to SeaMonkey.

Unless I get a solution, SeaMonkey is history as far as I am concerned.

  
  
Excuse me, but did you address the issue "Certificates meant for MS
products will not work on Mozilla Products"?
  
  

The certificates worked in Thunderbird without problems. They do not
work in SeaMonkey. I presume my initial inquiry was too complex. Certificate encrypted emails from SeaMonkey to
Thunderbird do not decrypt. Certificate encrypted emails from
Thunderbird to SeaMonkey do not decrypt. That is as simple
as I can explain the problem. Does anyone have a solution?

Since both SeaMonkey and Thunderbird are both Mozilla products, I do
not see how your reference applies. I do not use Micro$oft products
unless I require a function found there that is not available
elsewhere. For instance, I use Micro$oft Internet Explorer for those
web pages that do not function using any other browser. Another example
is that I only use Micro$oft Word when I must manipulate lists where
tabs and paragraph marks must be used in 'search and replace'
operations as Open Office does not support that function.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Mark Hansen wrote:

On 10/23/2010 6:24 PM, James wrote:
   

I have been using email certificates for years. The only time I had
email certificate problems is when I started using SeaMonkey.
 

Have you considered using Enigmail? To be honest, I didn't even know
SeaMonkey had a built-in way to send/receive encrypted e-mail messages.

Enigmail provides this and has been working for me for years.
   
I have been looking at the documentation and found no reference to how 
the other user would be able to use anything I sent to them encrypted. 
Does each party need the same program? If so, then this application will 
be severely limited as most of my correspondents that use certificate 
encryption use Outlook, Outlook Express, or some other email client 
program. My problem is with the Thunderbird user.


I will continue to look into this and I thank you for your suggestion.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Mark Hansen]

On 10/24/2010 1:43 PM, James wrote:
 Mark Hansen wrote:
 On 10/23/2010 6:24 PM, James wrote:

 I have been using email certificates for years. The only time I had
 email certificate problems is when I started using SeaMonkey.
  
 Have you considered using Enigmail? To be honest, I didn't even know
 SeaMonkey had a built-in way to send/receive encrypted e-mail messages.

 Enigmail provides this and has been working for me for years.

 I have been looking at the documentation and found no reference to how 
 the other user would be able to use anything I sent to them encrypted. 
 Does each party need the same program? If so, then this application will 
 be severely limited as most of my correspondents that use certificate 
 encryption use Outlook, Outlook Express, or some other email client 
 program. My problem is with the Thunderbird user.
 
 I will continue to look into this and I thank you for your suggestion.

From what I understand, the encrypted e-mail message is done in an
industry-standard way, so anyone (with the correct public pgp key)
should be able to read it.

However, I don't know for sure. You might want to check with the author's
site. I'm sure he has an FAQ or is willing to answer questions, etc.

Good luck.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Phillip Jones]

James wrote:

Rick Merrill wrote:

James wrote:

Phillip Jones wrote:

James wrote:

Phillip Jones wrote:

James wrote:

I set up SeaMonkey with certificates for each email account. The
major
problem is to get the certificates recognized in Thunderbird and
vice
versa. I keep getting the broken key symbol. Something similar
happens
on the other end.

The certificates are functional between the accounts I manage, but
I do
not have any external correspondents with other certificate enabled
email clients to extend my range of testing.

Unless I get a solution soon, I must abandon SeaMonkey. Has anyone
compiled a list of email certificate problems, with or without
solutions?


The same certificates will work just as good SeaMonkey as in
Thunderbird.
export your personal certificates (from Versign or thawte) to folder
(directory) on your hard drive. you will have to supply your password
used to create the certificate. and in some cases if you have
password
protected Thunderbird you'll have to supply that as well. When you
import into SM you have to supply those password(s) again.
Certificate meant for MS products will not work on Mozilla Products.
The certificate have to be customized by the company (Thawte /
Versign) for the email Client and the OS. But any customized for
Mozilla (or Netscape) works on any Mozilla Product.

You misunderstand. The certificates are properly installed and
working,
but a recipient that is using Thunderbird can not read encrypted email
sent to him and I can not read encrypted email received from him.
SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird
does
not work at all.


Oh you and he is supposed to send you public key to each other. The
public key that each other receives works with the private keys if
they fit you can talk. Go to Versign and look up Private key and
Public key also look in SeaMonkey's help.


We each have traded certificate and public key data, yet it does not
function. No help here. I am not a novice as I have been using email
certificates for years without problems until I migrated to SeaMonkey.
Unless I get a solution, SeaMonkey is history as far as I am concerned.


Excuse me, but did you address the issue Certificates meant for MS
products will not work on Mozilla Products?


The certificates worked in Thunderbird without problems. They do not
work in SeaMonkey. I presume my initial inquiry was too complex.
*Certificate encrypted emails from SeaMonkey to Thunderbird do not
decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey do
not decrypt.* That is as simple as I can explain the problem. Does
anyone have a solution?

Since both SeaMonkey and Thunderbird are both Mozilla products, I do not
see how your reference applies. I do not use Micro$oft products unless I
require a function found there that is not available elsewhere. For
instance, I use Micro$oft Internet Explorer for those web pages that do
not function using any other browser. Another example is that I only use
Micro$oft Word when I must manipulate lists where tabs and paragraph
marks must be used in 'search and replace' operations as Open Office
does not support that function.
 How did you migrate the certificates did you do and export and then an 
import?


--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.net/   mailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

email certificates

[James]

I set up SeaMonkey with certificates for each email account. The major 
problem is to get the certificates recognized in Thunderbird and vice 
versa. I keep getting the broken key symbol. Something similar happens 
on the other end.


The certificates are functional between the accounts I manage, but I do 
not have any external correspondents with other certificate enabled 
email clients to extend my range of testing.


Unless I get a solution soon, I must abandon SeaMonkey. Has anyone 
compiled a list of email certificate problems, with or without solutions?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Phillip Jones]

James wrote:

I set up SeaMonkey with certificates for each email account. The major
problem is to get the certificates recognized in Thunderbird and vice
versa. I keep getting the broken key symbol. Something similar happens
on the other end.

The certificates are functional between the accounts I manage, but I do
not have any external correspondents with other certificate enabled
email clients to extend my range of testing.

Unless I get a solution soon, I must abandon SeaMonkey. Has anyone
compiled a list of email certificate problems, with or without solutions?


The same certificates will work just as good SeaMonkey as in Thunderbird.
export your personal certificates (from Versign or thawte) to folder 
(directory) on your hard drive. you will have to supply your password 
used to create the certificate. and in some cases if you have password 
protected Thunderbird you'll have to supply that as well.  When you 
import into SM you have to supply those  password(s) again.
Certificate meant for MS products will not work on Mozilla Products. The 
certificate have to be customized by the company (Thawte / Versign) for 
the email Client and the OS. But any customized for Mozilla (or 
Netscape) works on any Mozilla Product.

--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.net/   mailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Phillip Jones wrote:

James wrote:

I set up SeaMonkey with certificates for each email account. The major
problem is to get the certificates recognized in Thunderbird and vice
versa. I keep getting the broken key symbol. Something similar happens
on the other end.

The certificates are functional between the accounts I manage, but I do
not have any external correspondents with other certificate enabled
email clients to extend my range of testing.

Unless I get a solution soon, I must abandon SeaMonkey. Has anyone
compiled a list of email certificate problems, with or without 
solutions?


The same certificates will work just as good SeaMonkey as in Thunderbird.
export your personal certificates (from Versign or thawte) to folder 
(directory) on your hard drive. you will have to supply your password 
used to create the certificate. and in some cases if you have password 
protected Thunderbird you'll have to supply that as well.  When you 
import into SM you have to supply those  password(s) again.
Certificate meant for MS products will not work on Mozilla Products. 
The certificate have to be customized by the company (Thawte / 
Versign) for the email Client and the OS. But any customized for 
Mozilla (or Netscape) works on any Mozilla Product.
You misunderstand. The certificates are properly installed and working, 
but a recipient that is using Thunderbird can not read encrypted email 
sent to him and I can not read encrypted email received from him. 
SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does 
not work at all.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[James]

Phillip Jones wrote:

James wrote:

I set up SeaMonkey with certificates for each email account. The major
problem is to get the certificates recognized in Thunderbird and vice
versa. I keep getting the broken key symbol. Something similar happens
on the other end.

The certificates are functional between the accounts I manage, but I do
not have any external correspondents with other certificate enabled
email clients to extend my range of testing.

Unless I get a solution soon, I must abandon SeaMonkey. Has anyone
compiled a list of email certificate problems, with or without 
solutions?


The same certificates will work just as good SeaMonkey as in Thunderbird.
export your personal certificates (from Versign or thawte) to folder 
(directory) on your hard drive. you will have to supply your password 
used to create the certificate. and in some cases if you have password 
protected Thunderbird you'll have to supply that as well.  When you 
import into SM you have to supply those  password(s) again.
Certificate meant for MS products will not work on Mozilla Products. 
The certificate have to be customized by the company (Thawte / 
Versign) for the email Client and the OS. But any customized for 
Mozilla (or Netscape) works on any Mozilla Product.
I have been using email certificates for years. The only time I had 
email certificate problems is when I started using SeaMonkey.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: email certificates

[Phillip Jones]

James wrote:

Phillip Jones wrote:

James wrote:

I set up SeaMonkey with certificates for each email account. The major
problem is to get the certificates recognized in Thunderbird and vice
versa. I keep getting the broken key symbol. Something similar happens
on the other end.

The certificates are functional between the accounts I manage, but I do
not have any external correspondents with other certificate enabled
email clients to extend my range of testing.

Unless I get a solution soon, I must abandon SeaMonkey. Has anyone
compiled a list of email certificate problems, with or without
solutions?


The same certificates will work just as good SeaMonkey as in Thunderbird.
export your personal certificates (from Versign or thawte) to folder
(directory) on your hard drive. you will have to supply your password
used to create the certificate. and in some cases if you have password
protected Thunderbird you'll have to supply that as well.  When you
import into SM you have to supply those  password(s) again.
Certificate meant for MS products will not work on Mozilla Products.
The certificate have to be customized by the company (Thawte /
Versign) for the email Client and the OS. But any customized for
Mozilla (or Netscape) works on any Mozilla Product.

You misunderstand. The certificates are properly installed and working,
but a recipient that is using Thunderbird can not read encrypted email
sent to him and I can not read encrypted email received from him.
SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does
not work at all.


Oh you and he is supposed to send you public key to each other. The 
public key that each other receives works with the private keys if they 
fit you can talk.  Go to Versign and look up Private key and Public key 
also look in SeaMonkey's help.


--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.net/   mailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Daniel]

Leonidas Jones wrote:

Bush wrote:

Leonidas Jones wrote:

Bush wrote:

Leonidas Jones wrote:

Bush wrote:

NoOp wrote:

On 11/30/2009 06:33 PM, Bush wrote:

Graham wrote:

Bush wrote:

/snip/

/snip/


snip


Thanks for the help Lee .I may answer some more of you inquiries later.
But typing with one hand makes the good Hand Hurt .. I already lost one
hand and do not want to loose the remaining one .




One of our valued contributors here types one handed as well.  (Hi 
Daniel)  I don't have any personal experience with one handed typing, 
but I manage to do badly enough with two hands :)  I do appreciate your 
efforts in improving this valued suite.


Lee



Gee, Lee, I was thinking of asking Bush how he lost his hand (Me Right 
Arm, above elbow, in car accident) but thought TPTB might get nasty, and 
wasn't sure Bush would follow me if I cross posted to m.gen.


Daniel
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Graham]

Bush wrote:
I got ris of seamonkey 2.0 and went back to ver 1.1.18 and No problems 
with Certificates


Having read your ranting in other threads, and not paying attention to 
what you've been told (esp re user agent spoofing), I'd say you've made 
the best choice - for all of us.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Leonidas Jones]

Bush wrote:

Graham wrote:

Bush wrote:

I got ris of seamonkey 2.0 and went back to ver 1.1.18 and No
problems with Certificates


Having read your ranting in other threads, and not paying attention to
what you've been told (esp re user agent spoofing), I'd say you've
made the best choice - for all of us.


No one told me How I Spoofed ? So How Do you Spoof Seamonkey ?


The main thing is I went back to Seamonkey 1.1.18 and no problems

Still looking for Spoofing ...

New hard drive
New install of Win 7
New install of Seamonkey 2.0



No, NO NO!!

Its not the install of 2.0 that's reporting the wrong UA, its your 
1.1.18!!!





And I guess My install SPOOFED Mozilla's mistakes .


And Quit Adding to the problem, By telling me thing I NEVER DID .

The SOFTWARE DIDNOT install Correctly .


As far as the other post go '

http://www.glorecords.blm.gov/


Totslly useless information snipped.


I got right into it with Seamonkey 1.1.1



You got right in because the UA string which *you* reported in another 
thread is incorrect.  Someone, either you or someone with access to your 
machine permanently changed the UA string.  SeaMonkey will not do this 
by itself.


SeaMonkey is not going to report a UA of an antiquated version of 
Firefox without user intervention. If it was not you, it was someone 
with access to your machine.


I dare you to try creating a new profile in SeaMonkey 1.1.18, and see if 
you can get in.


Create this new profile, and report it back here.  It *will* show the 
correct UA for SeaMonkey.


Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[NoOp]

On 11/30/2009 06:33 PM, Bush wrote:
 Graham wrote:
 Bush wrote:
 I got ris of seamonkey 2.0 and went back to ver 1.1.18 and No problems 
 with Certificates
 
 Having read your ranting in other threads, and not paying attention to 
 what you've been told (esp re user agent spoofing), I'd say you've made 
 the best choice - for all of us.
 
 No one told me How I Spoofed ? So How Do you Spoof Seamonkey ?
 
 
 The main thing is I went back to Seamonkey 1.1.18 and no problems
 
 Still looking for Spoofing ...
 
 New hard drive
 New install of Win 7
 New install of Seamonkey 2.0
 
 And I guess My install SPOOFED  Mozilla's mistakes .
 
 
 And Quit Adding to the problem, By telling me thing I NEVER DID .
 
 The SOFTWARE DIDNOT install Correctly .
 
 
 As far as the other post go '
 
 http://www.glorecords.blm.gov/
 
 I got right into it with Seamonkey 1.1.18

Yes you did - you spoofed Firefox just fine:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23)
Gecko/20090825 Firefox/2.0.0.7

Now, toddle along  enjoy your ignorance.

But if you'd really like to understand what/when/where, why not try
being such an ass and work with the folks who are _trying_ to help you?

Please click 'Help|About SeaMonkey' and tell us what shows under
'SeaMonkey 1.1.18'. Don't be afraid, you can copy and paste the result
here. My guess is that it will show:
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23)
Gecko/20090825 Firefox/2.0.0.7

and you'll find that Firefox/2.0.0.7 is *not* a valid/normal UA in a
standard SeaMonkey install. Somewhere along the line you, or whoever
installed SeaMonkey for you, added the Firefox/2.0.0.7 into your
profile for Firefox spoofing. That's not necessarily a bad thing
(subject to some debate), but just understand it is *not* standard and
is there for Fx spoofing.

Please tell us what you see when you enter: about:plugins
Just the header/main such as:
Default Plugin
Java(TM) Plug-in 1.6.0_16
etc.

Now enter: about:config
and enter: firefox
in the Filter box. What do you see?



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Bush]

Leonidas Jones wrote:

Bush wrote:

Graham wrote:

Bush wrote:

I got ris of seamonkey 2.0 and went back to ver 1.1.18 and No
problems with Certificates


Having read your ranting in other threads, and not paying attention to
what you've been told (esp re user agent spoofing), I'd say you've
made the best choice - for all of us.


No one told me How I Spoofed ? So How Do you Spoof Seamonkey ?


The main thing is I went back to Seamonkey 1.1.18 and no problems

Still looking for Spoofing ...

New hard drive
New install of Win 7
New install of Seamonkey 2.0



No, NO NO!!

Its not the install of 2.0 that's reporting the wrong UA, its your 
1.1.18!!!





And I guess My install SPOOFED Mozilla's mistakes .


And Quit Adding to the problem, By telling me thing I NEVER DID .

The SOFTWARE DIDNOT install Correctly .


As far as the other post go '

http://www.glorecords.blm.gov/


Totslly useless information snipped.


I got right into it with Seamonkey 1.1.1



You got right in because the UA string which *you* reported in another 
thread is incorrect.  Someone, either you or someone with access to your 
machine permanently changed the UA string.  SeaMonkey will not do this 
by itself.


SeaMonkey is not going to report a UA of an antiquated version of 
Firefox without user intervention. If it was not you, it was someone 
with access to your machine.


I dare you to try creating a new profile in SeaMonkey 1.1.18, and see if 
you can get in.


Create this new profile, and report it back here.  It *will* show the 
correct UA for SeaMonkey.


Lee
 I already created a new profile and it Reads the Same . I even 
uninstalled 1.1.18 and Deleted all files and even wiped the folders .


And dowloaded Seamonkey 1.1.18 again and installed it .
Remade the profile . and here is what it says

SeaMonkey 1.1.18

Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23) 
Gecko/20090825 Firefox/2.0.0.7



Now Tell me How you Spoof it .  Where Do i type in SPOOF  ?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Leonidas Jones]

Bush wrote:

Leonidas Jones wrote:

Bush wrote:

Graham wrote:

Bush wrote:

I got ris of seamonkey 2.0 and went back to ver 1.1.18 and No
problems with Certificates


Having read your ranting in other threads, and not paying attention to
what you've been told (esp re user agent spoofing), I'd say you've
made the best choice - for all of us.


No one told me How I Spoofed ? So How Do you Spoof Seamonkey ?


The main thing is I went back to Seamonkey 1.1.18 and no problems

Still looking for Spoofing ...

New hard drive
New install of Win 7
New install of Seamonkey 2.0



No, NO NO!!

Its not the install of 2.0 that's reporting the wrong UA, its your
1.1.18!!!




And I guess My install SPOOFED Mozilla's mistakes .


And Quit Adding to the problem, By telling me thing I NEVER DID .

The SOFTWARE DIDNOT install Correctly .


As far as the other post go '

http://www.glorecords.blm.gov/


Totslly useless information snipped.


I got right into it with Seamonkey 1.1.1



You got right in because the UA string which *you* reported in another
thread is incorrect. Someone, either you or someone with access to
your machine permanently changed the UA string. SeaMonkey will not do
this by itself.

SeaMonkey is not going to report a UA of an antiquated version of
Firefox without user intervention. If it was not you, it was someone
with access to your machine.

I dare you to try creating a new profile in SeaMonkey 1.1.18, and see
if you can get in.

Create this new profile, and report it back here. It *will* show the
correct UA for SeaMonkey.

Lee

I already created a new profile and it Reads the Same . I even
uninstalled 1.1.18 and Deleted all files and even wiped the folders .

And dowloaded Seamonkey 1.1.18 again and installed it .
Remade the profile . and here is what it says

SeaMonkey 1.1.18

Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23)
Gecko/20090825 Firefox/2.0.0.7


Now Tell me How you Spoof it . Where Do i type in SPOOF ?


Reply in full to NoOP's post.

Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Bush]

NoOp wrote:

On 11/30/2009 06:33 PM, Bush wrote:

Graham wrote:

Bush wrote:
I got ris of seamonkey 2.0 and went back to ver 1.1.18 and No problems 
with Certificates
Having read your ranting in other threads, and not paying attention to 
what you've been told (esp re user agent spoofing), I'd say you've made 
the best choice - for all of us.

No one told me How I Spoofed ? So How Do you Spoof Seamonkey ?


The main thing is I went back to Seamonkey 1.1.18 and no problems

Still looking for Spoofing ...

New hard drive
New install of Win 7
New install of Seamonkey 2.0

And I guess My install SPOOFED  Mozilla's mistakes .


And Quit Adding to the problem, By telling me thing I NEVER DID .

The SOFTWARE DIDNOT install Correctly .


As far as the other post go '

http://www.glorecords.blm.gov/

I got right into it with Seamonkey 1.1.18


Yes you did - you spoofed Firefox just fine:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23)
Gecko/20090825 Firefox/2.0.0.7

Now, toddle along  enjoy your ignorance.

But if you'd really like to understand what/when/where, why not try
being such an ass and work with the folks who are _trying_ to help you?

Please click 'Help|About SeaMonkey' and tell us what shows under
'SeaMonkey 1.1.18'. Don't be afraid, you can copy and paste the result
here. My guess is that it will show:
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23)
Gecko/20090825 Firefox/2.0.0.7

and you'll find that Firefox/2.0.0.7 is *not* a valid/normal UA in a
standard SeaMonkey install. Somewhere along the line you, or whoever
installed SeaMonkey for you, added the Firefox/2.0.0.7 into your
profile for Firefox spoofing. That's not necessarily a bad thing
(subject to some debate), but just understand it is *not* standard and
is there for Fx spoofing.

Please tell us what you see when you enter: about:plugins
Just the header/main such as:
Default Plugin
Java(TM) Plug-in 1.6.0_16
etc.




File name: npoji610.dll
Classic Java Plug-in 1.6.0_17 for Netscape and Mozilla

MIME Type   Description SuffixesEnabled
application/x-java-vm   JavaYes
Java(TM) Platform SE 6 U17

File name: npjpi160_17.dll
Classic Java Plug-in 1.6.0_17 for Netscape and Mozilla


Now enter: about:config
and enter: firefox
in the Filter box. What do you see?


Nothing Happens . after pushing Enter Key . Bottom screen goes Blank


if I enter  Seamonkey I get


I only have one hand so hopefully I get this corect

general.useragent.extra.seamonkey  userset string firefox/2.0.0.7







___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Leonidas Jones]

Bush wrote:

NoOp wrote:

On 11/30/2009 06:33 PM, Bush wrote:

Graham wrote:

Bush wrote:

I got ris of seamonkey 2.0 and went back to ver 1.1.18 and No
problems with Certificates

Having read your ranting in other threads, and not paying attention
to what you've been told (esp re user agent spoofing), I'd say
you've made the best choice - for all of us.

No one told me How I Spoofed ? So How Do you Spoof Seamonkey ?


The main thing is I went back to Seamonkey 1.1.18 and no problems

Still looking for Spoofing ...

New hard drive
New install of Win 7
New install of Seamonkey 2.0

And I guess My install SPOOFED Mozilla's mistakes .


And Quit Adding to the problem, By telling me thing I NEVER DID .

The SOFTWARE DIDNOT install Correctly .


As far as the other post go '

http://www.glorecords.blm.gov/

I got right into it with Seamonkey 1.1.18


Yes you did - you spoofed Firefox just fine:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23)
Gecko/20090825 Firefox/2.0.0.7

Now, toddle along  enjoy your ignorance.

But if you'd really like to understand what/when/where, why not try
being such an ass and work with the folks who are _trying_ to help you?

Please click 'Help|About SeaMonkey' and tell us what shows under
'SeaMonkey 1.1.18'. Don't be afraid, you can copy and paste the result
here. My guess is that it will show:
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23)
Gecko/20090825 Firefox/2.0.0.7

and you'll find that Firefox/2.0.0.7 is *not* a valid/normal UA in a
standard SeaMonkey install. Somewhere along the line you, or whoever
installed SeaMonkey for you, added the Firefox/2.0.0.7 into your
profile for Firefox spoofing. That's not necessarily a bad thing
(subject to some debate), but just understand it is *not* standard and
is there for Fx spoofing.

Please tell us what you see when you enter: about:plugins
Just the header/main such as:
Default Plugin
Java(TM) Plug-in 1.6.0_16
etc.




File name: npoji610.dll
Classic Java Plug-in 1.6.0_17 for Netscape and Mozilla

MIME Type Description Suffixes Enabled
application/x-java-vm Java Yes
Java(TM) Platform SE 6 U17

File name: npjpi160_17.dll
Classic Java Plug-in 1.6.0_17 for Netscape and Mozilla


Now enter: about:config
and enter: firefox
in the Filter box. What do you see?


Nothing Happens . after pushing Enter Key . Bottom screen goes Blank


if I enter Seamonkey I get


I only have one hand so hopefully I get this corect

general.useragent.extra.seamonkey userset string firefox/2.0.0.7








AHA!!


Note, *userset*!!!  Note that the pref is probably in bold.

That tells us that a user has changed the default setting.

Right click on the pref and choose reset.  That will set it back to the 
default setting.


Lee


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Bush]

Leonidas Jones wrote:

Bush wrote:

NoOp wrote:

On 11/30/2009 06:33 PM, Bush wrote:

Graham wrote:

Bush wrote:

I got ris of seamonkey 2.0 and went back to ver 1.1.18 and No
problems with Certificates

Having read your ranting in other threads, and not paying attention
to what you've been told (esp re user agent spoofing), I'd say
you've made the best choice - for all of us.

No one told me How I Spoofed ? So How Do you Spoof Seamonkey ?


The main thing is I went back to Seamonkey 1.1.18 and no problems

Still looking for Spoofing ...

New hard drive
New install of Win 7
New install of Seamonkey 2.0

And I guess My install SPOOFED Mozilla's mistakes .


And Quit Adding to the problem, By telling me thing I NEVER DID .

The SOFTWARE DIDNOT install Correctly .


As far as the other post go '

http://www.glorecords.blm.gov/

I got right into it with Seamonkey 1.1.18


Yes you did - you spoofed Firefox just fine:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23)
Gecko/20090825 Firefox/2.0.0.7

Now, toddle along  enjoy your ignorance.

But if you'd really like to understand what/when/where, why not try
being such an ass and work with the folks who are _trying_ to help you?

Please click 'Help|About SeaMonkey' and tell us what shows under
'SeaMonkey 1.1.18'. Don't be afraid, you can copy and paste the result
here. My guess is that it will show:
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23)
Gecko/20090825 Firefox/2.0.0.7

and you'll find that Firefox/2.0.0.7 is *not* a valid/normal UA in a
standard SeaMonkey install. Somewhere along the line you, or whoever
installed SeaMonkey for you, added the Firefox/2.0.0.7 into your
profile for Firefox spoofing. That's not necessarily a bad thing
(subject to some debate), but just understand it is *not* standard and
is there for Fx spoofing.

Please tell us what you see when you enter: about:plugins
Just the header/main such as:
Default Plugin
Java(TM) Plug-in 1.6.0_16
etc.




File name: npoji610.dll
Classic Java Plug-in 1.6.0_17 for Netscape and Mozilla

MIME Type Description Suffixes Enabled
application/x-java-vm Java Yes
Java(TM) Platform SE 6 U17

File name: npjpi160_17.dll
Classic Java Plug-in 1.6.0_17 for Netscape and Mozilla


Now enter: about:config
and enter: firefox
in the Filter box. What do you see?


Nothing Happens . after pushing Enter Key . Bottom screen goes Blank


if I enter Seamonkey I get


I only have one hand so hopefully I get this corect

general.useragent.extra.seamonkey userset string firefox/2.0.0.7








AHA!!


Note, *userset*!!!  Note that the pref is probably in bold.

That tells us that a user has changed the default setting.

Right click on the pref and choose reset.  That will set it back to the 
default setting.


Lee


 yes the whole line was in Bold ... Everyone in my home Has their own 
computers . I am the only one who uses this one .


Could it Be that Win 7 uninstaller left seamonker 2.0 setting in the 
Registry ?


look at my answer when I went to my wifes computer that has Seamonkey 
1.1.14


I Sent her about seamonkey to me

SeaMonkey 1.1.14

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) 
Gecko/20081204 SeaMonkey/1.1.14





http://www.tvguide.com/listings/default.aspx

and the above link works on hers.  I almost got Killed for waking her 
up. Almost hat a tiger wood situation ..




You think I am a Dick or pulling your chain. But in No way did I So 
called Spoof Seamonkey .





___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Leonidas Jones]

Bush wrote:

Leonidas Jones wrote:

Bush wrote:

NoOp wrote:

On 11/30/2009 06:33 PM, Bush wrote:

Graham wrote:

Bush wrote:

/snip/

general.useragent.extra.seamonkey userset string firefox/2.0.0.7



AHA!!


Note, *userset*!!! Note that the pref is probably in bold.

That tells us that a user has changed the default setting.

Right click on the pref and choose reset. That will set it back to the
default setting.

Lee



yes the whole line was in Bold ... Everyone in my home Has their own
computers . I am the only one who uses this one .

Could it Be that Win 7 uninstaller left seamonker 2.0 setting in the
Registry ?

look at my answer when I went to my wifes computer that has Seamonkey
1.1.14

I Sent her about seamonkey to me

SeaMonkey 1.1.14

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19)
Gecko/20081204 SeaMonkey/1.1.14

http://www.tvguide.com/listings/default.aspx

and the above link works on hers. I almost got Killed for waking her up.
Almost hat a tiger wood situation ..

You think I am a Dick or pulling your chain. But in No way did I So
called Spoof Seamonkey .



I admit, I am getting frustrated, but I sense we are getting some light 
at the end of the tunnel.


The SeaMonkey UA will say SeaMonkey 2.0.  Here is mine, note I am on a Mac:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.4) 
Gecko/20091017 Lightning/1.0pre Mnenhy/0.7.6.0 SeaMonkey/2.0


Your wife has SM 1.1.14.  I suggest updating that to 1.1.18, by the way.

The TVGuide page does seem to work without spoofing, but note Danny's 
original post, with the following:


When looking and the program listing if you click on a show it will 
display a opening that show a description. However, in Seamonkey if just 
show a blank.


So, rather then just opening the page, you have to go to the program 
listings, then click on a show to see details.  If SM has its proper UA, 
it will show a blank space.  If it is spoofed as FF, it will work.


You, or someone using your computer did change the UA.  There is no 
other way for this to happen.  I can see how SM *might* reset to its 
default on its own, but there is no way it will change the UA to an 
antiquated version of Firefox on its own.


FF 2.0.0.7 was released over two years ago. It is certainly possible 
that you had a problem viewing a site, were advised to reset the UA to 
the then current version of Firefox, and, over these more then two 
years, forgot that you had done it. I know that I can not certainly 
swear to things I did over two years ago.


Anyhow, if you reset the pref in about:config as I described elsewhere, 
you will find that reverting to 1.1.18 is not an answer to these kind of 
problems.


Lee





___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Bush]

Leonidas Jones wrote:

Bush wrote:

Leonidas Jones wrote:

Bush wrote:

NoOp wrote:

On 11/30/2009 06:33 PM, Bush wrote:

Graham wrote:

Bush wrote:

/snip/

general.useragent.extra.seamonkey userset string firefox/2.0.0.7



AHA!!


Note, *userset*!!! Note that the pref is probably in bold.

That tells us that a user has changed the default setting.

Right click on the pref and choose reset. That will set it back to the
default setting.

Lee



yes the whole line was in Bold ... Everyone in my home Has their own
computers . I am the only one who uses this one .

Could it Be that Win 7 uninstaller left seamonker 2.0 setting in the
Registry ?

look at my answer when I went to my wifes computer that has Seamonkey
1.1.14

I Sent her about seamonkey to me

SeaMonkey 1.1.14

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19)
Gecko/20081204 SeaMonkey/1.1.14

http://www.tvguide.com/listings/default.aspx

and the above link works on hers. I almost got Killed for waking her up.
Almost hat a tiger wood situation ..

You think I am a Dick or pulling your chain. But in No way did I So
called Spoof Seamonkey .



I admit, I am getting frustrated, but I sense we are getting some light 
at the end of the tunnel.


The SeaMonkey UA will say SeaMonkey 2.0.  Here is mine, note I am on a Mac:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.4) 
Gecko/20091017 Lightning/1.0pre Mnenhy/0.7.6.0 SeaMonkey/2.0


Your wife has SM 1.1.14.  I suggest updating that to 1.1.18, by the way.

The TVGuide page does seem to work without spoofing, but note Danny's 
original post, with the following:


When looking and the program listing if you click on a show it will 
display a opening that show a description. However, in Seamonkey if just 
show a blank.



Just tried my computer at tvguid and clicked a show showing on HBO and I 
get a  RED box with a desription of the movie .


So, rather then just opening the page, you have to go to the program 
listings, then click on a show to see details.  If SM has its proper UA, 
it will show a blank space.  If it is spoofed as FF, it will work.


I wish it were Daytime.. I would go try it on my wifes computer . But I 
do not need her Chasing me down the driveway with a Golf Club .


You, or someone using your computer did change the UA.  There is no 
other way for this to happen.  I can see how SM *might* reset to its 
default on its own, but there is no way it will change the UA to an 
antiquated version of Firefox on its own.


Sorry .. I do all the computer repair here . And no way did I mess with 
any setting other That What is in the Menu's .





FF 2.0.0.7 was released over two years ago. It is certainly possible 
that you had a problem viewing a site, were advised to reset the UA to 
the then current version of Firefox, and, over these more then two 
years, forgot that you had done it. I know that I can not certainly 
swear to things I did over two years ago.


I got interested in my Family history, After I lost my hand. on April 1, 
1998 .  And I created a cd that I gave to all my relatives ( starting 
around 2001) with the info I discovered . and a lot of that info came 
from the Blm site


I only started having problems when I installed seamonkey 2.0 ,  It 
looks suspicious to you, But I have never installed Firefox or 
thunderbird on any of the computers Here . But that is Beside the point 
Because when win 7 was released ( I bought it From microsoft ) I bought 
a new Sata Drive . installed win7 pro  and then Seamonkey 1.1.18  Then I 
saw that 2.0 was on the seamonkey site as the Current release .. 
Uninstalled 1.1.18  and installed 2.0 . Had too many problems access 
e-mail and certain sites, So I uninstalled 2.0 and reinstalled 1.1.18 
and Now u say I spoofed it ...





Anyhow, if you reset the pref in about:config as I described elsewhere, 
you will find that reverting to 1.1.18 is not an answer to these kind of 
problems.



 Right now I donot think I should mess with something that is access 
all the websites . I know u are trying to figure out WHY . and I hope 
your Conversations May help the develpers figure this out in the Future .




Thanks for the help Lee  .I may answer some more of you inquiries later. 
But typing with one hand makes the good Hand Hurt .. I already lost one 
hand and do not want to loose the remaining one .


Lee






___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Leonidas Jones]

Bush wrote:

Leonidas Jones wrote:

Bush wrote:

Leonidas Jones wrote:

Bush wrote:

NoOp wrote:

On 11/30/2009 06:33 PM, Bush wrote:

Graham wrote:

Bush wrote:

/snip/

/snip/

Just tried my computer at tvguid and clicked a show showing on HBO and I
get a RED box with a desription of the movie .


If you did not reset the about:config pref as i described, yes that is 
what would happen.  The site thinks you are using Firefox, and serves 
you a working version.


/snip/

You, or someone using your computer did change the UA. There is no
other way for this to happen. I can see how SM *might* reset to its
default on its own, but there is no way it will change the UA to an
antiquated version of Firefox on its own.


Sorry .. I do all the computer repair here . And no way did I mess with
any setting other That What is in the Menu's .


I can't say anything more then I have already said, some user reset the 
pref.  *userset* means some *user* *set* the pref.  There is no other 
way for it to happen.






/snip/


I only started having problems when I installed seamonkey 2.0 , It looks
suspicious to you, But I have never installed Firefox or thunderbird on
any of the computers Here . But that is Beside the point Because when
win 7 was released ( I bought it From microsoft ) I bought a new Sata
Drive . installed win7 pro and then Seamonkey 1.1.18 Then I saw that 2.0
was on the seamonkey site as the Current release .. Uninstalled 1.1.18
and installed 2.0 . Had too many problems access e-mail and certain
sites, So I uninstalled 2.0 and reinstalled 1.1.18 and Now u say I
spoofed it ...


You installed SeaMonkey 1.1.18 first. Did you transfer settings and 
files from your previous windows installation?  Specifically, did you 
transfer your 1.1.18 profile from your previous Windows installation?


If so, anything you did with SeaMonkey 1.1.18 was carried over. Heck, 
I've forgotten about more things I've done with computers then I 
remember. I've often switched the UA to troubleshoot an issue, then 
forgot that I did it. Fortunately the Prefbar extension reset it as the 
true UA on a restart, or all of you might be wondering how I am posting 
here in IE6 on XP  :)




Anyhow, if you reset the pref in about:config as I described
elsewhere, you will find that reverting to 1.1.18 is not an answer to
these kind of problems.



Right now I donot think I should mess with something that is access all
the websites . I know u are trying to figure out WHY . and I hope your
Conversations May help the develpers figure this out in the Future .


The problem with a permanent UA spoofing is that the web sites' logs 
will indicate that any visit you make with is with Firefox, not 
SeaMonkey. These web site developers will then have no real reason to 
update their browser sniffers to include SeaMonkey.


What I do when I encounter such a site is to spoof the UA to Firefox. 
If I am successful in getting in, I write the web developer of that site 
to tell them that SeaMonkey can in fact deliver their page accurately, 
and ask them to adjust their browser sniffer accordingly.


I'm not saying that you should go that far.  However, if you leave your 
UA permanently spoofed, you are not helping to broaden web access for 
SeaMonkey. The user does play an important part here.


I would suggest returning to the true UA.  Then, via an extension such 
as Preference Toolbar, or the UA switcher, switch the us on an as needed 
basis.  That way, at least the web logs will indicate a attempted visit 
by SeaMonkey, so an tech evangelism attempt will have more credence.






Thanks for the help Lee .I may answer some more of you inquiries later.
But typing with one hand makes the good Hand Hurt .. I already lost one
hand and do not want to loose the remaining one .




One of our valued contributors here types one handed as well.  (Hi 
Daniel)  I don't have any personal experience with one handed typing, 
but I manage to do badly enough with two hands :)  I do appreciate your 
efforts in improving this valued suite.


Lee

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Certificates.

[Bush]

Ever time I go to a site that I have never Been to, I have ADD their 
Certificate to the list Manually .Preference / privacy amd security/ 
certificates/ manage certificates .


What should I have Click in Preference / privacy amd security 
/validation ...

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Certificates.

[Bush]

Bush wrote:
Ever time I go to a site that I have never Been to, I have ADD their 
Certificate to the list Manually .Preference / privacy amd security/ 
certificates/ manage certificates .


What should I have Click in Preference / privacy amd security 
/validation ...
I got ris of seamonkey 2.0 and went back to ver 1.1.18 and No problems 
with Certificates

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM 2.0 b2 Problem with bank certificates

[Martin Freitag]

Terje J. Hanssen schrieb:
 Martin Freitag wrote:

 I never needed to manually import bank certificates... they should be
 known by the default authorities SM knows usually.

 But what do you mean with haven't suceeded? What exactly did you try?
 Importing them in the preferences? (Security... =  Manage Certificates
 =  Import?)
 regards

 Martin
 
 I've used bank certificate with SM 1.1.x, and I think it was valid also
 with SM 1.1.18 before upgrade to SM 2.0b. Now, when I enter the url to
 my netbank and try to login, it starts out to download a new bank
 certifate. Get the normal message about generating a privat key and at
 last Your personal certificate has been installed. Restart you browser.
 
 So far so good. The problem is that on the follow up re-login to the
 bank, it starts to download a new certificate yet another time, just as
 if there isn't any valid certificate available. And so on. This was what
 I meant with haven't succeeded.
 
 I know I experienced a similar or identical problem with a previous SM
 version, maybe around 1.x a couple of years ago. The problem wasn't
 fixed before the next version.
Uh sry, it seems I got that wrong, I do not need to generate private
certificates.
Feel free to file a bug with steps to reproduce in bugzilla (can you
reproduce that yourself on another computer?), although I think that one
might be hard for others to reproduce without having such a bank or
similar...
regards

Martin
-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - http://www.gerstbach.at/2004/ascii
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM 2.0 b2 Problem with bank certificates

[Martin Freitag]

Terje J. Hanssen schrieb:
 I haven't succeeded to use existing bank certifates or download and save
 a new bank certificate with SM 2.0 b2 on Linux. I have to use Firefox
 3.5 for this.
 
 Better experiences?

I never needed to manually import bank certificates... they should be
known by the default authorities SM knows usually.

But what do you mean with haven't suceeded? What exactly did you try?
Importing them in the preferences? (Security... = Manage Certificates
= Import?)
regards

Martin
-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - http://www.gerstbach.at/2004/ascii
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM 2.0 b2 Problem with bank certificates

[Terje J. Hanssen]

Martin Freitag wrote:

Terje J. Hanssen schrieb:

I haven't succeeded to use existing bank certifates or download and save
a new bank certificate with SM 2.0 b2 on Linux. I have to use Firefox
3.5 for this.

Better experiences?


I never needed to manually import bank certificates... they should be
known by the default authorities SM knows usually.

But what do you mean with haven't suceeded? What exactly did you try?
Importing them in the preferences? (Security... =  Manage Certificates
=  Import?)
regards

Martin


I've used bank certificate with SM 1.1.x, and I think it was valid also 
with SM 1.1.18 before upgrade to SM 2.0b. Now, when I enter the url to 
my netbank and try to login, it starts out to download a new bank 
certifate. Get the normal message about generating a privat key and at 
last Your personal certificate has been installed. Restart you browser.


So far so good. The problem is that on the follow up re-login to the 
bank, it starts to download a new certificate yet another time, just as 
if there isn't any valid certificate available. And so on. This was what 
I meant with haven't succeeded.


I know I experienced a similar or identical problem with a previous SM 
version, maybe around 1.x a couple of years ago. The problem wasn't 
fixed before the next version.


And it works ok with Firefox.

Rgds,
Terje


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Multiple certificates per e-mail account

[Ben Stone]

Hi,

I am using SeaMonkey 2.0b2. I have an e-mail account with several 
identities (e-mail addresses) for some of which I have S/MIME 
certificates. Now it seems that I can only select *one* of those 
certificates in the account settings. Is there any way of assigning 
multiple certificates to an account so that SeaMonkey automatically 
chooses the right one depending on which identity I use?



-Ben.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Multiple certificates per e-mail account

[Jens Hatlak]

On 9/24/2009 7:01 PM Ben Stone wrote:
I am using SeaMonkey 2.0b2. I have an e-mail account with several 
identities (e-mail addresses) for some of which I have S/MIME 
certificates. Now it seems that I can only select *one* of those 
certificates in the account settings. Is there any way of assigning 
multiple certificates to an account so that SeaMonkey automatically 
chooses the right one depending on which identity I use?


Click the Manage Identities... button in Mail  Newsgroups Account 
Settings, edit an identity and switch to the Security tab.


HTH

Jens

--
Jens Hatlak http://jens.hatlak.de/
SeaMonkey Trunk Tracker http://smtt.blogspot.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Multiple certificates per e-mail account

[Ben Stone]

On 2009-09-24 19:57, Jens Hatlak wrote:

Click the Manage Identities... button in Mail  Newsgroups Account
Settings, edit an identity and switch to the Security tab.


Cool. Thanks!

-Ben.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey