silc-devel — Main SILC development mailing list

damn cores...

[damm <da...@bo...>]

nuff said
#0  0x14540c in silc_client_close_connection_real (client=0x1fae80, 
sock=0x0,
    conn=0x0) at client.c:1449
1449    client.c: No such file or directory.
(gdb) bt
#0  0x14540c in silc_client_close_connection_real (client=0x1fae80, 
sock=0x0,
    conn=0x0) at client.c:1449
#1  0x18d660 in silc_file_readfile (filename=0x0, return_len=0x1fae80)
    at silcfileutil.c:150
#2  0x143c14 in silc_client_connect_to_server_start (schedule=0x1fa970,
    type=3505168, fd=2442024, context=0x3) at client.c:510
#3  0x1431e4 in Perl_do_sv_dump ()
#4  0x189558 in silc_calloc (items=2076288, size=1) at silcmemory.c:29

Not properly clearing memory on key generation

[Michael L. <you...@sn...>]

Looking through the silc code, I happened upon this in
irssi/src/silc/core/clientutil.c:
    memset(key, 0, sizeof(key_len));

This seems wrong.  key_len is just an int containing the length of key.
Simple patch:

--- clientutil.c        Thu Apr 11 10:40:26 2002
+++ clientutil.c-       Tue May 28 18:40:09 2002
@@ -223,7 +223,7 @@
   if (ret_pub_key)
     *ret_pub_key = pub_key;

-  memset(key, 0, sizeof(key_len));
+  memset(key, 0, key_len);
   silc_free(key);

   /* Save private key into file */
@@ -239,7 +239,7 @@
   printf("Press <Enter> to continue...\n");
   getchar();

-  memset(key, 0, sizeof(key_len));
+  memset(key, 0, key_len);
   silc_free(key);

   silc_rng_free(rng);

Re: Vhosts... and key negotiation screwed

[damm <da...@bo...>]

Update on this,

Well i Negotiated a key with myself, and when i msg myself now... i get 
nothing

IS that normal? or would that be uncommon?

Also trying to key a different cipher/hmac with private keys working in 
bsd

and unfortunatly it seems that no one can hear me, nor speak to me :(

unfortunates...

i've got this,
+ Private message keys with Damm
+   Client                         Cipher         Key
+   Damm                           aes-256-cbc    *generated*


then i do /msg Damm hi hi hey hey
[msg(damm)] HYI HI HEY HEY
[msg(damm)] HYI HI HEY HEY


and i get nothing back... those are msg to's damm

but nothing back...

Re: Patch to support multiple interfaces...

[Jochen E. <joc...@gm...>]

Hi,

[Pekka Riikonen]
> I don't mean that.  I mean that the fd argument to the function is
> equal of having a
> "here_is_variable_that_i_pass_since_i_may_need_it_later_in_the_callba
> ck_even_though_it_has_no_meaning_to_the_procedure_in_hand" argument in
> the function.  You have the "context" for that. :)
So you suggest introducing a SilcAcceptNewConnectionLookupContextStruct
which has two members, fd and server, right?

Would it be save to silc_free() this struct in the lookup callback?
Should be rather easy then to implement...

regards
-- jochen

