On Sat, 10 Feb 2007, James Li <[EMAIL PROTECTED]> wrote:-
>line 432
>should be:
>FREE_CD=$(echo ${CD_LINE}|awk '{print $(NF-2)}')
The preceding line, and the following two lines also need replacing.
These should do the job:
TESTCD=$(echo ${CD_LINE}|awk '{print $(NF)}')
FREE_CD=$(echo ${CD
Il giorno dom, 11/02/2007 alle 11.00 +1300, Volker Kuhlmann ha scritto:
> > > Isn't it sufficient for share browsing to open ports 137 to 139 (udp
> > > and/or tcp) for smb related traffic?
> >
> > You also need port 445 and, unfortunately, to accept packets from a
> > random high port which is dy
> > Isn't it sufficient for share browsing to open ports 137 to 139 (udp
> > and/or tcp) for smb related traffic?
>
> You also need port 445 and, unfortunately, to accept packets from a
> random high port which is dynamically assigned.
Thanks. Accept packets on what port from the random high port
createrepo seems to have been updated and appears to have obtained
functionality to create an sqlite database, besides or instead of the xml
data file. More about this on in this email:
http://lists.laiskiainen.org/pipermail/apt-rpm-laiskiainen.org/2007-February/000585.html
Would it be possible
Il giorno dom, 11/02/2007 alle 09.20 +1300, Volker Kuhlmann ha scritto:
> Isn't it sufficient for share browsing to open ports 137 to 139 (udp
> and/or tcp) for smb related traffic?
You also need port 445 and, unfortunately, to accept packets from a
random high port which is dynamically assigned.
On Sunday 11 February 2007 05:46, James Tremblay wrote:
> sounds like YAST needs to be modified to modify the firewall
> automatically when opensuse joins a "workgroup" or Windows "domain".
When you configure the desktop machine as smb client in yast, the
firewall on that desktop needs to be appr
On 2/10/07, Markus Koßmann <[EMAIL PROTECTED]> wrote:
I have the both the KDE3 and KDE4 repos added to my installation sources on
SUSE-10.2. Today morning I decided to update all packages to the current
version with yast2. That included a update of the KDE4 packages. After a
restart KDE3 came u
Hans Witvliet <[EMAIL PROTECTED]> writes:
> Hi all,
>
> any chance for a recent upgrade of ccid?
>
> In -current it is still: pcsc-ccid-1.0.1
> In the mean time, 1.1 was released, 1.2.0 and 1.2.1
>
> AFAIK, the Midentity tokens from KOBIL need the latest version.
> Perhaps a candidate for 10.3?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dominique Leuenberger schreef:
"M9." <[EMAIL PROTECTED]> 02/10/07 2:43 PM >>>
>> Do I have to understand you are 'responsible' for the FW?
>> And if so, do you want these logs sent to you?
>> Or do I attach them to Bug # 243809 ?
>
> Hi,
>
> No.
>>> "M9." <[EMAIL PROTECTED]> 02/10/07 2:43 PM >>>
>
> Do I have to understand you are 'responsible' for the FW?
> And if so, do you want these logs sent to you?
> Or do I attach them to Bug # 243809 ?
Hi,
No.. so far I'm not associated more to Novell than you. Except maybe
also having other pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dominique Leuenberger schreef:
"M9." <[EMAIL PROTECTED]> 02/10/07 11:49 AM >>>
>> I did not encounter 'real' attacks yet, but
>> I also agree that this should be fixed properly: Why does the firewall
>> not respond to the usernames and passwords
>>> "M9." <[EMAIL PROTECTED]> 02/10/07 11:49 AM >>>
>I did not encounter 'real' attacks yet, but
>I also agree that this should be fixed properly: Why does the firewall
>not respond to the usernames and passwords?
>If it would, there would be no problem at all.
>Normally one should be able to verif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Volker Kuhlmann schreef:
>>> It worked in 9.3 (if I remember right), and it's actually an obstacle
>>> for new users who try to configure samba, do that properly in Yast, but
>>> can't browse the local network even after selecting "Open firewall
>>>
13 matches
Mail list logo
