Lionel Debroux

There's a drawback to memoizing the output of strings, though: DoS upon huge rcfiles... Here's another take on optimizing the possible_rkt_strings check, which no longer memoizes anything. I split the work between a fast path which tries to find all strings at once in every rcfile, and a slow path if the first check returns at least one match. Core i7-6700 HQ (SMP, SMT disabled), 32 GB DDR4-2133, Debian sid amd64, cache hot: before: \time rkhunter_ --cronjob --report-warnings-only --enable possible_rkt_strings...

Redundant operations: possible rootkit strings check

New version: the warnings-only mode works better.

I gave my idea a go, stopping at the point where the /var/log/rkhunter.log file created by rkhunter -c --sk does not contain relevant changes anymore, when LANGUAGE=en. On two computers ~15 years apart, both equipped with SATA SSDs, my changes seem to yield a significant speedup, without significant adverse effect on memory consumption. Core i7-6700 HQ (SMP, SMT disabled), 32 GB DDR4-2133, Debian sid amd64, cache hot (second run): before: 211.88user 153.26system 4:47.00elapsed 127%CPU (0avgtext+0avgdata...

Redundant operations: parsing of the external translations file ?

libti*, gfm and tilp only deal with transferring data to/from TI graphing calculators (and in the development version, some pieces of lab equipment related to such calculators). Detokenization, edition and tokenization of programs are performed by other programs; TI's official GraphLink software from at least 20 years ago targeting contemporary versions of Windows comes to my mind, but off the top of my head, I'm not sure which newer pieces of software might support the aforementioned operations...

Use 2nd + LINK, then: * F1 to set the calculator in send mode and select what you want to send from the calculator for TILP to receive; * F2 to set the calculator in receive mode before sending from TILP.

It's a good thing that screenshots work, it means that your Windows computer is correctly configured :) Unlike newer models, the 85 and 82 do not support so-called silent linking mode for variable / backup transfer: on the calculator side, they need to be manually put into send / receive mode. So, is it what you're doing when attempting to communicate with TILP ? I'm asking because I've already seen other persons unaware that the 85 & 82 only support non-silent linking mode for transferring non-screenshot...