[BUG?] busybox sed fails to process ncurses scripts

2012-05-06 Thread John Spencer
when compiling ncurses 5.9 with busybox sed, it'll produce invalid C files ../ncurses/lib_gen.c:27:3: error: expected identifier or '(' before 'int' the file contains: /* DO NOT EDIT THIS FILE BY HAND! * It is generated by ./base/MKlib_gen.sh generated. */ the line that errs is * int waddch(std

Re: OTP feature for /bin/login

2012-05-06 Thread Guylhem
Hello On Sun, May 6, 2012 at 11:51 AM, Rich Felker wrote: > This argument can be made for any _ONE_ custom authentication feature. > The problem is that if it's made for _EVERY_ custom authentication > feature, you have a bloatware nightmare. Very true. But at least one authentification feature

Re: Miscellaneous Busybox patches.

2012-05-06 Thread Denys Vlasenko
On Fri, Apr 27, 2012 at 4:14 AM, Simon B wrote: > However on this occasion, I've needed to patch busybox to support some extra > flags that it is currently missing, and that I have scripts that need to run > in a cut-down environment that rely on that functionality. Given the scripts > are less in

Re: OTP feature for /bin/login

2012-05-06 Thread Rich Felker
On Sun, May 06, 2012 at 10:48:35AM -0400, Guylhem wrote: > IMHO a PAM module is overtly complicated. I noticed correct_password > did also handle shadow password verification. > > Considering OTP just adds a little bit to the file size (and the code > is not optimized yet - it could certainly be i

Re: OTP feature for /bin/login

2012-05-06 Thread Guylhem
Hello On Sun, May 6, 2012 at 4:02 AM, Tito wrote: > The implementation explained in the article seems to differ a little from > what you propose but the "sheet of paper" weak point still remains No - I do not pregenerate any kind of list of password. The shared secret is stored in the MOTP appli

Re: OTP feature for /bin/login

2012-05-06 Thread Tito
On Sunday 06 May 2012 08:22:49 Alexander Kriegisch wrote: > Guylhem, 05.05.2012 23:50: > > I was thinking about someone at work behind a company firewall where > > maybe only outgoing port 80 and port 23 are opened, along with deep > > packet inspection to avoid ssh listening on port 80. Or add p

Re: OTP feature for /bin/login

2012-05-06 Thread Sedat Dilek
On Sun, May 6, 2012 at 8:22 AM, Alexander Kriegisch wrote: > Guylhem, 05.05.2012 23:50: >> I was thinking about someone at work behind a company firewall where >> maybe only outgoing port 80 and port 23 are opened, along with deep >> packet inspection to avoid ssh listening on port 80. Or add port