Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #135161
| From | clv2020 <clv2020@vodafonemail.de> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Back to the Forth Virus |
| Date | 2026-06-10 15:55 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <110bqbs$p1bl$1@dont-email.me> (permalink) |
| References | <11069n1$3617t$1@dont-email.me> <1108phc$3tf69$1@dont-email.me> |
Am 09.06.2026 um 12:22 schrieb Stephen Pelc: >> ... (gForth, bigForth, VFX, Swiftforth are too big for me for >> the moment). ... > > What do you mean by "too big" For the moment my little brain tries to understand the traditional indirect-threading. Optimized native code might come later for me. >> The second question: All Forth systems I tried showed critical virus >> warnings from Google Chrome or Microsoft defender. Even an old >> volksForth vf38141.arc - no modern archive utiliy could read this format >> - was captured by Chrome. Win32Forth seems to be kidnapped on about each >> start by the Defender. I'm not very amused to turn all IT security off >> to use Forth. Is there a chance to solve this issue? > > Without code signing, nearly all Windows Forths will be caught by Defender at > some stage. However, adding relevant sections to the executable with something > like ResHacker reduces the issues greatly. The reason for all this is that > Forth > usually requires a main section to have read, write and execute permissions. > Such a section is often treated as a virus. > > Stephen > I'm not really involved in Resources and ResHack. Virustotal backs your opinion. For Win32Forth the only real hint showed: Contained Resources SHA-256 File Type Type Language Entropy Chi2 88479a7c699e9aaa67141fba8271a4eac894467e4268795907e82364e386172f unknown RT_ICON NEUTRAL 3.16 34436.72 61e4d7114d33c4d5320da94000d1816511ec5e511c0b9b71a3a215375888b0cc unknown RT_ICON NEUTRAL 2.86 19575.13 b10e28a32eddb2ab20a46ceae59d9c0786911eb20f0c8dd2a28421f226ea2b8b ICO RT_GROUP_ICON NEUTRAL 2.37 2345.29 b987ff8b14f04477e603e5cb00b2ac25c3b91afee3e929c84c44fd884717c883 unknown RT_MANIFEST NEUTRAL 5.18 5109.05 I have no idea, if this indicates a problem. For me it sounds not critical. And the other Forths catched by Defender seem too old for resources and memory permissions issues. Claus -- Ich bin nicht die Signatur. Ich putze hier nur.
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Back to the Forth Virus clv2020 <clv2020@vodafonemail.de> - 2026-06-08 13:40 +0200
Re: Back to the Forth Virus Jan Coombs <jan4etsept@murray-microft.co.uk> - 2026-06-08 13:16 +0100
Re: Back to the Forth Virus Ruvim <ruvim.pinka@gmail.com> - 2026-06-08 12:23 +0000
Re: Back to the Forth Virus Daniel Cerqueira <dan.list@lispclub.com> - 2026-06-08 13:56 +0100
Re: Back to the Forth Virus anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-08 15:40 +0000
Re: Back to the Forth Virus Daniel Cerqueira <dan.list@lispclub.com> - 2026-06-08 19:26 +0100
Re: Back to the Forth Virus anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-08 20:06 +0000
GForth reproducible builds (was Re: Back to the Forth Virus) Kragen Javier Sitaker <kragen@canonical.org> - 2026-09-02 14:40 -0300
Re: Back to the Forth Virus minforth <minforth@gmx.net> - 2026-06-09 01:01 +0200
Re: Back to the Forth Virus clv2020 <clv2020@vodafonemail.de> - 2026-06-10 13:13 +0200
Re: Back to the Forth Virus minforth <minforth@gmx.net> - 2026-06-11 10:01 +0200
Re: Back to the Forth Virus anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-11 17:28 +0000
Naming issues in create-does (was: Back to the Forth Virus) Ruvim <ruvim.pinka@gmail.com> - 2026-06-12 17:23 +0000
Re: Naming issues in create-does (was: Back to the Forth Virus) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-12 17:52 +0000
Re: Naming issues in create-does (was: Back to the Forth Virus) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-12 18:22 +0000
Re: Naming issues in create-does dxf <dxforth@gmail.com> - 2026-06-13 13:14 +1000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-13 06:33 +0000
Re: Naming issues in create-does dxf <dxforth@gmail.com> - 2026-06-13 22:20 +1000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-13 15:55 +0000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-15 13:08 +0000
Re: Naming issues in create-does Hans Bezemer <the.beez.speaks@gmail.com> - 2026-07-23 19:58 +0200
Defining words in more than one step (was: Naming issues in create-does) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-13 06:46 +0000
Re: Defining words in more than one step dxf <dxforth@gmail.com> - 2026-06-14 12:29 +1000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-12 19:59 +0000
Re: Naming issues in create-does anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-13 10:25 +0000
Re: Naming issues in create-does Ruvim <ruvim.pinka@gmail.com> - 2026-06-13 15:30 +0000
Re: Naming issues in create-does anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-06-13 17:30 +0000
Re: Naming issues in create-does (was: Back to the Forth Virus) peter <peter.noreply@tin.it> - 2026-06-13 20:21 +0200
Re: Back to the Forth Virus dxf <dxforth@gmail.com> - 2026-06-09 12:14 +1000
Re: Back to the Forth Virus "Kerr-Mudd, John" <admin@127.0.0.1> - 2026-06-10 18:54 +0100
Re: Back to the Forth Virus dxf <dxforth@gmail.com> - 2026-06-11 16:32 +1000
Re: Back to the Forth Virus "Kerr-Mudd, John" <admin@127.0.0.1> - 2026-06-11 14:20 +0100
Re: Back to the Forth Virus Stephen Pelc <stephen@vfxforth.com> - 2026-06-09 10:22 +0000
Re: Back to the Forth Virus clv2020 <clv2020@vodafonemail.de> - 2026-06-10 15:55 +0200
Re: Back to the Forth Virus albert@SPENARNC.XS4ALL.NL - 2026-07-24 13:35 +0200
csiph-web