Was soll das?
Schon wieder ein “neues” SUSE 11.1.
Seid Ihr so selbstverliebt, dass Ihr bei jedem gelösten BUG (siehe KDE4) ein neues Release rausbringt?
Damit macht Ihr Euch keine Freunde.
Seht lieber zu, dass Ihr Eure Hausarbeiten(Bugbehebungen) erledigt, damit SUSE 11 mit KDE4 benutzbar wird.
Kein Schwein braucht SUSE 11.1.
Ein paar Updates berechtigen noch lange nicht zu einem Release.
Warum nicht? OpenSUSE 11.1 is nicht nur KDE4. There are many other updated software packages.
Hello jschleede.
Why do you not speak directly to us?
So I have to guess what you say. A wild guess from Google translator:
What gives?
Again, a “new” SUSE 11.1.
Are you so proud that you bring a new release before resolving the BUG (see KDE4)?
It makes you no friends.
Prefer to see that your work on your house to repair SUSE 11 with KDE4 usable.
No pig needs SUSE 11.1.
A few updates – still a long way to a release.
We are working to make KDE4 integrated into openSUSE, a legitimate endeavour. And as ken_yap noted, there is more to openSUSE than KDE4, so the other advances need to roll forward too.
Since you are looking for mischief, this discussion does not belong in the beta forum where it will distract from serious discussion. I will transfer it to the chat forum for you and you can carry on your mischief there – for a time.
And OP, if you don’t like the KDE4 improvements in 11.1, feel free to use KDE3 which will be supported for one more release, and let other people help improve KDE4 if you do not wish to take part.
Personally I think its best to stick with 11.0 until the final release of 11.1
Updated Software? Bugreleasing or new Features?
Why curl,wget,ldapclient,wlan-client and other still uses CLEARPASSWORDS?
Because you play with your Linux and dont work with this.
For Company is NOVELL-SUSE ,OpenSUSE or other linuxe not useful, if you and your friends make so on.
Ah, the troll English writes.
Don’t know what you are smoking. OpenLDAP has supported LDAPS for a long time. curl and wget support https. Filezilla supports FTP over SSL.
And anyway feel free to file a bug at Novell’s bugzilla. I am a developer not. Or you can just use OpenSUSE not and be happy. Or not.
im not smoker.
you know the file /etc/ldap.conf ?
a good ldap dont allow anonymous search, thats why you have an entry “bindpw” and that is CLEAR!!!
btw im not stupid.
joerg
i forgot.
curl use a file .curlrc. in different homedirectorys.
If im behind a proxy with authentication,i need an CLEARTEXT-Entry in this file.
You know this?
wget use the same fabulous technic in wgerrc or get an Proxypassword from an environmentvariable saved in /etc/sysconfig/proxy. (also CLEARTEXT)
Oh dear, I guess you don’t know how to configure openldap2 config files with a text editor instead of expecting the GUI to do everything for you?
So make the file 600 for root. And report the bug at Novell.
this me to dumb.
since 1995 i use linux.
i get no answers in this forum but stupid comments from young green geeks.
good bye.
On Mon, 03 Nov 2008 11:46:03 +0000, jschleede wrote:
> im not smoker.
>
> you know the file /etc/ldap.conf ?
> a good ldap dont allow anonymous search, thats why you have an entry
> “bindpw” and that is CLEAR!!!
chmod 600 /etc/ldap.conf
Problem solved. Unless root is compromised.
Jim
I thought that after 13 years with Linux you would know the answers yourself. Anyway, glad to be of help. 
and if the laptop was stolen,the atacker have the Cleartextpaaaword and the ssid in the /etc/sysconfig/network/wlanxyz123.
then he read in the /etc/ldap.conf.
Now he can login over wlan in the companynet with an valid user/password.
lies doch bitte nochmal Deinen ersten Beitrag und sag mir, was Du erwartet hast, insbesondere unter Berücksichtigung der Tatsache, dass hier mitnichten Suse-Entwickler arbeiten, sondern Leute, die einen großen Teil ihrer Freizeit damit verbringen, anderen bei Problemen mit Opensuse zu helfen.
Gruß
Uwe
If that’s the situation you should encrypt your disk. I’m sure with your vast experience you can work out how to do this.
I don’t know what this has to do with your original whinge that Novell isn’t fixing bugs. Of course software has bugs. But I think that you are in the tiny minority, wanting to hold back progress just so that everything can be fixed for you, if that is even possible.
On Tue, 04 Nov 2008 09:06:02 +0000, jschleede wrote:
> and if the laptop was stolen,the atacker have the Cleartextpaaaword and
> the ssid in the /etc/sysconfig/network/wlanxyz123. then he read in the
> /etc/ldap.conf.
> Now he can login over wlan in the companynet with an valid
> user/password.
That’s what on-disk encryption is for. With regard to something like
ldap.conf, that’s something the openldap folks would have to address; it
wouldn’t be very good for Novell to fork every common package when
there’s a better solution - namely disk encryption - to solve that
problem.
I’ve got a couple of laptops; on the one that I have sensitive company
info on, I use encfs for data that needs encryption and a hard drive
password set in the BIOS. I also make sure I don’t do something silly
like leave the machine on the train; heck, I don’t even leave it in my
car so I can run into the grocer’s to get a gallon of milk.
Jim
Will it be possible to update completely to 11.1 from 11.0 after the release?
Don’t know how good this works in openSuse in the past so far.
Could someone tell me? 
BTW /etc/ldap.conf was never meant to be a storage location for bind passwords, it is merely a place for default settings for utilities like ldapsearch. It’s up to the client app to store any passwords appropriately.