powershell_attack.txt is not working just after a day about unicorn HOT 7 CLOSED

Hey @beethical - there is no time or expiration built anywhere in the code. I use the same powershell code in my demonstrations that span months without issue. There's nothing in the code that prohibits time at all.

from unicorn.

I appreciate your attention to solve this problem but I have used those powershell_attack codes for myriad times on various systems and conditions and even 2 last versions of Unicorn but the codes no longer work after this amount of time (24h) .please consider another testing ...

from unicorn.

I use it for the same thing and use it almost daily and use the same code spanning days, weeks, and months.

from unicorn.

Just as an example. I generated this powershell code 4 days ago, works great:

msf exploit(handler) > [] https://192.168.170.136:443/ handling request from 192.168.170.135; (UUID: xqbqqzyz) Staging Native payload...
[] https://192.168.170.136:443/ handling request from 192.168.170.135; (UUID: xqbqqzyz) Encoded stage with x86/shikata_ga_nai
[*] Meterpreter session 1 opened (192.168.170.136:443 -> 192.168.170.135:54113) at 2016-05-26 15:16:25 -0400

msf exploit(handler) >

from unicorn.

I use DDNS for ip to connect out side of network. I think your ip is within network .Is it possible that Unicorn has a bug around DDNS?

from unicorn.

Unicorn does absolutely nothing for DDNS - maybe a metasploit bug which I wouldn't have a control over but I doubt it. I use DNS all the time - used it yesterday (code generated weeks ago), still no issues.

from unicorn.

@trustedsec We are very thankful for the solutions and comments.
Cheers ;)

from unicorn.