Page MenuHomePhabricator

Security: no forced logout on multiple logins
Closed, DeclinedPublic

Description

Author: hemanshu_desai

Description:
MediaWiki allows people to login under same username from different computers at
the same time. This means that if I forget to logout from a computer, anyone at
that computer can access Wikipedia and pretend to be me. This is a security hazard.


Version: unspecified
Severity: enhancement

Details

Reference
bz1548
TitleReferenceAuthorSource BranchDest Branch
docker-hub-mirror: Use chart 1.7.0repos/releng/gitlab-cloud-runner!378dancymain-Ic3976a0a0e2478b35f4d2a95901dbadd1de54df3main
Chart 1.7.0: Add workaround for https://github.com/distribution/distribution/issues/2367repos/releng/docker-hub-mirror!34dancymain-I91e047b8a2f12671b77f6a6138acf15d0f195466main
Remove MetricsClient#dispatch()repos/data-engineering/metrics-platform!31phuedxwork/phuedx/T354823main
d/changelog: bump to 0.0.13repos/cloud/toolforge/builds-cli!56raymond-ndibebump_versionmain
docker-hub-mirror: Use chart 1.6.0 and enable debuggingrepos/releng/gitlab-cloud-runner!309dancymain-I523d0628677e6cfd6b4e5090783d0a91053a7c86main
Chart 1.6.0: Use registry version 2.8.3repos/releng/docker-hub-mirror!33dancymain-If32043bc39e96cbc0a0b7ff3874454381b38d4a1main
builds-api: bump to 0.0.122-20240117053308-11168593repos/cloud/toolforge/toolforge-deploy!176project_1317_bot_df3177307bed93c3f34e421e26c86e38bump_builds-apimain
[Java] Update submit methods to require stream namerepos/data-engineering/metrics-platform!22cjmingT354819/java-require-stream-namemain
[builds-api] increase build init wait timeoutrepos/cloud/toolforge/builds-api!70raymond-ndibeincreate_build_init_wait_timemain
builds-builder: bump to 0.0.88-20240111172456-b0def00arepos/cloud/toolforge/toolforge-deploy!174project_1317_bot_df3177307bed93c3f34e421e26c86e38bump_builds-buildermain
bump_version/build_deb: use podman binary if podman detectedrepos/cloud/toolforge/builds-cli!50dcarouse_podman_binarymain
dotnet: add procfile buildpackrepos/cloud/toolforge/builds-builder!28dcaroadd_procfile_to_dotnetmain
Show related patches Customize query in GitLab

Revisions and Commits

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 8:15 PM
bzimport set Reference to bz1548.
bzimport added a subscriber: Unknown Object (MLST).

richholton wrote:

I would be against this kind of feature, unless it was an individual user option.

I setup my laptop to "remember me between sessions". Basically, I never logout.
I would be very disappointed if this would mean I could not use Wikipedia from
another system.

Also, it would really do nothing to help security. If you forget to logout from
computer A, how will preventing you from logging in from computer B help?
Computer A remains open for anyone to use either way.

hemanshu_desai wrote:

(In reply to comment #1)

I would be against this kind of feature, unless it was an individual user option.

Also, it would really do nothing to help security. If you forget to logout from
computer A, how will preventing you from logging in from computer B help?
Computer A remains open for anyone to use either way.

The idea is not to prevent login from computer B but if same login is from
computer B, the user from computer A should be logged off automatically... again
when you login on computer A, the login at computer B should expire so that
noone else can use it.

Hemanshu

richholton wrote:

The idea is not to prevent login from computer B but if same login is from
computer B, the user from computer A should be logged off automatically... again
when you login on computer A, the login at computer B should expire so that
noone else can use it.

Of course. This makes sense. However, if someone has "remember password across
sessions" checked in preferences, then this would not occur. Am I correct?

I am totally against that feature, I use the same account on multiple
computers and browsers at home.
Users should probably remember to logout when they use their account
on another computer.

Changed severity to enhancement and priority to low, given the opposing comments
above.

epriestley changed the task status from Declined to Resolved by committing Unknown Object (Diffusion Commit).Mar 4 2015, 8:22 AM
epriestley added a commit: Unknown Object (Diffusion Commit).
Aklapper changed the task status from Resolved to Declined.Mar 4 2015, 11:42 AM
Aklapper claimed this task.