FC3 Security
Robin Laing
Robin.Laing at drdc-rddc.gc.ca
Thu Mar 10 16:56:00 UTC 2005
Rick Bilonick wrote:
> Les Mikesell wrote:
>
>> On Wed, 2005-03-09 at 07:03, Rick Bilonick wrote:
>>
>>
>>> Again, a logical solution (to a totally unnecssary problem).
>>> Unfortunately, the university does not allow having more than one
>>> computer on a port. (I don't think they really enforce this from what
>>> I have seen but the data center again would go ballistic even
>>> mentioning it.)
>>>
>>
>>
>> Is it just an accident of location that you are dealing with the
>> data center people rather than the university IT dept? If not,
>> I'd take the box home and start looking for a more helpful university.
>> I can understand the data center not wanting unknown boxes on their
>> LAN, but then that LAN shouldn't be your only choice.
>>
>> But, for a quick fix: could you set up some kind of VPN for your
>> inbound connection other than ssh? IPSec, OpenVPN, CIPE, etc.
>> and shut off all other services? Those would not respond to the
>> port tests that found your ssh server, but you would need a
>> matching client wherever you work.
>>
>>
>>
> The data center won't consider ANY solution. They won't let me buy my
> own port and they won't accomodate me in ANY way. I guess I will either
> have to get the department to find me another office or take the machine
> home. Needless to say, I haven't found this place to be very accomodating.
>
> Rick B.
>
My sympathies.
Get a couple of more computers and tie them together in a beowulf
cluster which is great for number crunching. When they ask about
Windows, get them to source you a beowulf cluster package that uses
windows with the same specs.
beowulf.org
I would also be writing to the department head that you work under
about your problems.
How do they feel about wireless in your university? Get a wireless
port off of the other network.
And if you were evil, usenet, anonymous postings, hum ...
Now I have said enough. :)
--
Robin Laing
More information about the fedora-list
mailing list