Francisco José Nina Rente | 7 Dec 16:21 2005

Re: [WEB REQ] don\'t compile - silc-server-1.0.1.tar.bz2

Works fine :) Tks!

i will do gentoo ebuild with your patch, there is any problem with that?

Cheers,
FRente

On Nov 29, 2005, at 7:01 AM, Patrik Weiskircher wrote:

>>
>> Can you try applying the attached patch?
>> cd lib/silccrypt/
>> patch -p1 < silccrypt_sha256_compilefix.patch
>>
>
> Its patch -p0 < silccrypt_sha256_compilefix.patch
>
> Way too early to fix any bugs ;)
>
> Patrik
>

  - ----------------------------------------------------- -
                       Francisco José Nina Rente
                               rAsTeJaNtE

                         - frente@...
                         - www.cognitrap.org

       pgp.dei.uc.pt:11371/pks/lookup?search=frente&op=index
(Continue reading)

M. Hornung | 12 Dec 20:21 2005
Picon

nick reserved/remembered by server...timeout?

Please bear with me, as I'm a newbie to the SILC toolkit.  I'm working on 
a bot for SILC, using the template "mybot" that came with the toolkit. 
As I'm testing, I kill and restart the bot often.  Whenever I restart the 
bot, the server seems to "remember" a recent connection and the bot nick 
gets set but you can't msg the bot itself without specifying the hostname 
too.  (I presume since the server remembers a recent client connection 
with the same nick)

Example.

Start bot named "foo"
/msg foo something
foobot does something in return

<kill foobot>

Start bot named "foo"
Nick is "foo" but '/msg foo something' returns:
 	*** foobot: There is no such client
But if I do:
 	/msg foo <at> hostname something
then it works as expected.

So, as the server operator (with no router connections), is there a way I 
can do something so the "foo" namespace clears before I restart the bot?

I apologize for probably using the wrong terminology, but as I said, I'm a 
newb.  It's ok if you want to respond to me with RTFM, but that wouldn't 
be as helpful.  Cheers, and thanks!

(Continue reading)

Toni Willberg | 12 Dec 20:29 2005
Picon
Picon

Re: nick reserved/remembered by server...timeout?

M. Hornung wrote:
> Please bear with me, as I'm a newbie to the SILC toolkit.  I'm working 
> on a bot for SILC, using the template "mybot" that came with the 
> toolkit. As I'm testing, I kill and restart the bot often.  Whenever I 
> restart the bot, the server seems to "remember" a recent connection and 
> the bot nick gets set but you can't msg the bot itself without 
> specifying the hostname too.  (I presume since the server remembers a 
> recent client connection with the same nick)
> 
> Example.
> 
> Start bot named "foo"
> /msg foo something
> foobot does something in return
> 
> <kill foobot>
> 
> Start bot named "foo"
> Nick is "foo" but '/msg foo something' returns:
>     *** foobot: There is no such client
> But if I do:
>     /msg foo <at> hostname something
> then it works as expected.
> 
> So, as the server operator (with no router connections), is there a way 
> I can do something so the "foo" namespace clears before I restart the bot?
> 
> I apologize for probably using the wrong terminology, but as I said, I'm 
> a newb.  It's ok if you want to respond to me with RTFM, but that 
> wouldn't be as helpful.  Cheers, and thanks!
(Continue reading)

Patrik Weiskircher | 12 Dec 20:34 2005
Picon

Re: nick reserved/remembered by server...timeout?


On Dec 12, 2005, at 8:21 PM, M. Hornung wrote:

> Please bear with me, as I'm a newbie to the SILC toolkit.  I'm  
> working on a bot for SILC, using the template "mybot" that came  
> with the toolkit. As I'm testing, I kill and restart the bot  
> often.  Whenever I restart the bot, the server seems to "remember"  
> a recent connection and the bot nick gets set but you can't msg the  
> bot itself without specifying the hostname too.  (I presume since  
> the server remembers a recent client connection with the same nick)

Its not like that.  The problem is that you connect too fast for your  
client.
As nicknames are *not* unique in SILC, if your client still knows  
about the last incarnation of your bot, and you connect quickly  
enough with a new instance, the new instance will get the hostname  
appended.
Only way to fix this is to not start another instance of your bot  
until the first one is truly unregistered.

