Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

lenny: win98 kliens -> samba server suxx

0 views
Skip to first unread message

SZABO Zsolt

unread,
Oct 29, 2009, 6:04:01 AM10/29/09
to

Lenny upgrade ota a halozaton levo par win98 kliens nem bir kapcsolodni a
samba szerverhez.

Mit jelent a NEWS.Debian.gz-ben olvashato alabbi bekezdes:

The "lanman auth = no" setting will also cause lanman password hashes to
be deleted from smbpasswd and prevent new ones from being written, so
that these can't be subjected to brute-force password attacks. This
means that re-enabling lanman auth after it has been disabled is more
difficult; it is therefore advisable that you re-enable the option as
soon as possible if you think you will need to support Win9x clients.

(az utolso 3 sor elegge homalyos megfogalmazasu: "more difficult", "as
soon as possible"...)

Mert en beallitottam, hogy "lanman auth = yes", de a helyzet valtozatlan.
Az "encrypt passwords = true" van me'g a smb.conf-ban, ahogy korabban is
volt.

--
sZs
_________________________________________________
linux lista - li...@mlf.linux.rulez.org
http://mlf2.linux.rulez.org/mailman/listinfo/linux

Gabor HALASZ

unread,
Oct 29, 2009, 6:20:04 AM10/29/09
to

SZABO Zsolt wrote:
> Lenny upgrade ota a halozaton levo par win98 kliens nem bir kapcsolodni a
> samba szerverhez.
>
> Mit jelent a NEWS.Debian.gz-ben olvashato alabbi bekezdes:
>
> The "lanman auth = no" setting will also cause lanman password hashes to
> be deleted from smbpasswd and prevent new ones from being written, so
> that these can't be subjected to brute-force password attacks. This
> means that re-enabling lanman auth after it has been disabled is more
> difficult; it is therefore advisable that you re-enable the option as
> soon as possible if you think you will need to support Win9x clients.
>
> (az utolso 3 sor elegge homalyos megfogalmazasu: "more difficult", "as
> soon as possible"...)
>
> Mert en beallitottam, hogy "lanman auth = yes", de a helyzet valtozatlan.
> Az "encrypt passwords = true" van me'g a smb.conf-ban, ahogy korabban is
> volt.

Szerintem ki es vissza kellene leptetni oket a domainbol/be, ha egyszer
deleted a password hash.


--
Gabor HALASZ <hala...@freemail.hu>

SZABO Zsolt

unread,
Oct 29, 2009, 6:48:54 AM10/29/09
to

On Thu, 29 Oct 2009, Gabor HALASZ wrote:

>> The "lanman auth = no" setting will also cause lanman password hashes to
>> be deleted from smbpasswd and prevent new ones from being written, so
>> that these can't be subjected to brute-force password attacks. This
>> means that re-enabling lanman auth after it has been disabled is more
>> difficult; it is therefore advisable that you re-enable the option as
>> soon as possible if you think you will need to support Win9x clients.
>>
>> (az utolso 3 sor elegge homalyos megfogalmazasu: "more difficult", "as
>> soon as possible"...)
>>
>> Mert en beallitottam, hogy "lanman auth = yes", de a helyzet valtozatlan.
>> Az "encrypt passwords = true" van me'g a smb.conf-ban, ahogy korabban is
>> volt.
>
> Szerintem ki es vissza kellene leptetni oket a domainbol/be, ha egyszer
> deleted a password hash.

Kossz... ez nyeronek tunt. Most mar csak azt kell kideritenem, hogy miert
tuntek el a nyomtatasi sorok (win98, XP...)
Hiaba inditom ujra a cups-t, es hiaba van a cups megadva a samba.conf-ban.
Lehet, hogy ujra vegig kell jatszanom a cupsaddsmb-t...?

--
sZs

SZABO Zsolt

unread,
Oct 31, 2009, 12:28:21 PM10/31/09
to

On Thu, 29 Oct 2009, SZABO Zsolt wrote:

>>> Mert en beallitottam, hogy "lanman auth = yes", de a helyzet valtozatlan.
>>> Az "encrypt passwords = true" van me'g a smb.conf-ban, ahogy korabban is
>>> volt.
>>
>> Szerintem ki es vissza kellene leptetni oket a domainbol/be, ha egyszer
>> deleted a password hash.
>
> Kossz... ez nyeronek tunt. Most mar csak azt kell kideritenem, hogy miert
> tuntek el a nyomtatasi sorok (win98, XP...)
> Hiaba inditom ujra a cups-t, es hiaba van a cups megadva a samba.conf-ban.
> Lehet, hogy ujra vegig kell jatszanom a cupsaddsmb-t...?

Ugy tunik a cups csak UTF8-ban hajlando mukodni:

DefaultCharset UTF-8

a cupsd.conf-ba es

display charset = UTF8
unix charset = UTF8

az smb.conf-ba, majd cupsd es samba restart.
(Es az smb.conf-ba irt bejegyzesek sorrendje sem mindegy... nekem ugy
tunt.)

Ezutan a cupsaddsmb-vel ujra kellett telepiteni a /usr/share/cups/drivers
-be bemasolt wind*zos driver-eket, es a hozzajuk tartozo nyomtatokat.
(Egyebkent eleg suxx volt, hogy barmilyen hiba eseten --- pl. nincs root
jog a sambahoz, nem latja a nyomtatokat, stb. --- a cupsaddsmb vegtelen
ciklusba zuhant...)

--
sZs
PS: +1: a lenny upgrade ota bizonyos nyomtatokhoz hiaba van beallitva a
windows kliensen, hogy kizarolag a Tray1-et hasznalja, figyelmen kivul
hagyja (pl. a bw ill. color kivalasztas mukodik).

0 new messages