@lakshmana said in Timeout in .sh file:
@thwr said in Timeout in .sh file:
@lakshmana said in Timeout in .sh file:
@scottalanmiller said in Timeout in .sh file:
@lakshmana said in Timeout in .sh file:
@scottalanmiller If i am giving the .sh file to be runned with ny collegues system i cannot share that the executable file since it may lead Infosec Issue
How will that work regardless of the tool used?
@scottalanmiller said in Timeout in .sh file:
@lakshmana said in Timeout in .sh file:
@scottalanmiller If i am giving the .sh file to be runned with ny collegues system i cannot share that the executable file since it may lead Infosec Issue
How will that work regardless of the tool used?
That .sh file should download the data by terminal or by Browser inside the machine without using credentials!!!
Ok, full stop. What happens here is that your web server simply tells you: "Hey, dude, I would love to give you that file, but your f'ing unauthorized, so just leave me alone. I won't give you the file unless you can present me a valid auth".
In other words: HTTP 401 Unauthorized.
So what needs to be done is simple: we need to authenticate against the server. This does not relate to the client side in any way. You will see the same behavior in Internet Explorer, Edge, Chrome, misc. PowerShell cmdlets or whatever else you may use to access that file.
Like SAM said, let us stop talking about client side tools for now. Let us instead discuss very basic authentication mechanisms.
I understood but in Browser the file will download from the cache credentials since the cookies make to download the data Right?????
Yep. And it's a very bad idea to rely on something you can't control: a users cached cookies.