42
linuxxx
6y

The security blog is up again, I fixed the bug.

Just wondering, why did it work in the first place? I simply required a composer autoloader twice but I've been doing that from the beginning and it didn't play up until last night...

I guess it shall remain a mistery 😞

Comments
  • 3
    Now your feeds give 500 x)
  • 4
    @Forside Mother of god, thanks :|
  • 4
    @Forside Know the cause already, I'll fix that in a second, thanks for reporting! I'm fucking stupid.
  • 4
  • 2
    @linuxxx is this intended? Or is it already fixed? 🤔🤔
  • 3
    @kolaente Which page are you visiting?
  • 3
    @linuxxx "about", from the link on the top on the home page
  • 3
    @kolaente Ahh right, known bug, let me fix that right away :P
  • 3
    @kolaente Aaand fixed, it's just supposed to link to the introduction blog post :)
  • 2
    @linuxxx ahhhhh ok. So the site throws an error if nothing is found?
  • 3
    @kolaente I haven't setup a 404 page yet xD
  • 3
    @linuxxx Well done, but the Introduction does still not appear in the feed. Is this intended?
    Also please add this to your todo list: There's no way to navigate back to the home page from an article.
  • 5
    @Forside That's simply because I haven't added it yet. I have to enter everything manually :). A function to automatically add new posts to the feed is on my todo list as well! And yes, good one!
  • 2
    @linuxxx you're not generating the feed from the posts?🤔🤔🤔
  • 3
    @kolaente Nope. I've got external and 'own' posts (external ones are literally external articles I find interesting/worthy of reading from other sites). I build a tiny form thingy to submit new rss items and rebuild the feed files (last 20 items are shown)
  • 3
    @linuxxx ahhh okaaayyy... But wouldnt it be easier to either automatically add posts to the list or build the list with the posts? (=build two lists, one of the posts and one of external articles and merge them into one)
  • 2
    404 security not found
    <Picture of a dashed-outline brick wall with some burglars giggling as they dash through>
  • 4
    @kolaente As I said above, it's on my todo list ;)

    @Root Hahaha genius idea!
  • 5
    © Belongs to the person who made this website.

    I like that
  • 5
    @BambuSource Thanks haha! Currently writing the first blog post, wondering what people will think :)
  • 2
    @linuxxx you should open a github/gitlab issue tracker, where we can submit feature requests and bug reports, for example the about header is still too high and cut off and the article doesn't have some call-to-action like "Read more.." to indicate that the article actually continues and is clickable 😊
  • 4
    @linuxxx also since you often have to say "its on my todo", maybe consider something like trello (or some OS alternative, if there is?..) to publicly have a todo, so people could check on it (then also link it in the issue tracker template, so people would first check?)
  • 3
    @JoshBent Fun fact - I actually programmed that read more thingy in and then removed it again xD. But yeah good idea, will probs work on that upcoming weekend! Working on the first blog post right now ;), it's a privacy one, would you like a hint? :P
  • 1
    @JoshBent He will publish the source when he cleaned it up. Guess on github or whatever, then we will also have the issue tracker.
  • 2
    @JoshBent That idea is also very good, thanks! I'll put that on my todo list 😜
  • 3
    @Forside On GitLab to be exact :)
  • 1
    @linuxxx Any words on that decision? I am planning to use gitlab to store my private projects (as some kind of backup in case my drives fail) but for publications I am currently using github, just because it's used by virtually everyone.
  • 2
    site was down because of bug and not a DDOS? aww...

    Security sites should only go down when experiencing a security attack it cant handle right? 😁
  • 3
    @linuxxx ofcourse I want a hint :)
  • 4
    @JoshBent "Privacy, I have nothing to hide" ;)
  • 5
    @linuxxx
    "why do you close the bathroom door", "why do you have curtains", I see 😉
  • 3
    @JoshBent Actually very good examples! ;)
  • 3
    @JoshBent Psst, first blog post is up! (not going to do this every time but since you came up with the idea I thought I'd notifiy you ;)
  • 2
    @linuxxx Feedly can't find any posts in the RSS because you are not using encoding="UTF-8". I copied the xml to my server and changed to utf-8 just to try if this was the cause and it directly worked. Would you mind changing that?
  • 3
    @Forside Yes, will do for sure! It's going to be tomorrow though as I'm in bed already just devRanting around. I'm still not entirely better :/. Thanks for the heads up!
  • 2
    @linuxxx Never mind, it also works with the ISO charset on my server. There seems to be something different wrong. No idea what it could be.
  • 2
    @Forside Thing is, you're not the only one where it's going wrong :/
  • 2
    @linuxxx nice, thanks for doing that, going to make sure to read it now.
  • 3
    Can you please put the link here?
    Thanks in advance
  • 1
    @drekhi12 This one? much-security.nl
  • 3
    @Forside thanks that's the one
  • 3
    @linuxxx not sure if somebody mentioned it already, but it came to my mind, you should probably rewrite the blog urls to be without the get parameter, would look more cleaner and also deactivate the server tokens via: "server_tokens off;" in your nginx config.
  • 1
    @JoshBent I agree that getting rid of that get param would make things alot better. Unfortunately I have a feeling that hes not going to fix it XD or who knows maybe theirs a security reason?
  • 1
    @gitlab What exactly would get better? I haven't seen problems in using get parameters yet.
  • 1
    @Forside It just doesn't look right for one, and search engines generally don't parse them nicely/lower ranks
  • 1
    @gitlab I guess you'd suggest replacing it with rewrites? It gave me many headaches before, so I don't mind using it. Also in my eyes get parameters are nothing bad or ugly, whily being easy to use and understand. Don't know much about how search engines work though.
  • 2
    @gitlab "search engines generally don't parse them nicely/lower ranks" thats exactly what I did not mention on purpose, I don't think @linuxxx cares or even wants that anyway?
  • 2
    @Forside that's probably exactly what I meant by saying "you should probably rewrite the blog urls to be without the get parameter"...
  • 1
    @Forside I would personally recommend rewrites yes. At least for search engines. I like to treat get params as variables that change little things and routes and functions. So get params for filters are great, but for post slugs not so much.
  • 2
    I once said you will write a book about "Privacy, I have nothing to hide." and it was close enough, you wrote a blog post about it XD
  • 2
    @JoshBent Good one, only that would mean that I can't share links through the RSS feed either :/.

    The nginx thingy part, what's that?
  • 3
    @Forside I'm already rewriting girl's haha
  • 1
    @linuxxx Is the poor "About" supposed to be squished in the corner there?
  • 2
    @linuxxx why wouldnt you be able to share links? the nginx thing is to deactivate the footer that appears in error messages to get a fingerprint of your server more easier.
  • 2
    @JoshBent How'd I share links when the posts are 'requested' through POST requests? You can't type post variables into the URL :)
  • 3
    @PrivateGER Nope, I 'fixed' it into that by accident 😅
  • 2
    @linuxxx Free the poor "About" :(
  • 1
    @linuxxx via rest api and routing?.. I don't see the problem 😅

    You could for example do following routing:

    GET much-security.nl/post/introduction

    which then gets the post itself from:

    POST much-security.nl/api/get/post

    though getting things via post is not very rest, it should be a get request iirc. (if youre not actually posting things to the server first)
  • 1
    @linuxxx You're rewriting girls? God bless you! Finally someone who makes them more developer friendly. Please integrate a well documented API!
  • 4
    @Forside Mother of autocorrect.... Also, were you the one mentioning the encoding? I set it to UTF-8 now :).

    @PrivateGER the poor thing has been fixed 😊
  • 2
    @JoshBent Why would I want to call an API to get the content instead of just throwing it to screen?
  • 2
    @linuxxx
    It's free (^o^)
  • 2
    @linuxxx 😄 Right, nice! But did you forget to change own.xml? It's still iso, main and external are utf8. Also only on own.xml I get an error in the js console that favicon.ico failed to load 🤔
    But nice new header!
  • 3
    @Forside I have had that for years and still no clue where that ico thingy comes from!

    Will fix that soon and also get ready for a dark theme ;)
  • 2
    @linuxxx you don't have a favicon, thats why chrome throws that error, since it tries to autoload domain.com/favicon.ico
  • 1
    @linuxxx https://stackoverflow.com/questions... it can be either an 16x16 .ico or .png for example
  • 2
    @JoshBent I don't use Chrome, it's a Firefox thing as well then?
  • 2
    @JoshBent @linuxxx But even so, it shouldn't complain about not finding it. Just maybe to make the dev throw in an icon 🤔
  • 1
    @linuxxx well you can check your dev console if it tells you anything, chrome just usually tries to be as informative about errors as possible (be it automated favicon fetching or something else), firefox in the past I encountered suppresses a lot of errors or ignores stuff that didnt work.
  • 1
    @Forside I prefer chrome telling me that to be honest, a website without a favicon is hard to find amongst many tabs
  • 3
    @JoshBent I do use Chromium sometimes and I personally see the exact opposite, hence why I use Firefox for web development mostly instead of Chromium
  • 1
    @linuxxx well chromium vs chrome, I guess 😏
  • 1
    @JoshBent Did you use the firefox developer edition?
  • 3
    @JoshBent I've used Chrome in the past and except for the icons and some colors, I couldn't notice a difference tbh.

    Then, Chromium is literally chrome without proprietary code so yah
  • 1
    @Forside last time I tried - it couldn't even mark the selected sourcecode element in the page, since the rectangles around the elements were always atleast 200px off.
  • 1
    @linuxxx "without proprietary code" so basically without anything that actually matters most likely - never used chromium instead of chrome, just joking around, really.
  • 3
    @JoshBent Well as I said, I've used both next to each other and I didn't notice any difference (same for a friend who I asked to at least try it once). But yah fair enough haha
  • 2
    @linuxxx Hey! Saw your first article, it was a great read. Will you have some sort of comment system on there? I immediately felt like bouncing a couple of things, and realised there was no way to do so.
    If you don't, I'm just gonna have to create a blog so I can start a conversation with you :p
  • 2
    @Synth-Synapses didn't the very first intro blog actually address exactly that?.. 😮
  • 2
    @Synth-Synapses He said he's not going to add a comment system. The sole purpose of the blog will be to spread information, not discussing about the topics.
  • 3
    @JoshBent ...I didn't read that one. huh. Well well. I'll have to email him. Again and again then. :P
  • 2
    @Synth-Synapses just wondering if you mean bouncing a few things in a good or bad way :P
Add Comment