I'm leaving a company, and I have too many passwords/keysWorking with many programming languages - Is doing too many different things bad for my career?Should I tell my boss I'm leaving because of them?Should I sign a non-compete as I'm leaving a company?Do I have to tell my colleagues that I'm leaving?Boss will resigning from job position in a few days and I'll be alone at the officeIs it impolite to reject new tasks while I'm leaving the company?Sending multiple applications to many companies and leaving if I get a better opportunityShould I be honest telling my current boss why I want to move?
Calculate the shadow on earth of a large orbital disk
Is there a practical way of making democratic-like system skewed towards competence?
Based on true story rules
First aid scissors confiscated by Dubai airport security
I'm largest when I'm five, what am I?
Non-Legendary Planeswalkers
Giving a character trauma but not "diagnosing" her?
SQL server backup message
Is there an engine that finds the best "practical" move?
An employee has low self-confidence, and is performing poorly. How can I help?
What does IKEA-like mean?
Fill a bowl with alphabet soup
Is consistent disregard for students' time "normal" in undergraduate research?
What is the meaning of "shop-wise" in "… and talk turned shop-wise"?
Does Australia produce unique 'specialty steel'?
How to respond when insulted by a grad student in a different department?
Numbering like equations for regular text
Is this an error...?
Disrespectful employee going above my head and telling me what to do. I am his manager
Print the sequence
Is data science mathematically interesting?
How long should a test wait to assume that the result remains fixed
What is the word for things that work even when they aren't working - e.g escalators?
Slow coworker receiving compliments while I receive complaints
I'm leaving a company, and I have too many passwords/keys
Working with many programming languages - Is doing too many different things bad for my career?Should I tell my boss I'm leaving because of them?Should I sign a non-compete as I'm leaving a company?Do I have to tell my colleagues that I'm leaving?Boss will resigning from job position in a few days and I'll be alone at the officeIs it impolite to reject new tasks while I'm leaving the company?Sending multiple applications to many companies and leaving if I get a better opportunityShould I be honest telling my current boss why I want to move?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I'm an European software developer and I am changing company. To do my job, during the years I have received (from my boss and colleagues) a lot of secrets, like:
- root accounts passwords (eg. AWS, Google Cloud, Azure, ...)
- access to servers (passwords and/or SSH keys)
- company-wise online accounts credentials (eg. GitHub, elearning platforms, ...)
- API keys
Clearly, anyone with this kind of information would be able to do nasty things, like accessing customer's data, or even deleting S3 buckets. That's needless to say that something like that would be huge for a small company.
To be clear: I do not want to fight/revenge my current company in any way. Despite my contract did not require me for a quit notice period, I proposed to stay one month after my announcement to prepare the team (document things, help hiring someone else, etc.). I even said to my boss and colleagues that they will be free to text me after my leave if they will need my help.
My boss initially was quite "fine" with my resignation; however during the last few days he started to act in a weird way to me (cold greetings, "forgetting" to CC me in some emails, ...). Maybe those things are just in my head, however I would like to protect me against any kind of future issues. What if one day a colleague of mine would accidentally destroy a database and to protect himself would blame me because I had the passwords?
Those access details are either stored on my company email (that I would lose access after quitting), on my computer (the policy is "bring your own laptop") or my Google account (I use "save password" in Chrome). That's not the best practices, but everyone else does the same. I will clearly clean my computer/accounts after quitting, but there will be no evidence that I did not print or memorize such secrets.
As a final note of mess, they will not be able to rotate keys/passwords in the short term (eg. the day next my quit). Some passwords have never been changed since the accounts were created, even after other employees left.
What would you do? Thank you in advance!
software-industry resignation europe
New contributor
add a comment
|
I'm an European software developer and I am changing company. To do my job, during the years I have received (from my boss and colleagues) a lot of secrets, like:
- root accounts passwords (eg. AWS, Google Cloud, Azure, ...)
- access to servers (passwords and/or SSH keys)
- company-wise online accounts credentials (eg. GitHub, elearning platforms, ...)
- API keys
Clearly, anyone with this kind of information would be able to do nasty things, like accessing customer's data, or even deleting S3 buckets. That's needless to say that something like that would be huge for a small company.
To be clear: I do not want to fight/revenge my current company in any way. Despite my contract did not require me for a quit notice period, I proposed to stay one month after my announcement to prepare the team (document things, help hiring someone else, etc.). I even said to my boss and colleagues that they will be free to text me after my leave if they will need my help.
My boss initially was quite "fine" with my resignation; however during the last few days he started to act in a weird way to me (cold greetings, "forgetting" to CC me in some emails, ...). Maybe those things are just in my head, however I would like to protect me against any kind of future issues. What if one day a colleague of mine would accidentally destroy a database and to protect himself would blame me because I had the passwords?
Those access details are either stored on my company email (that I would lose access after quitting), on my computer (the policy is "bring your own laptop") or my Google account (I use "save password" in Chrome). That's not the best practices, but everyone else does the same. I will clearly clean my computer/accounts after quitting, but there will be no evidence that I did not print or memorize such secrets.
As a final note of mess, they will not be able to rotate keys/passwords in the short term (eg. the day next my quit). Some passwords have never been changed since the accounts were created, even after other employees left.
What would you do? Thank you in advance!
software-industry resignation europe
New contributor
add a comment
|
I'm an European software developer and I am changing company. To do my job, during the years I have received (from my boss and colleagues) a lot of secrets, like:
- root accounts passwords (eg. AWS, Google Cloud, Azure, ...)
- access to servers (passwords and/or SSH keys)
- company-wise online accounts credentials (eg. GitHub, elearning platforms, ...)
- API keys
Clearly, anyone with this kind of information would be able to do nasty things, like accessing customer's data, or even deleting S3 buckets. That's needless to say that something like that would be huge for a small company.
To be clear: I do not want to fight/revenge my current company in any way. Despite my contract did not require me for a quit notice period, I proposed to stay one month after my announcement to prepare the team (document things, help hiring someone else, etc.). I even said to my boss and colleagues that they will be free to text me after my leave if they will need my help.
My boss initially was quite "fine" with my resignation; however during the last few days he started to act in a weird way to me (cold greetings, "forgetting" to CC me in some emails, ...). Maybe those things are just in my head, however I would like to protect me against any kind of future issues. What if one day a colleague of mine would accidentally destroy a database and to protect himself would blame me because I had the passwords?
Those access details are either stored on my company email (that I would lose access after quitting), on my computer (the policy is "bring your own laptop") or my Google account (I use "save password" in Chrome). That's not the best practices, but everyone else does the same. I will clearly clean my computer/accounts after quitting, but there will be no evidence that I did not print or memorize such secrets.
As a final note of mess, they will not be able to rotate keys/passwords in the short term (eg. the day next my quit). Some passwords have never been changed since the accounts were created, even after other employees left.
What would you do? Thank you in advance!
software-industry resignation europe
New contributor
I'm an European software developer and I am changing company. To do my job, during the years I have received (from my boss and colleagues) a lot of secrets, like:
- root accounts passwords (eg. AWS, Google Cloud, Azure, ...)
- access to servers (passwords and/or SSH keys)
- company-wise online accounts credentials (eg. GitHub, elearning platforms, ...)
- API keys
Clearly, anyone with this kind of information would be able to do nasty things, like accessing customer's data, or even deleting S3 buckets. That's needless to say that something like that would be huge for a small company.
To be clear: I do not want to fight/revenge my current company in any way. Despite my contract did not require me for a quit notice period, I proposed to stay one month after my announcement to prepare the team (document things, help hiring someone else, etc.). I even said to my boss and colleagues that they will be free to text me after my leave if they will need my help.
My boss initially was quite "fine" with my resignation; however during the last few days he started to act in a weird way to me (cold greetings, "forgetting" to CC me in some emails, ...). Maybe those things are just in my head, however I would like to protect me against any kind of future issues. What if one day a colleague of mine would accidentally destroy a database and to protect himself would blame me because I had the passwords?
Those access details are either stored on my company email (that I would lose access after quitting), on my computer (the policy is "bring your own laptop") or my Google account (I use "save password" in Chrome). That's not the best practices, but everyone else does the same. I will clearly clean my computer/accounts after quitting, but there will be no evidence that I did not print or memorize such secrets.
As a final note of mess, they will not be able to rotate keys/passwords in the short term (eg. the day next my quit). Some passwords have never been changed since the accounts were created, even after other employees left.
What would you do? Thank you in advance!
software-industry resignation europe
software-industry resignation europe
New contributor
New contributor
New contributor
asked 23 mins ago
throwawaythrowaway
11 bronze badge
11 bronze badge
New contributor
New contributor
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
What would you do?
I would make a list of all these logins and offer to help the person who was tasked with changing all of them. As each password change was completed (by the other person, using passwords unknown to me), I would cross it off the list.
During my final month, I would send the updated list with each of my weekly status reports, and then the final list on my last day.
If any remained unchanged, I would rest easy, knowing that I gave them a month along with everything they needed to get the job done.
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "423"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
throwaway is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f145980%2fim-leaving-a-company-and-i-have-too-many-passwords-keys%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
What would you do?
I would make a list of all these logins and offer to help the person who was tasked with changing all of them. As each password change was completed (by the other person, using passwords unknown to me), I would cross it off the list.
During my final month, I would send the updated list with each of my weekly status reports, and then the final list on my last day.
If any remained unchanged, I would rest easy, knowing that I gave them a month along with everything they needed to get the job done.
add a comment
|
What would you do?
I would make a list of all these logins and offer to help the person who was tasked with changing all of them. As each password change was completed (by the other person, using passwords unknown to me), I would cross it off the list.
During my final month, I would send the updated list with each of my weekly status reports, and then the final list on my last day.
If any remained unchanged, I would rest easy, knowing that I gave them a month along with everything they needed to get the job done.
add a comment
|
What would you do?
I would make a list of all these logins and offer to help the person who was tasked with changing all of them. As each password change was completed (by the other person, using passwords unknown to me), I would cross it off the list.
During my final month, I would send the updated list with each of my weekly status reports, and then the final list on my last day.
If any remained unchanged, I would rest easy, knowing that I gave them a month along with everything they needed to get the job done.
What would you do?
I would make a list of all these logins and offer to help the person who was tasked with changing all of them. As each password change was completed (by the other person, using passwords unknown to me), I would cross it off the list.
During my final month, I would send the updated list with each of my weekly status reports, and then the final list on my last day.
If any remained unchanged, I would rest easy, knowing that I gave them a month along with everything they needed to get the job done.
answered 10 mins ago
Joe StrazzereJoe Strazzere
274k147 gold badges827 silver badges1130 bronze badges
274k147 gold badges827 silver badges1130 bronze badges
add a comment
|
add a comment
|
throwaway is a new contributor. Be nice, and check out our Code of Conduct.
throwaway is a new contributor. Be nice, and check out our Code of Conduct.
throwaway is a new contributor. Be nice, and check out our Code of Conduct.
throwaway is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f145980%2fim-leaving-a-company-and-i-have-too-many-passwords-keys%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown