News for hackers. Stuff that matters.
Re:Falsehoods programmers believe about networks by rvense on Monday October 24, 2016 @03:39AM (#12777219)
It'd be great if someone wrote three lines explaining why one would believe each of those, why it's wrong, and why that's important.
Re:Falsehoods programmers believe about networks by developer2 on Monday October 24, 2016 @03:55AM (#12777258)
And by "it'd be great", what you really mean is "the article is completely useless without them". Half of the items are "no shit"; another 20% is "huh?", and the remaining are "that might be interesting to learn more about - but with no additional information, I don't even have enough keywords to Google to find out more".
Re:Falsehoods programmers believe about networks by chris_wot on Monday October 24, 2016 @04:49AM (#12777421)
You aren't using Google effectively enough then.
Re:Falsehoods programmers believe about networks by thecatspaw on Monday October 24, 2016 @06:31AM (#12777753)
>It's an internal web app -- outsiders won't be able to discover where it is (@biosshadow)

explain

Re:Falsehoods programmers believe about networks by chris_wot on Monday October 24, 2016 @06:45AM (#12777791)
If it has a public IP address, it can be discovered.
Re:Falsehoods programmers believe about networks by extra88 on Monday October 24, 2016 @07:03AM (#12777855)
Even if it doesn't have a public ip address, its existence can be discovered if an organization's DNS isn't separated into public and private.

Then there are all the ways an employee can inadvertently or intentionally make its existence public.

Re:Falsehoods programmers believe about networks by chris_wot on Monday October 24, 2016 @09:40AM (#12778637)
Re:Falsehoods programmers believe about networks by Somasis on Monday October 24, 2016 @04:34AM (#12777377)
This is effectively the problem with all of these "things programmers assume" articles: they give no solutions and effectively just moan about possible problems.
Re:Falsehoods programmers believe about networks by dllthomas on Monday October 24, 2016 @05:16AM (#12777513)
"Things people writing Things Programmers Assume articles assume..."
Re:Falsehoods programmers believe about networks by TheRealEdAbbey on Monday October 24, 2016 @06:34AM (#12777761)
They honestly read like clickbait: "10 myths programmers always assume - #6 will SHOCK you!"
Re:Falsehoods programmers believe about networks by Vendan on Monday October 24, 2016 @04:01AM (#12777274)
I tried to write up a little about the ones that I know something about, here it is:

  Data on the network cannot be altered.
False, if something goes through another device, it can be altered. Important because, well, man in the middle.

  Encrypted data on the network cannot be altered.
Same as the above. Harder, but still doable

  Data cannot be accidentally corrupted, because TCP has checksums and Ethernet has CRCs
This is about like saying "only 1 bit can be flipped at once, so parity checking will always catch it"

  If it's inside my perimeter firewall, that means I have total control over it (@armorguy)
Similar to the top ones, still harder, but it's a weak point if someone gets into your perimeter at all.

  Packets arrive in the order in which they were sent.
Completely false, though TCP will reorder them back to the original order for you.

  If you can't ping the target, then it doesn't exist. (@jjarmoc)
  
Trivial to make a host not respond to pings

  If you can ping the target, then it does exist.
  
Again, trivial to make a router or any device respond to pings for a lot of IPs

  TCP RSTs come from end-nodes.
Devices in the middle sending RSTs is really common, google "comcast rst packets"

  Bytes must be "swapped" from the network byte-order to the host CPU byte-order.
IP/TCP and such protocol bytes must be swapped. The only thing that cares at the application layer is the application code, it can just say "everything is little endian" and be done with it.

  It's an internal web app -- outsiders won't be able to discover where it is (@biosshadow)
  
if this is about a "exposed under an obscure name", the tools like fierce can probe for it. If it's exposed to the internet at all, consider it under attack at all times.

  The DHCP address will be the same after a reboot (@shewfig)
Not necessarily true, depends on the DHCP server and such.

  The DHCP address will remain the same until the next reboot.
You get a lease time, OBSERVE IT. Don't just keep using it cause you say "this is mine still!"

  Well, it'll last a long time between changes
One culprit is coffeeshops, there have been reports of coffeeshops with 30 minute lease times. I've seen cable modems hand out 30 second leases, but that was when it was still trying to connect to the cable side, so it wanted the computer to keep checking back

  The DHCP server and local router are the same (@schrotthaufen)
  
Not at all a requirement, and would cause your packets to go off into nowhere if you tried to rely on it.
Re:Falsehoods programmers believe about networks by dllthomas on Monday October 24, 2016 @05:15AM (#12777509)
> The only thing that cares at the application layer is the application code,

True, but...

> it can just say "everything is little endian" and be done with it.

... doesn't quite follow. If you're blitting integers directly, your code will break on either a big- or little-endian boxes. Better to pick a standard encoding and always serialize/deserialize properly whatever that means. That standard encoding may be little-endian (maybe better than big-endian - such systems are overwhelmingly more common on the desktop/server) or may be some packed representation. But ideally you could change the representation without changing application code other than the serialization/deserialization itself (which may well live in a library).

Re:Falsehoods programmers believe about networks by saurik on Monday October 24, 2016 @07:09AM (#12777878)
I had taken that to read that there are programs in the wild that assume hosts are little endian and always "swap" bytes as opposed to converting between the two orders (which might be a no-op on a big endian system).
Re:Falsehoods programmers believe about networks by dllthomas on Monday October 24, 2016 @11:36AM (#12779740)
Yeah, that's probably the case, and quite possibly what was intended. I think my elaboration deals fine with that case too, though.
Re:Falsehoods programmers believe about networks by crottypeter on Monday October 24, 2016 @06:09AM (#12777695)
Also : Browser history is synced via 'the cloud'

>> It's an internal web app -- outsiders won't be able to discover where it is (@biosshadow)

>if this is about a "exposed under an obscure name", the tools like fierce can probe for it. If it's exposed to the internet at all, consider it under attack at all times.

Re:Falsehoods programmers believe about networks by dllthomas on Monday October 24, 2016 @05:02AM (#12777462)
> TCP will reorder them back to the original order for you.

And of course even that's only true within a single connection.

Re:Falsehoods programmers believe about networks by vlodiag on Monday October 24, 2016 @03:40AM (#12777222)
Yeah I agree post seems to be a bit too dry. I would like that too.