boerde.lists.suse-security
  Home FAQ Contact Sign in
boerde.lists.suse-security only
 
Advanced search
January 2007
motuwethfrsasuw
1234567 1
891011121314 2
15161718192021 3
22232425262728 4
293031     5
2007
 Jan   Feb   Mar   Apr 
 May   Jun   Jul   Aug 
 Sep   Oct   Nov   Dec 
2007 2006    
total
boerde.lists.suse-security Profile…
RELATED GROUPS

POPULAR GROUPS

more...

 Up
  Re: [opensuse-security] Keep FW_ALLOW_INCOMING_HIGHPORTS_UDP in SuSEfirewall2         


Author: Ludwig Nussel
Date: Jan 18, 2007 04:43

Andreas Wagner wrote:
> [...]
> I took this to mean thatI had to specify
>
> FW_ALLOW_INCOMING_HIGHPORTS_UDP="20 6277"
> (and possibly FW_SERVICES_EXT_UDP="ntp 6277")
>
> in /etc/sysconfig/SuSEfirewall2, which brought up the alerts above.
>
>
> Can you tell me if I got it right and if this would be considered a
> reason to keep FW_ALLOW_INCOMING_HOGHPORTS_UDP?

I didn't understand the description that way. FW_SERVICES_EXT_UDP should be
sufficient. If you use FW_SERVICES_ACCEPT_EXT instead you can also limit the IP
addresses that have access to the port.

cu
Ludwig
Show full article (0.90Kb)
1 Comment
  Re: [opensuse-security] Problem right after install. On two systems.         


Author: Boyd Lynn Gerber
Date: Jan 17, 2007 09:09

On Wed, 17 Jan 2007, Cristian Rodriguez R. wrote:
> Boyd Lynn Gerber escribió:
> : output (stdout && stderr) follows
>>
>> file: could not find any magic files!
>
> hrmm..seems the file package is b0rked, reinstall it.

Which package? I went into yast2 installation and selected update on all
installed files waited 2 hours for all packages to be installed again and
still same problem. I really do not know how to fix this. Google was no
help. This probem exits on 2 systems. Both upgraded and then installed
from scratch. Upgrade 1 10.1 to 10.2, 1 10.0 to 10.2. also wiped HD and
installed from scratch. I really do not know what is causing this. I can
install 10.1 on either of these systems and works not error, but 10.2 has
this error. I really am at a loss of what else to do to fix this problem.
Something must not be working. I also tried a network install. Same
problem. Retail DVD, Download DVD, Network install all the same problem.
Memory test for 48 hours no problem. What else can I try?
Show full article (1.31Kb)
no comments
  Re: [opensuse-security] Problem right after install. On two systems.         


Author: Boyd Lynn Gerber
Date: Jan 17, 2007 08:53

On Wed, 17 Jan 2007, Carlos E. R. wrote:
> The Tuesday 2007-01-16 at 18:42 -0700, Boyd Lynn Gerber wrote:
>> Script replacements
>> Checking /bin/psfile: could not find any magic files!
>
> I'm not sure this is a security related problem but... anyway, do you have
> "/etc/magic"? It belongs to the "file...rpm" package.

Yes...

-rw-r--r-- 1 root root 113 2006-11-25 05:18 /etc/magic

The reason I ask is this shows up using security software.

--
Boyd Gerber zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]opensuse.org
For additional commands, e-mail: [email protected]opensuse.org
no comments
  [opensuse-security] Question on wiping S390 fiber attached storage         


Author: Greg Byrd
Date: Jan 12, 2007 07:45

Everyone,

Since there isn't a list on the S390 architecture, it seems this list is the closest to what I'm looking for. In a nutshell, I'm looking for software that supports S390 architecture and wiping fiber attached storage to DOD standards. The S390 software we have only wipes mainframe storage, not fiber attached storage.

I've used shred with great results, but it does have the caution on journaled file systems (we're using reiser and ext3). Let me know if there are suggestions.

Thanks in advance,
Greg

