Re: TLF logger, countrylist file format?

2022-03-06 Thread Ervin Hegedüs
Hi Gerard,

On Mon, Mar 07, 2022 at 07:09:36AM +, Gerard van Antwerpen wrote:
> Thanks for your time to help.

you're welcome,

> First of all I installed originally using the easy way, using apt install tlf.
> Then, after your reply, used the git clone method, which failed for some 
> reason (I'm not a Linux wizz, so probably operator error!).
> Then used the tar ball, and that worked, and I'm now seeing Version 1.4.1.

no worries, it's good to see that you're using the last stable
version.

> However I'm still getting the error on the buffer overflow:
> ++
> Welcome to tlf-1.4.1 by PA0R!!
> 
> Reading country data
> Reading configuration data
> Reading config file: logcfg.dat
> Reading contest rules file: rules/beru*** buffer overflow detected ***: 
> terminated
>   Aborted
> +++
> I tried this in a virtual terminal as well, with the same results.
> If you feel this is something to do with my local setup here, which would be 
> hard to check for you, please let it be and I'll get by without a countylist.

as Zoli HA5CQZ mentioned previously, triggering the buffer overflow
is not easy.

Which OS do you use? An `lsb-release -a` output would be fine.


73, Ervin
HA2OS




Re: TLF logger, countrylist file format?

2022-03-06 Thread Gerard van Antwerpen
Hi Ervin,
Thanks for your time to help.
First of all I installed originally using the easy way, using apt install tlf.
Then, after your reply, used the git clone method, which failed for some reason 
(I'm not a Linux wizz, so probably operator error!).
Then used the tar ball, and that worked, and I'm now seeing Version 1.4.1.
However I'm still getting the error on the buffer overflow:
++
Welcome to tlf-1.4.1 by PA0R!!

Reading country data
Reading configuration data
Reading config file: logcfg.dat
Reading contest rules file: rules/beru*** buffer overflow detected ***: 
terminated
  Aborted
+++
I tried this in a virtual terminal as well, with the same results.
If you feel this is something to do with my local setup here, which would be 
hard to check for you, please let it be and I'll get by without a countylist.
Kind regards,
Gerard, ZL2GVA

From: Ervin Hegedüs 
Sent: Saturday, March 5, 2022 8:15 PM
To: Gerard van Antwerpen 
Cc: tlf-devel@nongnu.org 
Subject: Re: TLF logger, countrylist file format?

Hi Gerard,

On Fri, Mar 04, 2022 at 07:02:21AM +, Gerard van Antwerpen wrote:
> I tried to add the beru: to the start of the file, and it gets read now (I 
> also think it needs to be in the main contest directory, not the one with the 
> rules in it), however I am getting the following error message:
>
> +++
>Welcome to tlf-1.4.0 by PA0R!!
>
> Reading country data
> Reading configuration data
> Reading config file: logcfg.dat
> Reading contest rules file: rules/beru*** buffer overflow detected ***: 
> terminated
>   Aborted
> +++
>
> It is a long list of countries, but trimming it back doesn't help.
> Putting a short country list in the rules file does get read, but doesn't 
> seem to affect scoring, all contacts are given 5 points (as I set with 
> CWPOINTS=5), and also points for my call area while I set MY_COUNTRY_POINTS=0
>
> Attached my config files.

thanks, I've checked your setup, but couldn't reproduce the
issue. Tlf started and worked like a charm.

Note, that I'm using the (nearly) latest git version of Tlf:

$ git describe
tlf-1.4.1-249-gebe9341

(which shows 1.5~git at the startup).

Could you try the lates git version?

And my 2cents:

44  #
45  #   #
46  #  Time offset from UTC #
47  #   #
48  #
49  #
50  TIME_OFFSET=-13

(this is your logcfg.dat).

Don't touch TIME_OFFSET, keep is as is.

TIME_OFFSET=0

unless your workstation's time is not where you are.

For more info, please check the manual.


73, Ervin
HA2OS



Re: TLF logger, countrylist file format?

2022-03-06 Thread Csahok Zoltan
Hi Gerard,

Even if it's not easy to trigger the buffer overflow, things do not work
as expected. I've opened an issue: https://github.com/Tlf/tlf/issues/319

Thanks for reporting!

I suggest generally to use the latest code (master branch from github)
if possible, as it contains a number of fixes and improvements.
It also shortens the feedback loop for any issues found.

73,
Zoli