Autor: Piotr Pogorzelski (ppogorze_at_jukebox.ippt.gov.pl)
Data: Tue 24 Oct 1995 - 08:38:13 MET
Na liscie poswieconej sambie znalazlem swietny kawalek.
I just received a message from Microsoft <WinNews_at_microsoft.com> titled:
> Microsoft(R) WinNews Electronic Newsletter
> Special Issue, October 20, 1995
that contained the following:
>File and Printer Sharing for Microsoft Networks (not MSN:
> The Microsoft Network online service)
>
>Microsoft is also issuing an update for a known problem
>with File and Printer Sharing for Microsoft Networks and a
>certain UNIX shareware network client (Samba's SMBCLIENT).
>The update corrects a problem with share-level security
>documented in the Microsoft Knowledge Base on October 9th.
>The update also includes a correction for a similar problem
>with user-level security that Microsoft recently discovered
>as part of its internal testing of the new driver.
>
>Customers whose environments meet all of the conditions
>below, may have their data susceptible to network or
>Internet hackers:
>
> 1. They configure their machine to share files and
> printers with other users on the network using File
> and Printer Sharing for Microsoft Networks (This
> option is not turned on by default)
>
> 2. They share a LAN, Internet, or Dial-Up connection
> with a UNIX-based computer running Samba's
> SMBCLIENT software
>
> 3. The network administrator does not disable peer
> services using System Policies
>
>The Samba SMB client allows its users to send illegal
>networking commands over the network. The Samba client is
>the only known SMB client at this time that does not filter
>out such illegal commands. SMBCLIENT users do not
>automatically have access to the Windows 95 drive, and
>must know the exact steps to send these illegal commands.
>
>The updated driver prevents these illegal commands from
>being executed, preventing SMBCLIENT users from accessing
>the drive on which sharing is enabled. With the updated
>driver, the SMBCLIENT user will only have access to those
>shared folders that the Windows 95 user has designated.
To jes na prawde SWIETNE. Poprawne dzialanie Servera zalezy od tego
jak jest napisany klient. I to klient jest odpowiedzialny za podawanie
poprawnych rozkazow. Moze weryfikacje uzytkownika tez??
Juz raz uzytkownicy samby znalezli swietny blad. Proste Del kasowalo
caly dysk sieciowy pod Win95.
Jak rozumiem, odpowiedzia majkrofona, bedzie dodanie nieudokumentowanego
bajtu do protokolu, aby zadne inne oprogramowanie nie moglo przypadkiem
porozumiec sie z tym co oni oferuja. Wtedy nikt nie znajdzie nowych
bledow.
Oby tak dalej.
-- piotr pogorzelski ppogorze_at_ippt.gov.pl
To archiwum zostało wygenerowane przez hypermail 2.1.7 : Tue 18 May 2004 - 12:26:05 MET DST