thank you very much for your kind praise.
I know a lot of bank are going insane security wise, adopting all this
crappy protection as a soft keyboard, when it is known that some
keylogger already take screenshot of the monitor close where the mouse
click happened. But let's not digress.
About your suggestion of uploading files to Clipperz, this was an idea
we already had, but we could not solve it technically; let me try to
explain why.
Clipperz strength is that we never have any plain data on our server;
we only receive and store encrypted data. But when you want to upload
a file, the Javascript code is not able to read it right from the file
system due to legitimate security restrictions enforced by the
browser.
This means that, in order to be able to process the data of the file,
we would need to have the plain data make a round-trip to one server.
And this is obviously a very bad option, even if we could implement
the system to just return the data without ever storing anything.
Showing up the data afterwords would be tricky, but probably possible.
But we need to find out a way to securely upload the data in the first
place.
At this point, even if it can be a real pain, you could try to
transcribe the table in a text format and put it in the note field in
the card. Not a great alternative, though.
Hope this helps.
Best regards,
Giulio Cesare
the note field should not have any hard limits.
Your idea is interesting, but it basically just shift the problem to
upload the image to Clipperz, to upload the image to the encoding web
app.
Technically, encoding the image using a local application should do
the trick. I think that it should be feasible to later recreate the
whole picture right inside the browser. But asking average Joes to get
a desktop application in order to encode the file content and later to
copy/paste it into Clipperz and setting the right content type is just
too much effort.
Regards,
Giulio Cesare