Nabble - GnuNet

Re: Typo on "papers and related work" webpage

2009-11-19T23:44:11Z

Fixing. Thanks! -Christian

On Thursday 19 November 2009 06:54:50 Sergey Matveev wrote:
> Greetings,
>
> There is "An Analysis of GNUnet and the Implications for Anonymous,
> Censorship-Resistant Networks" link to book in "Paper about GNUnet"
> section. And "PS" (PostScript) format is in the brackets, but it leads
> to PDF document, instead of PS. Just a small typo.
>

--
http://grothoff.org/christian/

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Typo on "papers and related work" webpage

2009-11-18T21:54:50Z

Greetings,

There is "An Analysis of GNUnet and the Implications for Anonymous,
Censorship-Resistant Networks" link to book in "Paper about GNUnet"
section. And "PS" (PostScript) format is in the brackets, but it leads
to PDF document, instead of PS. Just a small typo.

--
Happy hacking, Sergey Matveev () ASCII Ribbon Campaign
FSF Associate member #5968 | FSFE Fellow #1390 /\ Keep it simple!

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Re: Installing

2009-10-01T14:31:59Z

> I think so, does GNUnet work with utorrent?
No.
GNUnet does not anonymize arbitrary TCP streams like Tor but has a
special plugin that allows for anonymous P2P.

Best,

Nils

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Re: Installing

2009-09-30T14:12:38Z

