The so-called-better-way of doing this using Unicode substitution can be found at http://smartdata.cs.unibo.it/watermark/
Be careful what you copy: Invisibly inserting usernames into text
131–140 of 200 posts
Re: Be careful what you copy: Invisibly inserting usernames into text
#132This sort of thing is one of the reasons I never liked the "noise texture" that appeared on MacOS X and other GUIs and websites not so long ago. I always thought my (former) OS was fingerprinting every screenshot I made. I'd love to be proven wrong, but you are never too careful.
I remember that Blizzard had secretly watermarked WoW screenshots.
Re: Be careful what you copy: Invisibly inserting usernames into text
#133How difficult would it be to write a browser extension to either remove all zero-width characters or somehow make it super obvious that they are being used on the page? I just searched for "zero-width" and "zero width" in Chrome and Firefox's extensions stores, but didn't come up with anything.
Zero width characters have legitimate uses such as family emojis and certain Indic scripts. You don't want to break these.
Re: Be careful what you copy: Invisibly inserting usernames into text
#134Interestingly, pasting text with zero width chars into an iMessage chat box does alert the user by showing "question in a box" chars for the zero-width chars.
Re: Be careful what you copy: Invisibly inserting usernames into text
#135Earlier quoted context omitted.
Just last week we got a patch were they capped the jump fatigue significantly. I don't know how much as I don't use jump drive, but it should be better now. Also just sell your stuff and rebuy it. You don't need many ships to have some fun. Roaming is .. not that common any more. What we do is live in a Wormhole, jump into 0.0 and try to tackle something big and hope they form a defense fleet. Roll the hole to get a…
> Roaming is .. not that common any more. Nor is gatecamping because some genius decided that instawarping bubble immunity (with optional covops cloak functionality) was a good idea so people could move through null in virtually perfect safety. There have been so many changes which I find fundamentally stupid that it's hard for me to engage with the game these days. One day I'll probably play for a bit again though
Was killing ceptors and pods fundamental for your eve game play?
Edit: Also people stil gatecamp.
Re: Be careful what you copy: Invisibly inserting usernames into text
#136I did this (non-publicly) many years ago for my eve online alliance. A substantial problem exists in that forging the identity of _someone else_ is fairly easy in a naive scheme if someone detects these characters. That means you can sow chaos by blaming innocent folks. In practice you'll want to "sign" the inserted data as well. Also because of the overhead here and the fact that you will want the signature to occur…
On forging the identity of someone else, the author did mention it and the workaround is pretty simple (using a secret ID for each user): > There are some caveats to this method of course. For example, if a user knew of the script they could theoretically insert their own zero-width characters and accuse someone else. A better solution would be to insert a unique user ID that is not publicly available instead of the…
If someone manages to determine the secret ID then it fails. What about signing a combination of part of the message (likely some hash) and the user ID. This would create a secret ID, but one which if stolen can be shown to be false since trying to recreate the signature with their ID and the message would fail. Hash collisions between different messages are still a concern, but aren't their known solutions to that problem that can be implemented in combination?
Re: Be careful what you copy: Invisibly inserting usernames into text
#137Earlier quoted context omitted.
> Roaming is .. not that common any more. Nor is gatecamping because some genius decided that instawarping bubble immunity (with optional covops cloak functionality) was a good idea so people could move through null in virtually perfect safety. There have been so many changes which I find fundamentally stupid that it's hard for me to engage with the game these days. One day I'll probably play for a bit again though
Was killing ceptors and pods fundamental for your eve game play? Edit: Also people stil gatecamp.
I think he's talking about the luxury yachts... interceptors can't covops cloak. (And t3's can't instant warp _and_ have bubble immunity)
Re: Be careful what you copy: Invisibly inserting usernames into text
#138How difficult would it be to write a browser extension to either remove all zero-width characters or somehow make it super obvious that they are being used on the page? I just searched for "zero-width" and "zero width" in Chrome and Firefox's extensions stores, but didn't come up with anything.
Would probably be better to do this at the OS level, no? Just ensure that shift-cmd-V/shift-ctrl-V strips zero-width characters in addition to formatting. I can't think of a situation where I'd want to keep one but not the other, and you could always do that manually if it came up.
Arabic? I think the are cases where letters are joined or not by default, but sometimes need to be forced to the other state, depending on meaning that the text layout engine isn't expected to be able to figure out.
Re: Be careful what you copy: Invisibly inserting usernames into text
#139How do I see those invisible characters in emacs or vim ? In emacs I thought that whitespace-mode would do the trick but apparently it doesn't.
vim (7.4) seems to display them by default. With my whole vimrc commented out (just to be sure it wasn't a setting I changed), I get this: F or exam ple, I’ve ins erted 10 ze ro-width spa ces in to thi s sentence, c an you tel l? (The is also highlighted a different color than the rest of the text, and acts like a single character when moving the cursor through it. It's really, really obvious.)
Indeed, I copy-pasted in emacs but not in vim, my bad...
Re: Be careful what you copy: Invisibly inserting usernames into text
#140Earlier quoted context omitted.
On forging the identity of someone else, the author did mention it and the workaround is pretty simple (using a secret ID for each user): > There are some caveats to this method of course. For example, if a user knew of the script they could theoretically insert their own zero-width characters and accuse someone else. A better solution would be to insert a unique user ID that is not publicly available instead of the…
If someone manages to determine the secret ID then it fails. What about signing a combination of part of the message (likely some hash) and the user ID. This would create a secret ID, but one which if stolen can be shown to be false since trying to recreate the signature with their ID and the message would fail. Hash collisions between different messages are still a concern, but aren't their known solutions to that p…
Can't you just use a whitelist of allowable characters?