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.
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.
OMG that's stupid of the FTC.
I'm a pro "repair man" and if hp for instance, made a computer, offered a standard one year warranty, and the HD failed. I might crack the plastic trying to dig out that "hidden" hard drive. HP should not have to then warrant that pc and it's cracked case.
They're not saying "warranty void if you broke the device" is illegal, just that you can't slap a sticker on top of a screw and void the warranty for breaking the sticker to prevent people from attempting a repair.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
HP should not have to then warrant that pc and it's cracked case.
Why not? If the device had (for example) bad soldering on the memory and you open it up to switch the hdd, even splitting the case in two, why does that mean that if the memory fails a month later that HP aren't responsible for it? They're not responsible for the case you broke, obviously, but why are they no longer responsible for the bad memory?
In the above example HP are (wrongly) saying they're not, and the government are (rightly) saying they are, and laws like that just reinforce people's rights make it harder for companies to shirk their legal responsibilities. It also stops them ripping consumers off by charging extortionate amounts for repairs knowing you have no alternative (*cough*Apple*cough*).
ah, but the point is what if the software they give you is broken, and they do not fix it?
If you say rent a car and it's broken they rental co will usually fix it or more often give you another.
Now for software say microsoft provides a product that has bugs that sometimes date back years and often they won't even acknowledge let alone fix it. Taking them to court will never work - your attorney vs their large building full of lawyers and more. The agreement prohibits reverse engineering but it also states they provide a working product.
They've already broken the agreement, why can't your take measures to fix it? They provide the software to do X, it fails, you fix the product to do X - it necessitated some reverse engineering but that was never to steal secrets, rather to fix their product to meet their agreement.
So for mine, there are cases you should be allowed to take the lid off software code too, and if you want to sell (or give away) your fix to others also having the problem - also legal.
Here's a real case:
I recently helped a company move some XP software to new (well less old) hardware, microsoft no longer support xp and hence no will longer licence for it - previously under the licence it was allowed (with ms help) to move xp between machines [as long as the other machine is uninstalled]. ms will no longer help but the licence terms remain, and so the company that bought the software can take any other measures they want to achieve their goal, no breakage of the agreement by the customer, only ms broke the agreement.
Is "no looking at the code" the same as "looking under the sticker" - absolutely from where I see it, regardless if it's an item or licence to install and use software. (really software is just a visualised copy of a thing.)
Signature ready for installation. Please Reboot now.