-- 
  "I'd rather die before using Micro$oft Word"
    -- Donald E. Knuth 
     (asked whether he'd reinvent TeX in the light of M$ Word)
      
  GnuGP public key for joc...@gm...:
      http://penguin-breeder.org/?page=sigs (0x8AEB7AE3)

Vhosts... and key negotiation screwed

[damm <da...@bo...>]

> Anyone notice a key negotiation problems?
> 
> Here's my problem, shell.bourg.net 207.229.76.2 has a interface 
> 207.229.76.120 for livid.de, i do
> silc -h livid.de
> 
> and then do /key msg ax negotiate
> 
> problem is it starts listening on 207.229.76.2 instead of .120, which in 
> any sense of anyone's mind would scream ALARM why am i connecting to .2 
> instead of .120?
> 
> [ax(tes...@80...)] send this too to them that 
> i did
>         a `/key msg damm negotiate 207.229.76.2 45430' and it resulted in 
> an
>         error sent to stdout. [<timestamp>] [Error] Cant connect to remote
>         host: Invalid argument
> 
> that's what ax got... when he tried to connect.  Aparently it didnt even 
> try and connect.  
> 
> My problem is more that it should have went to .120 instead of .2, but i 
> was wondering the status of the private keys.
> 
> That and i modified the hmac and cipher on channel bsd,
> 
> and no one can listen to anyone, i changed it to,
> 
> hmad-md5-96
> 
> and the cipher to,
> 
> cast-192-cbc
> 
> I cannot figure out how to convert the channel to private keys via /key 
> channel bsd change private
> 
> doesn't do/say anything.
> 
> Any thoughts?
> 
> Thanks
> 

(no subject)

[Frederic A. <Fre...@ex...>]

		___________________________________
L'integrite de ce message n'etant pas assuree sur Internet, EXANE ne peut etre tenue responsable de son contenu.
Si vous n'etes pas destinataire de ce message, merci de le detruire et d'avertir l'expediteur.
		-----------------------------------
The integrity of this message cannot be guaranteed on the Internet. Therefore EXANE cannot be considered responsible for the contents.
If you are not the intended recipient of this message, please delete it and notify the sender.
		___________________________________

Re: Patch to support multiple interfaces...

[Pekka R. <pri...@ik...>]

: [Pekka Riikonen]
: > I guess it's fine, except that I don't much like the interface change
: > for the socket_host_lookup.  The fd doesn't really belong there.
:
: johnny suggested added a local_port member to the SilcSocket struct,
: however this would require rewriting large parts to keep the whole thing
: consistent (the listening sockets are using the port member which is
: here refering to a local port for example). Furthermore, the fd contains
: more data than only the local port, which might be needed to check
: incoming connections in future extensions (i.e. to restrict certain
: connections to certain interfaces).
:
I don't mean that.  I mean that the fd argument to the function is equal
of having a
"here_is_variable_that_i_pass_since_i_may_need_it_later_in_the_callback_even_though_it_has_no_meaning_to_the_procedure_in_hand"
argument in the function.  You have the "context" for that. :)

	Pekka
________________________________________________________________________
 Pekka Riikonen                                 priikone at silcnet.org
 Secure Internet Live Conferencing (SILC)       http://silcnet.org/

Re: Patch to support multiple interfaces...

[Jochen E. <joc...@gm...>]

Hi,

[Pekka Riikonen]
> I guess it's fine, except that I don't much like the interface change
> for the socket_host_lookup.  The fd doesn't really belong there.

johnny suggested added a local_port member to the SilcSocket struct,
however this would require rewriting large parts to keep the whole thing
consistent (the listening sockets are using the port member which is
here refering to a local port for example). Furthermore, the fd contains
more data than only the local port, which might be needed to check
incoming connections in future extensions (i.e. to restrict certain
connections to certain interfaces).

regards
-- jochen

-- 
  "I'd rather die before using Micro$oft Word"
    -- Donald E. Knuth 
     (asked whether he'd reinvent TeX in the light of M$ Word)
      
  GnuGP public key for joc...@gm...:
      http://penguin-breeder.org/?page=sigs (0x8AEB7AE3)

Re: Patch to support multiple interfaces...

[Pekka R. <pri...@ik...>]

: Hi,
:
: here we go... a patch to support multiple interfaces (both IPv4 and
: IPv6). Server & Router work here on my local net... thou I tested not
: extensivly.
:
: Some details about the patch:
:
: * in silcutil I added support for an fd parameter for the host_lookup
:   callback
: * in serverconfig I added the config stuff described in my last mail
: * in server(_backup)
:   - fixed config interface to use the new primary{} and secondary{}
:   - using fd instead of server->sock in accept_new_connection
:   - using passed throu fd in accept_new_connection_lookup
:   - added function silc_server_init_secondary which adds all secondary
:     listeners
:
I guess it's fine, except that I don't much like the interface change for
the socket_host_lookup.  The fd doesn't really belong there.

	Pekka
________________________________________________________________________
 Pekka Riikonen                                 priikone at silcnet.org
 Secure Internet Live Conferencing (SILC)       http://silcnet.org/

Re: Patch to support multiple interfaces...

[Jochen E. <joc...@gm...>]

gna gna gna

The first patch was against a wrong server.c... take this one, should be
better... I'll get me some beer now, man

Re: Patch to support multiple interfaces...

[Jochen E. <joc...@gm...>]

... and where's the patch? :/

regards
-- jochen

-- 
  "I'd rather die before using Micro$oft Word"
    -- Donald E. Knuth 
     (asked whether he'd reinvent TeX in the light of M$ Word)
      
  GnuGP public key for joc...@gm...:
      http://penguin-breeder.org/?page=sigs (0x8AEB7AE3)

Patch to support multiple interfaces...

[Jochen E. <joc...@gm...>]

Hi,

here we go... a patch to support multiple interfaces (both IPv4 and
IPv6). Server & Router work here on my local net... thou I tested not
extensivly.

Some details about the patch:

* in silcutil I added support for an fd parameter for the host_lookup
  callback
* in serverconfig I added the config stuff described in my last mail
* in server(_backup)
  - fixed config interface to use the new primary{} and secondary{}
  - using fd instead of server->sock in accept_new_connection
  - using passed throu fd in accept_new_connection_lookup
  - added function silc_server_init_secondary which adds all secondary
    listeners

and what does it do?

Well you can define several secondary interfaces on which the server
listens. The server ID will be always the one of the primary interface,
the server adds itself only once to the ID cache, all server connections
are established using the primary interface (incoming server connections
can also use the secondary interfaces)

Oh, and why?

Well, if this works, I hope somebody will setup an server which listens
also on an IPv6 interface... :)

regards
-- jochen

ps: comments are welcome!

-- 
  "I'd rather die before using Micro$oft Word"
    -- Donald E. Knuth 
     (asked whether he'd reinvent TeX in the light of M$ Word)
      
  GnuGP public key for joc...@gm...:
      http://penguin-breeder.org/?page=sigs (0x8AEB7AE3)

Irssi SILC Client & Irssi backdoor issues (was silc-0.91 client)

[Pekka R. <pri...@ik...>]

:   Is irssi supposed to be in the source of the silc-client-0.91
: tarball? Isn't this the irc client that was reported as backdoored?
: I was planning to try to compile silc on OpenBSD 3.0 however wanted
: to check first as well as see if there was any ./configure issues.
:

Last week the Irssi IRC client (from http://irssi.org) was reported to
have a backdoor in the configure script which can compromise your system.
This backdoor does not, and have not in any stage affected the Irssi SILC
client, which uses parts from the original Irssi client.  All code that is
taken from the irssi.org CVS are always diffed by myself before they are
merged into silcnet.org CVS repository.  This has been the standard way to
merge code from outside projects, and will remain so in the future as
well.  Furthermore, the irssi.org's CVS was reported to not have been
affected by this backdoor.

All SILC packages, including binary packages were checked and confirmed
when thisbackdoor was found and none of them was found to be affected by
the backdoor.

In short, this backdoor does not affect any of the SILC packages that
have code from irssi.org (silc-client and silc-toolkit).

	Pekka
________________________________________________________________________
 Pekka Riikonen                                 priikone at silcnet.org
 Secure Internet Live Conferencing (SILC)       http://silcnet.org/

silc-0.91 client

[dreamwvr <dre...@dr...>]

Hi,
  Is irssi supposed to be in the source of the silc-client-0.91 
tarball? Isn't this the irc client that was reported as backdoored?
I was planning to try to compile silc on OpenBSD 3.0 however wanted
to check first as well as see if there was any ./configure issues.
( I have checked the source with md5 so it seems it is approved.)
I am assuming that --without=asm is required in configure. 
Appreciate any feedback. Is there a general question list?

TIA
 
Best Regards,
dre...@dr...

SILC Toolkit 0.9.1

[Pekka R. <pri...@ik...>]

The SILC Toolkit version 0.9.1 is now available!  The software is
available from the following sources:

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

Just a update version to bring the Toolkit up to date with the latest
server changes.  It is recommended that if you were using 0.9 you would
upgrade to this version to better compatibility.  Lots of bugfixes has
also been made to the client library.

Please refer to the ChangeLog on the website, or the CHANGES file in the
package for complete list of changes.

	Pekka
________________________________________________________________________
 Pekka Riikonen                                 priikone at silcnet.org
 Secure Internet Live Conferencing (SILC)       http://silcnet.org/

config file format patches for silcd

[Jochen E. <joc...@gm...>]

Hi,

I've modified the silcd config file format a little removing the ip and
port option from the ServerInfo block and adding two subblocks:

primary {
  ip = "ip";
  port = "port";
}

and

secondary {
  ip = "ip";
  port = "port";
}

where you can specify zero or one primary block and as many secondary as
you want. These patches ignore all secondary blocks but the primary
block replaces the functionality of the old ip and port options.

Planning to add support for multiple interfaces... the idea is to have
one primary interface which is used for generating the server id and
connecting to the router and optionally severall secondary interfaces to
listen on.

regards
-- jochen

-- 
  "I'd rather die before using Micro$oft Word"
    -- Donald E. Knuth 
     (asked whether he'd reinvent TeX in the light of M$ Word)
      
  GnuGP public key for joc...@gm...:
      http://penguin-breeder.org/?page=sigs (0x8AEB7AE3)

Possible memory leaks in silcd/serverconfig.c

[Jochen E. <joc...@gm...>]

Hi,

I'm just browsing serverconfig.c a little and wondered why in
silc_server_config_destroy() the fields
 logging_info
 logging_warnings
 logging_errors
 logging_fatals
 server_info
are not freed?

regards
-- jochen

-- 
  "I'd rather die before using Micro$oft Word"
    -- Donald E. Knuth 
     (asked whether he'd reinvent TeX in the light of M$ Word)
      
  GnuGP public key for joc...@gm...:
      http://penguin-breeder.org/?page=sigs (0x8AEB7AE3)

Re: silc_client_send_channel_message segfault

[Pekka R. <pri...@ik...>]

:
: hi. I was going to say "morning" on a channel, but silc didn't
: like it.
:
: RH Linux 2.4.x, glibc-2.2.4-24, gcc-3.1, silc-0.9.1.
:
We alredy debugged once this with you, and answer is exactly the same
thing as the last time.  It is fixed in CVS, just wait for next version.

	Pekka
________________________________________________________________________
 Pekka Riikonen                                 priikone at silcnet.org
 Secure Internet Live Conferencing (SILC)       http://silcnet.org/

SILC: tilde expansion broken in path variables

[<si...@fj...>]

I just upgraded from silc 0.7.9 and hit an immediate problem:
my log was getting sent to a garbage directory under my home directory
instead of ~/log/silc/$tag/$0.log like my autolog_path specifies.

The bug is in convert_home() - the memory address of the get_home_dir
function is being passed into g_strconcat instead of actually calling
get_home_dir and building the string on the result:

--- silc-client-0.9.1/irssi/src/core/misc.c-	Fri Apr  5 08:54:43 2002
+++ silc-client-0.9.1/irssi/src/core/misc.c	Sun May 26 04:49:09 2002
@@ -466,7 +466,7 @@
 char *convert_home(const char *path)
 {
 	return *path == '~' && (*(path+1) == '/' || *(path+1) == '\0') ?
-		g_strconcat((char *)get_home_dir, path+1, NULL) :
+		g_strconcat(get_home_dir(), path+1, NULL) :
 		g_strdup(path);
 }
 

silc_client_send_channel_message segfault

[Sami F. <sa...@ik...>]

hi. I was going to say "morning" on a channel, but silc didn't
like it.

RH Linux 2.4.x, glibc-2.2.4-24, gcc-3.1, silc-0.9.1.

#0  0x401aa4bc in memcpy () at memcpy:-1

0x401aa4bc <memcpy+108>:        repz movsb %ds:(%esi),%es:(%edi)
(gdb) print $esi
$1 =3D 0

#1  0x082654fa in ?? ()
#2  0x081a35d3 in silc_buffer_format (dst=3D0xbfffda70) at silcbuffmt.c:4=
6
#3  0x081716c9 in silc_packet_assemble (packet=3D0x0, rng=3D0x81fdcd8, ci=
pher=3D0x0,=20
    hmac=3D0x82658e8, sock=3D0x825a620,=20
    data=3D0x827c600 ".=E3=AD\200=E2\216\001=C5=D9G=E9=C3=B6=B8BL\002C\02=
6\214\202~TZ\200\222\aa=A3=CA\0365L^=F4\230=D1\020R\017B=E1\021=C5 &\006=F6=
", data_len=3D136729850, assembled_packet=3D0xbfffda70)
    at silcpacket.c:167
#4  0x08161d48 in silc_client_send_channel_message (client=3D0x81fbfa0,=20
    conn=3D0x825a1e0, channel=3D0x8266770, key=3D0x81fdcd8, flags=3D0,=20
    data=3D0x827c600 ".=E3=AD\200=E2\216\001=C5=D9G=E9=C3=B6=B8BL\002C\02=
6\214\202~TZ\200\222\aa=A3=CA\0365L^=F4\230=D1\020R\017B=E1\021=C5 &\006=F6=
", data_len=3D48, force_send=3D1) at client_channel.c:151
#5  0x080a065f in send_message (server=3D0x821aa90, target=3D0x827e209 "s=
ilc",=20
    msg=3D0x827e20e "morning", target_type=3D136734576) at silc-servers.c=
:64
#6  0x080c0295 in cmd_msg (data=3D0x0, server=3D0x821aa90, item=3D0x82661=
c0)
    at chat-commands.c:363
#7  0x080bdc23 in signal_emit_real (rec=3D0x81fb480, params=3D0, va=3D0x1=
7,=20
    first_hook=3D0x81fb4a0) at signals.c:242
#8  0x080bdd88 in signal_emit (signal=3D0x81b8e5c "command msg", params=3D=
136295552)
    at signals.c:286
#9  0x0809d761 in event_text (data=3D0x81fb4a0 "", server=3D0x821aa90, it=
em=3D0x82661c0)
    at chat-completion.c:866
#10 0x080bdc23 in signal_emit_real (rec=3D0x8209cb0, params=3D0, va=3D0x1=
7,=20
    first_hook=3D0x8206238) at signals.c:242
#11 0x080bdd88 in signal_emit (signal=3D0x81bb346 "send text", params=3D1=
36354992)
    at signals.c:286
#12 0x080ace25 in event_command (line=3D0x8209cd0 "", server=3D0x821aa90,=
 item=3D0x0)
    at commands.c:928
#13 0x080bdc23 in signal_emit_real (rec=3D0x81f3a90, params=3D0, va=3D0x1=
7,=20
    first_hook=3D0x820de50) at signals.c:242
#14 0x080bdd88 in signal_emit (signal=3D0x81abcf3 "send command", params=3D=
136264336)
    at signals.c:286
#15 0x08072dfd in key_send_line () at gui-readline.c:191
#16 0x080bdc23 in signal_emit_real (rec=3D0x8217cc0, params=3D0, va=3D0x1=
7,=20
    first_hook=3D0x8217ce0) at signals.c:242
#17 0x080bdd88 in signal_emit (signal=3D0x827e2c0 "key send_line", params=
=3D136412352)
    at signals.c:286
#18 0x0809399d in sig_multi (data=3D0x8217c28 "check_replaces;send_line",=
=20
    gui_data=3D0x0) at keyboard.c:638
#19 0x080bdc23 in signal_emit_real (rec=3D0x820ae80, params=3D0, va=3D0x1=
7,=20
    first_hook=3D0x820aea0) at signals.c:242
#20 0x080bdd88 in signal_emit (signal=3D0x8279088 "key multi", params=3D1=
36359552)
    at signals.c:286
#21 0x08093685 in key_emit_signal (keyboard=3D0x82654fa, key=3D0x820aea0)
    at keyboard.c:532
#22 0x08072ca3 in handle_key (key=3D10) at gui-readline.c:168
#23 0x0807320e in sig_input () at gui-readline.c:369
#24 0x080b2566 in irssi_io_invoke (source=3D0x8215fb0, condition=3D0, dat=
a=3D0x8215fc8)
    at misc.c:57
#25 0x400b428e in g_io_unix_dispatch (source_data=3D0x82654fa,=20
    current_time=3D0xbfffe2a8, user_data=3D0x8215fc8) at giounix.c:135
#26 0x400b5a72 in g_main_dispatch (dispatch_time=3D0xbfffe2a8) at gmain.c=
:656
#27 0x400b5e84 in g_main_iterate (block=3D1074563812, dispatch=3D1) at gm=
ain.c:877
#28 0x400b61ce in g_main_iteration (block=3D1) at gmain.c:907
#29 0x08083231 in main (argc=3D1, argv=3D0x0) at silc.c:350
#30 0x4013d647 in __libc_start_main (main=3D0x8083190 <main>, argc=3D1,=20
    ubp_av=3D0xbfffe374, init=3D0x806f3b0 <_init>, fini=3D0x81ab970 <_fin=
i>,=20
    rtld_fini=3D0x4000dcd4 <_dl_fini>, stack_end=3D0xbfffe36c)
    at ../sysdeps/generic/libc-start.c:129



--=20
Safari - sa...@ik... - PGP key 0x427E7914 - http://iki.fi/safari/
"Talk is cheap. Show me the code." - Linus Torvalds

IPV6 Server...

[Scott M L. <da...@bo...>]

I've been graced with a decent IPV6 Tunnel which has some really DECENT 
latency actually, and was wanting to setup a ipv6 server and whatnot.

But here's my problem,

How do you get silc to listen on the ipv6 interface?

let alone... it seems that i have a hard time connecting to the aaaa or the 
address... But i'm positive that it's not listening on the tunnel and want 
to know what i can do, to make it listen.

Thanks

PS, uhm if i get this working i know silc.silcnet.org is ipv6, maybe i can 
setup a pub ipv6 server... if anyone cares.

Damm


---

"If Thyne Eyes Deceivee Thee, Pluck Them Out".

UMode being broken...

[Scott M L. <da...@bo...>]

Well as i'm playing with UMODE i notice that i cant set a umode at all...

Using Client stock .9.1 and Server of .9.1 on silc.silcnet.org

Anyone able to set their Umodes?

Thanks


---

"If Thyne Eyes Deceivee Thee, Pluck Them Out".

SILC Server 0.9.1

[Pekka R. <pri...@ik...>]

The SILC Server version 0.9.1 is now available!  The software is available
from the following sources:

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

A bugfix release that supposedly fixees most of the crashes that people
have experienced since the 0.9 came out.  Lets hope this is a bit more
stable, but if needed I shall release new bugfix versions.  Please test a
lot and report bugs here on the mailing list.  If your server crashes,
getting the backtrace of the crash in the bugreport would be appreciated.

Please refer to the ChangeLog on the website, or the CHANGES file in the
package for complete list of changes.

	Pekka
________________________________________________________________________
 Pekka Riikonen                                 priikone at silcnet.org
 Secure Internet Live Conferencing (SILC)       http://silcnet.org/

File Transfer...

[Scott M L. <da...@bo...>]

Well i tried my first File Transfer tonite, of course i startup silc with 
-h livid.de which has the ip of,

207.229.76.120

Well when they saw the file transfer it was sending it over 207.229.76.2 
(which is my main interface) instead of using the defined virtualhost.

Of course then it failed because the ip's are wrong and couldnt pass the 
key check.  We sent a key for .120 i believe, and it said wowah buddy this 
is on .2

Well anyhow, you know my story now...


---

"If Thyne Eyes Deceivee Thee, Pluck Them Out".

Re: silc license change before v1.0 ?

[Matthew A. <ma...@al...>]

<two cents>

I'm very happy to see this thread in silc-devel, and that there may
a silc license change before v1.0 - I speak as the developer of
milc (http://milc.sourceforge.net), which is at the moment just
a small (barely working) cross platform client using
wxGTK/MSW/MAC libraries (http://www.wxwindows.org) and
silcclient libraries.

I also speak as a long term NetBSD user, a longer term IRC
user, and longer still Altos user - but my ramblings should be
considered from a 'potential developer' perspective.

I'm enjoying a 3 month vacation between changing jobs at
the moment, and decided to release something 'public-domain'
while I had the opportunity to do so, without invoking some
unknown intellectual property law.

(If I develop anything whilst an employee, there is the very
real chance that an employer can claim intellectual property
rights to the application, or at least attempt to do so. Try
telling me that the words I include in a text file will protect
me from being inconvenienced, when I'm wasting my time
in court with my former employeer's liquidator who is
trying to raise as much value from a company that went
belly up. I don't want to make this a possibility.)

I decided to try something with all the sexy buzzwords, like
XML, SSL, IRC, cross-platform, open-source, etc., and
'milc' is the current result. I'm very 'license-aware', and was
concerned to see the GPL on the silc source.

I'm between jobs. I have the very real possibility of
approaching someone to develop a commercial product,
based on milc, or something else based on silc. There is
also the very real possibility that intellectual property will
become an issue, just as above.

Sure, there are plenty of commercial GPL success stories
out there, but, I'm between jobs. You give me the money
to make a commerical GPL success, and then I won't be
between jobs.

When I do start working again, then my employeer will
decide if milc will continue. (if i want to avoid the the
possibility of a courtroom.) reality bites, film at 11, etc.

Without a GPL license, my employeer can do as he
needs, I can do as I need, and we're all happy. (the
employeer could decide to release a GPL branched
version of milc for all I care.)

With a GPL license, silc is telling me, and my employeer
what to do, and we're not at all happy.

A GPL license also means I have to raise the whole
intellectual property issue with an potential employeer,
or at least risk conflict with the 'standard' employeer
contract agreements which usually attempt to establish
some type of 'business confidentiality' clause.

I'd *much* rather silc be GPL free.

What I do with milc when I'm employeed is up in the
air. The reality is, that with a GPL license, I'd probably
stop working on milc, and hope that someone else
decides to try to do something with it.

I'd also probably start working on it again, after getting
my self settled at work, and past the standard probation
periods, but I have no control over how long this might
be. (I'm also not too keen on being labelled the 'GPL
intellectual property guy', because of something the silc
license told me to do.)

</two cents>

Matthew Aldous.