Open ApxToTop opened 3 years ago
I don't have a definite timeline for implementing OCR - at the moment finishing the web rendering rewrite is higher priority.
Noting down some initial thoughts for when I get some time for this:
I don't have a definite timeline for implementing OCR - at the moment finishing the web rendering rewrite is higher priority.
Noting down some initial thoughts for when I get some time for this:
- There are rust bindings for tesseract-ocr
- If we opt for tesseract then it'll ideally need to be statically linked on all supported platforms, and we'll need to distribute a set of training data alongside scrying
- Will tesseract give sensible output if it's given the full RDP captures or would it benefit from having the images somehow cropped down to just the usernames?
- Would it make sense to implement this at the same time as heuristics for determining the server version (e.g. because different Windows versions have slightly different username displays and it might be more performant to search the image for multiple features at the same time rather than running them through separate pipelines)
- Does username parsing need the full feature set of tesseract or would a simpler implementation make sense, based on commonly used fonts?
It is also suggested that a parameter switch should be added to the html report. If a large number of detections are carried out, html will become extremely large and affect program performance.
Thank you for your selfless dedication.
When does the Ocr function be added?