Elinks with GoogleCL (Grant Access/Verification)
Kyle Grieb
GoogleCL opens 'elinks' fine with the 'auth_browser' setting. Once I am
sent to google [ https://www.google.com/accounts/OAuthAuthorizeToken ] I
login, then directed to the Grant Access page to which I follow the link
'Grant Access', which sends POST to
https://www.google.com/accounts/CookieMismatch. I want to verify that
is is not a 'user setting' error, I have checked all elinks settings to
make sure I understand their meaning. GMail works fine (I can login and
perform functions).
Now the only post I have come across is with Cygwin and elinks. That
user had issues unrelated to mine, but they were still able to see the
verification code. I have also seen a function (within elinks git)
related to the utilization of elinks, so I think elinks is a supported
medium of verification.
I am surprised by the lack of information I have been able to obtain in
regards to this issue, this leads me to believe this is an uncommon one.
-Buglouse
--
Jason Holt
Kyle Grieb
> >
> > I had trouble using elinks to authenticate too, and couldn't figure out how it
> > had even been launched, since my BROWSER was unset.
> >
> On Thu, Dec 2, 2010 at 11:41 AM, Kyle Grieb <[1]grieb...@gmail.com> wrote:
>
> This post may be more appropriate for the Elinks list.
> sent to google [ [2]https://www.google.com/accounts/OAuthAuthorizeToken ] I
> login, then directed to the Grant Access page to which I follow the link
> 'Grant Access', which sends POST to
> is is not a 'user setting' error, I have checked all elinks settings to
> perform functions).
>
> Now the only post I have come across is with Cygwin and elinks. That
> user had issues unrelated to mine, but they were still able to see the
> related to the utilization of elinks, so I think elinks is a supported
> medium of verification.
>
> I am surprised by the lack of information I have been able to obtain in
> regards to this issue, this leads me to believe this is an uncommon one.
>
> -Buglouse
> --
I don't think it is so much related to how google authenticates, I can
identify and auth with their servers fine using elinks. I am having a
bit of difficulty identifying the core issue here, I still do not know
if it is client or server. At first I thought it was Javascript
related, I have come to believe this is not dependent on that. If
this is related to cookie verification/retention then what would be
a method of diagnosis? I have removed cookies listed as google
before re-authenticating, to no avail.
Ok, I created an empty config. It worked. -cookies.max_age = 0
+cookies.max_age = -1 (Thought I tested this, sorry for the confusion,
now we know.)
-Buglouse
--