TCP/UDP is also one of those things that unless you're doing VPNs and port forwarding you probably don't give a fuck about the difference. "Oh this service needs UDP? Okay alright whatever."
Maybe someone briefly talked about in some class but all in all it doesn't really matter from an IT perspective all too much (I mean it matters a little if you're doing some wireshark stuff maybe). The real keys unlock when you do software dev and need to know why UDP is different from TCP.
Not knowing it doesn't seem like a deal breaker to me from an IT perspective. If I was interviewing I'd be like "meh oh well, did I like this person? Are they a good fit? "
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
TCP/UDP is also one of those things that unless you're doing VPNs and port forwarding you probably don't give a fuck about the difference. "Oh this service needs UDP? Okay alright whatever."
Maybe someone briefly talked about in some class but all in all it doesn't really matter from an IT perspective all too much (I mean it matters a little if you're doing some wireshark stuff maybe). The real keys unlock when you do software dev and need to know why UDP is different from TCP.
Not knowing it doesn't seem like a deal breaker to me from an IT perspective. If I was interviewing I'd be like "meh oh well, did I like this person? Are they a good fit? "
I believe it was a security-related position the question was being asked for, and it is more relevant in that case than in some others.
TCP/UDP is also one of those things that unless you're doing VPNs and port forwarding you probably don't give a fuck about the difference. "Oh this service needs UDP? Okay alright whatever."
Maybe someone briefly talked about in some class but all in all it doesn't really matter from an IT perspective all too much (I mean it matters a little if you're doing some wireshark stuff maybe). The real keys unlock when you do software dev and need to know why UDP is different from TCP.
Not knowing it doesn't seem like a deal breaker to me from an IT perspective. If I was interviewing I'd be like "meh oh well, did I like this person? Are they a good fit? "
I need to know it because I need to allow specific traffic to my customers and opening more shit than necessary is kinda bad form on my part. But they never know what they need and their IT guys never know what they need and their MSP never knows what they need so I open it all up individually and turn off shit that has no traffic after a few minutes of testing.
TCP/UDP is also one of those things that unless you're doing VPNs and port forwarding you probably don't give a fuck about the difference. "Oh this service needs UDP? Okay alright whatever."
Maybe someone briefly talked about in some class but all in all it doesn't really matter from an IT perspective all too much (I mean it matters a little if you're doing some wireshark stuff maybe). The real keys unlock when you do software dev and need to know why UDP is different from TCP.
Not knowing it doesn't seem like a deal breaker to me from an IT perspective. If I was interviewing I'd be like "meh oh well, did I like this person? Are they a good fit? "
I need to know it because I need to allow specific traffic to my customers and opening more shit than necessary is kinda bad form on my part. But they never know what they need and their IT guys never know what they need and their MSP never knows what they need so I open it all up individually and turn off shit that has no traffic after a few minutes of testing.
Yeah, you're a WISP so very network related right?
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
TCP/UDP is also one of those things that unless you're doing VPNs and port forwarding you probably don't give a fuck about the difference. "Oh this service needs UDP? Okay alright whatever."
Maybe someone briefly talked about in some class but all in all it doesn't really matter from an IT perspective all too much (I mean it matters a little if you're doing some wireshark stuff maybe). The real keys unlock when you do software dev and need to know why UDP is different from TCP.
Not knowing it doesn't seem like a deal breaker to me from an IT perspective. If I was interviewing I'd be like "meh oh well, did I like this person? Are they a good fit? "
I need to know it because I need to allow specific traffic to my customers and opening more shit than necessary is kinda bad form on my part. But they never know what they need and their IT guys never know what they need and their MSP never knows what they need so I open it all up individually and turn off shit that has no traffic after a few minutes of testing.
Yeah, you're a WISP so very network related right?
Right, sorry, that was the point I was making, but I did it poorly.
Interview time is much better spent figuring out if you're a gaping asshole. I can teach you how to fix all our shit, or you can google most of it. You can't google how to not be an insufferable cockwipe.
Or well, you can but figuring out that ICMP traffic doesn't have a port number is a much faster google search than "do my coworkers hate me?", so I'll take the person I can stand.
Interview time is much better spent figuring out if you're a gaping asshole. I can teach you how to fix all our shit, or you can google most of it. You can't google how to not be an insufferable cockwipe.
Or well, you can but figuring out that ICMP traffic doesn't have a port number is a much faster google search than "do my coworkers hate me?", so I'll take the person I can stand.
Interview time is much better spent figuring out if you're a gaping asshole. I can teach you how to fix all our shit, or you can google most of it. You can't google how to not be an insufferable cockwipe.
Or well, you can but figuring out that ICMP traffic doesn't have a port number is a much faster google search than "do my coworkers hate me?", so I'll take the person I can stand.
Ehhhh, yes, I mostly agree, but when I came into my current position, my IT department was full of people who lacked technical knowledge but had good "soft skills"
Guess what? There were only two people who were actually getting anything done, they were burned out and overworked, and producing shoddy output not because they were incompetent but because they were carrying the whole team. It was like a hospital where everybody had good bedside manner but nobody had actually ever been to medical school.
You can shore up some technical knowledge gaps but it's easy to too far in the other direction.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
I'm not sure if having a really abrasive personality or literally cannot figure out how to do your job is technically worse. Probably the latter.
At least with the graybeard you know they're going to at least accomplish shit even if you can't really talk to them and you have to email a list of tasks. The other one will make you pull your fucking hair out because they're just chatting with George and Cathy in accounting for 4 hours but can't be assed to figure out that the network cable at their local switch was cut off from the main trunk or something stupid.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
Interview time is much better spent figuring out if you're a gaping asshole. I can teach you how to fix all our shit, or you can google most of it. You can't google how to not be an insufferable cockwipe.
Or well, you can but figuring out that ICMP traffic doesn't have a port number is a much faster google search than "do my coworkers hate me?", so I'll take the person I can stand.
Man... Someone manages to google "how to not be a douche", and manages to DO it? That dude weird, but I wanna work with that dude. He can probably get shit done.
I'm not sure if having a really abrasive personality or literally cannot figure out how to do your job is technically worse. Probably the latter.
At least with the graybeard you know they're going to at least accomplish shit even if you can't really talk to them and you have to email a list of tasks. The other one will make you pull your fucking hair out because they're just chatting with George and Cathy in accounting for 4 hours but can't be assed to figure out that the network cable at their local switch was cut off from the main trunk or something stupid.
Eddie the Extrovert has a role, too. He can do the support theater that gives end users the warm fuzziest while Greybeard the Wizard gets shit done. That's uncharitable but in all seriousness we do need a balance of soft and hard skills.
That said, Greybeard the Wizard has to remember to:
1) Document his shit
2) Coach junior employees
3) Use comments/naming-conventions/etc so his shit is readable
4) Stick to best practices where possible
5) Learn new technologies and methodologies
As long as Greybeard does that stuff, basically do his work in a way that other people can step in when he inevitably sails into the west, then I don't give a shit how much of a BOFH he is.
But too many Greybeards don't do that shit. I've encountered too many who give literally zero thought to how other people might deal with his work product. He leaves and all you can do is forklift all his tech out and start over.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
the "no true scotch man" fallacy.
+5
thatassemblyguyJanitor of Technical Debt.Registered Userregular
TCP/UDP is also one of those things that unless you're doing VPNs and port forwarding you probably don't give a fuck about the difference. "Oh this service needs UDP? Okay alright whatever."
Maybe someone briefly talked about in some class but all in all it doesn't really matter from an IT perspective all too much (I mean it matters a little if you're doing some wireshark stuff maybe). The real keys unlock when you do software dev and need to know why UDP is different from TCP.
Not knowing it doesn't seem like a deal breaker to me from an IT perspective. If I was interviewing I'd be like "meh oh well, did I like this person? Are they a good fit? "
It's always a deal breaker.... when the ask, "Tell me the difference between TCP and UDP." is NOT answered in the form of an interpretive dance.
I need to troubleshoot Sophos on a PC. We want to try it outside the firewall. They told me it was a laptop, so I bring along a wifi hotspot. It's not a laptop, it's a desktop.
Great... Okay, well, the hotspot can do usb tethering. Except whoever used it last at my company forgot to put the microUSB cable in the box.
Great... Okay, well, I have a multi-adapter that has microUSB. Except it apparently doesn't allow for data transfer, just charging, so it won't work for tethering.
Great... Okay, well, I found someone at the client's office who has a droid and borrowed their cable. Except the hotspot is apparently old enough that when you install the driver, it bluescreens windows 10.
Great... Okay, well, I can do a USB tether on my iPhone. Except the simplest way to install the driver for the PC to recognize the phone is to install iTunes.
Great... Okay, well, fuck it, I'll install it and then remove it when I'm done. Fine. Except my iphone is a 6s and needs USB 2.0 for tethering and the PC only has USB 3.0 and my phone wont tether on 2.0.
I've been on site for 2 hours and I haven't even gotten the fucking PC an outside internet connection yet.
"You guys shut off my Internet, but I've been paying!"
"I know you've been paying, ma'am, and I also know we haven't shut you off, there's likely some other issue at play. Can you tell me what you're trying to do and see if I can help?"
"Well when I boot up my computer it says 'Disk boot failure'"
I need to troubleshoot Sophos on a PC. We want to try it outside the firewall. They told me it was a laptop, so I bring along a wifi hotspot. It's not a laptop, it's a desktop.
Great... Okay, well, the hotspot can do usb tethering. Except whoever used it last at my company forgot to put the microUSB cable in the box.
Great... Okay, well, I have a multi-adapter that has microUSB. Except it apparently doesn't allow for data transfer, just charging, so it won't work for tethering.
Great... Okay, well, I found someone at the client's office who has a droid and borrowed their cable. Except the hotspot is apparently old enough that when you install the driver, it bluescreens windows 10.
Great... Okay, well, I can do a USB tether on my iPhone. Except the simplest way to install the driver for the PC to recognize the phone is to install iTunes.
Great... Okay, well, fuck it, I'll install it and then remove it when I'm done. Fine. Except my iphone is a 6s and needs USB 2.0 for tethering and the PC only has USB 3.0 and my phone wont tether on 2.0.
I've been on site for 2 hours and I haven't even gotten the fucking PC an outside internet connection yet.
I need to troubleshoot Sophos on a PC. We want to try it outside the firewall. They told me it was a laptop, so I bring along a wifi hotspot. It's not a laptop, it's a desktop.
Great... Okay, well, the hotspot can do usb tethering. Except whoever used it last at my company forgot to put the microUSB cable in the box.
Great... Okay, well, I have a multi-adapter that has microUSB. Except it apparently doesn't allow for data transfer, just charging, so it won't work for tethering.
Great... Okay, well, I found someone at the client's office who has a droid and borrowed their cable. Except the hotspot is apparently old enough that when you install the driver, it bluescreens windows 10.
Great... Okay, well, I can do a USB tether on my iPhone. Except the simplest way to install the driver for the PC to recognize the phone is to install iTunes.
Great... Okay, well, fuck it, I'll install it and then remove it when I'm done. Fine. Except my iphone is a 6s and needs USB 2.0 for tethering and the PC only has USB 3.0 and my phone wont tether on 2.0.
I've been on site for 2 hours and I haven't even gotten the fucking PC an outside internet connection yet.
Whelp, Sophos mystery solved. It's the firewall. Install while on client's internal network: fails. Install while on mobile hotspot: works. Pretty cut and dried.
Firewall team assured me two weeks ago that it was not blocking, filtering, or inspecting any Sophos related traffic.
Sophos assured me two weeks ago that the installation does not attempt to connect to the internet in any way.
I get to tell two people that they're objectively, demonstrably wrong. Things are looking up.
TCP/UDP is also one of those things that unless you're doing VPNs and port forwarding you probably don't give a fuck about the difference. "Oh this service needs UDP? Okay alright whatever."
Maybe someone briefly talked about in some class but all in all it doesn't really matter from an IT perspective all too much (I mean it matters a little if you're doing some wireshark stuff maybe). The real keys unlock when you do software dev and need to know why UDP is different from TCP.
Not knowing it doesn't seem like a deal breaker to me from an IT perspective. If I was interviewing I'd be like "meh oh well, did I like this person? Are they a good fit? "
It's always a deal breaker.... when the ask, "Tell me the difference between TCP and UDP." is NOT answered in the form of an interpretive dance.
If someone answers that in the form of dance, that's a hire on the spot.
F3, Shift+tab, del, space, F3, Shift+tab, del, space, F3, Shift+tab, del, space, F3, Shift+tab, del, space, F3, Shift+tab, del, space, F3, Shift+tab, del, space, F3, Shift+tab, del, space
Can I ask why Secure Shell makes it better? Is it just because its simpler/more bare bones?
Basically, there are three protocols that people colloquially call "FTP:"
FTP, which is unencrypted and typically on port 21
FTPS, which is encrypted and can be either port 21 or 990, and may require an additional port range for data transfer.
SFTP, which isn't actually FTP at all, it's SSH with file transfer functions. Typically on port 22.
Another way to look at it:
FTPS = FTP with encryption stapled to it
SFTP = SSH with file transfer stapled to it
Assume that you want encryption in motion. That eliminates FTP.
Given the choices between SFTP and FTPS, the disadvantages of FTPS are:
Certificate-based. If your cert expires or is self-signed, you might not be able to establish a connection. (Most clients work around this by just ignoring certificate validity by default.)
Encryption can be either implicit or explicit, which changes your port assignment and client settings, and may require more ports to be opened. This increases the complexity of troubleshooting on the client side.
FTPS is only for file transfers. SFTP, if it's riding on a full SSH server, can do all the other nifty stuff that SSH can do. (Or you can lock it down to just file transfers.)
SFTP can use SSH keys to authenticate which is sometimes preferable for automation.
FTPS needs to advertise it's WAN address to the client, which can make disaster recovery & failover a little more complicated. You can't just spin up an FTPS server in a new datacenter on a new public subnet, point a CNAME at it, and expect it to work. Changing the WAN address for advertisement is rarely a big deal, but it is an extra step in a failover scenario.
None of these are deal-breakers for FTPS but they do make SFTP a little easier to work with.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
Windows is adopting a lot of linux strategies lately. I fully expect windows to become a linux distro with a PE layer over top and basically you buy that form microsoft instead. I think that's what they're prototyping some concepts with .NET core to see the viability of it.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
Windows is adopting a lot of linux strategies lately. I fully expect windows to become a linux distro with a PE layer over top and basically you buy that form microsoft instead. I think that's what they're prototyping some concepts with .NET core to see the viability of it.
Yeah. I do like this direction they're taking.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
I need to troubleshoot Sophos on a PC. We want to try it outside the firewall. They told me it was a laptop, so I bring along a wifi hotspot. It's not a laptop, it's a desktop.
Great... Okay, well, the hotspot can do usb tethering. Except whoever used it last at my company forgot to put the microUSB cable in the box.
Great... Okay, well, I have a multi-adapter that has microUSB. Except it apparently doesn't allow for data transfer, just charging, so it won't work for tethering.
Great... Okay, well, I found someone at the client's office who has a droid and borrowed their cable. Except the hotspot is apparently old enough that when you install the driver, it bluescreens windows 10.
Great... Okay, well, I can do a USB tether on my iPhone. Except the simplest way to install the driver for the PC to recognize the phone is to install iTunes.
Great... Okay, well, fuck it, I'll install it and then remove it when I'm done. Fine. Except my iphone is a 6s and needs USB 2.0 for tethering and the PC only has USB 3.0 and my phone wont tether on 2.0.
I've been on site for 2 hours and I haven't even gotten the fucking PC an outside internet connection yet.
I try not to listen to people's conversations when I'm at client's sites, but sometimes they forget I'm here cause I sit in empty cubes and meeting rooms and work quietly.
I was mostly tuning out the people in the office next door, something about Epsom salts and cracked skin and lotions and "THIS IS WHY I DON'T STICK MY HAND UP MY OWN ASS".
Posts
Maybe someone briefly talked about in some class but all in all it doesn't really matter from an IT perspective all too much (I mean it matters a little if you're doing some wireshark stuff maybe). The real keys unlock when you do software dev and need to know why UDP is different from TCP.
Not knowing it doesn't seem like a deal breaker to me from an IT perspective. If I was interviewing I'd be like "meh oh well, did I like this person? Are they a good fit? "
I believe it was a security-related position the question was being asked for, and it is more relevant in that case than in some others.
I need to know it because I need to allow specific traffic to my customers and opening more shit than necessary is kinda bad form on my part. But they never know what they need and their IT guys never know what they need and their MSP never knows what they need so I open it all up individually and turn off shit that has no traffic after a few minutes of testing.
Yeah, you're a WISP so very network related right?
Right, sorry, that was the point I was making, but I did it poorly.
Or well, you can but figuring out that ICMP traffic doesn't have a port number is a much faster google search than "do my coworkers hate me?", so I'll take the person I can stand.
https://www.businessinsider.com/signs-your-coworkers-secretly-hate-you-2015-9
Ehhhh, yes, I mostly agree, but when I came into my current position, my IT department was full of people who lacked technical knowledge but had good "soft skills"
Guess what? There were only two people who were actually getting anything done, they were burned out and overworked, and producing shoddy output not because they were incompetent but because they were carrying the whole team. It was like a hospital where everybody had good bedside manner but nobody had actually ever been to medical school.
You can shore up some technical knowledge gaps but it's easy to too far in the other direction.
the "no true scotch man" fallacy.
At least with the graybeard you know they're going to at least accomplish shit even if you can't really talk to them and you have to email a list of tasks. The other one will make you pull your fucking hair out because they're just chatting with George and Cathy in accounting for 4 hours but can't be assed to figure out that the network cable at their local switch was cut off from the main trunk or something stupid.
Man... Someone manages to google "how to not be a douche", and manages to DO it? That dude weird, but I wanna work with that dude. He can probably get shit done.
Eddie the Extrovert has a role, too. He can do the support theater that gives end users the warm fuzziest while Greybeard the Wizard gets shit done. That's uncharitable but in all seriousness we do need a balance of soft and hard skills.
That said, Greybeard the Wizard has to remember to:
1) Document his shit
2) Coach junior employees
3) Use comments/naming-conventions/etc so his shit is readable
4) Stick to best practices where possible
5) Learn new technologies and methodologies
As long as Greybeard does that stuff, basically do his work in a way that other people can step in when he inevitably sails into the west, then I don't give a shit how much of a BOFH he is.
But too many Greybeards don't do that shit. I've encountered too many who give literally zero thought to how other people might deal with his work product. He leaves and all you can do is forklift all his tech out and start over.
the "no true scotch man" fallacy.
It's always a deal breaker.... when the ask, "Tell me the difference between TCP and UDP." is NOT answered in the form of an interpretive dance.
I need to troubleshoot Sophos on a PC. We want to try it outside the firewall. They told me it was a laptop, so I bring along a wifi hotspot. It's not a laptop, it's a desktop.
Great... Okay, well, the hotspot can do usb tethering. Except whoever used it last at my company forgot to put the microUSB cable in the box.
Great... Okay, well, I have a multi-adapter that has microUSB. Except it apparently doesn't allow for data transfer, just charging, so it won't work for tethering.
Great... Okay, well, I found someone at the client's office who has a droid and borrowed their cable. Except the hotspot is apparently old enough that when you install the driver, it bluescreens windows 10.
Great... Okay, well, I can do a USB tether on my iPhone. Except the simplest way to install the driver for the PC to recognize the phone is to install iTunes.
Great... Okay, well, fuck it, I'll install it and then remove it when I'm done. Fine. Except my iphone is a 6s and needs USB 2.0 for tethering and the PC only has USB 3.0 and my phone wont tether on 2.0.
I've been on site for 2 hours and I haven't even gotten the fucking PC an outside internet connection yet.
"I know you've been paying, ma'am, and I also know we haven't shut you off, there's likely some other issue at play. Can you tell me what you're trying to do and see if I can help?"
"Well when I boot up my computer it says 'Disk boot failure'"
:rotate:
the "no true scotch man" fallacy.
the "no true scotch man" fallacy.
Firewall team assured me two weeks ago that it was not blocking, filtering, or inspecting any Sophos related traffic.
Sophos assured me two weeks ago that the installation does not attempt to connect to the internet in any way.
I get to tell two people that they're objectively, demonstrably wrong. Things are looking up.
Having evaluated all the enterprise Dropbox clones in the universe, I can say with confidence that no one should ever share files
We're a SaaS company that require access to the customer's domain.
It's always WAF.
Can I ask why Secure Shell makes it better? Is it just because its simpler/more bare bones?
I wish Microsoft had a native SFTP server and client
Microsoft gives you FTPS on IIS which is fine, but the lack of SFTP is a problem sometimes
We just use WinSCP for the client because it plays nice with automation
the "no true scotch man" fallacy.
I like box.com, personally
the "no true scotch man" fallacy.
If someone answers that in the form of dance, that's a hire on the spot.
Guess what I'm doing
XBL:Phenyhelm - 3DS:Phenyhelm
Basically, there are three protocols that people colloquially call "FTP:"
FTP, which is unencrypted and typically on port 21
FTPS, which is encrypted and can be either port 21 or 990, and may require an additional port range for data transfer.
SFTP, which isn't actually FTP at all, it's SSH with file transfer functions. Typically on port 22.
Another way to look at it:
FTPS = FTP with encryption stapled to it
SFTP = SSH with file transfer stapled to it
Assume that you want encryption in motion. That eliminates FTP.
Given the choices between SFTP and FTPS, the disadvantages of FTPS are:
Certificate-based. If your cert expires or is self-signed, you might not be able to establish a connection. (Most clients work around this by just ignoring certificate validity by default.)
Encryption can be either implicit or explicit, which changes your port assignment and client settings, and may require more ports to be opened. This increases the complexity of troubleshooting on the client side.
FTPS is only for file transfers. SFTP, if it's riding on a full SSH server, can do all the other nifty stuff that SSH can do. (Or you can lock it down to just file transfers.)
SFTP can use SSH keys to authenticate which is sometimes preferable for automation.
FTPS needs to advertise it's WAN address to the client, which can make disaster recovery & failover a little more complicated. You can't just spin up an FTPS server in a new datacenter on a new public subnet, point a CNAME at it, and expect it to work. Changing the WAN address for advertisement is rarely a big deal, but it is an extra step in a failover scenario.
None of these are deal-breakers for FTPS but they do make SFTP a little easier to work with.
the "no true scotch man" fallacy.
I literally went through that same exercise in January and came to the same conclusion.
It actually exists! Alongside the ssh support Microsoft put together via porting OpenSSH.
Oh this is excellent. I had no idea. Thank you!
the "no true scotch man" fallacy.
Yeah. I do like this direction they're taking.
the "no true scotch man" fallacy.
Your dreams are hilarious and sad.
I'm sure it's coming. MS love linux now, so getting their core killer app (office) to run on it would open up any remaining markets out there.
This is a clickable link to my Steam Profile.
I was mostly tuning out the people in the office next door, something about Epsom salts and cracked skin and lotions and "THIS IS WHY I DON'T STICK MY HAND UP MY OWN ASS".
*RECORD SCRATCH*