{"id":4099,"date":"2026-11-16T14:25:00","date_gmt":"2026-11-16T14:25:00","guid":{"rendered":"https:\/\/www.gujaratorbit.com\/blog\/?p=4099"},"modified":"2026-11-19T04:25:00","modified_gmt":"2026-11-19T04:25:00","slug":"four-person-tour-team-locks-down-shared-logins","status":"publish","type":"post","link":"https:\/\/www.gujaratorbit.com\/blog\/four-person-tour-team-locks-down-shared-logins\/","title":{"rendered":"How a Four-Person Tour Team Tidied Its Server Logins"},"content":{"rendered":"<p>Picture a team that never existed, although you may know one very much like it. Four people run a small tour-booking outfit out of an office in Gujarat: a founder, an operations lead, a developer and a part-time support person. Their booking site runs on two rented Linux servers. All characters and details here are invented for illustration, and every technical point comes from general practice and from the Ops Atlas entry on <a href=\"https:\/\/www.xopsschool.com\/sysops\/\">SysOps<\/a>.<\/p>\n<h2>Chapter one: the login everyone knew<\/h2>\n<p>It started with a mundane request. The support person needed to check a log file, and the developer, busy with a release, simply messaged the password for the main administrator account. Within a year, five people and one contractor knew it. Nobody thought of it as risky; it was convenient, and the site never went down.<\/p>\n<p>Then the contractor&#8217;s laptop was lost on a train. Nothing bad happened, as far as anyone could tell, and that was the problem: nobody could say for sure. There was one login, so there was no record of who did what. The operations lead, who had been reading about server care, said the sentence that began the project: &#8220;We cannot prove anything, and that is already a failure.&#8221;<\/p>\n<h2>Chapter two: a plan with an order<\/h2>\n<p>The team borrowed a thirty-day outline from the Atlas. Its opening moves are to make an inventory, remove any shared root-level access, switch on performance history, write a triage script and set a few meaningful alerts. They drew the line in one afternoon: two servers, four people, one contractor, and who needed what.<\/p>\n<p>Each person got a personal account. Administrator rights would come through sudo, granted per person, so every privileged action would carry a name.<\/p>\n<h2>Chapter three: the rule that never loaded<\/h2>\n<p>The developer wrote the sudo rules into small files in the include directory, naming one of them with a version number such as admin.v2. The rule looked right and the syntax check passed. Yet the support person could not use it. The cause, one the Atlas flags as a classic trap, is that a filename containing a period is ignored without any error message. The team renamed the file, fixed its mode to 0440, and ran the checker again, which also confirms ownership.<\/p>\n<p>They wrote a short note on the wiki: no dots in these filenames, and test with a real login, not only the syntax tool.<\/p>\n<h2>Chapter four: the remote-access surprise<\/h2>\n<p>Next the operations lead tightened remote access, wanting to allow only the team&#8217;s own group and ban password logins. The edit went in at the end of the configuration file, the service reloaded, and passwords still worked. This is another caveat from the Atlas: for most keywords in that service, whichever value appears first takes effect, and a later line is quietly ignored. The team&#8217;s fix was to print the effective settings with the daemon&#8217;s test mode, find the earlier line that was winning, and correct it there.<\/p>\n<p>They also adopted a rule that has rescued many teams: leave another terminal logged in while editing access settings, so a slip can be undone from inside. On the second server they tested the change on a spare virtual machine first.<\/p>\n<h2>Chapter five: the cloud tool with a shared user<\/h2>\n<p>The second server lives with a provider whose browser-based session tool defaults to a shared user that has passwordless sudo. The team had enabled it for convenience and forgotten. When the operations lead read the Atlas caution on this, the room went quiet, because they had rebuilt the very problem they had just fixed. They configured per-person run-as settings and narrowed the cloud permissions, so the tool would use each person&#8217;s own identity.<\/p>\n<h2>Chapter six: protections stay on<\/h2>\n<p>The last test came when the booking application failed to write to a new uploads folder. The developer&#8217;s first instinct was to switch off the mandatory access control layer. The operations lead stopped him, and they instead found which security label was blocking the folder and relaxed only that one domain. The host firewall got the same treatment: any change to it would be scheduled with an automatic revert, using a timed unit that undoes the edit unless it is made permanent.<\/p>\n<h2>Chapter seven: the argument about speed<\/h2>\n<p>Not everyone was delighted. The developer complained that personal accounts and sudo prompts slowed him down during a release, and for a week there was grumbling. The operations lead did not dismiss it. Together they measured: the extra friction was a few seconds per privileged command, while the lost-laptop scare had cost nearly two days of worry and an unplanned password change on every machine.<\/p>\n<p>They agreed on a compromise. Routine deployment steps were wrapped into a script that ran under a narrowly scoped rule, so the developer could release without typing long commands, while anything broader still needed a named, logged elevation. Convenience and accountability can live together if the rules are written for the work people actually do.<\/p>\n<p>The founder, who is not technical, asked one question at the review: &#8220;If something goes wrong tonight, who will know what happened?&#8221; The team could now answer it, and that answer was worth more to the business than any single technical fix.<\/p>\n<h2>What they had at day thirty<\/h2>\n<ul>\n<li>One named account per person, and the shared login disabled.<\/li>\n<li>Sudo rules in properly named files that actually applied.<\/li>\n<li>Verified remote-access settings, checked with the effective-configuration command.<\/li>\n<li>A short triage script and four alerts, including one for disk runway.<\/li>\n<li>A note on the wiki explaining each of the traps above, in the team&#8217;s own words.<\/li>\n<\/ul>\n<h2>What the story shows<\/h2>\n<p>Nothing here involved expensive tools. What changed was ownership and evidence. When the contractor&#8217;s replacement joined months later, the team could grant access in ten minutes and revoke it just as quickly, and the logs showed who did what. In the Atlas&#8217;s maturity staging, that is a move from ad hoc to documented, with the first steps toward baselined.<\/p>\n<p>Planning the work in order also felt a lot like preparing a first trip. The practical approach in the article about <a href=\"https:\/\/www.gujaratorbit.com\/blog\/how-can-visitors-plan-their-first-trip-to-gujarat\/\">organising a first trip across Gujarat<\/a> starts by deciding what matters, then fitting everything else around it, and the team used a similar approach for its security list. For a staff member who wanted to learn more, the overview of a <a href=\"https:\/\/www.gujaratorbit.com\/blog\/devopsschool-a-simple-step-by-step-guide-to-building-your-devops-career\/\">step-by-step DevOps career build<\/a> offered a map.<\/p>\n<p>If your own team shares one login, you already know what comes first. The fix takes an afternoon, and the story ends better when you start before the lost laptop.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>An invented story of a small Gujarat tour operator whose shared admin login, ignored sudo rule and risky session tool taught the team practical host security.<\/p>\n","protected":false},"author":7,"featured_media":4100,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2547],"tags":[],"class_list":["post-4099","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-security-tech"],"_links":{"self":[{"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/posts\/4099","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/comments?post=4099"}],"version-history":[{"count":1,"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/posts\/4099\/revisions"}],"predecessor-version":[{"id":4216,"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/posts\/4099\/revisions\/4216"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/media\/4100"}],"wp:attachment":[{"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/media?parent=4099"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/categories?post=4099"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gujaratorbit.com\/blog\/wp-json\/wp\/v2\/tags?post=4099"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}