Looking for beta testers for v0.3

[Thomas Fors]

I've made a number of enhancements since ver 0.2 including PPP version
2 support now. It should prompt the user to update their key in a
safe manner so they aren't locked out.

I'm going to hold off on labeling it 0.3 until I allow some time for
people to test and provide feedback.

To test it, you'll want to update to rev 66:

svn update -r 66

Then rebuild and install.

To get the warnings at login, you'll need to add the following line
to /etc/pam.d/sshd

session required pam_ppp.so

To see a more complete list of what's changed since ver 0.2, run:

svn log -r 34:66

--Tom

[zzzirk]

Tom, I've built this on my debian system and have tested that it both
prompts me for an upgrade, and that the upgrade works. I've yet to
build it on my PPC OSX Leopard system, but will try and do that and
get back here with results.

Everything in the build and install under debian went without flaws
for me. Not much of a status report other than a 'it works for me',
sorry. Hopefully that's a good sign though. :D

[Clay Calvert]

Tom:

I'm trying, but I've never used subversion before.

Thanks,
Clay

[Thomas Fors]

Thanks zzzirk,

Glad to hear it!

--Tom

[Thomas Fors]

Clay,

There are some brief instructions on the Code tab of the ppp-pam site
that explains how to get the latest version of the code using svn.
Basically:

svn checkout http://ppp-pam.googlecode.com/svn/trunk/ ppp-pam

Once you've done that, you can cd into the ppp-pam folder and update
to the most recent version with:

svn update

or "update" to any previous revision with (for example):

svn update -r 66

Of course, this all assumes your computer already has svn installed.

I hope this helps.

--Tom

[Clay Calvert]

Tom:

Hmmm. My other response didn't make it. How odd. I thought I had
replied earlier saying that it is working on my Intel Tiger machine.
It prompted for the upgade quite nicely.

I should be trying to install on a Solaris 9 box later today.

Thank you very much,
Clay

[zzzirk]

Okay, I've built and tested this on my PPC OSX Leopard install.
Everything looks great to me.

[justarandomgeek]

I've compiled and installed it on both of my boxen (debian and
gentoo), but not updated my keys yet. I will generate new keys soon,
but until then, at least I can report that the backwards compatibility
works great and the warnings work as they should.

[Chris]

I upgraded to the new one tested the following:
1. Backwards compatibility
Successfuly logged in with passcode generated from PPP v1
Displayed message for me to generate new key.

2. Show message to warn of needing to print more passcards worked.
I think the Warning should read:
WARNING: You are on your last printed passcard. The message
below it is fine.
The current warning seems missleading because I still have 69 more
passcodes to use on that card.

3. Login succesful after new key generated.

All seems to be working well, just that warning message should be
tweaked.

On Nov 4, 1:03 pm, Thomas Fors <tomf...@gmail.com> wrote:

[Thomas Fors]

The warnings try to get progressively more "threatening".

Here's how they stand right now:

If you're on your last passcard:
                                ===========================================================
  You are on your last printed passcard. Please print
  more so you can continue to log into your account.
===========================================================

If you have less than 14 (2 rows) printed codes remaining:
                               @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
  You have %s printed passcode%s remaining. Please print
  more passcodes IMMEDIATELY so you can continue to log
  into your account.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

If you have no more printed passcodes remaining:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
            WARNING:  YOU ARE OUT OF PASSCODES            
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
  YOU MUST IMMEDIATELY PRINT MORE PASSCARDS if you wish to
  log in again.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Are you suggesting I add "Warning" to the beginning of the first two?

Thanks
--Tom

[Thomas Fors]

Great.  I'm a bit swamped at work at the moment.  Hopefully, I'll get some time this weekend to get it released as v0.3 although I'm tempted to wait and see how all the repeating passcode stuff turns out in grc.thinktank .

[Chris]

ok I see whats going on here now...I got that last error message the
first time I logged in under PPP v2 and as far is it was concerned I
hadn't printed codes yet. I hadn't actually looked in the code at that
point to see if there were any other messages. Now that I have seen
all the messages...everything looks good from my end. I give 0.3 the
green light.

Thanks Tom!

On Nov 6, 5:44 pm, "Thomas Fors" <t...@fors.net> wrote:
> The warnings try to get progressively more "threatening".
>
> Here's how they stand right now:
>
> If you're on your last passcard:
>
> ===========================================================
> You are on your last printed passcard. Please print
> more so you can continue to log into your account.
> ===========================================================
>
> If you have less than 14 (2 rows) printed codes remaining:
>
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> You have %s printed passcode%s remaining. Please print
> more passcodes IMMEDIATELY so you can continue to log
> into your account.
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>
> If you have no more printed passcodes remaining:
>
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> WARNING: YOU ARE OUT OF PASSCODES
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> YOU MUST IMMEDIATELY PRINT MORE PASSCARDS if you wish to
> log in again.
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>
> Are you suggesting I add "Warning" to the beginning of the first two?
>
> Thanks
> --Tom
>

> On Nov 6, 2007 4:00 PM, Chris <codeb...@gmail.com> wrote:
>
>
>
>
>
> > I think the Warning should read:
> > WARNING: You are on your last printed passcard. The message
> > below it is fine.
> > The current warning seems missleading because I still have 69 more

> > passcodes to use on that card.- Hide quoted text -
>
> - Show quoted text -

[Chris]

I noticed something interesting after I entered the command pppauth --
html --next 3
The following displayed after the web browsers connected, not a big
deal just thought it was interesting.

Please launch a browser on this machine and go to the URL:
http://localhost:41404/2tAgcioT9m5bhmwXTSt0wiaAScONmXv7u9B01gufI8Y=
To get your passcards for printing.

Waiting for browser to access URL...

[Thomas Fors]

Thanks Chris. I'll take a look at it. I suspect it's the forked
thread printing the error, but I'll have to look at the code to track
it down for sure.

[Thomas Fors]

Ok, I've fixed this in -r74. Thanks.

--Tom

On Nov 6, 8:26 pm, Chris <codeb...@gmail.com> wrote:

[Orson]

On Nov 4, 11:03 am, Thomas Fors <tomf...@gmail.com> wrote:

> I've made a number of enhancements since ver 0.2 including PPP version
> 2 support now. It should prompt the user to update their key in a
> safe manner so they aren't locked out.
>
> I'm going to hold off on labeling it 0.3 until I allow some time for
> people to test and provide feedback.

I have installed rev 76, updated my key, and it seems to work.
(Ubuntu 7.04)

Can't wait for PPPv3

Orson

PS.
I tried the -a option, but it doesn't seem to do anything. (it doesn't
error though.)

pppauth --passphrase zombie -t --card 1 -a '23456789!@#%+=:?
abcdefghijkmnopqrstuvwxyzABCDEFGHJKLMNPRSTUVWXYZ' --verbose
pppauth --passphrase zombie -t --card 1 -a '!#%+23456789:=?
@ABCDEFGHJKLMNPRSTUVWXYZabcdefghijkmnopqrstuvwxyz' --verbose

Both produce the same output.