Re: signed vs unsigned char issue with silc-server config parser

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-526906207-1232359379=:2425
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE


:=20
: The silc-server config parser has an issue with signed vs unsigned char
: usage in the code. This causes the config parser to break on PowerPC
: and ARM systems.
:=20
: $ ./silcd
: Error while parsing config file: Unknown option.
:   file /home/brad/etc/silcd/silcalgs.conf line 121:  =FF
:=20
: There are only 120 lines in the file.
:=20
Thanks for the patch.  Indeed there's bug with the signed vs. unsigned EOF=
=20
handling in the code.  Actually I was thinking I'm going to change the=20
code support unsigned char instead of signed char.  Next version will=20
include the fix.

=09Pekka
________________________________________________________________________
 Pekka Riikonen                                 priikone at silcnet.org
 Secure Internet Live Conferencing (SILC)       http://silcnet.org/
--0-526906207-1232359379=:2425
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________________________________
Info:    https://lists.silcnet.org/mailman/listinfo/silc-announce
Archive: https://lists.silcnet.org/pipermail/silc-announce
FAQ:     http://silcnet.org/support/faq/
--0-526906207-1232359379=:2425--