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!"
fix that link...
I know I'm going to get modded down for this but the link in the article is wrong.
http://freebsdfoundation.org/
How about this statement instead?
The other one is boring. 404 blah blah blah.
I have found there are just two ways to go.
It all comes down to livin' fast or dyin' slow. -REK, Jr.
The requested Comment (Slashdot post) was not found.
'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
FOR THE LOVE OF GOD - let the free bsd foundation have a logo. Please, please, please reopen the contest. How can you close a contest without picking a winner? Think of the humanity.
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."
Run *BSD? Chances are that your SSH *will* be comprimised sometime after tuesday.
www.deadly.org
Quick hacks to fix:
filter out port 22 on your firewall.
shut down sshd process.
Proper fix:
Upgrade to OpenSSH 3.3 and you *must* have privilage separation on. Then, after Monday, upgrade to the new OpenSHH that will be released.
3.3 is only vunerable if pivilage separaiton is off. No true patches are being released as nasty-type people will be able to quickly find trhe vunerability by reading the patch.
For your consideration:
As a tempory hack, I ssh'ed into my servers, started Telnetd and loged into them via Telnet. I then killed telnetd, and kept my open Telnet connection. I've left these open telnet connections in case I have to manage my servers.
I've firewalled port 22 from the outside and will upgrade the systems at my leasure when the new version of SSH comes out around monday or tuesday.
Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.
ok, what if we run openssh on a linux box? are we still in danger of compromise? I imagine that linux machines would be more vulnerable due to their increased popularity over the BSDs. Of course, someone will want to be the first to claim ending on openbsd's four year run.
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.
It's their perogative not to pick a winner if they don't like them. After all, knowing this world 104 of them were of the goatse guy, 1 was the exisiting freebsd daemon with "I made this myself" in the email, and 1 of tux. I'd leave things open if that happened too.
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.
this seems stupid title, every live in the world is dying, it is always true, not just FreeBSD.
They got 106 entries and not one was worth using? You've got to be kidding me! Are BSD supporters really that uncreative or is BSD way too anal? Either way it doesn't bode well.
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!
Perhaps they wanted a more "businesslike" logo rather than the cutesy FreeBSD Daemon that we all know. Linux has somewhat succeeded with it's penguin mascot...
What might be wanted is a logo which may be put on letterheads and correspondences - sans mascot.
I am no graphic artist so I cannot submit a usuable entry but if all the hundred or so submissions featured the mascot, I might choose for no winner. The FreeBSD foundation can become a very important and serious entity and as such it deserves a serious logo.
All said, some of the "new and better" logos which many high profile companies have changed to lately strike me as silly and pointless...
See PriceWaterHouse ==> "MONDAY"
Or the obsurd new BP "Sunflower" logo.
The British Telecom logo... What was wrong with the old one?
Branding is an important issue and maybe the judges wanted a logo which could become a brand symbol which is recognised and respected.
Examples of brand logos which people recognise (and don't have sillyness in their logos, nor the company name) in no particular order
1. Chevron
2. Nike
3. Pepsi Cola
4. Apple Computer
5. Mitsubishi
...
Hmm... Run out of things to say.
-- The universe began. Life started on a billion worlds...
-- Except on one where stupidity was there first.
Quick hacks to fix:
filter out port 22 on your firewall. shut down sshd process.
Proper fix:
Upgrade to OpenSSH 3.3 and you *must* have privilage separation on. Then, after Monday, upgrade to the new OpenSHH that will be released.
3.3 is only vunerable if pivilage separaiton is off. No true patches are being released as nasty-type people will be able to quickly find the vunerability by reading the patch.
Seeing as it just came out, I doubt very much whether Linux would be considered "secure" in this respect either. Face it, when a new hack is released, it takes a little while for the various releases to get up to speed, be it *BSD or Linux or MicroSloth (although MS seems to be a lot slower).
Besides which, the new OpenSSH does not address any *specific* hack, its simply to make OpenSSH *more* secure than it was. This is not to say that it was insecure in any specific way, just that through privelege seperation it can be made *more* modular and easier to validate for security and less chance of any hole that *is* found being used to hack root.
...but if I am, surely others are too. Isn't the "Devil" logo FreeBSD's?
-twb
The 2.9 version in 4.6 is not vulnerabe to this attack. I see no rush to upgrade other than Theo trying to push FreeBSD into the mix in order to keep OpenBSD from being one of the few that are affected. Really lame if you ask me.
scott
I agree, and IIS' early disclosure may have been provoked by this (not that I have a lot of respect for their behaviour lately).
I'm sure the artist put a lot of effort into it, but there really wasn't one design that I would have chosen for a logo.
So I take it you don't have any "Dirt Devil" vacuum cleaners at the church?
Boy, that really sucks. (heh, get it?)
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.
Most people have no sense of aesthetics whatsoever. They might vote for a logo because they like Elvis or Smurfs or something - which has nothing to do with the vision that the foundation had in mind.
I have but one thing to say:
BSD IS DYING.
- IP