Thanks to all for the help and suggestions.
The fedora build with an executable stack resolves the jt9 crashes.
mike, kj6vcp
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdo
- Original Message -
> On Fri, Jan 19, 2018 at 9:03 AM, Jaroslav Skarvada < jskar...@redhat.com >
> wrote:
>
>
>
>
>
>
> OK, no problem, I added you. I have no problem with EPEL-7, I didn't request
> it in the beginning, just because I didn't need it :)
>
> Thanks. I'm running Fedo
Several topics on this in the group that can be found via a brief search.
People are sending images over the internet to each other via JT65HF Image
Controller and the “/Image” is the prompt to go download the image.
(This is probably less a development question and one for the WSJT-Group
ref
On Fri, Jan 19, 2018 at 9:03 AM, Jaroslav Skarvada
wrote:
> OK, no problem, I added you. I have no problem with EPEL-7, I didn't
> request it in the beginning, just because I didn't need it :)
>
Thanks. I'm running Fedora 27 but there are a number of hams that prefer
the stability of the EL dist
[ resend - mailman rejected the zipped attachments, so I forwarded
them directly to Bill. ]
On Fri, Jan 19, 2018 at 5:40 AM, Michael Pittaro wrote:
> Here are some sample .wav files and my config file.
>
> All my ft8 samples crash with with a SIGSEGV, but only some of the
> JT65 ones so I include
On 19/01/2018 14:14, Claude Frantz wrote:
On 01/19/2018 12:41 PM, Bill Somerville wrote:
Hi Bill & all,
Perhaps is this problem related to the recent effort to avoid W+X pages.
I'm no sure.
if that is the case then it is not acceptable. I cannot think of any
attack vector on the jt9 executabl
- Original Message -
> I somehow completely missed that. I've been maintaining a COPR for some time
> now which includes support for EL 7.
> If you want to add me as a maintainer (FAS: hobbes1069) I'll put in a ticket
> for EPEL 7 so I can close my COPR.
> Thanks,
> Richard
OK, no probl
On 01/19/2018 12:41 PM, Bill Somerville wrote:
Hi Bill & all,
>> Perhaps is this problem related to the recent effort to avoid W+X pages.
>> I'm no sure.
> if that is the case then it is not acceptable. I cannot think of any
> attack vector on the jt9 executable that could do harm that is enable
I somehow completely missed that. I've been maintaining a COPR for some
time now which includes support for EL 7.
If you want to add me as a maintainer (FAS: hobbes1069) I'll put in a
ticket for EPEL 7 so I can close my COPR.
Thanks,
Richard
---
Hi, Bill,
My issue with the WSJT project rpm mysteriously 'went away'. jt9
definitely crashed intermittently on the first few decodes while I was
setting up and twiddling things, but I don't have the core files or
any notes on what what going on at the time. I don't like heisenbugs,
but after th
>> On Fri, Jan 19, 2018 at 6:44 AM, Jaroslav Skarvada
>> wrote:
>> I am Fedora packager, and AFAIK the answer is NO. Also it seems there is
>> no Fedora global policy about it. Just rpmlint is complaining. I fixed the
>> spec not to enforce the NX stack and released updated builds. Feel free to
>
On 19/01/2018 03:16, Ian Lee wrote:
Dear wsjtx Devlop team.
I uploaded it as a topic to wsjtx group but it did not go up well.
then send you an e-mail to find this e-mail address on the
Internet. It seems to be the first time I've used the Yahoo group.
HI Ian,
your post did make it to the
Dear wsjtx Devlop team.
I uploaded it as a topic to wsjtx group but it did not go up well. then
send you an e-mail to find this e-mail address on the Internet. It seems to
be the first time I've used the Yahoo group.
First I love wsjtx too much.I restarte
On 19/01/2018 13:22, Michael Pittaro wrote:
Here's the read elf result on my machine with the original build I
reported the problem with - the stack is not marked executable. Also,
selinux is in permissive mode, and it's kernel 4.14.8-300.fc27.x86_64
[mikeyp@microhertz ft8_samples]$ readelf -
On Fri, Jan 19, 2018 at 6:44 AM, Jaroslav Skarvada
wrote:
>
> I am Fedora packager, and AFAIK the answer is NO. Also it seems there is
> no Fedora global policy about it. Just rpmlint is complaining. I fixed the
> spec not to enforce the NX stack and released updated builds. Feel free to
> test a
Here's the read elf result on my machine with the original build I
reported the problem with - the stack is not marked executable. Also,
selinux is in permissive mode, and it's kernel 4.14.8-300.fc27.x86_64
[mikeyp@microhertz ft8_samples]$ readelf -lW `which jt9` | grep GNU_STACK
GNU_STACK
On 19/01/2018 12:44, Jaroslav Skarvada wrote:
stack, are the Fedora team really going to deny that technique for all
applications?
I am Fedora packager, and AFAIK the answer is NO. Also it seems there is
no Fedora global policy about it. Just rpmlint is complaining. I fixed the
spec not to enfor
> stack, are the Fedora team really going to deny that technique for all
> applications?
I am Fedora packager, and AFAIK the answer is NO. Also it seems there is
no Fedora global policy about it. Just rpmlint is complaining. I fixed the
spec not to enforce the NX stack and released updated build
What is this, what I can see decoded, namely some CALL/IMAGE?
Ie. example xx0xx/image and also sometimes xx0xx/cmd?
Using wsjtx-1.8,0 in Fedora 26..
Jarmo
--
Check out the vibrant tech community on one of the world's most
I can confirm Tom's idea, CAT command keys the radio but audio not come
through, same as VOX..
You must have extra RTS/DTR keying..
Easiest way is USB-RS232 adapter and add optocoupler circuit to RTS (or DTR)
pin.
See https://www.nf8m.com/nf8m/rig-control-and-keying/.
Unfortunately can't help wi
On 19/01/2018 06:45, Claude Frantz wrote:
Perhaps is this problem related to the recent effort to avoid W+X pages.
I'm no sure.
In order to avoid problems, in the general sense, in some environments,
I suggest to change the programming style such that the programs do not
need an executable stack
- Original Message -
> On 18/01/2018 17:38, Jaroslav Skarvada wrote:
>
>
>
> - Original Message -
>
>
>
> Out of curiosity I ran rpmlint on wsjtx and most of the output was pretty
> much what I expected but one line in particular caught my eye.
>
> wsjtx.x86_64: W: executab
22 matches
Mail list logo
