Package: wesnoth
Version: 1:1.14.13-1
Followup-For: Bug #970520
X-Debbugs-Cc: gera...@malazdrewicz.com.ar
Dear Maintainer,
Patch 99wolfssl-options attached adding
#include
to affected files:
src/build_info.cpp
src/hash.cpp
src/preferences/credentials.cpp
src/server/user_handler.cpp
This
Hi Bernhard,
On Fri, Oct 2, 2020 at 8:06 AM Bernhard Übelacker wrote:
>
> @Felix Lechner: Hope it is ok to add you in CC?
Absolutely. I was already in touch with wolfSSL upstream, who process
my tickets at their highest support level. They tasked two employees
with analyzing the backtrace but
Dear Maintainer,
I could reproduce this stack smashing inside a testing amd64 VM.
The stack canary gets overwritten in the stack below.
It looks like there is a disagreement of wesnoth and wolfssl in
the size of sha/hasher wc_Sha/WOLFSSL_SHA_CTX, the first allocates
112 bytes, the latter thinks
The game can be started with the following command:
$ wesnoth --nocache
I'm not a Wesnoth player, so I don't know if all work correctly after it
start.
Ciao
Davide
Package: wesnoth
Version: 1:1.14.13-1
Severity: important
Dear Maintainer,
when I start wesnoth it crashed with follwoing output:
START OF TERMINAL OUTPUT -
Battle for Wesnoth v1.14.13
Started on Thu Sep 17 22:33:45 2020
Data directory:
5 matches
Mail list logo
