On Jun 8, 5:54 pm, mabshoff <[EMAIL PROTECTED]> wrote:
>
> >http://www.testdrive.hp.com/
>
> I got an account there, but I got put off by the fact by you can only
> log in via telnet.

To be honest, I don't blame HP. The lack of security only affects
them, not you. If someone sniffs your password on HP's servers, they
can only get into your account at HP. That should be no big loss to
you. It is not intended for confidential information.

By forcing one to use telnet/ftp, HP do at least have the possibility
of sniffing the traffic on their servers. I personally don't have a
problem with that. If they give me free access to nice computers, I
don't really care if they look what I am doing. It would tend to
discourage hacking attempts, when people know their traffic can be
seen.

>
> > I found no such warning issued. It might be worth putting a warning,
> > and again allow someone to bypass it by setting $SAGE_PORT  to
> > something non-empty.
>
> > Comments???
>
> Yes, we should definitely print some warning statement. The logic
> right now is that we test for known bad cases, but we should
>
> a) test for known good combos, i.e Linux, 32 bit OSX
> b) test for experimental stuff: 64 bit OSX, Solaris, FreeBSD, Cygwin
>
> If we do not his (a) or (b) print an unsupported warning that is
> overridable and tell people to email the list to let us know that
> someone is working on this.
>
> If you agree please open a ticket and post the trac number :)
>
> Cheers,
>
> Michael


Yes, basically I agree. I've not proposed any exact wording, but
opened the ticket

Ticket #3384 (new enhancement)

Not quite sure if you consider it a new enhancement, a bug fix, or
whatever. Change priority etc as you see fit.




--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to