i can't figure swaret out

darkchild · 09-01-2004, 06:18 PM

when ever i do the swaret --upgrade command it keeps telling me that everything is up to date. now is there nothing to upgrade after a fresh install, is everything up to date? i changed the .conf file so i dunno any suggestions?

sh1ft · 09-01-2004, 06:22 PM

You need to update swaret itself first. Do swaret --update.

joe83 · 09-01-2004, 06:27 PM

A few questions:
Did you do swaret --update first??
What version is swaret set to?

If you want the latest do swaret --set VERSION=current
then swaret --update Be advised though that current is sometimes unstable I wouldn't recommend it if you're new to slack. Keeping the version at 10 and periodically updating swaret is probably the safest way.to go.

darkchild · 09-01-2004, 06:30 PM

i did do all that and i tried the VERSION=10 but still the same thing

predator.hawk · 09-01-2004, 06:38 PM

Steps to Get Swaret to work right

1. Install it (witch i take it you have already done :P)

2. run as root swaret --update to get the latest file lists

3. Run as root swaret --upgrade to upgrade packages to the latest versions.

that sould help

.

lupin_the_3rd · 09-01-2004, 07:36 PM

Quote:

Originally posted by joe83
A few questions:
Did you do swaret --update first??
What version is swaret set to?

If you want the latest do swaret --set VERSION=current
then swaret --update Be advised though that current is sometimes unstable I wouldn't recommend it if you're new to slack. Keeping the version at 10 and periodically updating swaret is probably the safest way.to go.

I've never noticed current to be unstable... at least compared to some other "bleeding edge" distros...

noxious · 09-01-2004, 08:38 PM

I'm new to Slackware also, but swaret works fine - as long as the correct tweaks are made.

Look at http://swaret.sourceforge.net/index.php and follow the directions CLOSELY. You must make some adjustments to the update addresses and a few other swaret.conf editing to get it all to come together.

... If I can do it, anybody can!

joe83 · 09-01-2004, 09:51 PM

Quote:

Originally posted by lupin_the_3rd
I've never noticed current to be unstable... at least compared to some other "bleeding edge" distros...

I recently did an upgrade with current after which I did an rkhunter scan. It returned 7 bad MD5 checksums.Since I haven't figured out what happened yet I was erring on the side of caution.

lupin_the_3rd · 09-01-2004, 10:02 PM

I get that too but that's it for the scan... 7 incorrect... wonder if the author should be notified?

joe83 · 09-01-2004, 10:12 PM

Interesting. I'll post the affected files when I get back to my machine. I'm curious to see if our results match.

joe83 · 09-02-2004, 10:48 AM

Quote:

Originally posted by lupin_the_3rd
I get that too but that's it for the scan... 7 incorrect... wonder if the author should be notified?

Here are some of the results from my rkhunter scan:

/bin/Killall
/bin/ps
/sbin/sysctl
/usr/bin/ps
/usr/bin/w
/usr/bin/pstree
/usr/bin/watch

All returned bad checksum, no whitelisted hash I scanned the system with SARA and Nessus and no problems were found.
IDS logs from snort show nothing unusual , firewall logs (smoothwall) show no unusual activity, leading me to believe it's something in rkhunter. Are these the same seven you found?

lupin_the_3rd · 09-02-2004, 11:27 AM

yep, exactly the same ones... hmmm... it's got to be something with rkhunter... are you using the package from linuxpackages by any chance?

joe83 · 09-02-2004, 11:44 AM

Yep. That had me going there for a little while. I'll put together a bug report and send it to the rkh folks. In the meantime I uninstalled 1.1.7 and reinstalled 1.1.6
Thanks for your help.

sh1ft · 09-02-2004, 12:28 PM

I get the same too.. good I thought I had been rooted for a second

lupin_the_3rd · 09-02-2004, 01:12 PM

guess I'll bump down my version too for the time being...