News for hackers. Stuff that matters.

vtsingaras

Re:DoH: Anti-Competitive and Network Neutrality Aspects on Thursday December 05, 2019 @01:27AM (#21710374)
But the original post makes not mention of anything other than non-optimal answers.

Before comparing various methods of contacting a recursor you have to decide what your threat model is; does it include your ISP snooping on you? If so then an encrypted transport of your dns queries is mandatory. If it doesn’t, stick with DNS53.

Re:DoH: Anti-Competitive and Network Neutrality Aspects on Wednesday December 04, 2019 @07:22AM (#21701551)
The point presented by the post is plain wrong, people were using non-ISP recursors for a long time already and this was not problem due to the fact that EDNS Client Subnet has been a thing for a while now.

The problem mentioned in the post is specific to Cloudflare, as they do not support EDNS Client Subnet anyway, even over plain UDP53

more reading: https://www.samknows.com/blog/dns-over-https-performance

Why is this submission worthy? Apart from the cringey Engrish, that post is basically this:

"How to fix your computor: 1. Click dis 2. CLick dat. 3. Congratz your computor performs $100% better now 4. Click advanced error detail, click OK 5. ??? 6. Prfot!1!!

Re:Let's Encrypt now holds 35% of the market on Tuesday November 21, 2017 @06:18AM (#15747152)
- Opaque and uncommon/needlessly-unfamiliar command-line management toolkit (seriously, what is so difficult about 'output text, receive text as input' in 2017?)

^^^ PowerShell solves this. (AD,DNS,IIS,Exchange,DPM,Hyper-V...)

- I cannot, yet, fully manage a Microsoft host from the CLI. What I consider to be 'fully managed' revolves around: installing software, updating software, adding/removing/'managing' users, setting up basic server-like features such as simple firewall rules, viewing common log-files ('user X logged in', 'software Y tried to execute Z task, the result was A'), starting/stopping/troubleshooting daemons, etc

^^^ Solved by PowerShell (You can even install a GUI-less version of WS2016 and all these will work.)

- Pick a major config-management system (my direct experience is with Puppet/Chef/Ansible/Salt). Configuring them to play nice with Windows-anything is an order of magnitude more difficult than even the most baroque *nix-like operating system.

^^^ I use Ansible Tower to manage a mixed WS and Linux fleet with great success, I only need to run `kinit` once every day to obtain a ticket, all logins afterwards are passwordless.

Re:OVH Incident in Strasbourg on Thursday November 09, 2017 @05:25AM (#15661291)
Exactly that, we too suffered a power loss at our DC that was due to faults in the power supervising and switch-over circuits; we test both generators weekly.
Re:Ask HN: How to get a job when you suck at coding? on Wednesday June 14, 2017 @03:15AM (#14551166)
'Facebook is just a php website'

....... ok then

Re:KARL – kernel address randomized link (OpenBSD) on Tuesday June 13, 2017 @07:41AM (#14544072)
```within a compilation unit```

It's the compiler that needs to do the job.

Just add '.keys' after the profile URL. eg. for me this lists my ssh keys https://github.com/vtsingaras.keys
Re:Ask HN: Who is hiring? (January 2017) on Tuesday January 03, 2017 @01:38PM (#13311677)
You may wish to look into the workable form, the 'Were you referred by a Gitlab employee' field is marked as mandatory. (It kept throwing "can't be blank")
Re:Show HN: Whosfiring on Tuesday November 15, 2016 @05:28AM (#12956953)
Getting spammed at the moment...
Re:TLS Everywhere, not https: URIs (2015) on Monday August 08, 2016 @01:41AM (#12245696)
The problem with opportunistic TLS is that while it protects from wide-scale DPI it doesn't protect against MITM. Personally I think that the effort that would be put to implementing opportunistic TLS in all web servers and browsers would be better put to migrating all web applications to HTTPS only.