Glad to hear you got there.
Congrats -- Ross
On 7/06/2013, at 13:47, Craig McQueen <912...@bugs.launchpad.net> wrote:
> I've sorted it out now. Sorry, I was doing something stupid. I had
> thought "it was working" but I was still actually running the original
> pam-blue. I thought it was "worki
Dear Craig
No I can't see why it wouldn't work -- it worked for me with gnome-screensaver
and Ubuntu 10.
Perhaps you will get a clue from the system logfiles.
You might also try running hcitool as the user running the screensaver and make
sure that user has bluetooth access permissions.
Good
Dear Craig
As you'll see from the bug report, I found it easier to replace l2ping
with hcitool. That worked for me, and I moved on.
Kind regards -- Ross
On 4/06/2013, at 11:36, Craig McQueen <912...@bugs.launchpad.net> wrote:
> Is pam_blue maintained? It's looking a bit dead at the moment. How
OK, so this version of the patch to bluescan.c is fixed to handle error
conditions gracefully { return(false) instead of exit(1) } and to
report errors using syslog()
Another strange point that I don't understand -- pam_blue, as compiled from the
source package, expects its configuration files i
Patching bluescan.c to follow hcitool rather than l2ping seems to work for both
login and gnome-screensaver.
The disadvantage that I can see is that there is no way to change the timeout.
The patch is attached.
** Patch added: "Patch bluescan.c to use hci_read_remote_name"
https://bugs.l
Public bug reported:
I modified /etc/pam.d/common-auth to allow two-factor authentication
using password and either bluetooth proximity or, if that fails, google-
authenticator:
. . .
# here are the per-package modules (the "Primary" block)
auth[success=1 default=ignore] pam_unix.so null