After you have configured GNUnet (the configuration wizard is also
reachable via the start menu), you can start the background process
gnunetd either as a service (if you checked the option "Launch GNUnet on
computer startup" in the wizard), via the "General" tab in the UI, or
manually via command line:

cd c:\gnunet\bin
gnunetd -d -L DEBUG

The parameters "-d -L DEBUG" start GNUnet in debug mode, so can see
what's happening.

Do you use the latest version 0.8.0c?

Nils

> Yes, this did solve the problem, but when I open it it still seems to
> be having problems. What is the first thing that should be run after
> installation?
> Thanks!
> Ethan
>
>
> On Wed, Sep 30, 2009 at 3:39 PM, Nils Durner <ndurner@...
> <mailto:ndurner@...>> wrote:
>
> Hi Ethan,
>
> which version of Windows is this?
> If it is Vista, launch the installer as administrator, install into a
> folder other than c:\program files ("c:\gnunet" for example) and
> report
> if this solves the problem.
>
>
> Thanks,
>
> Nils
>
>

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Re: Installing

2009-09-30T13:39:29Z

Hi Ethan,

which version of Windows is this?
If it is Vista, launch the installer as administrator, install into a
folder other than c:\program files ("c:\gnunet" for example) and report
if this solves the problem.

Thanks,

Nils

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Installing

2009-09-29T15:47:31Z

Hello. I installed the GNU setup wizard, and after it ran I cannot find GNU on my system, it seems to have only installed some parts but not their .exe files.
Thanks!
Ethan

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Re: GNUnet-0.8.0c dies with assertion failures

2009-09-28T10:19:42Z

I don't think my messages are getting through. Evidently Spamhaus took control
of the Internet's mail and is making me pay for something someone else did,
sans proof.

----- The following addresses had permanent fatal errors -----
<grothoff@...>
(reason: 554 5.7.1 Service unavailable; Client host [67.242.55.204] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=67.242.55.204)

----- Transcript of session follows -----
... while talking to mailin.informatik.tu-muenchen.de.:
>>> DATA
<<< 554 5.7.1 Service unavailable; Client host [67.242.55.204] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=67.242.55.204
554 5.0.0 Service unavailable
<<< 554 5.5.1 Error: no valid recipients

Reporting-MTA: dns; atr2.ath.cx
Received-From-MTA: DNS; localhost
Arrival-Date: Mon, 28 Sep 2009 12:46:50 -0400

Final-Recipient: RFC822; grothoff@...
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mailin.informatik.tu-muenchen.de
Diagnostic-Code: SMTP; 554 5.7.1 Service unavailable; Client host [67.242.55.204] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=67.242.55.204
Last-Attempt-Date: Mon, 28 Sep 2009 12:50:08 -0400

Date: Mon, 28 Sep 2009 12:46:49 -0400
From: jayjwa <jayjwa@...>
To: Christian Grothoff <grothoff@...>
Cc: bug-gnunet@...
Subject: Re: [bug-GNUnet] GNUnet-0.8.0c dies with assertion failures

On Thu, 24 Sep 2009, Christian Grothoff wrote:

> On Wednesday 23 September 2009 02:47:29 jayjwa wrote:
>> The gnunet daemon always dies with the following assertion errors:
>>
>> Sep 22 20:23:09 FATAL: Internal error: assertion failed at mysql.c:427.
>> zsh: abort gnunetd -u daemon -d
>>
>> The gnunetd logfiles fill with these messages, but no other info.
>
> Hmm. That should happen if the DB contains an entry that is corrupted in a
> particular way (and the code fails to test for it "nicely"). The following
> patch (also now in SVN HEAD) should fix this:
>
> sh-4.0$ svn diff mysql.c
> Index: mysql.c
> ===================================================================
> --- mysql.c (revision 9006)
> +++ mysql.c (working copy)
> @@ -418,6 +418,11 @@
> contentSize = *(unsigned int *) result[0].buffer;
> if (contentSize < sizeof (GNUNET_DatastoreValue))
> return NULL; /* error */
> + if (contentSize > GNUNET_MAX_BUFFER_SIZE)
> + {
> + GNUNET_GE_BREAK (NULL, 0); /* far too big */
> + return NULL;
> + }
> contentSize -= sizeof (GNUNET_DatastoreValue);
> type = *(unsigned int *) result[1].buffer;
> prio = *(unsigned int *) result[2].buffer;
>
>
> Alternatively you could drop the GNUnet database and recreate (but that's
> obviously not a good solution and would not prevent this from happening
> again). With the above patch, you'll still get a warning printed whenever
> this corrupt DB entry is hit (but no more crashes).

Before getting this reply, I tried the drop database solution and that seems
to have worked. I just deleted it and then recreated it the same again. It was
originally made on an older MySQL back when I had an older version. Perhaps
there's something different about the new version. I'll try the patch as well.

>> Running the test suite also ends similarly:
>>
>> Sep 22 20:20:57 `lt_dlopenext' failed for library
>> `libgnunetmodule_transport' with error: file not found
>> Sep 22 20:20:57 Internal error: assertion failed at handler.c:840.
>> /bin/sh: line 4: 13511 Aborted ${dir}$tst
>> FAIL: identitytest
>> ===================================
>> 1 of 1 tests failed
>> Please report to bug-gnunet@...
>> ===================================
>>
>> Which is odd because that file does exist at
>> /usr/lib/GNUnet/libgnunetmodule_transport.so
>
>
> That's a completely different error. You need to set "GNUNET_PREFIX=/usr"
> before running the testsuite and then this crash should disappear. Without
> this environment variable, the code does not look in "/usr" and fails to find
> the plugin.
>

I thought I set it, but it's quite possible I didn't.

>> Since then, I've updated to the most recent versions of MySQL and
>> libmicrohttp and recompiled GNUnet. The problems still presists. The
>> database server appears fine - I can login as the GNUnet user, work with
>> the gnunet database, etc.
>>
>> As a side note, I tried to sign up for bug tracking to better follow this
>> issue, but there appears to be errors there too. I enter the confirmation
>> URL, click 'update account' after supplying the requested info, and I only
>> get the follow:
>>
>>
>> This account is protected. You are not allowed to access this until the
>> account protection is lifted.
>>
>> Please use the "Back" button in your web browser to return to the previous
>> page. There you can correct whatever problems were identified in this error
>> or select another action. You can also click an option from the menu bar to
>> go directly to a new section.
>
> Strange, I can see your account but it is not marked as "protected". I've
> clicked the button for resetting your password. If that does not help, please
> contact me off-list and maybe we can figure it out.

It seems to be fixed now, thanks.

>> Since I have no other way to send this, I'm using bug-gnunet@....
>
> No problem, thanks for your report! Let me know if the above patch does not
> fix the problem.

Since the database recreation fixed it for the moment, the patch probably
won't get a chance to work, but I'll apply it and see if anything further
happens.

--
===[* Spamhaus: Internet terrorists - Don't support them *]=======
(noun; one who hurts innocents without care to further a cause)
Spammers add to your inbox; Spamhaus makes sure you'll never
get your email, period. Now, which one is worse? See why:
https://atr2.ath.cx/~jayjwa/RBLs-hurt-innocent-people/abusive-abuse-lists.html
=====[ finger://atr2.ath.cx/jayjwa for contacts, PGP, etc. ]=====

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Re: GNUnet-0.8.0c dies with assertion failures

2009-09-28T09:46:49Z

On Thu, 24 Sep 2009, Christian Grothoff wrote:

I thought I set it, but it's quite possible I didn't.

From forum: GnuNet - Bugs

Re: GNUnet-0.8.0c dies with assertion failures

2009-09-24T07:09:24Z

On Wednesday 23 September 2009 02:47:29 jayjwa wrote:
> The gnunet daemon always dies with the following assertion errors:
>
> Sep 22 20:23:09 FATAL: Internal error: assertion failed at mysql.c:427.
> zsh: abort gnunetd -u daemon -d
>
> The gnunetd logfiles fill with these messages, but no other info.

Hmm. That should happen if the DB contains an entry that is corrupted in a
particular way (and the code fails to test for it "nicely"). The following
patch (also now in SVN HEAD) should fix this:

sh-4.0$ svn diff mysql.c
Index: mysql.c
===================================================================
--- mysql.c (revision 9006)
+++ mysql.c (working copy)
@@ -418,6 +418,11 @@
contentSize = *(unsigned int *) result[0].buffer;
if (contentSize < sizeof (GNUNET_DatastoreValue))
return NULL; /* error */
+ if (contentSize > GNUNET_MAX_BUFFER_SIZE)
+ {
+ GNUNET_GE_BREAK (NULL, 0); /* far too big */
+ return NULL;
+ }
contentSize -= sizeof (GNUNET_DatastoreValue);
type = *(unsigned int *) result[1].buffer;
prio = *(unsigned int *) result[2].buffer;

Alternatively you could drop the GNUnet database and recreate (but that's
obviously not a good solution and would not prevent this from happening
again). With the above patch, you'll still get a warning printed whenever
this corrupt DB entry is hit (but no more crashes).

> Running the test suite also ends similarly:
>
> Sep 22 20:20:57 `lt_dlopenext' failed for library
> `libgnunetmodule_transport' with error: file not found
> Sep 22 20:20:57 Internal error: assertion failed at handler.c:840.
> /bin/sh: line 4: 13511 Aborted ${dir}$tst
> FAIL: identitytest
> ===================================
> 1 of 1 tests failed
> Please report to bug-gnunet@...
> ===================================
>
> Which is odd because that file does exist at
> /usr/lib/GNUnet/libgnunetmodule_transport.so

That's a completely different error. You need to set "GNUNET_PREFIX=/usr"
before running the testsuite and then this crash should disappear. Without
this environment variable, the code does not look in "/usr" and fails to find
the plugin.

> Since then, I've updated to the most recent versions of MySQL and
> libmicrohttp and recompiled GNUnet. The problems still presists. The
> database server appears fine - I can login as the GNUnet user, work with
> the gnunet database, etc.
>
> As a side note, I tried to sign up for bug tracking to better follow this
> issue, but there appears to be errors there too. I enter the confirmation
> URL, click 'update account' after supplying the requested info, and I only
> get the follow:
>
>
> This account is protected. You are not allowed to access this until the
> account protection is lifted.
>
> Please use the "Back" button in your web browser to return to the previous
> page. There you can correct whatever problems were identified in this error
> or select another action. You can also click an option from the menu bar to
> go directly to a new section.

Strange, I can see your account but it is not marked as "protected". I've
clicked the button for resetting your password. If that does not help, please
contact me off-list and maybe we can figure it out.

> Since I have no other way to send this, I'm using bug-gnunet@....

No problem, thanks for your report! Let me know if the above patch does not
fix the problem.

Best,

Christian

> Versions:
>
> GNUnet-0.8.0c
> libmicrohttpd-0.4.2 (also tried with previous version)
> mysql-5.1.39 (also tried with mysql-5.1.37)
> libtool-2.2.6
> gcc-4.4.1
> glibc-2.10.1
> linux-2.6.30.5
>
> Any help would be greatly appreciated.
>
>
>
> _______________________________________________
> Bug-GNUnet mailing list
> Bug-GNUnet@...
> http://lists.gnu.org/mailman/listinfo/bug-gnunet
>

--
http://grothoff.org/christian/

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Re: GNUnet-0.8.0c dies with assertion failures

2009-09-24T06:50:53Z

--
http://grothoff.org/christian/

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

GNUnet-0.8.0c dies with assertion failures

2009-09-22T17:47:29Z

The gnunet daemon always dies with the following assertion errors:

Sep 22 20:23:09 FATAL: Internal error: assertion failed at mysql.c:427.
zsh: abort gnunetd -u daemon -d

The gnunetd logfiles fill with these messages, but no other info.

Running the test suite also ends similarly:

Sep 22 20:20:57 `lt_dlopenext' failed for library
`libgnunetmodule_transport' with error: file not found
Sep 22 20:20:57 Internal error: assertion failed at handler.c:840.
/bin/sh: line 4: 13511 Aborted ${dir}$tst
FAIL: identitytest
===================================
1 of 1 tests failed
Please report to bug-gnunet@...
===================================

Which is odd because that file does exist at
/usr/lib/GNUnet/libgnunetmodule_transport.so

Since then, I've updated to the most recent versions of MySQL and libmicrohttp
and recompiled GNUnet. The problems still presists. The database server
appears fine - I can login as the GNUnet user, work with the gnunet database,
etc.

As a side note, I tried to sign up for bug tracking to better follow this
issue, but there appears to be errors there too. I enter the confirmation URL,
click 'update account' after supplying the requested info, and I only get the
follow:

This account is protected. You are not allowed to access this until the
account protection is lifted.

Please use the "Back" button in your web browser to return to the previous
page. There you can correct whatever problems were identified in this error
or select another action. You can also click an option from the menu bar to
go directly to a new section.

Since I have no other way to send this, I'm using bug-gnunet@....

Versions:

GNUnet-0.8.0c
libmicrohttpd-0.4.2 (also tried with previous version)
mysql-5.1.39 (also tried with mysql-5.1.37)
libtool-2.2.6
gcc-4.4.1
glibc-2.10.1
linux-2.6.30.5

Any help would be greatly appreciated.

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Re: Debian Dependency

2009-09-20T12:27:13Z

Hi!

Why do you believe that? We use libgcrypt, not OpenSSL. Note that you can
have CURL installations using either libgcrypt or libssl, but that's an
*indirect* dependency which we don't list anyway (otherwise the list would be
*very* long).

If you would provide a more specific (compiler/linker) error message, I might
be able to say more.

Best,

Christian

On Saturday 19 September 2009 02:31:22 Kris Carlson wrote:
> Hello,
> I'm not sure but I believe libssl-dev is also required to compile gnunet
> for Debian Squeeze.
> ~Kris
>

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Debian Dependency

2009-09-18T17:31:22Z

Hello,
I'm not sure but I believe libssl-dev is also required to compile gnunet for Debian Squeeze.
~Kris

_______________________________________________
Bug-GNUnet mailing list
Bug-GNUnet@...
http://lists.gnu.org/mailman/listinfo/bug-gnunet

From forum: GnuNet - Bugs

Re: New GNUnet publication program

2009-09-15T00:56:05Z

On Monday 14 September 2009 17:38:46 you wrote:

> > This is interesting, in part because I recently did a similar split into
> > two steps for the new 0.9.x FS publishing API. Now, what is not yet
> > possible with that API is the serialization into a specification file for
> > the end-user between the two stages, but that might be a possibility. The
> > main problem I see is that the new API allows for "files" to be published
> > that are not on disk (the caller would just have to specify a function
> > for how to get the data); that kind-of conflicts with the ability to
> > serialize to a human-readable file.
>
> I haven't seen anything about the new API on the web site; do you
> have a draft written yet?

Yes: https://gnunet.org/svn/gnunet/src/include/gnunet_fs_service.h

> The way I handle files that are not on disk is to write them to files
> at the same time the specification file is written. Basicly, if you give
> a specification file name "a/b/c", then the specification is written
> to that file, and any data that isn't already in files is written to files
> named "a/b/0001.dat", "a/b/0002.gnd", and so on. In order to make
> this a bit more convenient to put each specification file in its own
> directory, the directory "a/b" is created if it does not exist. If higher
> level directories (such as the directory "a" in "a/b/c") do not exist,
> that is treated as an error.

Right, one should write them to disk. Now, I'm not sure about why you need to
generate errors (never good) if higher-leveld dirs don't exist; since this
would be all relative to the location of the specification file, we could just
create those dirs.

> The other issue with files is that the current working directory of a
> process which reads a specification file might be different than the
> current working directory of the program that wrote the file. So
> relative file names in a specification file are relative to the directory
> containing the specification file.

I agree, good thing to remember when writing that code...

Best,

Christian
--
http://grothoff.org/christian/

_______________________________________________
GNUnet-developers mailing list
GNUnet-developers@...
http://lists.gnu.org/mailman/listinfo/gnunet-developers

Nabble - GnuNet

Re: Typo on "papers and related work" webpage

Typo on "papers and related work" webpage

Re: Installing

Re: Installing

Re: Installing

Installing

Re: GNUnet-0.8.0c dies with assertion failures

Re: GNUnet-0.8.0c dies with assertion failures

Re: GNUnet-0.8.0c dies with assertion failures

Re: GNUnet-0.8.0c dies with assertion failures

GNUnet-0.8.0c dies with assertion failures

Re: Debian Dependency

Debian Dependency

Re: New GNUnet publication program

Re: New GNUnet publication program

RE: New GNUnet publication program

Re: NAT library (Was: towards gnunet 0.9.x)

NAT library (Was: towards gnunet 0.9.x)

Re: New GNUnet publication program

Looking for PhD students

New GNUnet publication program

Re: number of connected peers 1

number of connected peers 1

Re: How do updates work?

How do updates work?

Re: Specifying file names for uploaded files

Specifying file names for uploaded files

Re: Build issues with 0.9

Build issues with 0.9

Re: Approximate Searches

Re: Approximate Searches

Re: Approximate Searches

Approximate Searches

Re: Economic System

Re: Same Key - different content