The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I left that part out - my boss (IT director) and I work very closely on development (he still is fully down in the trenches). When planning something, if we both had ideas on how to go about it, we'd fight it out and pick the better of the two, a hybrid, or something altogether new that came out of it. It didn't matter - we both wanted the best solution.
I cannot say the same for the rest of the department. I'm so autonomous from the rest of them that it's only an occasional annoyance when someone doesn't do their job (even when it's very easy). Sadly, for a few, I no longer as they say "have their backs" and they've past all pretense on my part that they're just simply as dumb as the users.
There was a short period of a couple of years when everyone pulled together. Still - there's the fun of coding and seeing/knowing five hundred or so users/day have your work in front of them.
And, finally, when dealing with the idiots my credo is: "Diplomacy? We don't need no stinkin' Diplomacy!"
(I do my own file handling in C# scripts in SSIS.)
Closer to your problem... Some months ago, the server folk updated the MySQL ADO.net drivers on all the SSIS servers -- no warning of course -- and the SSIS packages that rely on it have been failing ever since. Yet, of course, the desktop folk haven't yet approved the drivers for developer use, so I can't fix them.
Are you using secure FTP (SFTP) to transfer files ? Some places require you to lock down on security and allow sftp. If your are connecting to a unix box then you need to setup sftp on that and connect using a sftp client.
The port is blocked for everything except the database servers. No amount of work-around is going to fix firewall settings.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
And if they give me the credentials to run it remotely on the server, why would that be any different than just running it on my own machine - without credentials - like I've been doing for the last 4+ years?
So they can code sign the binary with a special certificate once it's verified/approved. You can then install that certificate on all workstations in the network and enable the group policy: "Only allow code signed binaries to run"
Sounds like your employer needs some security professionals on-site... I am surprised that you were able to run WinSCP under the radar for so long undetected.
Once they get you on the 'new setup' maybe you should show them how to use OpenProcess to dump the binary out of memory to your local disk for bypassing the UNC path. Then show them your 'PE File' Ninja skills by stripping out the code signing certificate from the binary converting it back to unsigned.
Then for testing if they have setup the certificate store security correctly... generate a self-signed certificate[^] to potentially allow your workstation to execute locally 'trusted' executables. Windows 10'Developer Mode' workstations allows self-signed binaries and local certificate trust.
I don't actually recommend doing any this. You'd be surprised how many 'security professionals' are nothing more than certified 'script kiddies' who memorized barely just enough for a week to pass a test.
Might want to get approval if you do decide to test the above.
Just got back from skiing, and I did the infamous Wall. One of the five worst slopes in the alps. Swiss Wall[^]
It starts very steep, about 70` and then eases off to a relatively gentle 50` for much of it. The really scary thing though is the height of it. It is this steep for about half a kilometer, so you are looking down, way way down, towards the end of the piste where it flatttens out.
It was damn hard skiing, completely knackering. Added to the fear the technique starts to fall apart pretty quickly so it is more survival skiing than pleasure.
The traverse was a major part, trying to scrub height. Problem with the 3 day old powder we had was that it isnt great for side slipping, so couldnt lose much height that way, it had to be turns, which also in old powder isnt much fun since the tips can catch quite easily, and if you do.... its a LONG way down.
Sounds a bit like the Hahnenkamm in Kitzbühel (Austria). A few years ago a friend and I did The Strief; pretty much straight down for the first 80% and then slowing for a hard curve to the left to prevent flying off the edge and a loooong fall down to the village. After the hard curve the track narrows to about a metre and a half wide across a wooden footbridge with some vicious wooden handrails you absolutely mustn't touch!
Much screaming was involved but we ended up doing it three times that day! A hell of a trip.
- I would love to change the world, but they won’t give me the source code.