I just noticed that I have a little bug in there, triggered through
"exec -a foo" with no parameter following, it can be fixed by replacing the
line
if (strcmp(argv[1], "-a") == 0 && argv[2]) {
with
if (strcmp(argv[1], "-a") == 0 && argv[2] && argv[3]) {
to check whether an argument
Hello,
As noted in http://unix.stackexchange.com/q/340333/117599 BBox's login has no
way for setting LOGIN_TIMEOUT, it's always there and hardcoded to 60 seconds.
What would you think if there was support for it but not through a setting in
/etc/login.conf or similar but instead through a
Hey,
> And, don't duplicate another function if what you did is only extending a
> functionality of that function. BusyBox is coded with size in mind.
I know, and I am reminded of it whenever I look at Busybox's source code.
:)
I thought that this way it might be easier to comment out, but
On 01/19/2017 08:17 AM, Denys Vlasenko wrote:
> Hi folks,
>
> Now that I have some code reaching a state where
> it does talk TLS 1.2, the question is how to integrate it.
This is one of my longstanding todo items for toybox too.
> TLS i/o entails some buffering.
Possibly protocol-required? You
On Fri, Jan 27, 2017 at 7:56 AM, Patrick Pief wrote:
> There were several times where I thought that having "exec -a" in busybox
> would
> be neat, and while "exec -a" is not POSIX it is still supported in a lot of
> shells (see http://unix.stackexchange.com/q/250681/117599 ).
>