09-27-2023, 01:51 PM | #16 | |
the rook, bossing Never.
Posts: 11,166
Karma: 85874891
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
Quote:
Xournal is pointless if you have Nebo or similar. |
|
09-27-2023, 06:58 PM | #17 |
Groupie
Posts: 185
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
|
***
The landscape does look pretty bleak so not arguing with you but, for the record: [WIP] Lua Plugin for Handwriting recognition #2176 https://github.com/xournalpp/xournalpp/pull/2176 There is a link to this: Lipi Toolkit https://lipitk.sourceforge.net/lipi-toolkit.htm https://sourceforge.net/projects/lip...pi_toolkit4.0/ $ cd rmkit-build/ $ tar zxvf lipi-toolkit4.0.0-src-linux.tar.gz lipi-toolkit4.0.0-src-linux/ $ cd lipi-toolkit4.0.0-src-linux/ $ nano -l src/build-x64.sh Code:
80 # if [ $os != "Ubuntu" ] 81 # then 82 # echo "\nERROR: lipi-core-toolkit can be built only on Ubuntu Linux\n" 83 # exit 1 84 # fi ... 88 find /lib/x86_64-linux-gnu -print | grep "$filename\." 1>/dev/null 2>&1 Building lipitk objects and binaries.....OK $ LIPI_ROOT=~/rmkit-build/lipi-toolkit4.0.0-src-linux src/apps/samples/shaperectst/linux-x64/shaperectst SHAPEREC_NUMERALS projects/demonumerals/data/1/1_0.txt Input Logical project name = SHAPEREC_NUMERALS Input ink file for recognition = projects/demonumerals/data/1/1_0.txt Recognition Results Choice[0] Recognized Shapeid = 1 Confidence = 0.549951 Choice[1] Recognized Shapeid = 2 Confidence = 0.126473 Over a decade old and still ticking! *** jersou/mouse-actions https://github.com/jersou/mouse-actions $ cd rmkit-build/ $ wget https://github.com/jersou/mouse-acti...heads/main.zip $ mv main.zip mouse-actions-main.zip $ unzip mouse-actions-main.zip $ cd mouse-actions-main/ $ cargo build --release Ran out of cell data, so had to abort, LOL |
Advert | |
|
09-27-2023, 07:07 PM | #18 |
Groupie
Posts: 185
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
|
|
09-28-2023, 04:42 PM | #19 |
BLAM!
Posts: 13,478
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
|
09-28-2023, 08:22 PM | #20 | |
Groupie
Posts: 185
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
|
Quote:
https://www.mobileread.com/forums/sh...46&postcount=3 And looking at the rest of the Kobo lineup, I see mostly Freescale (other than Sage/Elipsa): https://en.m.wikipedia.org/wiki/Kobo_eReader So can we infer that the other Kobos should support rmkit? But there's something {among many other things) that still troubles me. The Pocketbook lineup appears to be largely Allwinner, like the dreaded Sage/Elipsa: https://en.m.wikipedia.org/wiki/Pock..._International Yet by some feate of Magicke there has appeared fbink supporton the Pocketbook: https://github.com/NiLuJe/FBInk Some of the conjurations have even been revealed: https://github.com/NiLuJe/FBInk/pull/64 So is there no way to use a similar incantation for rmkit?? |
|
Advert | |
|
09-30-2023, 08:24 AM | #21 |
Groupie
Posts: 185
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
|
POSSIBLE SECURITY ISSUES OF RMKIT
POSSIBLE SECURITY ISSUES OF RMKIT
Since rmkit makes it easier to quickly develop cross-platform apps, some might roll their eyes and say, "Great, more junk apps". Security-conscious people should also be concerned that a proliferation of low quality apps makes a nice target for malware. -C++ requires effort and skill to be done correctly, and therefore securely. -Kobo Nickel is designed for reading, not networking. It lacks up-to-date kernel, fine-grained permissions in the user partition, and kernel support for firewalls, among other issues. How can this problem be addressed? Kobo is even less equipped to deal with this than old Windows was. Some random ill-thought out musings: - Use InkBox instead of Nickel - Only allow signed apps to launch in rmkit - Run an app scanner over apps in the rmkit repository. - Run a user-space firewall in rmkit (all i/o accesses only allowed through "secure" api) - Require users who want to run Simple framework to self-sign any app they want to give run permission to. Who would do all this work? Not me - I'm not a dev, and definitely not a C++ dev. But I want to enjoy my Kobo in a secure way. Last edited by elinkser; 09-30-2023 at 11:28 AM. |
09-30-2023, 05:46 PM | #22 | |
BLAM!
Posts: 13,478
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Quote:
We tried to live with it for a while in KOReader, but it required a gigantic and brittle pile of hacks, so we simply caved in and now go through the native middleware (InkView). FBInk doesn't (as much as possible, we still use it for device identification, although that can be disabled, because bringing in InkView introduces brand new ways to break stuff in fun and interesting ways), and still includes the bare minimum of said pile of hacks. TL;DR: It works. Not well, but it "works". In any case, definitely *not* an example to follow. Last edited by NiLuJe; 09-30-2023 at 05:49 PM. |
|
10-01-2023, 05:05 AM | #23 | |
Connoisseur
Posts: 88
Karma: 3892
Join Date: Feb 2022
Device: Kobo nia
|
Quote:
Running rmkit as a InkBox user apps makes it extremely sandboxed, but it wouldn't protect against all ( Only some, we limit access to /dev and /sys ) kernel level exploits. And you worry about it too much. Who cares about the x users using rmkit? You would need to special prepare malware for what? |
|
10-01-2023, 06:21 PM | #24 |
Groupie
Posts: 185
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
|
|
10-04-2023, 11:21 AM | #25 | ||
Member
Posts: 23
Karma: 11102
Join Date: Jan 2022
Device: kobo libra h2o, kobo clara hd, kobo elipsa 2e
|
Quote:
Quote:
i'm not a security person, so i don't know how they grade security issues, but i think there are two major portions: opportunity size and risk size. the opportunity is low (not that many users: maybe dozens or low hundreds, i have no way of knowing) and the risk is also low (people do not keep sensitive personal information on their readers. the major risk is having your data deleted on you or someone install spyware to report on your activity). probably we mostly need to watch out for people who get some fun out of harming other people's daily life (a griefer) |
||
10-04-2023, 05:51 PM | #26 |
Groupie
Posts: 185
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
|
@raisjn
I appreciate your consideration of my concerns. I'm familiar enough about computer security to avoid using a cool network app to connect from my insecure kobo to my phone I use for banking, but I don't necessrily expect regular users to be. They may have an expectation that they are being taken care of. On a funner note, I finally got around to trying the remarkable port of Simon Tatham's Portable Puzzle Collection! (I first tried the binary, then recompiled it for my Clara HD - attached). mv puzzles.bin puzzles.xz xz -d puzzles.xz First tried the binary: mrichards42/remarkable_puzzles https://github.com/mrichards42/remarkable_puzzles Simon Tatham's Portable Puzzle Collection for the reMarkable tablet. $ mkdir mypuzzles $ cd mypuzzles/ $ wget https://github.com/mrichards42/remar...puzzles.tar.gz $ tar zxvf puzzles.tar.gz On the kobo create etc/puzzles/ folder in /mnt/onboard/.adds/rmkit/. Copy the config/, help/, icons/ folders to the /mnt/onboard/.adds/rmkit/etc/puzzles/ folder. Copy the puzzles binary to the /mnt/onboard/.adds/rmkit/bin/apps/ folder. /mnt/onboard/.adds/rmkit/bin/apps/puzzles: /lib/libm.so.6: version `GLIBC_2.27' not found (required by /mnt/onboard/.adds/rmkit/bin/apps/puzzles) OK let's try to build: $ git clone --recurse-submodules https://github.com/mrichards42/remarkable_puzzles.git $ cd remarkable_puzzles/ $ source ~/koxtoolchain/refs/x-compile.sh kobo env bare $ nano -l defs.mk Code:
... 11 export BUILD ?= release ... 26 else ifeq ($(ARCH),kobo) 27 CXX = arm-kobo-linux-gnueabihf-g++ 28 CC = arm-kobo-linux-gnueabihf-gcc 29 STB = stb.arm.o $ nano -l vendor/rmkit/src/common.make Code:
3 CXX_BIN?=arm-kobo-linux-gnueabihf-g++ 4 CC_BIN?=arm-kobo-linux-gnueabihf-gcc 5 STRIP_BIN?=arm-kobo-linux-gnueabihf-strip Code:
241 // case ABS_MT_SLOT: 242 // slot = data.value; 243 // break ... 282 // case ABS_MT_DISTANCE: 283 // slots[slot].distance = self.distance = data.value 284 // if self.distance > 0: 285 // self.left = 0 286 // break Code:
69 // if ev_data[i].code == SYN_DROPPED: 70 // syn_dropped = true 71 // event.handle_drop(fd) 72 // continue Code:
31 #define TOUCH_FLOOD_EVENT ABS_DISTANCE $ cp build/release/puzzles . $ arm-kobo-linux-gnueabihf-strip -s puzzles $ ls -l puzzles -rwxr-xr-x 1 1892712 puzzles $ zip puzzles.zip puzzles $ ls -l puzzles.zip -rw-r--r-- 1 1119921 puzzles.zip $ xz puzzles $ ls -l puzzles.xz -rwxr-xr-x 1 919152 puzzles.xz On the kobo create etc/puzzles/ folder in /mnt/onboard/.adds/rmkit/. Copy the config/, help/, icons/ folders to the /mnt/onboard/.adds/rmkit/etc/puzzles/ folder. Copy the puzzles binary to the /mnt/onboard/.adds/rmkit/bin/apps/ folder. mv puzzles.bin puzzles.xz xz -d puzzles.xz Works great, puzzle lovers rejoice! Last edited by elinkser; 02-28-2024 at 07:31 PM. |
01-25-2024, 03:05 PM | #27 |
Member
Posts: 24
Karma: 10
Join Date: Aug 2017
Device: Kobo Aura One
|
Would it be possible to get rmkit working on an Aura One?
I installed rmkit, which according to ps | grep remux is running, but doesn't appear to do anything beyond that. As per https://rmkit.dev/rmkit-comes-to-kobo/ by @raisjn I guess support needs to be added first (if possible at all)? |
01-25-2024, 05:25 PM | #28 | |
Groupie
Posts: 185
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
|
Quote:
https://en.m.wikipedia.org/wiki/Kobo_eReader The developer says in your link: Currently, the Libra H20 and Clara are supported, but if you have any requests, please get in touch and I’ll look into enabling more devices If there is enough interest, hopefully Raisjn will port to FBInk as a general solution, though device touch input handling is also needed. Here is what I used to debug in Post#7: When I run from SSH on PC: # ps | grep remux 1514 root 0:00 sh /opt/bin/remux.sh 1516 root 0:00 /opt/bin/apps/remux 1648 root 0:00 grep remux # kill -KILL 1514 # kill -KILL 1516 # sh /opt/bin/remux.sh Then swipe up to start remux, and select e.g the drawing_demo app: DISPLAYED LAUNCHER FOR 2200 MS LAUNCHING APP drawing_demo drawing_demo POWER MANAGEMENT: 1 RESETTING MT GESTURES CHECKING PROCESS drawing_demo 0 RENDERING drawing_demo DECOMP TOOK 0.00358233 RUNNING ON CLARA HD SETTING SCREEN DEPTH 32 W: 1072 H: 1448 S: 1088 XRES 1072 YRES 1448 BPP 32 GRAYSCALE 0 OPENING /dev/input/event0 AS BUTTONS OPENING /dev/input/event1 AS TOUCH ERROR OPENING INPUT DEVICE /dev/input/event2 ERROR OPENING INPUT DEVICE /dev/input/event3 ERROR OPENING INPUT DEVICE /dev/input/event4 on_mouse_move debug, ev= 262 on_mouse_move debug, prevx= 262 on_mouse_move debug, ev= 262 on_mouse_move debug, prevx= 262 on_mouse_move debug, ev= 262 on_mouse_move debug, ev= 263 on_mouse_move debug, prevx= 263 *Note that you have to swipe up along the edge of the display to bring the up the rmkit menu. (I would try swiping all directions in your case since the touch support is not specified for your device. If you are lucky, you will get messages like above. |
|
01-26-2024, 12:57 PM | #29 |
Member
Posts: 24
Karma: 10
Join Date: Aug 2017
Device: Kobo Aura One
|
Thanks for your reply.
When I do what you did for debugging, # sh /opt/bin/remux.sh results in an endless loop of FATAL: kernel too old Aborted I take that to mean rmkit doesn't currently work on KA1. Whether that is because of the different chipset or simply because the device isn't added as supported yet (as per "Individual devices have to be enabled so as to not cause issues, so seriously: please get in touch!"), I don't know. Hopefully Raisjn can shed some light on that |
01-26-2024, 06:38 PM | #30 |
Groupie
Posts: 185
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
|
Yes, letting Raisjn know would be good for supporting older devices.
I did try building the remux bin with an older kernel - you can try it if you want. Last edited by elinkser; 01-28-2024 at 02:27 PM. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
rmkit comes to kobo! | raisjn | Kobo Developer's Corner | 25 | 04-21-2024 10:23 PM |
Native FBInk: Another small tool to print crap on your screen! | NiLuJe | Kindle Developer's Corner | 282 | 12-05-2022 03:04 PM |
fbink image scaling question | handyguy | Kindle Developer's Corner | 6 | 12-17-2020 07:01 PM |
Latest fbink install? | handyguy | Kindle Developer's Corner | 3 | 12-11-2020 09:13 PM |
Pre-Purchase Questions ... Clara/Libra/Forma | Catsnkites | Kobo Reader | 9 | 10-27-2019 11:28 AM |