Hey misc,
so I know there is a better way to posting Bugs. But i not really got
all information needed to post it to bugs@ or better: i have the
information in a unpropper way. So I dont really mind if you not
answer i just thought it would be a nice information that my panic
happened.
So I insta
KET, SO_PFTAG, bla, &a);
Bye
Konrad
[demime 1.01d removed an attachment of type application/octet-stream which had
a name of sockopt.diff]
So sorry its not a propper diff anymore but this is what i've done:
--- sys.bak/kern/uipc_socket.c Wed Mar 5 21:11:31 2008
+++ sys/kern/uipc_socket.c Thu Mar 6 06:50:29 2008
@@ -48,6 +48,8 @@
#include
#include
+#include
+
void filt_sordetach(struct knote *kn);
intfilt_soread(
Hey
so now I changed the tagging from tcp_output to ip_output.
I also put an pf_tag_unref to so_free and sosetopt (in case that there
is allready a tag set).
I couldn't see a reason for a pf_tag_unref in the so_accept because
the socket could be reused.
Thanks to Henning for the ideas!
Any furthe
> Nice, you probably want to keep the application/kernel tag name spaces
> distinct though. Otherwise it would be easy for any local user/program
> to mess with pf.conf generated tags and bypass filtering etc. It could
> be as easy as adding a prefix ("APP_" ?) to all application generated
> ta
> > I couldn't see a reason for a pf_tag_unref in the so_accept because
> > the socket could be reused.
>
> don't we need an additional ref (aka tagname2tag or the like), not unref,
> since the socket gets cloned?
>
if you want a diffrent tag on the resulting socket, then we have a
problem, bec
So now I added the ip6_output and I think i got a solution for the
accept, but I'm not 100% sure if that is enough. I tested it and it
looked fine. I couldn't test the ip6_output, because i don't have the
enviroment for it till now :) I'll hope to do this tommorw.
The '@'-thing is something comple
hmm so by the way.. it was a mistake form my side, the pf.conf takes
the @ if the rule is:
block out on fxp1 tagged "@foo"
instead of:
block out on fxp1 tagged @foo
I allready implement it and test it would work, the question for me
is, if the uid would be necessary and the namespace is enough,
Yes it is.
After install, you copy ofwboot in your root of Mac OS X and after
reboot holding O + F+ ALT + APPLE ;) and type:
boot hd:,ofwboot /bsd
but you should simply read the install instruction:
ftp://ftp.openbsd.org/pub/OpenBSD/4.2/macppc/INSTALL.macppc
greetz
Konrad
2007/12/3, Paolo
... but I found out that
I never booted Linux so I do a dual boot now.
Regards
-Konrad
Humppa,
this all is a proof that OpenBSD is much more than a ordinary OS
2007/7/19, Serge Basterot <[EMAIL PROTECTED]>:
On Wed, Jul 18, 2007 at 10:45:56AM +0200, Guido Tschakert wrote:
> Peter N. M. Hansteen wrote:
> > "Anton Karpov" <[EMAIL PROTECTED]> writes:
> >
> >> People who don't know ea
Hey List,
I've testing the installation after reading this thread on my ibook G4
(Mid 2005) and the installation in current faild by the devel/boost
port.
It ist not sooo important for me, because of the lack of nice color on
X but it would be funny.
bye Konrad
===> gnash-0.8.0p0 de
stall
OpenBSD without this driver! I see that the driver is listed in the
man pages so i hope...
bye
Konrad
I had the same problem like Ikmal but now is alright!
2007/5/25, Ioan Nemes <[EMAIL PROTECTED]>:
No problem here.
Ioan
>>> "Ikmal Ahmad" <[EMAIL PROTECTED]> 05/25 1:18 pm >>>
Hi,
http://www.openbsd.org/
Forbidden
You don't have permission to access / on this server.
Apache/1.3.34 Server
Hey at all,
I know the most people dont like trolls and me too! But the last to
days I've laughed so often ... the misc@ list has a pretty cool humor,
for sure.
Bye
Konrad
15 matches
Mail list logo