• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • injection attacks on websites means that someone managed to add some unintended part to the website, as if the webserver had sent a different page. So it does allow all things the website could do, no more - no less.
    If I type <style>*{display:none}</style>, that is escaped. If this would get inserted into the website as “cleartext”, it would be valid html that would hide the entire page, turning it blank. Ofc a comment should not be able to do that, so a > in text is changed to something like &⁤gt;
    ![alt text]⁤(http⁤s://link⁤.to/an/image.png) is a syntax to insert an image into the comment, so it is parsed into an <img src="http⁤s://link⁤.to/an/image.png" alt="alt text"> html element. In that insertion the contained text was not properly escaped in some cases, so you could have the image contain valid html which would continue on writing into the website. Basically for the alt text ⁤ ⁤ ⁤ " other attribute="attribute val ⁤ ⁤ ⁤ you would get <img src="http⁤s://link⁤.to/an/image.png" alt="" other attribute="attribute val"> instead of <img src="http⁤s://link⁤.to/an/image.png" alt="&⁤quot; other attribute=&⁤quot;attribute val"> which it should have been. And one of the attributes you can add is javascript that is executed at certain times, so you can inject javascript into the page which can do pretty much everything at that point











  • Can you please make http://shota.nu redirect to https? enabling hsts would also be nice.

    First experience I had was typing it out from memory, seeing the blank nginx page, and looking up the announcement post thinking I had misremembered.

    example nginx config
    server {
        listen 80;
        #server_name shota.nu;
        
        return 301 https://$server_name$request_uri;
    }
    
    server {
        #listen 443 ssl;
        #server_name shota.nu;
        
        # max-age of 15768000 and over will get hsts permanently compiled into some static lists!
        # If you're unsure about maybe disabling it later, reduce it to say 7884000
        add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload" always;
    }
    


    Also you may wanna add server_tokens off; to your html{} block if you don’t want to show off your 3 year old nginx that has been deprecated since 2021.