Mercurial > dropbear
view list.h @ 1930:299f4f19ba19
Add /usr/sbin and /sbin to default root PATH
When dropbear is used in a very restricted environment (such as in a
initrd), the default user shell is often also very restricted
and doesn't take care of setting the PATH so the user ends up
with the PATH set by dropbear. Unfortunately, dropbear always
sets "/usr/bin:/bin" as default PATH even for the root user
which should have /usr/sbin and /sbin too.
For a concrete instance of this problem, see the "Remote Unlocking"
section in this tutorial: https://paxswill.com/blog/2013/11/04/encrypted-raspberry-pi/
It speaks of a bug in the initramfs script because it's written "blkid"
instead of "/sbin/blkid"... this is just because the scripts from the
initramfs do not expect to have a PATH without the sbin directories and
because dropbear is not setting the PATH appropriately for the root user.
I'm thus suggesting to use the attached patch to fix this misbehaviour (I
did not test it, but it's easy enough). It might seem anecdotic but
multiple Kali users have been bitten by this.
From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903403
author | Raphael Hertzog <hertzog@debian.org> |
---|---|
date | Mon, 09 Jul 2018 16:27:53 +0200 |
parents | 9169e4e7cbee |
children |
line wrap: on
line source
#ifndef DROPBEAR_DROPBEAR_LIST_H #define DROPBEAR_DROPBEAR_LIST_H struct _m_list; struct _m_list_elem { void *item; struct _m_list_elem *next; struct _m_list_elem *prev; struct _m_list *list; }; typedef struct _m_list_elem m_list_elem; struct _m_list { m_list_elem *first; m_list_elem *last; }; typedef struct _m_list m_list; m_list * list_new(void); void list_append(m_list *list, void *item); /* returns the item for the element removed */ void * list_remove(m_list_elem *elem); #endif /* DROPBEAR_DROPBEAR_LIST_H */