No Logo Wins FreeBSD Foundation Contest
RJPDeanLO writes: "The FreeBSD Foundation logo contest has ended with no winners! Check out their statement on the site.
To support FreeBSD ... I'm hoping that we can all get a second chance at it. Please reopen the contest!"
I know I'm going to get modded down for this but the link in the article is wrong.
http://freebsdfoundation.org/
'Editor' One who edits.
'Edit' To prepare (written material) for publication or presentation, as by correcting, revising, or adapting.
Jesus was all right but his disciples were thick and ordinary. -John Lennon
This is the type of critique that will drive a designer insane. Most artists are used to taking criticism (at least ones with actual art training) - but it's very difficult to take "no direction" criticism, as it leaves you with no way to improve your work.
Instead of saying none of the entries were "it", they should be saying WHY none of the entries are acceptable so that future designers will have some idea what to do so as not to make the same mistakes apparently made by the first crew.
Sounds suspiciously like "we each had our favorites, and couldn't reach a consensus."
ok, what if we run openssh on a linux box? are we still in danger of compromise?
According to the scant information available, yes, Linux useres are at risk. Keep in mind, their warnings could also be a case where the OpenSSH people are telling people that every platform is at risk in order to not give nasty-people any additional infomration.
I'd beleive the OpenSSH people at face value and upgrade myself.
Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.
Unfortunately, for FreeBSD-stable this means that they'll have to jump versions to openssh-3.3 most likely by using the openssh-portable port and introducing that into the base distribution. Work is already being done (notably by DES, one of the commiters, hats off!)
Some people advised getting rid of the default openssh and installing the newer one through ports. Trouble is that the functionality that "separates privileges" is relatively new and has to be incorperated into -stable quickly now.
Many people didn't like this especially because Theo's comments seem to indicate that the required fix in question is small and simple. And the new feature in openssh may only be *one* way to prevent said exploit from causing serious harm. That's something entirely different from an actual fix of course. So some folks felt that they were being dragged into a major version bump maybe unnescessary.
Consider for example that OpenBSD doesn't use PAM while FreeBSD does use it (extensively), and you can imagine a bumpy ride on -stable soon.
I don't mean to take sides or something, just let you know what's going on.
Can't they be put up online and let the people decide?
If not, why not?
It is a shame there were no winners. I hope they reopen it and display all the entries again. This way all of us can see what was entered and maybe that would guide us on creating bigger and better logos? I already have an idea to out do my entered logo :)
Please re-open the contest FreeBSD Foundation.
We want to show our appreciation to the foundation and to freeBSD itself!
You make a very good point atcurtis. If they want a "serious" logo ... then they just need to let us know. :)
...but if I am, surely others are too. Isn't the "Devil" logo FreeBSD's?
-twb
Scared me for a minute. From the headline, it sounded like the incredibly annoying No Logo had won! Thank the Lord that's not the case.
sulli
RTFJ.