On Thu, May 31, 2018 at 10:25:54PM +0200, Eric Faurot wrote:
>
> Hello.
>
> This makes sense, indeed.
>
> Here is a slightly updated diff for your proposal. It makes the
> documentatino more accurate: the server certificate is always
> verified, the flag is only meant to accept invalid certific
To make testing easier, I temporarily committed a port to WIP repo:
https://github.com/jasperla/openbsd-wip/tree/master/editors/umg
I won't submit it to ports@, this is experimental and only for testing.
Hi,
Is there any feedback on this?
Thanks
> > > I tested removing some slop (i.e. structure packing/de-holing) on amd64,
> > > this went through a full kernel + userland build.
> > >
> >
> > Parts of this are probably okay, but there's some stuff which needs better
> > placement vs comments an
On Thu, May 31, 2018 at 10:25:54PM +0200, Eric Faurot wrote:
> On Thu, May 31, 2018 at 04:06:31PM +0200, Sebastien Marie wrote:
> > Hi,
> >
> > When using smarthost ("host" option of "relay") for outgoing mails, TLS
> > connection aren't verified. If it could make sens for standard MX, I
> > think
On Thu, May 31, 2018 at 04:06:31PM +0200, Sebastien Marie wrote:
> Hi,
>
> When using smarthost ("host" option of "relay") for outgoing mails, TLS
> connection aren't verified. If it could make sens for standard MX, I
> think it would be better to verify the connection by default if the user
> spe
Here's a fixed version of my previous diff that does not accidentally
add a walk over the ifa_list to SIOCSIFADDR.
Instead, start with a merged version of SIOCSIFADDR, add a copy of the
walk to both SIOCAIFADDR and SIOCDIFADDR and add the allocation of the
ia to SIACAIFADDR. As before, start each
On Thu, May 31, 2018 at 04:06:31PM +0200, Sebastien Marie wrote:
> Hi,
>
> When using smarthost ("host" option of "relay") for outgoing mails, TLS
> connection aren't verified. If it could make sens for standard MX, I
> think it would be better to verify the connection by default if the user
> spe
On Thu, May 31, 2018 at 11:12:38AM +, Job Snijders wrote:
> On Wed, May 30, 2018 at 03:18:45PM +0200, Claudio Jeker wrote:
> > This adds a protection to handle aspaths overly large attributes in
> > bgpd. The main idea is to protect other bgp routes downstream for
> > hitting the limit with is
Hi,
When using smarthost ("host" option of "relay") for outgoing mails, TLS
connection aren't verified. If it could make sens for standard MX, I
think it would be better to verify the connection by default if the user
specifies a TLS-aware url for the relay.
The diff below changes the behaviour o
On Thu, May 31, 2018 at 03:22:02PM +0200, Sebastien Marie wrote:
> Hi,
>
> The following diff corrects smtpd.conf man page in two ways:
>
> - Replace virtual(5) reference by table(5) as virtual table format is
> documentation in table(5) man page under "Aliasing tables" section.
>
> - Add "aut
Hi,
The following diff corrects smtpd.conf man page in two ways:
- Replace virtual(5) reference by table(5) as virtual table format is
documentation in table(5) man page under "Aliasing tables" section.
- Add "auth " documentation. Example at end of the man page uses
it, so it should be docu
On Wed, May 30, 2018 at 04:49:15AM +0200, Theo Buehler wrote:
> We can finally get rid of one switch in both, in_ioctl() and
> in_ioctl_change_ifaddr(). With this diff we have one case per ioctl,
> each case dealing with an ioctl starts with a privilege check before any
> global data is modified an
On 09/05/18(Wed) 14:19, Paul Irofti wrote:
> > [...]
> > I'd prefer if we could teach each other how stuff really work :o)
>
> Frankly someone else will have to enlighten me (or us) if we really
> need to do this.
That's what guenther@ and visa@ did. So I believe you should move
forward and comm
Martin Pieuchot wrote:
> Here's a new version of my diff to remove the FIF_LARVAL flag.
>
> Larval files still exist, but at this stage they aren't present in
> `fd_ofiles[]'. That means we don't need specific tricks in fd_getfile()
> and fd_iterfile(). The idea is to put files in shared data st
On Wed, May 30, 2018 at 03:18:45PM +0200, Claudio Jeker wrote:
> This adds a protection to handle aspaths overly large attributes in
> bgpd. The main idea is to protect other bgp routes downstream for
> hitting the limit with is often not well catched.
I am not sure this is sound logic. The BGP UP
Hi Gerhard,
Thanks for your reply!
Yes, if no "kvm_close(kd);", there will be resource (memory, file
descriptor) leak. So hope you can commit it, thanks!
On 5/30/2018 4:49 PM, Gerhard Roth wrote:
> On Wed, 30 May 2018 16:25:55 +0800 Nan Xiao wrote:
>> Hi tech@,
>>
>> Maybe kvm_close is needed
It turns out that the split is now such that 'ifra' is only used once in
in_ioctl() and 'ifr' is only used once in in_ioctl_change_ifaddr().
Is there a reason not to do this?
Index: sys/netinet/in.c
===
RCS file: /cvs/src/sys/netinet
17 matches
Mail list logo