/hailmary/ and the inital blog post about the
phenomenon,
http://bsdly.blogspot.com/2008/12/low-intensity-distributed-bruteforce.html
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set
, but some other relevant network
config details changed between 2007 and 2010, and the second edition
reflects this.
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all
/FreeBSD-Archive/old-releases/i386/
or thereabouts has what looks like a fairly complete collection of
FreeBSD releases. For older stuff including 386bsd and 4.4BSD-lite
there's the archive at ftp://minnie.tuhs.org/BSD/
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http
), but I
would recommend that you pick literature that enables you to learn the
basics of TCP/IP as well as the actual commands needed. Looking into
packet filtering for basic protection won't hurt either. With those
keywords in hand, you should be able to dig up something useful.
- Peter
--
Peter N
, but being
sort of a PF guy I found the PF-based solution quite attractive and flexible.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah
to the part about state tracking and bruteforcers
at http://home.nuug.no/~peter/pf/en/bruteforce.html.
(and of course there's the book, nudge, nudge)
- P
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no
greytrapping for added bonus)
- P
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds
on for a while, but the existence of a WHITE
entry will ensure that the delivery will succeed on the next attempt.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all
Brent Jones [EMAIL PROTECTED] writes:
I for one prefer top posting, as usually I have read a particular thread
http://www.asciiartfarts.com/20011201.html
HTH, HAND
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.datadok.no/ http
if that doesn't help
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds
a matching pass rule.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds
descent into the spamd tarpit. Details via selected posts in my blog
(the blogspot.com ref in the signature).
Cheers,
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/
Remember to set the evil bit on all
that spamd from OpenBSD 4.1 onwards differs in several important ways from
earlier versions. And also, it's important not to confuse this spamd with
the program with the same name out of spamassassin.
Cheers,
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http
if your own blacklist gets updated and pruned regularly too.
- P
[1] http://home.nuug.no/~peter/pf/ (several formats), spamd parts start at
http://home.nuug.no/~peter/pf/en/spamd.html
[2] http://www.freebsddiary.org/pf.php
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation
a bit by introducing greylisting via PF (packet
filter) plugin spamd, which can just as easily run on a separate
machine such as your gateway. There are a few in-MTA options too, of
course.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149
unit and puts the too-chatty ones in a doghouse list of addresses.
One way to do it is described at
http://home.nuug.no/~peter/pf/en/bruteforce.html
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http
mail server kills an awful lot of spam. keep
spamassassin in there by all means, but after you start greylisting
you most likely will see the load on the machine drop considerably.
it's fairly easy to implement too.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http
Dave Carrera [EMAIL PROTECTED] writes:
Had a little nasty person trying to break my sshd on port 22.
You can head them off rather easily with a short PF rule set, see
eg http://home.nuug.no/~peter/pf/en/bruteforce.html.
They can actually be fun to watch :)
--
Peter N. M. Hansteen, member
(or k,M,G multiples of) of percentage of
available bandwidth, not number of packets. Your groups of source
addresses could be maintained as tables for easy manipulation.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http
the suggestions in
my tutorial at http://home.nuug.no/~peter/pf/en/bruteforce.html
(http://home.nuug.no/~peter/pf/ for the full manuscript in a variety
of formats).
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http
into
your favorite search engine.
Cheers,
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
delilah spamd[29949]: 85.152.224.147
where
things went wrong if they do.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
delilah spamd[29949]: 85.152.224.147
done with the other
firewalls FreeBSD has on tap) with 'overload' rules, ie
http://home.nuug.no/~peter/pf/en/bruteforce.html
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all
eg
http://home.nuug.no/~peter/pf/en/bruteforce.html
Cheers,
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
Dec 22 02:13:59
of greylisting (possibly supplemented with
a tarpit for known bad senders).
The greylisting/tarpitting part is really easy to do with PF, see eg
http://home.nuug.no/~peter/pf/en/spamd.html (part of my packet
filtering for fun and profit tutorial)
--
Peter N. M. Hansteen, member of the first RFC
feature, see
eg http://home.nuug.no/~peter/pf/en/bruteforce.html (part of my
EuroBSDCon and other places tutorial).
See http://home.nuug.no/~peter/pf/ for a choice of formats and languages.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149
David Schulz [EMAIL PROTECTED] writes:
process with zabbix agent. The problem is, i dont use ipfw, but pf,
and i dont know how a rule like that could look like using pf.
Maybe pfstat (/usr/ports/sysutils/pfstat) is worth looking into?
--
Peter N. M. Hansteen, member of the first RFC 1149
Ian Lord [EMAIL PROTECTED] writes:
It's an all in one solution that authorize wlan lan users before allowing
them access. It also filter traffic based on their username.
you could roll your own without too much trouble using pf and authpf.
--
Peter N. M. Hansteen, member of the first RFC
. ;-)
Well, fwiw it's one of the things I will be writing about in the near future.
Good luck,
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard
and greylisting at the moment is this
recent message to openbsd-misc:
http://marc.theaimsgroup.com/?l=openbsd-miscm=116136841831550w=2
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill
$iptostarve to any port $allowedports keep state queue notalot
- you get the idea.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice
OpenSSH
supported authentication methods you require before loading the rules
which actually let traffic through.
Cheers,
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers
-rate 15/5, \
overload bruteforce flush global)
for more detailed discussion see eg
http://www.bgnett.no/~peter/pf/en/bruteforce.html
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no
Noah [EMAIL PROTECTED] writes:
Any clues if a system like this is a already coded and out there somewhere?
Apart from the ipfw reqirement, you have just described authpf, see eg
http://www.freebsd.org/cgi/man.cgi?query=authpfapropos=0sektion=0manpath=FreeBSD+6.1-RELEASEformat=html
--
Peter N
, and you could probably do worse than spend a few moments
browsing the PF docs or for that matter my rather basic PF tutorial at
http://www.bgnett.no/~peter/pf/ to familiarize yourself with the
system.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no
. See if it makes a difference.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
20:11:56 delilah spamd[26905]: 146.151.48.74
/bruteforce.html.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
20:11:56 delilah spamd[26905]: 146.151.48.74: disconnected after
N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
20:11:56 delilah spamd[26905]: 146.151.48.74: disconnected after 36099 seconds
, ie
set limit table-entries 15
in your pf.conf would set the upper limit for number of entries in a
table to 15.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all
this route, you might want to use expiretable
(/usr/ports/security/expiretable) to trim the contents of the table
after a while (I tend to use 24 hours expiry).
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http
pointers. I suppose even people not in
your area should be able to burn you an install CD and mail it to you if
that is what you need to get started.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no
andrew clarke [EMAIL PROTECTED] writes:
Is it possible to configure the FreeBSD firewall to block ports on a
per-user or per-executable basis?
If your firewall is PF, you can use authpf(8) to configure per user rule sets.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation
want to look at
the expiretable utility (http://expiretable.fnord.se/).
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
Imran Imtiaz [EMAIL PROTECTED] writes:
how can i make my dlink DWL-G122 wireless usb adapter work with freebsd?
IIRC it's supported by the ural driver. With that knowledge and the
wireless networking chapter in the Handbook, you should be fine.
--
Peter N. M. Hansteen, member of the first
'ifconfig ath0'
showa status: associated, and finally
# dhclient ath0
should get you an IP address, again assuming a DHCP server is within reach.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First
that does - http://www.bgnett.no/~peter/pf/
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
://www.benzedrine.cx/transquid.html
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
overload tableofbadbuys in your pass rule. See pf.conf(5) for
details. There's probably some magic around to make this doable with
other firewalls as well.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http
these are common when either your reverse lookup isn't correct or
the name servers your domain/IP range are unavailable or slow in
answering.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we
should not be surprised that
one or more iso files have not appeared where you expect them yet.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard
to disable inetd, and
switch ftpd with pure-ftpd?
You could try running ftpsesame or pftpx instead.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet
little bits of ftp
through NAT and/or firewalls magic comes in very handy.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
, but none which let traffic in on the internal
interface.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
(or perhaps not in this particular case). I enjoy
reading Daemon News (http://daemonnews.org) for a variety of reasons,
and I vaguely remember some sensible articles on this very topic
there. That URL also takes you within clicking distance of a good number
of useful BSD sites.
--
Peter N. M
$allowedports keep state
or even
pass from $int_if:network to any port $allowedports keep state
(if you can do without the extra per interface housekeeping) would make
things a bit easier.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http
in 4.11 - kde
and gnome respectively - and I think tihs will also be the case for 5.n
releases from 5.4 onwards). disc2 is traditionally the live filesystem,
while miniinst is for a minimal install.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no
on very
little information.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
has not
been properly configured.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
user would get along fine on a typical
desktop system in their local language, IME. On the other hand your
friendly sysadmin would likely be at a great disadvantage with little or
no English.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149
, there's been a lot of
localization related trouble there. But then we're relatively safe from
the secret brainfarts of Microsoft developers here.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First
/programming language
keywords (yes, I have more than 15 years' experience in the localization
industry, I've seen quite a bit of such foolishness) and the software is
sanely written, messages are fairly straightforward and risk-free to
translate. .
--
Peter N. M. Hansteen, member of the first RFC
any replies sent to the list only. Anyway the mailing list's home
page is at http://www.benzedrine.cx/mailinglist.html
(Sorry for the delay - bgnett's mail servers apparently were a bit
overwhelmed some worm or other, leaving useful traffic queued rather
longer than I appreciate.)
--
Peter N. M
-in keep state
and so on. Hope this helps.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
initiated from the inside would match the pass out rule's
counters, while connections opened from the outside would count on the
pass in rules.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we
an angle we haven't thought of.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
wipe
out stuff it does not understand. There are several howtos out there
within search engine reach which will be helpful.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all
of bytes
and packets passed or blocked. If you use labels in your pass rules,
you'll get per label counters as well.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers
the relevant counters only once.
Perhaps you know where I can find workable example of this?
Randal Schwartz has a nice article called Monitoring Net Traffic with
OpenBSD's Packet Filter at
http://www.samag.com/documents/s=9053/sam0403j/0403j.htm
--
Peter N. M. Hansteen, member of the first RFC
know you're dying to ask - we do rsync to an off-site location
twice a day)
- P
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded
alone otherwise. Removing all traces of pf would
likely take a bit of effort.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded
prefer the Norwegian version)
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
, you
would normally use rc.conf settings, ie
gateway_enable=YES #for ipv4
ipv6_gateway_enable=YES #for ipv6
to enable gatewaying.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill
the anchor in the main pf.conf file produce different results?
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
Anthony Atkielski [EMAIL PROTECTED] writes:
Why are people asserting their own copyrights in the code?
Because they wrote the software in question, perhaps?
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http
holder who withdraws a license and an
entire package can become unusable.
i assume you have been told about the 'published under a license' phenomenon.
To me it sounds like you need to read up on a few things.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http
/ for some info on getting
started.
In the meantime, if short term migration is not an option, you might
want to look at something like Firewall Builder(http://www.fwbuilder.org)
which I believe is able to generate configurations for PF, IPFW,
IPFilter and iptables from a common XML source.
--
Peter N
you get here generally
improves with the precision in reporting such things as error messages.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice
) litters
messages with X-ThreadIndex and X-ThreadSubject headers, apparently
attempting to reinvent References: and other usenet features.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First
book stores (online or
otherwise).
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
, or for that
matter, from people who run rougly the same things you do. If you need a
different configuration for what you want to do, symptoms will show up
soon enough.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http
at
http://undeadly.org/cgi?action=articlesid=20041231195454
Then again, at least in some cases, the people listed in the whois info
for the offending IP appreciate a politely worded notification. Quite
likely they do not want this kind of activity either.
--
Peter N. M. Hansteen, member of the first
*and* tcp is turned off while you're at it.
These are at least some of the more common errors.
Good luck with the debugging!
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all
items I could tell you about if %#^
NO CARRIER
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
to making FreeBSD 1.1.4 packages yet. Then
again, I'm not sure what got fixed between 1.1.3 and 1.1.4.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard
ones in ports. imap-uw is very easy to set up.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
to boot at all, well, there it is. I'd
venture a guess that whichever software came with the machine originally
is not quite 64 bit clean either.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no
the java tools install which is needed to build the port. Unless that
challence is interesting in itself, it's probably more convenient to
download and install a binary package from somewhere in the general
direction of http://download.openoffice.org/1.1.4/index.html
--
Peter N. M. Hansteen, member
and the .inf file in a
directory together. After installation in a Microsoft file system that
may of course no longer be the case.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all
hardware, we never saw problematic media failure rates
back then. The awful media quality started after CDs became the default
software distribution medium.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http
this is the kind of challenge you were
longing for in the first place, I don't think it's worth the effort.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet
instructions to add spam and virus filtering to the
delivery process. Nice for those of us serving Microsoft desktops.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers
to happen.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
___
freebsd-questions
was the one-line ZAxisMapping magic to make the touchpad's
scroll strip (similar to mouse wheel) work. Then again that was
cutpasteable from somewhere else. Everything else pretty much just
automagically worked.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http
to be quite functional so far). There's a bit more info available
at http://porting.openoffice.org/freebsd/ too.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers
-11/1534.html
which seems to do what you ask. Also, ntpd(8) might be of interest.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded
the program runs). Anybody else seen something like
this?
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
important data, then use
whichever tools come with the operating system you want to set up install
that system and configure it. The exact steps depend on which operating
system you want to run instead of FreeBSD.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http
contain quite a number of useful references).
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
Lowell Gilbert [EMAIL PROTECTED] writes:
I've moved password entries from 4.x to 5.x with no problem.
Did you remember to rebuild the database?
er, it seems that was the problem, exactly. Thanks!
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http
:
There was a change in the passwd format. Need more information.
Any pointers appreciated.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/
First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
1 - 100 of 105 matches
Mail list logo