Patrik

_______________________________________________________________
Info:    https://lists.silcnet.org/mailman/listinfo/silc-users
Archive: https://lists.silcnet.org/pipermail/silc-users
FAQ:     http://silcnet.org/support/faq/

M. Hornung | 12 Dec 20:51 2005
Picon

Re: nick reserved/remembered by server...timeout?

Hi Toni.  Thanks for your input.  In my experience you can't use the KILL 
command unless you have silcoper (router operator) privileges, which you 
can only get as a router operator.  Since my server is standalone, I can 
only get server operator privs, which don't let me use the KILL command.  
Or maybe there's something else I can put in my silcd.conf to allow me 
router operator privs?

By the way, this is server version 1.0.

I am probably not catching SIGINT as I should in order to shut down 
properly.  I will investigate that.

-Mike

On Mon, 12 Dec 2005 at 21:29, fnord, Toni Willberg wrote:

|M. Hornung wrote:
|> Please bear with me, as I'm a newbie to the SILC toolkit.  I'm working on a
|> bot for SILC, using the template "mybot" that came with the toolkit. As I'm
|> testing, I kill and restart the bot often.  Whenever I restart the bot, the
|> server seems to "remember" a recent connection and the bot nick gets set but
|> you can't msg the bot itself without specifying the hostname too.  (I presume
|> since the server remembers a recent client connection with the same nick)
|> 
|> Example.
|> 
|> Start bot named "foo"
|> /msg foo something
|> foobot does something in return
|> 
(Continue reading)

Toni Willberg | 12 Dec 21:35 2005
Picon
Picon

Re: nick reserved/remembered by server...timeout?

M. Hornung wrote:
> Hi Toni.  Thanks for your input.  In my experience you can't use the KILL 
> command unless you have silcoper (router operator) privileges, which you 
> can only get as a router operator.  Since my server is standalone, I can 
> only get server operator privs, which don't let me use the KILL command.  
> Or maybe there's something else I can put in my silcd.conf to allow me 
> router operator privs?
> 
> By the way, this is server version 1.0.
> 
> I am probably not catching SIGINT as I should in order to shut down 
> properly.  I will investigate that.
> 
> -Mike

Everyone can use KILL to kill oneself. You just need to have the private 
and public keys in your possession. See /help kill in the silc-client.

- Toni

_______________________________________________________________
Info:    https://lists.silcnet.org/mailman/listinfo/silc-users
Archive: https://lists.silcnet.org/pipermail/silc-users
FAQ:     http://silcnet.org/support/faq/

Patrik Weiskircher | 14 Dec 18:43 2005
Picon

SILC Server 1.0.2

SILC Server 1.0.2 Release Notes
================================

The new version of the SILC Server is now available!  The source package
of the software is available from the following sources:

          http://silcnet.org/
          ftp://ftp.silcnet.org/

This version fixes some security bugs and some other minor bugs.
Upgrading, as always, recommended.

Summary of Changes
------------------

   o Fixed compile error on non-i386 systems for sha256 algorithm.
   o Added SILC_ATTRIBUTE_USER_ICON.

The full list of changes is available on the website and in CHANGES file
in the source package.

Installation
------------

The source package is compiled and installed as instructed in the  
INSTALL
file found from the package.  Quick installation:

    ./configure
    make
(Continue reading)

Pekka Riikonen | 19 Dec 14:13 2005
Picon
Picon

SILC Toolkit 1.0.2


The new version of the SILC Toolkit is now available!  The source package
of the software is available from the following sources:

         http://silcnet.org/
         ftp://ftp.silcnet.org/

A quick bugfix release.  This fixes compilation problem on non-i386 
platforms.

Summary of Changes
------------------

o Fixed compilation problem on non-i386 platforms.

o Added SILC_ATTRIBUTE_USER_ICON allow user/buddy icon sending/receiving
   in WHOIS attributes.

The full list of changes is available on the website and in CHANGES file
in the source package.

Installation
------------

The source package is compiled and installed as instructed in the INSTALL
file found from the package.  Refer also to the building instructions in
the Toolkit Reference Manual:

   http://silcnet.org/docs/toolkit/building.html

(Continue reading)


Gmane