@asadz I wouldn't say I thought the answer we great.... For my voting standards it was to much someone else's work, but clearly not a case of plagiarism.
When I'm working an answer that is properly answered entirely by another source, say most of my work in the PCI-DSS tag, I try to provide context and explain.
It is one thing to say, "No, item 2.2.5 says that is exempted." That's a pretty lame, if factually correct, answer.
It is better to try to explain why it is exempted and good it specifically admitted to their situation.
That goes back to @Thomas' comments about communicating clearly being at least as important as being right.
What you are saying is correct but the question is "Is there any advantage in changing the SSH port, I've seen people do that, but I can't seem to find the reason why?" and not "Can I just change the SSH port without going through change management"
If you analyse it, bot me and @ScottPack are talking about the immediate down and up sides of changing the SSH port. What you are talking about is something completely different IMO.
but i don't see Op mentioning about this in his post
ops
i need coffee lol
i thought u mean on technical levels
sometimes on a switch when these ports flips / led lights go on / off its called port / led flippings
i mis-read u
i appologize @LucasKauffman
i'm not talking different my approach is different
its all management and decision making
when you have unregulated change which allowed the port to do this; we are not just talking about some change in functionality at worse it can mean a attack preparation for disgruntled employee to cover his tracks
@asadz If I may be so bold as to summarize. The question asked "Should I change my SSH port?" ScottPack, Lucas, and Jamie answered with various details of the implication of changing the SSH port are. Your answer was about your company's policy. Valid, certainly, but completely irrelevant to the question, and localized to people who work for your company.
@asadz No, I did read his comment. But again, your answer wasn't about the difference between a personal web server and a corporate environment in any technical sense, it was about your company's policy. I agree change management is important in a corporate environment, but not an answer to "Should I change my SSH port?"
@asadz I can't help how you feel, but speaking for myself, that's not true. I want to help you improve your answers (from my perspective) because I feel that's beneficial to the site as a whole, so I'll absolutely provide constructive criticism, but I certainly don't dislike you.
@asadz I think the difference is that we certainly understand your perspective. The concern is that it isn't applicable to the question as asked. Your answer would definitely apply to the question, "I work in an environment where changes are strictly controlled and frowned upon. How should I go about determining if changing the default SSH port fits within our change process?"
@asadz His imagination doesn't come into it. His question had nothing to do with navigating a change management process it was entirely to do with the technical reasons behind changing a default setting.
Also, for the record, if there's somebody that I don't like in chat I click the little block button so that their messages don't show up on my screen. Which also means I don't talk to them and given heartfelt advice on what I think makes for higher quality contributions.
there are two different things I'm afraid his question and his desire? Two very different things, he desired that YES i can give him the different side, (how effectively i responded that different) but he opened himself to a different view
what so amazing about it absolutely NOTHING
i can block one but what about others who are talking / feeding on his left-overs?
@asadz When you block a user, and it only works in chat, none of their messages show up on your screen. You can still see everyone else's messages. It is sometimes confusing, but I deal with it.
When I read the OPs comments to you I read them a little bit different. In the end, he wasn't asking for anything regarding change management. He was wanting to know why someone might want to do something.
Change management is about implementing a change that someone has decided to do. It has nothing to do with deciding if something should be done.
Right. Dinner plans calling for preparations. Gentlemen.
I don't know english as my mother language but his question started with the word (Should) and map this with change management you can get your answer.
would mean something like "Should management be considered of changing default ssh port"?
concerned(typo)
and also YES change management procedures have to be taken in considering whenever you plan for a change? Who authorizes the changes, who is the approval authority, who keeps the revision history, who does the documentation, and most importantly who test , and evaluates the change
@ThomasPornin And I think your answer neatly got around the fact that Vyatta doesn't appear to do switch emulation, from what I can see from the documentation. It appears to be routing only.
I see there is still a wee bit of guidance @asadz. Im a bit concerned that your statement 'why are you guys not understanding the perspectivei'm not answering his answeri have no intention' shows that you are kind of missing the point of the site. The first goal of any answer here is to answer the specific question. If you can do that but you feel there is further guidance you can give as well then adding extra viewpoints is useful.
I prefer to keep my online gaming accounts associated with an e-mail account which is separate from my normal e-mail. So, the Xbox Live account connected to my Xbox 360 is not registered to the same e-mail address I used for registering my Windows Phone.
When I went to download games for my phon...
