View previous topic :: View next topic |
Author |
Message |
TheGuv
Joined: 29 Oct 2010 Posts: 11
|
Posted: Fri Oct 29, 2010 8:42 Post subject: m23.sourceforg.net public key |
|
|
Hi all,
I'm trying out m23 internally - from the m23.sf.net debian packages as installation is on an existing shared server.
Trying to assimilate another debian server, I'm having some problems with the running of the 'work.php' script. Particularly, apt-get is giving an error as the public key C6F0913D3305E63A isn't available. The one on the m23 home page seems to be different:
pub 1024D/68943878 2003-11-27
uid Hauke Goos-Habermann (m23.sf.net) <hhabermann>
sub 1024g/DC9D42CB 2003-11-27
Please could somebody advise where to fetch the real pubkey from - it doesn't appear to be available on any public keyservers.
'guv |
|
Back to top |
|
|
Hauke
Joined: 02 Mar 2003 Posts: 1072
|
Posted: Fri Oct 29, 2010 10:59 Post subject: |
|
|
Hi,
I don't know a GPG key with the ID C6F0913D3305E63A, it is not part of m23.
Can you post the complete APT error?
The GPG key on the m23 page is for writing me encrypted eMails. _________________ Hauke Goos-Habermann
- project leader m23 (http://m23.sf.net) -
Jabber: dodgerm23@jabber.org
Schulung, Entwicklung und Support zu m23 und anderen OpenSource-Produkten: www.goos-habermann.de
Auch DU kannst etwas gegen Softwarepatente tun! www.patentfrei.de |
|
Back to top |
|
|
TheGuv
Joined: 29 Oct 2010 Posts: 11
|
Posted: Fri Oct 29, 2010 13:55 Post subject: |
|
|
Hi,
Doing an apt-get update produces the following:
W: GPG error: http://m23.sourceforge.net ./ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C6F0913D3305E63A
This is produced by the line added by m23 to /etc/apt/sources.list:
deb http://m23.sourceforge.net/m23debs/ ./
I've isolated that line to verify it is the cause of the error. Which it is.
I simply imported the gpg key from the SF page in case it was the one needed. Which as you already said isn't |
|
Back to top |
|
|
Hauke
Joined: 02 Mar 2003 Posts: 1072
|
Posted: Fri Oct 29, 2010 14:55 Post subject: |
|
|
Hi,
ok, now I found the correct key ID. This is 0x3305E63A and therefore the same key as you mentioned. I don't know why gpg uses a different ID format than apt-get, but it must make sense.
This key can be imported (as root) with:
Code: | wget -T1 -t1 -q http://m23.sourceforge.net/m23-Sign-Key.asc -O - | apt-key add - |
I will add this to the installation guide.
The import of the key is done in the postinst script of the m23 package. So it should be visible only, one time. If you ignore the apt-get warning and install the m23 package all should be fine. _________________ Hauke Goos-Habermann
- project leader m23 (http://m23.sf.net) -
Jabber: dodgerm23@jabber.org
Schulung, Entwicklung und Support zu m23 und anderen OpenSource-Produkten: www.goos-habermann.de
Auch DU kannst etwas gegen Softwarepatente tun! www.patentfrei.de |
|
Back to top |
|
|
TheGuv
Joined: 29 Oct 2010 Posts: 11
|
Posted: Mon Nov 01, 2010 12:16 Post subject: |
|
|
Hauke wrote: |
I don't know why gpg uses a different ID format than apt-get, but it must make sense.
|
If it used the same format, then life would be too easy!
Hauke wrote: |
This key can be imported (as root) with:
|
Thanks, that was exactly what I was looking for, but...
Hauke wrote: |
The import of the key is done in the postinst script of the m23 package. So it should be visible only, one time. If you ignore the apt-get warning and install the m23 package all should be fine. |
Sure, but it was on a _client_ that I was having to import the key for. When I assimilated the client, the m23.sf line was added to the clients /etc/apt/sources.list. It was _this_ that was causing an error during running of the work.php script due to the source being untrusted without the key.
Many thanks for the clue |
|
Back to top |
|
|
Hauke
Joined: 02 Mar 2003 Posts: 1072
|
Posted: Tue Nov 02, 2010 8:23 Post subject: |
|
|
Ok, now I understand, I thought you are talking about the m23 server
Edit the file /m23/inc/assimilate.php on the m23 server, to let the m23 clients import the m23 sign key before the installation of the m23 client packages.
Search for the function "ASSI_prepareClient" and place the following line
Code: | wget -T1 -t1 -q http://m23.sourceforge.net/m23-Sign-Key.asc -O - | apt-key add - |
in a new line before the line "apt-get update".
Then all new assimilated clients should get the key.
Please try and report, if all works well. _________________ Hauke Goos-Habermann
- project leader m23 (http://m23.sf.net) -
Jabber: dodgerm23@jabber.org
Schulung, Entwicklung und Support zu m23 und anderen OpenSource-Produkten: www.goos-habermann.de
Auch DU kannst etwas gegen Softwarepatente tun! www.patentfrei.de |
|
Back to top |
|
|
TheGuv
Joined: 29 Oct 2010 Posts: 11
|
Posted: Tue Nov 09, 2010 9:09 Post subject: |
|
|
Yes, that works nicely - thanks for the clue! I'm finding my way around m23 quite well doing this
Would you like me to report any other issue I find along the way or would that be too much noise here? |
|
Back to top |
|
|
Hauke
Joined: 02 Mar 2003 Posts: 1072
|
Posted: Tue Nov 09, 2010 10:31 Post subject: |
|
|
Hi,
please report all things you find. Only this way m23 can become better and better _________________ Hauke Goos-Habermann
- project leader m23 (http://m23.sf.net) -
Jabber: dodgerm23@jabber.org
Schulung, Entwicklung und Support zu m23 und anderen OpenSource-Produkten: www.goos-habermann.de
Auch DU kannst etwas gegen Softwarepatente tun! www.patentfrei.de |
|
Back to top |
|
|
|