I want to try to implement some form of concealed port knocking in
OpenBSD, along the lines of Martin Kirsch:
https://gnunet.org/sites/default/files/ma_kirsch_2014_0.pdf
The application is electronic democracy. I want to demonstrate how it
is possible to do secure comms. over untrusted networ
On Fri, Oct 10, 2014 at 08:02:17PM +0100, Stuart Henderson wrote:
> On 2014/10/10 15:19, Patrik Lundin wrote:
> > Not passing any arguments does not mean "do not modify any flags", it
> > means "make sure we have the default flags". Because of this I will need
> > to check if the current set of fla
On 2014/10/10 15:19, Patrik Lundin wrote:
> Not passing any arguments does not mean "do not modify any flags", it
> means "make sure we have the default flags". Because of this I will need
> to check if the current set of flags are the default or not.
Would it make sense for rcctl status to displa
On Fri, Oct 10, 2014 at 03:53:15PM +0200, Antoine Jacoutot wrote:
> > Maby the expected results of our tools are different. My goal for the
> > ansible module is that you either keep a specific set of flags in the
> >
> > playbook which will then get set if necessary, or you remove the flags
> > a
On Fri, Oct 10, 2014 at 01:02:17PM -0400, Ted Unangst wrote:
> On Sun, Oct 05, 2014 at 19:42, Martin Natano wrote:
> > Let's make tree.h conform to style(9).
> >
> > Index: tree.h
> > ===
> > RCS file: /cvs/src/sys/sys/tree.h,v
> > re
On Sun, Oct 05, 2014 at 19:42, Martin Natano wrote:
> Let's make tree.h conform to style(9).
>
> Index: tree.h
> ===
> RCS file: /cvs/src/sys/sys/tree.h,v
> retrieving revision 1.13
> diff -u -r1.13 tree.h
> --- tree.h9 Jul 2011 0
> Maby the expected results of our tools are different. My goal for the
> ansible module is that you either keep a specific set of flags in the
>
> playbook which will then get set if necessary, or you remove the flags
> and will instead get the system default.
>
> Not passing any arguments does
> 4. Enable the service *without* any arguments (even if it has
> default arguments).
It's been discussed at lenght in Slovenia -- that's a known issue; the move of
rc.conf to a parsed config file has had similar side effects on other stuffs.
> I see no way to do that with rcctl(8).
>
Ouch.
I just noticed the following problem.
There are four things a user might want:
1. Disable a service.
rcctl disable service
always does that,
and you can compare the output of
rcctl status service
to "NO" to decide whether running that is actually needed.
2. Enabl
On Fri, Oct 10, 2014 at 03:05:40PM +0200, Antoine Jacoutot wrote:
>
> But you should not have to.
> If you don't pass any flags to ansible, why is ansible looking at the output
> of rcctl status to compare flags?
> In saltstack, iirc what I implemented is that flags are only compared when
> one
On Fri, Oct 10, 2014 at 02:50:40PM +0200, Patrik Lundin wrote:
> On Fri, Oct 10, 2014 at 01:50:52PM +0200, Antoine Jacoutot wrote:
> > >
> > > If I now run the tool again, still without any supplied arguments, it
> > > will compare the empty set of user supplied flags to "-tun 4" which
> > > alway
On Fri, Oct 10, 2014 at 01:50:52PM +0200, Antoine Jacoutot wrote:
> >
> > If I now run the tool again, still without any supplied arguments, it
> > will compare the empty set of user supplied flags to "-tun 4" which
> > always differs. So ansible will now think it needs to change something
> > "fo
On Fri, 10 Oct 2014 15:17:55 +1000, David Gwynne wrote:
> theo made me look at where i was using POLLHUP, so i read your
> comment and the poll manpage again.
OK millert@
- todd
> The problem occurs when I try to manage a service like nfsd which has a
> default set of flags. Consider the following commands, which basically
> performs what ansible does when the user is not supplying any extra
> arguments:
> ---
> # rcctl status nfsd
> NO
> # rcctl enable nfsd
14 matches
Mail list logo
