61–70 of 76 posts
It'd be nice to be gender neutral :)
It'd be nicer if people could stop derailing interesting threads with their gender politics and pedantry.
Earlier quoted context omitted.
Check your monitor gamma and white level using something like this: http://www.lagom.nl/lcd-test/gamma_calibration.php You might be crushing whites, or just have incorrect gamma.
Thanks for the link! I've seen the site before but never thought of testing my screen when I got my new laptop. It's very difficult to tell, though. The gamma varies between 1.9 and 2.3 (roughly) depending on the angle at which I look at my screen. Every time I sit this will be different. Opening the article again, it also depends where I look: when tilting my laptop back a bit, the text appears darker (even black if…
Earlier quoted context omitted.
Really? While talking in a context of a specific post, written by a male?
Not to presume which gender OP identifies with, but if you take a look at their GitHub profile, you'd probably come to the conclusion the the writer is not male. Since the specific context matters to you, would you now suggest the parent of this thread then change the pronoun to "she" instead?
Answering your question: would he, or me, or other poster know the gender of author while writting about author -> we should use proper form. If no prior knowledge is present: it does not matter to me, and I consider it not worth mentioning or correcting.
Earlier quoted context omitted.
It'd be nicer if people could stop derailing interesting threads with their gender politics and pedantry.
I took it as a suggestion not to assume the author is a male so as not to embarrass yourself when it turns out they aren't, as a bare minimum of investigation would have revealed. Since when is basic politeness "gender politics"?
Nice. What first revealed me the hidden complexity of SSH was typing this during a live SSH session: ~? Which show you the SSH supported escape sequences.
Telnet had something similar.
It's interesting that "The transport protocol doesn’t cover who sends their banner first". It'd be good if I could configure my server to keep quiet until the client identifies itself as an SSH client. I run it on an unusual port and it gets scanned frequently. sshguard helps but I'd prefer it wasn't announcing to any client that it is an ssh server.
How does sshguard compare to fail2ban?
It's interesting that "The transport protocol doesn’t cover who sends their banner first". It'd be good if I could configure my server to keep quiet until the client identifies itself as an SSH client. I run it on an unusual port and it gets scanned frequently. sshguard helps but I'd prefer it wasn't announcing to any client that it is an ssh server.
This is unpopular, but you could implement port knocking.
Now the rest of the world doesn't even see your sshd - on any port. I love the idea and have implemented it everywhere that it's practical.
I really like stories like this where somebody was overly curious about something and instead of just reading about it, he takes it apart and puts it back together to gain the kind of knowledge you will never find in a book/blog post.
> takes it apart and puts it back together to gain the kind of knowledge you will never find in a book/blog post. Interestingly, the author still worked a lot with the docs (RFCs), not just with the software itself. I believe this is important for any hands-on activity. Even though the documentation isn't your starting point, and may be too cumbersome and badly structured, sooner or later you should go back to them,…
It'd be nice to be gender neutral :)