Hmm... maybe someone needs to create an easier library.
I think the library is a bad implementation of a bad idea is the real problem.
I dunno... it seems to me that having a third party for authenticating isn't a bad idea. I hate having to log into this place, then this place, then this other place, all because everyone maintains their own authentication schemes for whatever reason. The idea is good, really... and it could cut down on some of the problems associated with authentication, too, as you don't have to do as much.
Er, don't have as many sites whose password you need to maintain, is what I mean.
This said, maybe there's a better way to handle authentication in this fashion.
I couldn't say, really, as I haven't studied this problem very well.
And, well, I'm guessing the implementation probably is bad if so many people have trouble with it.
Hm. I jsust setup the current version of Debian on a 180 MHz PowerPC box for
a single purpose machine. I'm not very Linuxy, I mostly use FreeBSD for this
kind of stuff but Debian was easier to install.
Every other box I have that gets its IP by DHCP I can access thru its hostname. But for some reason tehe Debian box doesn't register its hostname with the DHCP server. Anyone know how I may go about fixing this?
Every other box I have that gets its IP by DHCP I can access thru its hostname. But for some reason tehe Debian box doesn't register its hostname with the DHCP server. Anyone know how I may go about fixing this?
8088, you do know that powerpc is non intel? ;-P
debian configures that stuff via /etc/network/interfaces
most probably you can set dhcp parameters there too.
I eventually gave up. The last thing openid resembles is something
that has anything to do with authentication or authorization.
I did end up writing my own OpenID 1 implementation for just that reason.
However I do think the protocol does need to be as complex as it is, because it is a three way handshake that requires different levels of trust in each direction.
OpenID 2, on the other hand, is more complex than it needs to be. There were issues that needed to be addressed, but there were also four different proposals for how to move forward, and instead of picking one they simply smashed them all together.
Yes indeed it is :)
In /etc/network/interfaces I have:
# The loopback network interface
auto lo
iface lo inet loopback
imary network interface
allow-hotplug eth0
iface eth0 inet dhcp
Nothing there really jumps out at me.
In /etc/network/interfaces I have:
# The loopback network interface
auto lo
iface lo inet loopback
imary network interface
allow-hotplug eth0
iface eth0 inet dhcp
Nothing there really jumps out at me.
I dunno... it seems to me that having a third party for authenticating
isn't a bad idea. I hate having to log into this place, then this
Sure. ONE third party so everybody can write to them. Wouldn't be so bad. But this all things for all people crap doesn't work.
Also, there is a solution to the zillions of logins you need all the time: browsers remembering and autofilling passwords.
Sure it's a pain that you still have to register on all these webistes, but once you do, you never have to login again by typing your credentials, you just click login, because the browser did autofill for you.
And while I'm not saying that having a zillion passwords is great, it's better than having 1 and then having that 1 compromised so anybody who gets your PW can be you on lots of sites. Like your bank.
Wed Sep 07 2011 16:00:03 EDT from Ford II @ UncensoredI dunno... it seems to me that having a third party for authenticating
isn't a bad idea. I hate having to log into this place, then this
Sure. ONE third party so everybody can write to them. Wouldn't be so bad. But this all things for all people crap doesn't work.
its name was M$ passport, and it miserably failed.
I sincerely doubt that any bank (or pretty much any site that has access to
your money) will ever accept OpenID. Most already require two factor authentication.
And it is true that since OpenID emerged from the world of blogging software, its real target isn't important stuff like banks; it's the zillions of little miscellaneous sites that you might just stumble into after following a link to an interesting article or something and perhaps you might like to leave a comment without having to go through a site registration process.
And it is true that since OpenID emerged from the world of blogging software, its real target isn't important stuff like banks; it's the zillions of little miscellaneous sites that you might just stumble into after following a link to an interesting article or something and perhaps you might like to leave a comment without having to go through a site registration process.
after following a link to an interesting article or something and
perhaps you might like to leave a comment without having to go through
a site registration process.
Then the blogging software can add that as a part of the link they forward to: here's this' guy's information and call me to verfiy if you want.
Much simpler.
I thought that was the idea behind OpenID?
Anyway, browsers remembering passwords is fine, until you are not at your browser but want to login....
Also, recently my browser had a severe amnesia and forgot all logindata, including account names. (First time in 11 years or so, but frustrating.) And browsers sometimes stop working if homepages change their layout or whatever too much. (The "send me a new password via email" doesnt always work, either...)
But what I really do hate is the thge registering process in itself:
- No, this paricular special character for your nickname isnt allowed here
- No, we don't accept mail.ru or your special mail server
- Your password is too long, too short, too friggin blonde or whatever (I recently used a 16char password on a site which only accepts 15 chars and wasnt able to login, because you CAN enter 16 chars and the last ones don't get truncated...)
- You failed at the captcha, please try again.. 25 times in a row?
- "Your activation email will arrive soon" <- yeah, sure, two days is soon
- Why do I have to register to use a friggin search button or see some information that is absolutely not priovacy relevant?!
Even if registering only took two minutes, it is lost time. Time better spent browsing cracked.com, xkcd or pr0n!
except they've got tight session timeouts, they'd be real good openid providers...
Wed Sep 07 2011 17:40:06 EDT from IGnatius T Foobar @ UncensoredI sincerely doubt that any bank (or pretty much any site that has access to your money) will ever accept OpenID. Most already require two factor authentication.
Erg. Annoying thing about Nautilus 2.30.1, which is apparently my file manager
on Linux Mint Debian Edition.
I'm searching for the LibreOffice templates directory so I can add some additional ones that I downloaded for a class I'm writing for drill this weekend. I decide that, rather than randomly browsing through the file tree, I will use the file manager's built-in search function. I search for "template" and then go do something else for a while (no rush). I come back and there's a list of icons showing the folder names, but nothing to indicate where in the directory tree they are. I click on one and it opens up--here are the ones I downloaded. I hit back--
--and it runs the search over again. I wait another minute. Now I have the list again. I try switching the view mode so I can see a directory tree (and eliminate some obvious possibilities) and--
--IT RUNS THE SEARCH AGAIN. And I wait another minute. What? Why?
Best of all? There's no easy way to see where in the file structure a given search result is located, even in the other view modes.
Given the inanities of this interface, I will try to come up with better search parameters, but why couldn't it cache the results for a minute or two?
Would that kill anyone? Hard drive searches are not exactly blisteringly fast on this netbook.
I'm searching for the LibreOffice templates directory so I can add some additional ones that I downloaded for a class I'm writing for drill this weekend. I decide that, rather than randomly browsing through the file tree, I will use the file manager's built-in search function. I search for "template" and then go do something else for a while (no rush). I come back and there's a list of icons showing the folder names, but nothing to indicate where in the directory tree they are. I click on one and it opens up--here are the ones I downloaded. I hit back--
--and it runs the search over again. I wait another minute. Now I have the list again. I try switching the view mode so I can see a directory tree (and eliminate some obvious possibilities) and--
--IT RUNS THE SEARCH AGAIN. And I wait another minute. What? Why?
Best of all? There's no easy way to see where in the file structure a given search result is located, even in the other view modes.
Given the inanities of this interface, I will try to come up with better search parameters, but why couldn't it cache the results for a minute or two?
Would that kill anyone? Hard drive searches are not exactly blisteringly fast on this netbook.
It was faster to search for an article on the Intarweb for how to manage my
LibreOffice templates than it was to search my hard drive to find the damned
things.
simply use rox-filer. lightningfast, and realy tiny.
I thought Gnome would use "tracker" as a successor to beagle...
I use tracker outside of Gnome here and it is farking brilliant: It indexes your files as the windows index stuff does, but this time it really works. After a while, all your files are indexed, then if you search for something, you instantly get results. Fresh files and file changes are indexed via some kernel interface. I love it.
Annoying. I installed alpine and started messing around with configuration
so I could access my work (US Army) e-mail account via IMAP/SSL. It's relatively
easy in Thunderbird, and I can make my Android phone do it even, so I always
have access to my work e-mail. This is important because a) we're not supposed
to do work-related things via personal comms methods (gmail, Facebook, etc.)
and b) the webmail client is a bloated piece of crap that crashes many modern
browsers.
In the process of digging into how to configure alpine to talk to the servers properly, I discovered that the Army is going CAC-only for access to e-mail effective 1 December.
This effectively cuts off all mobile devices and most non-Windows computers.
Configure Linux to use CAC authentication is possible but nontrivial; even the latest version of OS X is a step backward in that respect. Considering how much trouble most soldiers have with getting their CAC readers to work even in Windows, this is a major inconvenience. For reserve component soldiers (National Guard, Army Reserve) who don't have frequent access to Army-maintained computers with installed CAC readers and middleware, this will have a major impact on our ability to communicate during the month. And since we only meet once a month (except for those of us on full-time duty), e-mail is the PRIMARY method of communication.
I almost sold our 1SG on setting up a private messaging system (like, say, a citadel server) just so we could get company business done during the month; that was several years ago. He might be more willing now.
Honestly, if I can't get my Army e-mail on my phone any longer, it's not worth maintaining a data plan to me.
In the process of digging into how to configure alpine to talk to the servers properly, I discovered that the Army is going CAC-only for access to e-mail effective 1 December.
This effectively cuts off all mobile devices and most non-Windows computers.
Configure Linux to use CAC authentication is possible but nontrivial; even the latest version of OS X is a step backward in that respect. Considering how much trouble most soldiers have with getting their CAC readers to work even in Windows, this is a major inconvenience. For reserve component soldiers (National Guard, Army Reserve) who don't have frequent access to Army-maintained computers with installed CAC readers and middleware, this will have a major impact on our ability to communicate during the month. And since we only meet once a month (except for those of us on full-time duty), e-mail is the PRIMARY method of communication.
I almost sold our 1SG on setting up a private messaging system (like, say, a citadel server) just so we could get company business done during the month; that was several years ago. He might be more willing now.
Honestly, if I can't get my Army e-mail on my phone any longer, it's not worth maintaining a data plan to me.