On Tue, Feb 14, 2017 at 02:56:01PM -0500, Ted Unangst wrote:
| Paul de Weerd wrote:
| > Well, in my case I can simply not use doas -n and ensure my script
| > works without prompting for passwords more than once (which is what I
| > care about). However, I have to say that doas works great in
| >
>Synopsis: Feature request: honor proxy setting in pkg.conf
>Category: user
>Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0-current (GENERIC) #167: Sun Feb 12 13:50:27
MST 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/c
On 2017/02/14 16:56, Paul de Weerd wrote:
> On Tue, Feb 14, 2017 at 04:29:56PM +0100, Sebastian Benoit wrote:
> | > Is this a bug in doas or in the manpage?
> |
> | The -n option helps to use doas non-interactively.
> | Its debateable wether 'persist' is useful with non-interactive usage, but
> |
Otto Moerbeek wrote:
> On Tue, Feb 14, 2017 at 02:56:01PM -0500, Ted Unangst wrote:
>
> > Paul de Weerd wrote:
> > > Well, in my case I can simply not use doas -n and ensure my script
> > > works without prompting for passwords more than once (which is what I
> > > care about). However, I have t
On Tue, Feb 14, 2017 at 02:56:01PM -0500, Ted Unangst wrote:
> Paul de Weerd wrote:
> > Well, in my case I can simply not use doas -n and ensure my script
> > works without prompting for passwords more than once (which is what I
> > care about). However, I have to say that doas works great in
>
Paul de Weerd wrote:
> Well, in my case I can simply not use doas -n and ensure my script
> works without prompting for passwords more than once (which is what I
> care about). However, I have to say that doas works great in
> scripting setups: it asks for a password once and then all subsequent
Hi Ted,
On Tue, Feb 14, 2017 at 11:37:30AM -0500, Ted Unangst wrote:
| So the man page currently says "fail if doas would prompt for password."
| although it would be more accurate to say "fail if does may prompt for a
| password". The purpose of -n is to make sure a script will run with or withou
On Tue, Feb 14, 2017 at 03:50:05PM +0100, Federico Consoli wrote:
> Hi,
> I have a doubt about openbsd/usr.sbin/lpr/lpr/lpr.c function "static char
> * itoa(int i)", I see that it can cause a problem for i>(9+1).
> I don't test the code, I made only a code analysis.
>
> Regards
>
> Eng.
Sebastian Benoit wrote:
> The -n option helps to use doas non-interactively.
> Its debateable wether 'persist' is useful with non-interactive usage, but
> this fixes it:
So the man page currently says "fail if doas would prompt for password."
although it would be more accurate to say "fail if does
Theo Buehler wrote:
> On Tue, Feb 14, 2017 at 03:57:43PM +0100, Paul de Weerd wrote:
> > Consider the following:
> >
> >1 [weerd@despair] $ doas true
> >2 doas (we...@despair.weirdnet.nl) password:
> >3 [weerd@despair] $ doas true
> >4 [weerd@despair] $ doas -n tru
On Tue, Feb 14, 2017 at 04:29:56PM +0100, Sebastian Benoit wrote:
| > Is this a bug in doas or in the manpage?
|
| The -n option helps to use doas non-interactively.
| Its debateable wether 'persist' is useful with non-interactive usage, but
| this fixes it:
Thanks Benno, I'll test it later tonig
On 02/14/17 16:29, Sebastian Benoit wrote:
> Paul de Weerd(we...@weirdnet.nl) on 2017.02.14 15:57:43 +0100:
>> Consider the following:
>>
>>1 [weerd@despair] $ doas true
>>2 doas (we...@despair.weirdnet.nl) password:
>>3 [weerd@despair] $ doas true
>>4 [weerd@despai
On Tue, Feb 14, 2017 at 03:57:43PM +0100, Paul de Weerd wrote:
> Consider the following:
>
>1 [weerd@despair] $ doas true
>2 doas (we...@despair.weirdnet.nl) password:
>3 [weerd@despair] $ doas true
>4 [weerd@despair] $ doas -n true
>5 doas: Authorization r
Paul de Weerd(we...@weirdnet.nl) on 2017.02.14 15:57:43 +0100:
> Consider the following:
>
>1 [weerd@despair] $ doas true
>2 doas (we...@despair.weirdnet.nl) password:
>3 [weerd@despair] $ doas true
>4 [weerd@despair] $ doas -n true
>5 doas: Authorization r
Consider the following:
1 [weerd@despair] $ doas true
2 doas (we...@despair.weirdnet.nl) password:
3 [weerd@despair] $ doas true
4 [weerd@despair] $ doas -n true
5 doas: Authorization required
I have 'persist' to allow doas to not prompt for a password on
subse
Hi,
I have a doubt about openbsd/usr.sbin/lpr/lpr/lpr.c function "static char
* itoa(int i)", I see that it can cause a problem for i>(9+1).
I don't test the code, I made only a code analysis.
Regards
Eng. Consoli Federico
On Tue, Feb 14, 2017 at 02:02:46PM +0100, Peter Hessler wrote:
> On 2017 Feb 14 (Tue) at 23:26:32 +1100 (+1100), Jonathan Gray wrote:
> :On Tue, Feb 14, 2017 at 01:04:40PM +0100, Sebastian Benoit wrote:
> :> Jonathan Gray(j...@jsg.id.au) on 2017.02.14 20:23:51 +1100:
> :> > On Tue, Feb 14, 2017 at
On 2017 Feb 14 (Tue) at 23:26:32 +1100 (+1100), Jonathan Gray wrote:
:On Tue, Feb 14, 2017 at 01:04:40PM +0100, Sebastian Benoit wrote:
:> Jonathan Gray(j...@jsg.id.au) on 2017.02.14 20:23:51 +1100:
:> > On Tue, Feb 14, 2017 at 10:00:17AM +0100, Peter Hessler wrote:
:> > > On 2017 Feb 14 (Tue) at 1
On Tue, Feb 14, 2017 at 01:04:40PM +0100, Sebastian Benoit wrote:
> Jonathan Gray(j...@jsg.id.au) on 2017.02.14 20:23:51 +1100:
> > On Tue, Feb 14, 2017 at 10:00:17AM +0100, Peter Hessler wrote:
> > > On 2017 Feb 14 (Tue) at 15:39:45 +1100 (+1100), Jonathan Gray wrote:
> > > :The bgpctl parser for
Jonathan Gray(j...@jsg.id.au) on 2017.02.14 20:23:51 +1100:
> On Tue, Feb 14, 2017 at 10:00:17AM +0100, Peter Hessler wrote:
> > On 2017 Feb 14 (Tue) at 15:39:45 +1100 (+1100), Jonathan Gray wrote:
> > :The bgpctl parser for large communities makes invalid assumptions about
> > :the string passed i
On Tue, Feb 14, 2017 at 10:00:17AM +0100, Peter Hessler wrote:
> On 2017 Feb 14 (Tue) at 15:39:45 +1100 (+1100), Jonathan Gray wrote:
> :The bgpctl parser for large communities makes invalid assumptions about
> :the string passed into parse_largecommunity() and also seems to leak
> :the memory retu
On 2017 Feb 14 (Tue) at 15:39:45 +1100 (+1100), Jonathan Gray wrote:
:The bgpctl parser for large communities makes invalid assumptions about
:the string passed into parse_largecommunity() and also seems to leak
:the memory returned by strdup in the same function.
:
:(gdb) run show rib large-commun
22 matches
Mail list logo