|
Yes...
He thinks they are serious, but they don't trust the software escrow method...
Walking away or not... this is a though decision.
Let's see what he decides...
Thank you for posting!
|
|
|
|
|
It depends on how work is done. I for one commit to fixing bugs for free for life
(In the originally installed environment). In general, if it is my bug, I fix it.
Then, for updates, the environment matters. I deploy with an Updater allowing me to
save a new version to my server, and the client to reach it via their client software.
This alleviates the fear that updates are big and costly.
Finally, the point about Tech Support is usually pretty trivial:
A) I train someone in house
B) I get paid to document it well enough that anyone can support it
C) We go back to the part where, unless things change, the software should not need support
D) We review their Support Contracts with Dell, etc. Do they currently have, and to what level.
And I have faced this. I have 2-3 "associates" that can support anything I have developed.
(SUPPORT, not keep making enhancements to), and I give those numbers to the client, I bring them
in if needed. Because if I get hit by a bus, it matters to him. I replaced someone who up and died
without notifying his clients in advance (duh).
So understand the concerns are there. There is a reason. But there are numerous reasonable answers. If it is about future development support. I have one or two people that can carry that
on for me once I am gone, but that took a longer time to setup.
HTH
|
|
|
|
|
Yes, that's exactly what my friend has offered...
No associates here...
Thank you for posting!
|
|
|
|
|
An interesting story of how a manager at a large company discovered employees were sharing passwords in an excel spreadsheet for convenience.
Stop passing around those passwords! | Computerworld[^]
The first, named “password_list.xls,” was password-protected and appeared to be encrypted. Well, that was good, right? But the other file, called “password.txt,” was a text file with one entry. You guessed it: It was the password to the encrypted Excel file.
My forthcoming book, Launch Your Android App, is available for pre-sale at Amazon.com -- releases on April 1, 2016 (no joke).
|
|
|
|
|
That password protected Excel file is totally useless... The password should be stored in a plain text file from the beginning...
But seriously...We have a policy of 8 generations of complex passwords (to fulfill ISO) - do you think I make up a new password every 6 months? No! I have a file with 9 password and I circulate them... (the file password protected with a non-complex password)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
They've implemented an ingenius 2-factor auth.
User has to :
1. open the text file, retrieve password
2. open the excel file using the file from the original text file.
Nobody could crack that system.
My forthcoming book, Launch Your Android App, is available for pre-sale at Amazon.com -- releases on April 1, 2016 (no joke).
|
|
|
|
|
I follow a strategy parallel to yours - there are a number of passwords I use. These can be symbolized by something I'd call mnemonic-like, but it has nothing to do with anything anyone but I know about and only implies something about the (specific) password. The rarely used junk locations can then be written down, uid+mnemonic.
A few particularly important passwords, however, die with me.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "As far as we know, our computer has never had an undetected error." - Weisert | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
We have a requirement to change system passwords every 60 day; recently, that policy has changed to every 90 days. It takes 10 people 4 hours to change all of the passwords - tasks, services, application access, local users. A password scheme was devised to make it easier to remember what each system password is - and each system has it's own password.
Policy states: if a team member leaves or is reassigned, you have 6 days to change all of the passwords.
We don't look forward to password change day...
|
|
|
|
|
Tim Carmichael wrote: We don't look forward to password change day.
Yeah, that sounds like a lot of no-fun.
I can see it now when someone tries to go to a new job:
"Quick! Tie that guy to the chair. He's thinking about leaving the company and that means we would have to change passwords. No one leave this place!!"
My forthcoming book, Launch Your Android App, is available for pre-sale at Amazon.com -- releases on April 1, 2016 (no joke).
|
|
|
|
|
Oddly enough, there is very little turnover in our group. The company has a program where recent graduates come in for 3 years, changing jobs every year; that gives them a chance to experience different areas and that is most of the group turnover.
Other than that... I am the most recent member and have been there for almost 4 1/2 years. Someone is retiring so that will be an out-of-order password change, but, we refer to the group as 'the land of milk and honey.'
|
|
|
|
|
Tim Carmichael wrote: we refer to the group as 'the land of milk and honey.'
That's great to hear about a good workplace in the industry.
My forthcoming book, Launch Your Android App, is available for pre-sale at Amazon.com -- releases on April 1, 2016 (no joke).
|
|
|
|
|
This would make a great survey question. I've been through a few solutions including a plain text file, an html page, and now finally a hand-rolled password protected application that works great...except that it uses SQL Compact and after upgrading to 10 refuses to work on a synched network drive. (I'd like to share it with my laptop) Strangely, it still works on the laptop (Win10 pro) on a network drive, but not on my main development machine. (also Win10 pro) I may eventually switch the backend to Access since it works fine on network drives...still better than a spreadsheet!
"Go forth into the source" - Neal Morse
|
|
|
|
|
kmoorevs wrote: finally a hand-rolled password protected application
I did a hand-rolled solution myself so I could control the file distribution.
I used simple json format, then encrypted the entire json structure using AES and save it to a "text" file. It's all secured via one master password (long).
That way I can share the file across the Internet securely (AES encrypted). I also implemented a few features like copying the decrypted password to the clipboard when you decrypt it. Also, since it's based upon a standard encryption routine, I can (eventually) write a Android app which can decrypt the simple json which I can share on onedrive, dropbox, google docs, etc.
My forthcoming book, Launch Your Android App, is available for pre-sale at Amazon.com -- releases on April 1, 2016 (no joke).
|
|
|
|
|
Is renembering passwords harder than weiting a whole software
|
|
|
|
|
Yes!
My forthcoming book, Launch Your Android App, is available for pre-sale at Amazon.com -- releases on April 1, 2016 (no joke).
|
|
|
|
|
horse.
battery.
staple.
correct.
|
|
|
|
|
Here's a thought - stop password-protecting every damn thing.
And another - stop making the passwords impossible to remember.
|
|
|
|
|
That made me laugh out loud for real. Great stuff.
I agree. I have to create a password for every new site I visit, every new service. Ugh.
We've had discussions here before for (and against) SSO (single sign on) via Google+, Twitter, etc (OAUTH). I like it because it means one authority authenticates you and others just recognize you.
Fewer passwords ___should___ mean better security.
Then, Facebook went down for a few hours and that meant you couldn't sign into FB or anything else you used your SSO from FB with.
My forthcoming book, Launch Your Android App, is available for pre-sale at Amazon.com -- releases on April 1, 2016 (no joke).
|
|
|
|
|
...you certainly will now[^].
Or, for our 'Mercan cousins, this[^].
Just think - someone is making a living out of this.
|
|
|
|
|
Lovely spam[^]!
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Grilled Spam on toast! Yummy! I, for one, certainly don't hate it.
Spam, I'm sure, is not the healthiest food. It's not prime steak. It's not Vegan (in any way, thank goodness)! However, it is, when you are in the right mood, delicious!
Note: It is one of the few foods where the 'mercan version doesn't seem to be any different from the British.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
My hate wasn't for the Spam - just for whoever built the website. My brain actually tried to disconnect itself from the optic nerve, in order to relieve the pain.
Try a really fresh baguette, sliced down the longitudinal centre line, filled with thick sliced spam with lots of Branston pickle.
|
|
|
|
|
Branston Pickle was made for spam sandwiches! Yummy, yummy!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Spam could be made from hospital waste for all u know
|
|
|
|
|
Well, yes - but spam is classy stuff, you know - it would definitely be from a private ward.
|
|
|
|
|