|
Home > Archive > Anonymous Servers > May 2006 > Newbie hint
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Dingo Admin 2006-05-30, 7:12 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
I recently ran across a little problem with JBN, one that I have had
before. For some reason, the SPGP.DLL that JBN uses to read PGP keyrings
was not reading the whole keyring. If I chose Tools|View PGP Keyring, I
would only see about half the keyring in the dialog box. I could view the
whole keyring in PGP.
The solution is to use PGPkeys and export your keyring (make doubly,
absolutely certain that you check the box labeled "Include Private Key"!)
delete all your keys from and close PGP, then reimport them all. You will
then have to go through your list of keys and re-set "implicit trust" for
your own keys.
That's all there is to it.
I hope you never have to use this little fix, but if you do, don't forget
to include your private key information when you export.
Hoping this may help a poor struggling newbie somewhere,
Dingo Admin
dingoadmin@dingoremailer.com
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBRHyr7sP4uvjsmaBlAQGmdwf/R4agSUDzj9ydSOkK5q0mFgTYsGO6Bfp4
9e8F19A/ QijjKHyoY5W2TveSP089p+RgjS2ddoMNbYvxryu5
kmGBTwQxb1WNjXws
ENYEiZhD39jGAtnssmOmnHT7OtELE15oU2y+KnQx
QySKxFfYxnhAC8rd1cwlqj2p
leK9jY89eyizZDc7oZZYOZPm9mKkVleAKxdj3p7V
f3ryn9nKCxG2sQ7jVRwIdrZB
NKQv+HMU0Ty9IV4/ Mtl7W85xEWqwK6lK6vF44SE4fq9qg2KtSBLQG9SL
cy7xuh+i
HuIWu3oPY0Nj0HZBm0R6ymbotdIVJYEUkcq9Zvkm
hZaAUQlcbSWfDA==
=yHv7
-----END PGP SIGNATURE-----
| |
| BiKiKii 2006-05-31, 1:12 am |
| Dingo Admin wrote:
> the SPGP.DLL that JBN uses to read PGP keyrings
> was not reading the whole keyring.
> If I chose Tools|View PGP Keyring,
> I would only see about half the keyring in the dialog box.
> I could view the whole keyring in PGP.
>
What is the version of SPGP.DLL?
Version 2.5.6 is latest?
Same problem as below?
BiKiKii
See: <http://bikikii-remailer.noneto.com/...ls/reports.html>
Name: Keys appear missing from keyring
Version: JBN 2.1.4
Date: 28 Jan 2000
Status: Due to unresolved problems in SPGP.DLL
Report: With some PGP 5/6 setups, some keys may appear to be
missing
from Tools|View PGP Keyring, JBN2 may report keys missing,
or decryption may fail despite the key actually being present.
Comment: If the SPGP DLL has problems reading the keyring,
it will ignore the problematic key.
This problem is more prevalent with some versions of PGP
than others. (PGP 6.0.2ckt often produces this problem.)
Workaround: Try a different version of PGP 5 or 6, or use PGP 2.6.x.
Users may also wish to check the SPGP DLL Homepage for an
updated version of the DLL. JBN 2.1.4 is distributed with
SPGP DLL version 2.3.0.0 (31 Dec 99). This DLL is installed
into the JBN2 program folder (C:\JBN2) or may be relocated to
the Windows\System folder.
| |
| Dingo Admin 2006-05-31, 1:12 am |
| -----BEGIN PGP SIGNED MESSAGE-----
On 31 May 2006, BiKiKii <null@void.invalid> wrote:
>Dingo Admin wrote:
>
>
>What is the version of SPGP.DLL?
It's the version that is distributed with JBN (2.3.0.0 (31 Dec 99)). I have
looked for v. 2.5.6 but haven't been able to find it.
>Version 2.5.6 is latest?
I think so. It looks like development had stopped.
>
>Same problem as below?
Seems like it.
>
>BiKiKii
>
>
>
>See: <http://bikikii-remailer.noneto.com/...ls/reports.html>
>
>Name: Keys appear missing from keyring
>Version: JBN 2.1.4
>Date: 28 Jan 2000
>Status: Due to unresolved problems in SPGP.DLL
>Report: With some PGP 5/6 setups, some keys may appear to be
>missing
> from Tools|View PGP Keyring, JBN2 may report keys missing,
> or decryption may fail despite the key actually being present.
>Comment: If the SPGP DLL has problems reading the keyring,
> it will ignore the problematic key.
> This problem is more prevalent with some versions of PGP
> than others. (PGP 6.0.2ckt often produces this problem.)
>Workaround: Try a different version of PGP 5 or 6, or use PGP 2.6.x.
> Users may also wish to check the SPGP DLL Homepage for an
> updated version of the DLL. JBN 2.1.4 is distributed with
> SPGP DLL version 2.3.0.0 (31 Dec 99). This DLL is installed
> into the JBN2 program folder (C:\JBN2) or may be relocated to
>
> the Windows\System folder.
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBRH0N2cP4uvjsmaBlAQGMOwf/WHAhHSYFJ3PQBLPVZYPq7FrSmi7Gu5tu
VIJfZLhTQEXoa4lkKmIMaKb0xbGEkxqQnQxlkbqV
wm9S2/cbHTx8HpPkp6VAOexD
fXfakOfrmCba2NLGJYI/ Y0gmk7F5McLl4ea5S12yVnHc6I1MCw3mZi1S05sr
rA/z
cPi5x1nJK7Y13Wjbc4e0ea5z2+2Nw2gjn1N5hXR3
s0JHZ9HUUOr6m3J/yT3oyL+2
c0S2iqh3DE4mH4dgd8IXCnH+f6izpyqgP2taUslT
H6xl15iNQApg7ZMlOQBkuvcf
bGxMAAmmmKMVl+VXU9JZXw5xCEk3RT8YxCY/z7VpmwZ3Vsclvp8JFQ==
=0r60
-----END PGP SIGNATURE-----
| |
| BiKiKii Admin 2006-05-31, 1:12 am |
| -----BEGIN PGP SIGNED MESSAGE-----
On 31 May 2006, Dingo Admin wrote:
>On 31 May 2006, BiKiKii <null@void.invalid> wrote:
>
>It's the version that is distributed with JBN (2.3.0.0 (31 Dec 99)). I have
>looked for v. 2.5.6 but haven't been able to find it.
>
Here:
<http://xthost.info/bikikii/software/spgp2560.zip>
-----BEGIN PGP SIGNATURE-----
Version: N/A
iQEVAwUBRH0nGPRwi/QFFzi5AQHdjwf/QHLF246wKlWCAmvrZoX6Y2Cy8PwEunWT
UN+n8uSXphgPxVDZMe5vOmDemX4GnlGRIlKhwkTk
s3XLPpmrKFehCqgpObiP8gAe
JXmpiRa3SkriImeng1hnfkguVlPVDaLiR6iCB2jt
EveVpw1mjskgskYvturTR5Ae
X3/ wWw5Af3rTar4EaAxQb9fHANohMR2ZHgAJPQHbucF
QJms9S7QTig1x93NgpXHt
C51BSu6SjLHX4plel6cVyY7avWSdrjqdywpBW6T+
VBss46UOh7D/uA+s4kxQbOXf
pR+/ YEzIUR8fpReA2PAnvcJgPWykgIwdD2k62SjldB7w
ta+O7xl0vw==
=2nD6
-----END PGP SIGNATURE-----
| |
| [Anonymous] Persona 2006-05-31, 1:12 am |
| -----BEGIN TYPE III ANONYMOUS MESSAGE-----
Message-type: plaintext
In <HJPJUHZQ38867.6525462963@anonymous.poster> Dingo Admin <dingoadmin@dingoremailer.com> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>
>I recently ran across a little problem with JBN, one that I have had
>before. For some reason, the SPGP.DLL that JBN uses to read PGP keyrings
>was not reading the whole keyring. If I chose Tools|View PGP Keyring, I
>would only see about half the keyring in the dialog box. I could view the
>whole keyring in PGP.
>
>The solution is to use PGPkeys and export your keyring (make doubly,
>absolutely certain that you check the box labeled "Include Private Key"!)
>delete all your keys from and close PGP, then reimport them all. You will
>then have to go through your list of keys and re-set "implicit trust" for
>your own keys.
>
>That's all there is to it.
>
>I hope you never have to use this little fix, but if you do, don't forget
>to include your private key information when you export.
>
>Hoping this may help a poor struggling newbie somewhere,
>Dingo Admin
>dingoadmin@dingoremailer.com
>
I have noted that there seems to be a limit to the number of PGP
keys on the ring. If the number of keys exceeds this number
(400?) then simply deleting the expired keys, keys that have
been replaced with more recent ones, and perhaps a few contacts
that you don't expect to hear from would reduce the number of
keys to less than the "limit."
Of course, after doing this, it's necessary to close JBN and
open it again.
I wonder if, when exporting the keys and reimporting them,
you aren't simply eliminating the expired keys and thus
reducing the total number of keys on the ring to < 400?
Persona
-----END TYPE III ANONYMOUS MESSAGE-----
|
|
|
|
|