Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • https://transproxy.cit.cornell.edu:9443/Proxied/
  • Service is managed by IT Security Office (ITSO).
  • This service is running on really old hardware., and Oliver understands that it also has some scaling limitations so adding new allowed services
  • Question: What is the proxy service being used by RedRover/ eduroam, if different? And if different, what services are be proxied?
    • Answer: 2/16/16, per Michael's email conversation with GlennFFL: Yes, "proxy" service used by RedRover/ eduroam is different:
      • Traffic from EduRoam, RedRover, dorm networks, Access Nets, and a few other places is sent through a different Fortinet firewall infrastructure, and run through a NAT where it goes off-campus.
        Since *all* off-campus traffic is handled this way, there's no need for proxying, let alone the selective proxying provided by Transproxy.
        CIT Infrastructure provides this service - if you have issues or questions about the service, the IT Service Desk (itsd@, x5-5500) is probably the place to start.
  • Question: Couldn't one just use the new proxy-cabable devices currently being used by RedRover/ eduroam, etc., and get rid of old Transproxy hardware?
    • Answer: 2/23/16, per Oliver's brief phone conversation with LaurieC: Yes, services are redundant at a technical level. ITSO to consider migrating service to new Fortinet hardware, to our edge. Nothing scheduled yet, since migrating from ACLs to Managed Firewall is currently a key project they are focusing on, understandably. Long-term, such a change will put the Transproxy on a robust, scalable service platform. (ed. And 10-space can then continue to be relied on as a safe place to put vulnerable computers that need updates or file share access, but don't need full internet access.)

Used primarily for two reasons:

...