XPost: comp.mobile.android, alt.comp.freeware   
   From: arlen@arlen.com   
      
   On Thu, 24 Jan 2019 07:34:06 +0100 (GMT+01:00), Libor Striz wrote:   
      
   > You may have do too shallow tests.   
      
   Hi Poutnik,   
   I agree with you!   
   I do NOT know how to test keyboards.   
   I admit when I'm out of my league.   
      
   They all looked the same to me in my "shallow" tests.   
      
   If there was a good "yes/no" test for a custom keyboard,   
   that would be GREAT.   
      
   Right now, I'm testing iOS apps so I haven't gotten back   
   to the keyboard issue.   
      
   However, I do AGREE with you that avoiding keyloggers   
   for a password database is IMPORTANT!   
      
   > They use the same default keyboard,   
   > as there is the Android limitation  for them to change it on their own.   
      
   Thanks for clarifying their keyboards "look" like the defaults.   
      
   It would be nice if we can figure out a GOOD TEST to prove   
   whether we're using a default keyboard or a custom keyboard.   
      
   > The *user* has to switch the keyboard himself for security   
   >  reasons. It us often  possible from Android notification   
   >  field when a user is at text input fields.   
      
   My keyboard on my phone is the default keyboard.   
   I have, in the past, switched keyboards.   
   I did that mostly to get "bigger buttons" for my fat fingers.   
   I also tried, and failed, to find an AUDIO-default keyboard.   
      
   But those are topics for another day.   
      
   What we need now is a FOOLPROOF way to tell whether the password   
   manager is using the DEFAULT keyboard or a CUSTOM keyboard.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)