____________________________________________________________________________________
Finding fabulous fares is fun.
Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains.
http://farechase.yahoo.com/promo-generic-14795097
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]opensuse.org
For additional commands, e-mail: [email protected]opensuse.org
no comments
  [opensuse-security] OSS 10.2 e usbfs         


Author: Tolmino
Date: Jan 8, 2007 09:08

For upload firmare (via fxload) in usb devices as astribank for use with
asterisk.
> Why do you need it? The pseudo device nodes are now in /dev/bus/usb/....
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]opensuse.org
For additional commands, e-mail: [email protected]opensuse.org
no comments
  Re: [opensuse-security] rkhunter or chkrootkit on rescue system         


Author: Philippe Vogel
Date: Jan 1, 2007 16:56

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Show full article (2.10Kb)
no comments
  Re: [opensuse-security] Security report from rkhunter on default install of openSUSE 10.2         


Author: Carlos E. R.
Date: Dec 31, 2006 04:37

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The Sunday 2006-12-31 at 11:47 +0100, Pavel Chalupa wrote:
> invisible files detected by rkhunter you can see on fresh instalation which is
> completly disconnected (without ethernet NIC)
>
> /dev/.udev/
>
> /db/

I believe this is normal in udev. I don't know what it is used for. It is
a virtual filesystem, they are created when needed (boot).
> .pwd.lock (change time when system was installed)

Lock files are used by some applications when opening files.

- --
Cheers,
Carlos E. R.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Made with pgp4pine 1.76
Show full article (0.99Kb)
3 Comments
  [opensuse-security] loop-AES problems ...         


Author: Roman Pindela
Date: Dec 29, 2006 00:42

Hello, there !

I just need any kind of help with mentioned loop-AES's way of encrypting data.
It happend that I encrypted ..luckily ?, I don't know .. my super confidential
data... but I'm not able now to read it. .... I mean I can't setup encrypted
loop device on my files. That's what I get :
-----------------------------------------------------------------------------------------------------------------------------------------------------------
linux-ej56:/mnt/media/music # losetup \
-e aes-256 /dev/loop1 /mnt/media/music/DvM01a.data
Password:

<< and the answer is .. >>

ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256
bits) not supported by kernel
linux-ej56:/mnt/media/music #

-----------------------------------------------------------------------------------------------------------------------------------------------------------

Password is correct, loop1 is unused, algorithm name is ok as well ..so what
maybe wrong... ?
Show full article (1.24Kb)
1 Comment
  [opensuse-security] problems with smbmount and OSS10.2         


Author: Tolmino
Date: Dec 27, 2006 10:01

Hi, after oss10.2 installation i have tried to mount a smb filesystem:

mount -t smbfs -o ip=192.168.33.35,username=franky //franky/share /mnt

but i have received this message after i have inserted password

Suse Kernel don't support smb filesystem!!!

Do i must recompile?
thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]opensuse.org
For additional commands, e-mail: [email protected]opensuse.org
no comments
  [opensuse-security] snort in SLES9 and SLES10         


Author: shashi
Date: Dec 24, 2006 03:01

In SLES9 SP3, and in SLES10

SuSE:/usr/share/doc/packages/snort # pwd
/usr/share/doc/packages/snort

SuSE:/usr/share/doc/packages/snort # du -h *.bz2
4.0K ACID-0.9.6b21.tar.bz2
4.0K Guardian.tar.bz2
4.0K Net-SnortLog-0.1.tar.bz2
4.0K Spade-092200.1.tar.bz2
4.0K passiveOS.tar.bz2
4.0K snortdb-extra.bz2
4.0K snortnet.tar.bz2
4.0K snortwatch-0.7.tar.bz2
SuSE:/usr/share/doc/packages/snort #

Why Novell/SuSE is giving empty files of snort add-ons ? When i first saw, i thought Novell is
giving tested versions of snort add-ons which perfectly works with bundled snort version. But, when
i try to configure ACID in SLES9 SP3, i discovered that it is a empty file. Then i immediately look
into SLES10, and in SLES10 too those files are empty files.

Is it a mistake from Novell/SuSE side ? or is there any reason/purpose ?
Show full article (1.09Kb)
no comments
1 2 3 4 5 6 7 8 9