Ensuring safety and security in outdoor spaces stands as a paramount
concern, and ATISystems.com <http://atisystems.com/> leads the way with
innovative solutions crafted to safeguard communities and businesses.
Specializing in state-of-the-art giant voice systems and outdoor warning
On 1/18/2017 1:25 PM, Rick Stevens wrote:
That's not what's happening here. The user is starting a program, then
immediately typing in the expected password before the program starts,
essentially making use of the type-ahead capability of the shell.
The program hasn't, well, "registered" its stdi
On 01/18/2017 10:09 AM, Tom Rivers wrote:
> On 1/18/2017 12:24 PM, Rick Stevens wrote:
>> That's normal. The system (or shell) is echoing the input because the
>> program you expect to consume the input isn't running or hasn't
>> finished initializing yet. What do you expect the system to do? Not
>
On 1/18/2017 12:24 PM, Rick Stevens wrote:
That's normal. The system (or shell) is echoing the input because the
program you expect to consume the input isn't running or hasn't
finished initializing yet. What do you expect the system to do? Not
echo anything unless explicitly told to?
Perhaps I
On 01/18/2017 08:25 AM, Joachim Backes wrote:
> On 01/18/17 15:51, Patrick Dupre wrote:
>> Hello,
>>
>> When you log from the graphics interface (gnome) and provide the
>> password, if the system is slow (long response time), then the
>> password can appear in clear !!!
>
> Hi Patrick,
>
> having
On 01/18/17 15:51, Patrick Dupre wrote:
Hello,
When you log from the graphics interface (gnome) and provide the
password, if the system is slow (long response time), then the
password can appear in clear !!!
Hi Patrick,
having the same issue if booting into runlevel 3 and then login:
if I'm t
Hello,
When you log from the graphics interface (gnome) and provide the
password, if the system is slow (long response time), then the
password can appear in clear !!!
This my be annoying!
===
Patrick DUPRÉ | | email: pdu..
