help-gnunet
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-gnunet] gnunetd segmentation fault 0.5.5 + backtrace


From: Christian Grothoff
Subject: Re: [Help-gnunet] gnunetd segmentation fault 0.5.5 + backtrace
Date: Sun, 24 Aug 2003 17:08:54 -0500
User-agent: KMail/1.4.3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 24 August 2003 10:15 am, address@hidden wrote:
> Thanks guys, it works now (no segfault anymore)!

Well, thanks for reporting. That'd be the first patch to be scheduled for 
0.5.5a :-)

> I am getting following warnings, are these normal :
>
> Aug 24 18:13:08 WARNING: verifySKS: host
> 2F7A9C9A4D62E128EDD5D444346F129F9916CAC8 for sessionkey exchange not known
> Aug 24 18:13:08 WARNING: session key from
> 2F7A9C9A4D62E128EDD5D444346F129F9916CAC8 failed verification, ignored!
> Aug 24 18:13:29 WARNING: verifySKS: host
> 0949054F82BC25E2D9F696C771F3360D6588C2B1 for sessionkey exchange not known
> Aug 24 18:13:29 WARNING: session key from
> 0949054F82BC25E2D9F696C771F3360D6588C2B1 failed verification, ignored!
> Aug 24 18:13:42 WARNING: CRC failed from
> A1FB8A180FBBC6C9BE11415DC7D3B1FDC0F9CE54, msg ignored (wrong skey?)
> Aug 24 18:13:42 WARNING: CRC failed from
> 4A0B917BB74182ABE30A591E791C8A0FAEAD27C8, msg ignored (wrong skey?)

The "wrong skey" can happen in normal operation but should be rare. The "host 
XXX for sessionkey exchange not known" is also generally harmless but should 
not happen. The "failed verification" should NOT happen in practice and is an 
indicator that the RSA-signing of either your peer or the other peer has some 
problem. If your peer actually connects to other peers, it is probably not 
you (see output ofgnunet-stats | grep connected).

To summarize, the warnings are definitely harmless if you can connect to other 
peers (according to gnunet-stats).

> Additional question, how to use DYNDNS service. Can I have something like
>
> IP = l33thax0r.linuxbox.org (that would be using dyndns.org name)
>
> in config file?

Absolutely. That should work. Note that whenever your IP changes, GNUnet may 
need a few seconds to notice the change in the DYNDNS entry and even more to 
propagate that information. If your IP changes daily, you may want to reduce 
the HELOEXPIRES value to about 1h.

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE/STd29tNtMeXQLkIRAg7wAKCQnMBn1UpTW/L1z+0jWB31z3r7CwCdEpeH
uVHWjBvWwUgkgw/uPn59btI=
=EevR
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]