search

letsgetrandy / DICSS

Directly injected CSS
http://letsgetrandy.github.io/DICSS/
MIT License
1.35k stars 72 forks source link

DICCS injects self-replicating code when not using a wrapper #25

Open LegoStormtroopr opened 9 years ago

LegoStormtroopr commented 9 years ago

I first used DICSS about 8 and a half months ago. I followed the directions and thought it'd be safe to use DICCS without a wrapper.

I was wrong!!

DICCS injected some self-replicating code into my site several months back. It's caused my page size to increase dramatically and its caused some additional logging so I need to excuse myself to empty the logs several times a day. I sometimes even have to get up during the night to empty my logs!

The page pize increases are most noticable in my body but I've also noticed swelling in my footers.

At this point I've stopped using DICCS, but the code is still replicating. Are there any tips to remove the code?

ghost commented 9 years ago

There needs to be something that can be applied retroactively to stop the replication on it's early stages.

b4x commented 9 years ago

This issue is already addressed in #19. Using DICSS without a wrapper gives unwanted results such as stdin err. Always!, Always! use DICSS with the wrapper! The only time it's safe to use DICSS without the wrapper is if both ends are infection free.

fetalerror commented 9 years ago

I think refactoring the APIs may help. If DICSS didn't inject its payload upon putIn there would be an opportunity to pullout before injection occurred. I think this may also improve the client-side experience.

NitsuaRevaew commented 9 years ago

You can simply abort the program.