Finaly a Virus or another anomaly, --Kmail hangs on five emails and subsequently quits
Going through my sorted emails from the Suse list the curser hanged on an email with the subject line Re[2]: [SLE] Installing on a laptop. After approx 5 seconds Kmail quitted. After restart the same occurred when I reached this email. After having removed the offending email from my Suse folder with midnight commander I discovered four other emails with the same effect. They all had a cryptographic signature and they all had to do with Sean Rima. I still have an email with a strange header -Re: Re[2]: [SLE] installing on a laptop- but this email is not a problem. The problem seems to be neutralized. This is the first time I have seen this behavior on my Suse box (9.0) and I hope it is the last time;-). I have the problematic files in a temporary directory. Anybody with more grips about emails who want to have a look just tell me and they will be expedited.
Constant, On Friday 13 May 2005 05:26, Constant Brouerius van Nidek wrote:
Going through my sorted emails from the Suse list the curser hanged on an email with the subject line Re[2]: [SLE] Installing on a laptop. After approx 5 seconds Kmail quitted. After restart the same occurred when I reached this email. After having removed the offending email from my Suse folder with midnight commander I discovered four other emails with the same effect. They all had a cryptographic signature and they all had to do with Sean Rima. I still have an email with a strange header -Re: Re[2]: [SLE] installing on a laptop- but this email is not a problem. The problem seems to be neutralized.
You should give more information about software versions you're running and something about the hardware configuration you're using. Those messages are all signed, and back in the SuSE Linux 9.0 days, I had a problem with certain signed messages with symptoms identical to yours. While I never definitively diagnosed the problem (I used a filter to work around it), I believe it was a library version mismatch between KMail and a library used only when a signed message arrived. And it was not all signed messages, only some. Perhaps it was the particular signing algorithm, I don't know. The problem was eventually fixed when I upgraded KDE (and KMail along with it).
This is the first time I have seen this behavior on my Suse box (9.0) and I hope it is the last time;-). I have the problematic files in a temporary directory. Anybody with more grips about emails who want to have a look just tell me and they will be expedited.
Have you used the supplementary updates for 9.0 to update your KDE? If not, you probably should. It will (probably) fix this problem and get you newer versions of KDE software, which is a good thing. Randall Schulz
Randall R Schulz wrote:
Constant,
On Friday 13 May 2005 05:26, Constant Brouerius van Nidek wrote:
Going through my sorted emails from the Suse list the curser hanged on an email with the subject line Re[2]: [SLE] Installing on a laptop. After approx 5 seconds Kmail quitted. After restart the same occurred when I reached this email. After having removed the offending email from my Suse folder with midnight commander I discovered four other emails with the same effect. They all had a cryptographic signature and they all had to do with Sean Rima. I still have an email with a strange header -Re: Re[2]: [SLE] installing on a laptop- but this email is not a problem. The problem seems to be neutralized.
You should give more information about software versions you're running and something about the hardware configuration you're using.
Those messages are all signed, and back in the SuSE Linux 9.0 days, I had a problem with certain signed messages with symptoms identical to yours.
While I never definitively diagnosed the problem (I used a filter to work around it), I believe it was a library version mismatch between KMail and a library used only when a signed message arrived.
And it was not all signed messages, only some. Perhaps it was the particular signing algorithm, I don't know. The problem was eventually fixed when I upgraded KDE (and KMail along with it).
This is the first time I have seen this behavior on my Suse box (9.0) and I hope it is the last time;-). I have the problematic files in a temporary directory. Anybody with more grips about emails who want to have a look just tell me and they will be expedited.
Have you used the supplementary updates for 9.0 to update your KDE? If not, you probably should. It will (probably) fix this problem and get you newer versions of KDE software, which is a good thing.
Randall Schulz
I haven't come across any virus mails in a while, scanners have said everything is clean. Some years ago I got one from a manager at work, it refused to open, he later confirmed it had a virus. Perhaps running something like klamav or xfprot against those file will reveal if they are infected. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux for all Computing Tasks
On Friday 13 May 2005 20:03, Randall R Schulz wrote:
Constant,
On Friday 13 May 2005 05:26, Constant Brouerius van Nidek wrote:
Going through my sorted emails from the Suse list the curser hanged on an email with the subject line Re[2]: [SLE] Installing on a laptop. After approx 5 seconds Kmail quitted. After restart the same
Have you used the supplementary updates for 9.0 to update your KDE? If not, you probably should. It will (probably) fix this problem and get you newer versions of KDE software, which is a good thing.
Dear Randall Have used all the patches via Yast update. Started wit Synaptic but run into difficulties if I want to upgrade the KDE RPM file which supplies Kmail. Will have another try because today I had another file with signature. What makes them stick out is the fact that they include a number (seen a 2 and today a 4) behind the Re. How does the writer gets a number behind the Re and why. For now I will use the filter function and transport the email with Re[2] etc. direct to the trash file. Pity because it could that the originator has something of interest in his email but so be it.
Constant, On Saturday 14 May 2005 02:53, Constant Brouerius van Nidek wrote:
On Friday 13 May 2005 20:03, Randall R Schulz wrote:
Constant,
On Friday 13 May 2005 05:26, Constant Brouerius van Nidek wrote:
Going through my sorted emails from the Suse list the curser hanged on an email with the subject line Re[2]: [SLE] Installing on a laptop. After approx 5 seconds Kmail quitted. After restart the same
Have you used the supplementary updates for 9.0 to update your KDE? If not, you probably should. It will (probably) fix this problem and get you newer versions of KDE software, which is a good thing.
Dear Randall Have used all the patches via Yast update. Started wit Synaptic but run into difficulties if I want to upgrade the KDE RPM file which supplies Kmail. Will have another try because today I had another file with signature. What makes them stick out is the fact that they include a number (seen a 2 and today a 4) behind the Re. How does the writer gets a number behind the Re and why. For now I will use the filter function and transport the email with Re[2] etc. direct to the trash file. Pity because it could that the originator has something of interest in his email but so be it.
The "Re[2]" is just a particular mailer's way of indicating something about the replay (what, I'm not sure). It most certainly is not the source of the problem and when that user sends another signed message that doesn't have that pattern in the subject (and your filter fails to detect it) and you stumble upon it, the same thing will happen (i.e., your KMail will crash). And it's not just that user. It's just the particular cryptographic format chosen to sign their message. Here's the way to keep this kind of land-mine out of your way: Create a filter that: -) Detects messages whose "Content-Type" field contains "pkcs7-signature". -) Set the filter action to move the message to a folder that you'll assiduously avoid opening in KMail. -) Put the filter at or near the top of your filter set. You probably want to set the "If this filter matches, stop processing here" option. Keep in mind that you can still see these messages, albeit in a crude form, by simply opening the mailbox into which you filter them in a plain text editor. Good luck. Randall Schulz
On Saturday 14 May 2005 21:14, Randall R Schulz wrote:
Constant,
On Saturday 14 May 2005 02:53, Constant Brouerius van Nidek wrote:
On Friday 13 May 2005 20:03, Randall R Schulz wrote:
Constant,
On Friday 13 May 2005 05:26, Constant Brouerius van Nidek wrote:
Going through my sorted emails from the Suse list the curser hanged on an email with the subject line Re[2]: [SLE] Installing on a laptop. After approx 5 seconds Kmail quitted. After restart the same
Have you used the supplementary updates for 9.0 to update your KDE? If not, you probably should. It will (probably) fix this problem and get you newer versions of KDE software, which is a good thing.
Dear Randall Have used all the patches via Yast update. Started wit Synaptic but run into difficulties if I want to upgrade the KDE RPM file which supplies Kmail. Will have another try because today I had another file with signature. What makes them stick out is the fact that they include a number (seen a 2 and today a 4) behind the Re. How does the writer gets a number behind the Re and why. For now I will use the filter function and transport the email with Re[2] etc. direct to the trash file. Pity because it could that the originator has something of interest in his email but so be it.
The "Re[2]" is just a particular mailer's way of indicating something about the replay (what, I'm not sure). It most certainly is not the source of the problem and when that user sends another signed message that doesn't have that pattern in the subject (and your filter fails to detect it) and you stumble upon it, the same thing will happen (i.e., your KMail will crash). And it's not just that user. It's just the particular cryptographic format chosen to sign their message.
I knew that but due to the fact that this was one of the things they all had in common I thought it a good idea to use it to filter.
Here's the way to keep this kind of land-mine out of your way: Create a filter that:
-) Detects messages whose "Content-Type" field contains "pkcs7-signature". -) Set the filter action to move the message to a folder that you'll assiduously avoid opening in KMail. -) Put the filter at or near the top of your filter set. You probably want to set the "If this filter matches, stop processing here" option.
Keep in mind that you can still see these messages, albeit in a crude form, by simply opening the mailbox into which you filter them in a plain text editor.
Good luck.
Thanks Randall Sounds good. Will put it in my filters and wait for things to happen ;-)
On Friday 13 May 2005 04:26 am, Constant Brouerius van Nidek wrote:
. They all had a cryptographic signature and they all had to do with Sean Rima.
It seems to me you may have a miss-configured crypto plugin enabled in Kmail. You might try turning them all off, or fixing the plugin specific to the type of signature involved. The pause as one of these mails is clicked on happens when kmail tries to validate the signature using the crypto plug-in. Does it bomb on this message? (It is also signed). -- _____________________________________ John Andersen
John, On Saturday 14 May 2005 13:05, John Andersen wrote:
On Friday 13 May 2005 04:26 am, Constant Brouerius van Nidek wrote:
. They all had a cryptographic signature and they all had to do with Sean Rima.
It seems to me you may have a miss-configured crypto plugin enabled in Kmail.
You might try turning them all off, or fixing the plugin specific to the type of signature involved.
The pause as one of these mails is clicked on happens when kmail tries to validate the signature using the crypto plug-in.
Does it bomb on this message? (It is also signed).
You're using PGP, Sean Rima is using PKCS7 From John's signed message: Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_wnlhCpoyGQh+lYC"; charset="iso-8859-1" From one of Sean's messages: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------1DAA10E22FC6446" Randall Schulz
On Sunday 15 May 2005 10:01, Randall R Schulz wrote:
John,
On Saturday 14 May 2005 13:05, John Andersen wrote:
On Friday 13 May 2005 04:26 am, Constant Brouerius van Nidek wrote:
. They all had a cryptographic signature and they all had to do with Sean Rima.
It seems to me you may have a miss-configured crypto plugin enabled in Kmail.
You might try turning them all off, or fixing the plugin specific to the type of signature involved.
The pause as one of these mails is clicked on happens when kmail tries to validate the signature using the crypto plug-in.
Does it bomb on this message? (It is also signed).
You're using PGP, Sean Rima is using PKCS7
From John's signed message:
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_wnlhCpoyGQh+lYC"; charset="iso-8859-1"
From one of Sean's messages:
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------1DAA10E22FC6446"
No, it does not bomb out on this message. I do not use PGP or at least I have never worked with encryption. Will have a look if encryption is i use in my Kmail setup. Open PGP and SMime are initialised but not active. Do I remove them both?
Constant, On Saturday 14 May 2005 21:13, Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 10:01, Randall R Schulz wrote:
..
Does it bomb on this message? (It is also signed).
You're using PGP, Sean Rima is using PKCS7
From John's signed message:
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_wnlhCpoyGQh+lYC"; charset="iso-8859-1"
From one of Sean's messages:
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------1DAA10E22FC6446"
No, it does not bomb out on this message. I do not use PGP or at least I have never worked with encryption. Will have a look if encryption is i use in my Kmail setup.
We're not talking about your use of cryptographically signed email, we're talking about the use made by the sender and the fact that there's some library incompatibility, at least between your version of KMail and a library used when validating PGP signatures. It can happen when dependencies are not properly recorded. It happens, not often, but we've seen it on occasion.
Open PGP and SMime are initialised but not active. Do I remove them both?
As I said, you'd do well to upgrade to the latest KDE offered via a SuSE supplementary update. Otherwise, I don't think you'll sort out this problem. My 9.0 installation was like this, too, until I upgraded. Randall Schulz
On Sunday 15 May 2005 11:24, Randall R Schulz wrote:
Constant,
On Saturday 14 May 2005 21:13, Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 10:01, Randall R Schulz wrote:
..
Does it bomb on this message? (It is also signed).
You're using PGP, Sean Rima is using PKCS7
From John's signed message:
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_wnlhCpoyGQh+lYC"; charset="iso-8859-1"
From one of Sean's messages:
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------1DAA10E22FC6446"
No, it does not bomb out on this message. I do not use PGP or at least I have never worked with encryption. Will have a look if encryption is i use in my Kmail setup.
We're not talking about your use of cryptographically signed email, we're talking about the use made by the sender and the fact that there's some library incompatibility, at least between your version of KMail and a library used when validating PGP signatures.
It can happen when dependencies are not properly recorded. It happens, not often, but we've seen it on occasion.
Open PGP and SMime are initialised but not active. Do I remove them both?
As I said, you'd do well to upgrade to the latest KDE offered via a SuSE supplementary update. Otherwise, I don't think you'll sort out this problem. My 9.0 installation was like this, too, until I upgraded.
Thanks for the clarifying words. The 9.2 version is in progress but not yet up to date. No TV some other thinks where I am not happy with. And 9.0 works nearly perfect ;-).
Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 11:24, Randall R Schulz wrote:
Constant,
On Saturday 14 May 2005 21:13, Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 10:01, Randall R Schulz wrote:
..
Does it bomb on this message? (It is also signed).
You're using PGP, Sean Rima is using PKCS7
From John's signed message:
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_wnlhCpoyGQh+lYC"; charset="iso-8859-1"
From one of Sean's messages:
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------1DAA10E22FC6446"
No, it does not bomb out on this message. I do not use PGP or at least I have never worked with encryption. Will have a look if encryption is i use in my Kmail setup.
We're not talking about your use of cryptographically signed email, we're talking about the use made by the sender and the fact that there's some library incompatibility, at least between your version of KMail and a library used when validating PGP signatures.
It can happen when dependencies are not properly recorded. It happens, not often, but we've seen it on occasion.
Yeah I seen this before with some apps, never tried Kmail. The only reason I switched my main PC back to XP is because I need to use a Geovision DVR card which is not supported by linux at all :( Sean
On Sun, 2005-05-15 at 10:28 +0100, Sean Rima wrote:
Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 11:24, Randall R Schulz wrote:
<snip>
It can happen when dependencies are not properly recorded. It happens, not often, but we've seen it on occasion.
Yeah I seen this before with some apps, never tried Kmail. The only reason I switched my main PC back to XP is because I need to use a Geovision DVR card which is not supported by linux at all :(
Sean
I've been seeing a lot of messages lately that have signatures that are invalid. Even this one from Sean shows an "Invalid signature" line at the bottom. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Hello Ken, Sunday, May 15, 2005, 11:46:17 AM, you wrote:
On Sun, 2005-05-15 at 10:28 +0100, Sean Rima wrote:
Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 11:24, Randall R Schulz wrote:
<snip>
It can happen when dependencies are not properly recorded. It happens, not often, but we've seen it on occasion.
Yeah I seen this before with some apps, never tried Kmail. The only reason I switched my main PC back to XP is because I need to use a Geovision DVR card which is not supported by linux at all :(
Sean
I've been seeing a lot of messages lately that have signatures that are invalid. Even this one from Sean shows an "Invalid signature" line at the bottom. Maybe you don't have my key, that can always cause it. Or maybe it is Thunderbird doing it.
Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped
On Sun, 2005-05-15 at 12:04 +0100, Sean Rima wrote:
Hello Ken,
Sunday, May 15, 2005, 11:46:17 AM, you wrote:
On Sun, 2005-05-15 at 10:28 +0100, Sean Rima wrote:
I've been seeing a lot of messages lately that have signatures that are invalid. Even this one from Sean shows an "Invalid signature" line at the bottom. Maybe you don't have my key, that can always cause it. Or maybe it is Thunderbird doing it.
Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped
Well I am not using thunderbird I an using evolution. I went into the config and saw a key for you and removed it. Now it shows as a valid signature. Perhaps I had an old key left over. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Hello Ken, Sunday, May 15, 2005, 12:24:52 PM, you wrote:
On Sun, 2005-05-15 at 12:04 +0100, Sean Rima wrote:
Hello Ken,
Sunday, May 15, 2005, 11:46:17 AM, you wrote:
On Sun, 2005-05-15 at 10:28 +0100, Sean Rima wrote:
I've been seeing a lot of messages lately that have signatures that are invalid. Even this one from Sean shows an "Invalid signature" line at the bottom. Maybe you don't have my key, that can always cause it. Or maybe it is Thunderbird doing it.
Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped
Well I am not using thunderbird I an using evolution. I went into the config and saw a key for you and removed it. Now it shows as a valid signature. Perhaps I had an old key left over.
Yeah I did have a previous key that I lost when I had a house fire, the PC didn't bake too well. I now store a backup onto a USB key every week. Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped
On Sunday 15 May 2005 18:24, Ken Schneider wrote:
On Sun, 2005-05-15 at 12:04 +0100, Sean Rima wrote:
Hello Ken,
Sunday, May 15, 2005, 11:46:17 AM, you wrote:
On Sun, 2005-05-15 at 10:28 +0100, Sean Rima wrote:
I've been seeing a lot of messages lately that have signatures that are invalid. Even this one from Sean shows an "Invalid signature" line at the bottom.
Maybe you don't have my key, that can always cause it. Or maybe it is Thunderbird doing it.
Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped
Well I am not using thunderbird I an using evolution. I went into the config and saw a key for you and removed it. Now it shows as a valid signature. Perhaps I had an old key left over.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge And the email in with you mention your fire is also trouble. How do you do that? Is it a Win...s program you are using.
For that matter,could somebody explain me in plain English the use of cryptografic signatures.
On Sun May 15 2005 8:06 am, Constant Brouerius van Nidek wrote:
For that matter,could somebody explain me in plain English the use of cryptografic signatures. you might want to sign up for the pgp-basics list. They are a wonderful group of people that will bend over backwards to help you learn how to sign & encrypt messages.
http://groups.yahoo.com/group/PGP-Basics/ -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
On Sunday 15 May 2005 20:21, Paul Cartwright wrote:
On Sun May 15 2005 8:06 am, Constant Brouerius van Nidek wrote:
For that matter,could somebody explain me in plain English the use of cryptografic signatures.
you might want to sign up for the pgp-basics list. They are a wonderful group of people that will bend over backwards to help you learn how to sign & encrypt messages.
http://groups.yahoo.com/group/PGP-Basics/
-- Okay Paul, but why should I encrypt. Thanks for the URL. When I find out the "why" I may have a look.
On Sun May 15 2005 10:55 am, Constant Brouerius van Nidek wrote:
Okay Paul, but why should I encrypt. Thanks for the URL. When I find out the "why" I may have a look.
with pgp/Gnupg you can sign/and/or/encrypt messages. It isn't necessary to either sign or encrypt, but you can do either one. If you are sending sensitive data, such as card numbers, Soc. Sec. info, other personal data, in an email it would be wise to encrypt the data, otherwise, it is like a cordless phone, anyone who has the knowledge can steal it. I have always been told to never put ANY info in an email that you wouldn't put on a post card. -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
On Sunday 15 May 2005 21:55, Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 20:21, Paul Cartwright wrote:
On Sun May 15 2005 8:06 am, Constant Brouerius van Nidek wrote:
For that matter,could somebody explain me in plain English the use of cryptografic signatures.
you might want to sign up for the pgp-basics list. They are a wonderful group of people that will bend over backwards to help you learn how to sign & encrypt messages.
http://groups.yahoo.com/group/PGP-Basics/
--
Okay Paul, but why should I encrypt.
Would you send *all* your letters as postcards, without envelope, open to read for anyone? If yes, then you do not need encryption, and Big Brother loves you. Or would you use a closed envelope from time to time? If yes, why? There's your answer! Be aware that all emails you send unencrypted are like open postcards, everybody can read them.
On Sunday 15 May 2005 16:28, Sean Rima wrote:
Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 11:24, Randall R Schulz wrote:
Constant,
On Saturday 14 May 2005 21:13, Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 10:01, Randall R Schulz wrote:
..
Does it bomb on this message? (It is also signed).
You're using PGP, Sean Rima is using PKCS7
From John's signed message:
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_wnlhCpoyGQh+lYC"; charset="iso-8859-1"
From one of Sean's messages:
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------1DAA10E22FC6446"
No, it does not bomb out on this message. I do not use PGP or at least I have never worked with encryption. Will have a look if encryption is i use in my Kmail setup.
We're not talking about your use of cryptographically signed email, we're talking about the use made by the sender and the fact that there's some library incompatibility, at least between your version of KMail and a library used when validating PGP signatures.
It can happen when dependencies are not properly recorded. It happens, not often, but we've seen it on occasion.
Yeah I seen this before with some apps, never tried Kmail. The only reason I switched my main PC back to XP is because I need to use a Geovision DVR card which is not supported by linux at all :(
Sean Dear Sean, This message was received and showed that I do not have a key etc. etc. The next message that you produced with regard to this subject to Ken with the text "Maybe you don't have my key, that can...." was again a bomb. Do not know what you did different.
Hello Constant, Sunday, May 15, 2005, 12:34:26 PM, you wrote:
On Sunday 15 May 2005 16:28, Sean Rima wrote:
Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 11:24, Randall R Schulz wrote:
Constant,
On Saturday 14 May 2005 21:13, Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 10:01, Randall R Schulz wrote:
..
>Does it bomb on this message? (It is also signed).
You're using PGP, Sean Rima is using PKCS7
From John's signed message:
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_wnlhCpoyGQh+lYC"; charset="iso-8859-1"
From one of Sean's messages:
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------1DAA10E22FC6446"
No, it does not bomb out on this message. I do not use PGP or at least I have never worked with encryption. Will have a look if encryption is i use in my Kmail setup.
We're not talking about your use of cryptographically signed email, we're talking about the use made by the sender and the fact that there's some library incompatibility, at least between your version of KMail and a library used when validating PGP signatures.
It can happen when dependencies are not properly recorded. It happens, not often, but we've seen it on occasion.
Yeah I seen this before with some apps, never tried Kmail. The only reason I switched my main PC back to XP is because I need to use a Geovision DVR card which is not supported by linux at all :(
Sean Dear Sean, This message was received and showed that I do not have a key etc. etc. The next message that you produced with regard to this subject to Ken with the text "Maybe you don't have my key, that can...." was again a bomb. Do not know what you did different.
Now you are getting me to worry. All I can think is maybe it has something to do with Smime. How does this go without smime Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped
On Sun, 2005-05-15 at 12:41 +0100, Sean Rima wrote:
Hello Constant,
Sunday, May 15, 2005, 12:34:26 PM, you wrote:
Dear Sean, This message was received and showed that I do not have a key etc. etc. The next message that you produced with regard to this subject to Ken with the text "Maybe you don't have my key, that can...." was again a bomb. Do not know what you did different.
Now you are getting me to worry. All I can think is maybe it has something to do with Smime. How does this go without smime
Sean
-- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped This one showed an invalid signature.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Ken, Sunday, May 15, 2005, 12:53:48 PM, you wrote:
On Sun, 2005-05-15 at 12:41 +0100, Sean Rima wrote:
Hello Constant,
Sunday, May 15, 2005, 12:34:26 PM, you wrote:
Dear Sean, This message was received and showed that I do not have a key etc. etc. The next message that you produced with regard to this subject to Ken with the text "Maybe you don't have my key, that can...." was again a bomb. Do not know what you did different.
Now you are getting me to worry. All I can think is maybe it has something to do with Smime. How does this go without smime
Sean
-- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped This one showed an invalid signature.
Strange I have not altered anything Sean - -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFCh0CuRK72FvXlhZsRAtE1AJ0dTM7GkKjs8GXsQTrkdTkepkGBkACfSq9f VjbaDddP1KVzMphGPehVBiw= =UgC2 -----END PGP SIGNATURE-----
The Sunday 2005-05-15 at 13:29 +0100, Sean Rima wrote:
This one showed an invalid signature.
Strange I have not altered anything
Yes, you did. Or your MUA did. You usually use a detached pgp/gpg signature: [ Part 2, Application/PGP-SIGNATURE 190bytes. ] This last one you used an embedded pgp signature (no email parts). Both were made with "The Bat! (v3.5) Professional". Sometimes, you use pkcs7 instead, or added: [ Part 1.2, Application/PGP-SIGNATURE 190bytes. ] [ Part 2, "S/MIME Cryptographic Signature" Application/PKCS7-SIGNATURE 2.6KB. ] Also with the same program. -- Cheers, Carlos Robinson
Hello Carlos, Sunday, May 15, 2005, 3:16:01 PM, you wrote:
The Sunday 2005-05-15 at 13:29 +0100, Sean Rima wrote:
This one showed an invalid signature.
Strange I have not altered anything
Yes, you did. Or your MUA did.
You usually use a detached pgp/gpg signature:
[ Part 2, Application/PGP-SIGNATURE 190bytes. ]
This last one you used an embedded pgp signature (no email parts). Both were made with "The Bat! (v3.5) Professional". Sometimes, you use pkcs7 instead, or added:
[ Part 1.2, Application/PGP-SIGNATURE 190bytes. ] [ Part 2, "S/MIME Cryptographic Signature" Application/PKCS7-SIGNATURE 2.6KB. ]
Also with the same program.
ATM, I am OS chalenged until I get 9.3 for the laptop. Sometimes I forget to undo the SMIME signature but changed the template for the list now Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped
On Sunday 15 May 2005 18:41, Sean Rima wrote:
Hello Constant,
Sunday, May 15, 2005, 12:34:26 PM, you wrote:
On Sunday 15 May 2005 16:28, Sean Rima wrote:
Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 11:24, Randall R Schulz wrote:
Constant,
On Saturday 14 May 2005 21:13, Constant Brouerius van Nidek wrote:
On Sunday 15 May 2005 10:01, Randall R Schulz wrote: >.. > >>Does it bomb on this message? (It is also signed). > >You're using PGP, Sean Rima is using PKCS7 > >From John's signed message: > >Content-Type: multipart/signed; > protocol="application/pgp-signature"; > micalg=pgp-sha1; > boundary="Boundary-02=_wnlhCpoyGQh+lYC"; > charset="iso-8859-1" > > >From one of Sean's messages: > >Content-Type: multipart/signed; > protocol="application/pkcs7-signature"; > micalg=sha1; > boundary="----------1DAA10E22FC6446"
No, it does not bomb out on this message. I do not use PGP or at least I have never worked with encryption. Will have a look if encryption is i use in my Kmail setup.
We're not talking about your use of cryptographically signed email, we're talking about the use made by the sender and the fact that there's some library incompatibility, at least between your version of KMail and a library used when validating PGP signatures.
It can happen when dependencies are not properly recorded. It happens, not often, but we've seen it on occasion.
Yeah I seen this before with some apps, never tried Kmail. The only reason I switched my main PC back to XP is because I need to use a Geovision DVR card which is not supported by linux at all :(
Sean
Dear Sean, This message was received and showed that I do not have a key etc. etc. The next message that you produced with regard to this subject to Ken with the text "Maybe you don't have my key, that can...." was again a bomb. Do not know what you did different.
Now you are getting me to worry. All I can think is maybe it has something to do with Smime. How does this go without smime
Sean This message was received and read without problems. If that was without SMime, we just have to find out why it reacts with my Kmail ;-).
Hello Constant, Sunday, May 15, 2005, 1:09:12 PM, you wrote:
Now you are getting me to worry. All I can think is maybe it has something to do with Smime. How does this go without smime
Sean This message was received and read without problems. If that was without SMime, we just have to find out why it reacts with my Kmail ;-).
At least we know the proble, maybe someone can change something to stop the bug. Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped
On Sunday 15 May 2005 19:19, Sean Rima wrote:
Hello Constant,
Sunday, May 15, 2005, 1:09:12 PM, you wrote:
Now you are getting me to worry. All I can think is maybe it has something to do with Smime. How does this go without smime
Sean
This message was received and read without problems. If that was without SMime, we just have to find out why it reacts with my Kmail ;-).
At least we know the proble, maybe someone can change something to stop the bug.
Dear Sean, Completely agree. Hope that somebody can find and stop the bug. I do want to be able to read your email's without to much brain gymnastics ;-) Constant
The Sunday 2005-05-15 at 19:51 +0700, Constant Brouerius van Nidek wrote:
At least we know the proble, maybe someone can change something to stop the bug.
Dear Sean, Completely agree. Hope that somebody can find and stop the bug. I do want to be able to read your email's without to much brain gymnastics ;-)
The bug was found and solved "years" ago. It is a problem with kmail (yours). You have got to update, as Randall said. -- Cheers, Carlos Robinson
On Sunday 15 May 2005 21:18, Carlos E. R. wrote:
The Sunday 2005-05-15 at 19:51 +0700, Constant Brouerius van Nidek wrote:
At least we know the proble, maybe someone can change something to stop the bug.
Dear Sean, Completely agree. Hope that somebody can find and stop the bug. I do want to be able to read your email's without to much brain gymnastics ;-)
The bug was found and solved "years" ago. It is a problem with kmail (yours). You have got to update, as Randall said.
-- Cheers, Thanks Carlos, Think that years ago is an overdoing it. This 9.0 box is patched up to date. I know, Kmail 1.5.4 is not the latest but I will look into an update ;-).
The Sunday 2005-05-15 at 21:52 +0700, Constant Brouerius van Nidek wrote:
Dear Sean, Completely agree. Hope that somebody can find and stop the bug. I do want to be able to read your email's without to much brain gymnastics ;-)
The bug was found and solved "years" ago. It is a problem with kmail (yours). You have got to update, as Randall said.
Thanks Carlos, Think that years ago is an overdoing it.
Yes, I know, that's what I quoted "years". But I'm sure it was more than twelve months ago, anyway. :-)
This 9.0 box is patched up to date.
Security updates, sure. But not the rest, unless you do it yourself. That's why you have that problem with kmail, that was already solved.
I know, Kmail 1.5.4 is not the latest but I will look into an update ;-).
Right :-) -- Cheers, Carlos Robinson
The Sunday 2005-05-15 at 18:34 +0700, Constant Brouerius van Nidek wrote:
Dear Sean, This message was received and showed that I do not have a key etc. etc. The next message that you produced with regard to this subject to Ken with the text "Maybe you don't have my key, that can...." was again a bomb. Do not know what you did different.
The second one had both a PGP signature and a pkcs7 sig. The first one ony had a pgp signature. I don't know why he uses both types of signatures simultaneously, though it can have it uses (authenticating one with the other, for instance). [ Part 1.2, Application/PGP-SIGNATURE 190bytes. ] [ Part 2, "S/MIME Cryptographic Signature" Application/PKCS7-SIGNATURE 2.6KB. ] As Randall pointed out, it is kmail handling of PKCS7 signatures that is at fault (in suse 9.0). Move those emails to a different folder, and see them with mozilla for example; it can also verify those kinds of signatures. -- Cheers, Carlos Robinson
Hello Carlos, Sunday, May 15, 2005, 2:57:12 PM, you wrote:
The Sunday 2005-05-15 at 18:34 +0700, Constant Brouerius van Nidek wrote:
Dear Sean, This message was received and showed that I do not have a key etc. etc. The next message that you produced with regard to this subject to Ken with the text "Maybe you don't have my key, that can...." was again a bomb. Do not know what you did different.
The second one had both a PGP signature and a pkcs7 sig. The first one ony had a pgp signature. I don't know why he uses both types of signatures simultaneously, though it can have it uses (authenticating one with the other, for instance).
[ Part 1.2, Application/PGP-SIGNATURE 190bytes. ] [ Part 2, "S/MIME Cryptographic Signature" Application/PKCS7-SIGNATURE 2.6KB. ]
As Randall pointed out, it is kmail handling of PKCS7 signatures that is at fault (in suse 9.0). Move those emails to a different folder, and see them with mozilla for example; it can also verify those kinds of signatures.
My standard sig is SMime, but I do also use gpg. I must set this client to use only gpg for this list, until I convert the laptop to 9.3 :) Sean -- ICQ: 679813 YAHOO: thecivvie Jabber: thecivvie@jabber.org AIM: tcobone Vodafone +353879120530 Winamp is stopped
The Sunday 2005-05-15 at 15:06 +0100, Sean Rima wrote:
My standard sig is SMime, but I do also use gpg. I must set this client to use only gpg for this list, until I convert the laptop to 9.3 :)
I only use pkcs7 for oficial things: it identifies me with my national ID number. -- Cheers, Carlos Robinson
participants (9)
-
Carlos E. R. -
Constant Brouerius van Nidek -
John Andersen -
Ken Schneider -
Matt T. -
Paul Cartwright -
Randall R Schulz -
Sean Rima -
Sid Boyce