dynes-deployments - [dynes-deployments] impact of blocking traffic to normal SSH port
Subject: DYNES-Deployments
List archive
- From: Jay Ford <>
- To:
- Subject: [dynes-deployments] impact of blocking traffic to normal SSH port
- Date: Mon, 17 Dec 2012 15:45:15 -0600 (CST)
DYNES folk:
Our IT security folks are hell-bent on blocking all traffic destined for the
normal SSH port (TCP 22) as it comes into our campus. (This is an effort to
thwart brute-force SSH attacks.)
I think DYNES is dependent on SSH for normal operation, or at least
administration, so I suspect this traffic block will have a negative impact
on our DYNES participation.
Is there a reasonable way to have our DYNES connectivity continue to work in
the presence of the SSH traffic block (other than exempting our DYNES gear
from the traffic block)?
________________________________________________________________________
Jay Ford, Network Engineering Group, Information Technology Services
University of Iowa, Iowa City, IA 52242
email:
,
phone: 319-335-5555, fax: 319-335-2951
- [dynes-deployments] impact of blocking traffic to normal SSH port, Jay Ford, 12/17/2012
- Re: [dynes-deployments] impact of blocking traffic to normal SSH port, Shawn McKee, 12/17/2012
- Re: [dynes-deployments] impact of blocking traffic to normal SSH port, Jay Ford, 12/17/2012
- Re: [dynes-deployments] impact of blocking traffic to normal SSH port, Shawn McKee, 12/17/2012
- Re: [dynes-deployments] impact of blocking traffic to normal SSH port, Jay Ford, 12/17/2012
- Re: [dynes-deployments] impact of blocking traffic to normal SSH port, Shawn McKee, 12/17/2012
Archive powered by MHonArc 2.6.16.