Editing Talk:2700: Account Problems
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 24: | Line 24: | ||
I wrote most of the current page after the first paragraph. It's a fairly sloppy first draft that could probably use some editing. Anyone who can should feel free to clean it up. Especially since the page is now protected (I'm not complaining; it was necessary) and so I can't edit it any more. [[User:Equites|Equites]] ([[User talk:Equites|talk]]) 05:57, 19 November 2022 (UTC) | I wrote most of the current page after the first paragraph. It's a fairly sloppy first draft that could probably use some editing. Anyone who can should feel free to clean it up. Especially since the page is now protected (I'm not complaining; it was necessary) and so I can't edit it any more. [[User:Equites|Equites]] ([[User talk:Equites|talk]]) 05:57, 19 November 2022 (UTC) | ||
:Hi [[User:Equites|Equites]], I [[Special:Diff/299457|rewrote]] the explanation, hope that's okay. I removed the references to the security aspect because I didn't think it was relevant. (Also pinging [[User:FrankHightower|FrankHightower]].) --[[User:Hddqsb|Hddqsb]] ([[User talk:Hddqsb|talk]]) 07:59, 20 November 2022 (UTC) | :Hi [[User:Equites|Equites]], I [[Special:Diff/299457|rewrote]] the explanation, hope that's okay. I removed the references to the security aspect because I didn't think it was relevant. (Also pinging [[User:FrankHightower|FrankHightower]].) --[[User:Hddqsb|Hddqsb]] ([[User talk:Hddqsb|talk]]) 07:59, 20 November 2022 (UTC) | ||
− | |||
− | |||
Seems to be another Tech issue comic, its a tech issue with Cueball talking to Megan and the tech issue is extremely cursed. Should we add this one?[[Special:Contributions/162.158.22.98|162.158.22.98]] 06:00, 19 November 2022 (UTC) | Seems to be another Tech issue comic, its a tech issue with Cueball talking to Megan and the tech issue is extremely cursed. Should we add this one?[[Special:Contributions/162.158.22.98|162.158.22.98]] 06:00, 19 November 2022 (UTC) | ||
Line 38: | Line 36: | ||
:It is. And (with caveats, depending upon other issues and circumstances) Alt-numpad0 would give me the null-char wherever it's practical and not blocked (intentionally or just because it isn't specifically catered for).[[Special:Contributions/172.71.178.206|172.71.178.206]] 15:25, 20 November 2022 (UTC) | :It is. And (with caveats, depending upon other issues and circumstances) Alt-numpad0 would give me the null-char wherever it's practical and not blocked (intentionally or just because it isn't specifically catered for).[[Special:Contributions/172.71.178.206|172.71.178.206]] 15:25, 20 November 2022 (UTC) | ||
::I know a sysadmin friend of mine had to help a user whose account name was "🦙" (The Llama unicode symbol) and he was on a computer where not all layers between the username field and the password authentication understood unicode. Examples like this will happen in real life. [[User:IIVQ|IIVQ]] ([[User talk:IIVQ|talk]]) 11:16, 21 November 2022 (UTC) | ::I know a sysadmin friend of mine had to help a user whose account name was "🦙" (The Llama unicode symbol) and he was on a computer where not all layers between the username field and the password authentication understood unicode. Examples like this will happen in real life. [[User:IIVQ|IIVQ]] ([[User talk:IIVQ|talk]]) 11:16, 21 November 2022 (UTC) | ||
− | |||
As Cueball is showing and handing over his laptop, I don't think the issue is about a website account (where he could probably do a password reset), but his local account on the laptop, of which he is now locked out, and hopes Poneytail can break into it? [[User:Ghen|ghen]] ([[User talk:Ghen|talk]]) 18:28, 19 November 2022 (UTC) | As Cueball is showing and handing over his laptop, I don't think the issue is about a website account (where he could probably do a password reset), but his local account on the laptop, of which he is now locked out, and hopes Poneytail can break into it? [[User:Ghen|ghen]] ([[User talk:Ghen|talk]]) 18:28, 19 November 2022 (UTC) | ||
Line 52: | Line 49: | ||
I've actually had this problem long ago; I used the @ sign as part of my password, and it didn't let me log in anymore. Some systems in the good old days (I think it was an FTP server) used the @ character to separate username and password when authenticating. Also, I am still running into this problem sometimes with usernames (emails) allowing "+" in the address on registration, but not when logging in. [[User:Pbb|Pbb]] ([[User talk:Pbb|talk]]) | I've actually had this problem long ago; I used the @ sign as part of my password, and it didn't let me log in anymore. Some systems in the good old days (I think it was an FTP server) used the @ character to separate username and password when authenticating. Also, I am still running into this problem sometimes with usernames (emails) allowing "+" in the address on registration, but not when logging in. [[User:Pbb|Pbb]] ([[User talk:Pbb|talk]]) | ||
:The @-sign is used to separate authentication and hostname information in an URL, e.g. http://user:[email protected]:port/... Within an FTP-session it was commonly used in FTP-proxy scenarios, i.e. you've connected to an internal FTP-proxy-server providing username and hostname as username in the form [email protected] (similar to the syntax used for scp/sftp) and the password as is. An @-sign in the password in the latter shouldn't have any effect and within the URL an @-character would get URL-encoded not having an effect, either. URL-encoding might be the reason for the last problem, you've described leading to a space in the stored value on the server side. [[User:Kimmerin|Kimmerin]] ([[User talk:Kimmerin|talk]]) 15:50, 21 November 2022 (UTC) | :The @-sign is used to separate authentication and hostname information in an URL, e.g. http://user:[email protected]:port/... Within an FTP-session it was commonly used in FTP-proxy scenarios, i.e. you've connected to an internal FTP-proxy-server providing username and hostname as username in the form [email protected] (similar to the syntax used for scp/sftp) and the password as is. An @-sign in the password in the latter shouldn't have any effect and within the URL an @-character would get URL-encoded not having an effect, either. URL-encoding might be the reason for the last problem, you've described leading to a space in the stored value on the server side. [[User:Kimmerin|Kimmerin]] ([[User talk:Kimmerin|talk]]) 15:50, 21 November 2022 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |