topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Monday March 18, 2024, 11:51 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Option to use constant name in temp or set different temp folder?  (Read 9779 times)

jakaneko

  • Participant
  • Joined in 2010
  • *
  • default avatar
  • Posts: 3
    • View Profile
    • Donate to Member
Hello

First I like to thank for fsekrit, I really like it. :)

But I cannot use it any more, because I use AppLocker now. :(

When fsekrit start, it seems that it copy code to %temp% with name FSEKRIT-????.EXE where ???? part changing every time. Because of that changing part I cannot make AppLocker -rule for fsekrit (running in temp is prevented in that standard account I use my everyday use).

So could Fsekrit have option to use constant and same name in %temp% folder? Or maybe option to set different temp -folder so I can give that folder permission to execution?
« Last Edit: July 25, 2010, 10:12 AM by jakaneko »

Ampa

  • Charter Member
  • Joined in 2005
  • ***
  • Posts: 592
  • I am cute ;)
    • View Profile
    • MonkeyDash - 2 Player strategy boardgame
    • Donate to Member
I think I understand what you are asking.

I too have the same issue with the Defense+ component of Comodo Firewall. It is impossible to build a rule to allow fsekrit to access the temp files it reequires since the exe file is given a new randomly generated name each time.

As such I have to uncheck two boxes and click both when the program loads, and when it exits.

Not sure what the solution is, since I assume the random file name is done for security reasons.

jakaneko

  • Participant
  • Joined in 2010
  • *
  • default avatar
  • Posts: 3
    • View Profile
    • Donate to Member
Well, in my case solution could be very easy: possibility to set custom temp-folder for fsekrit.

That is because AppLocker approve *-wildcard in path like this c:\somepath\* (but not like c:\somepath\fsekrit-*). So setting up own temp-folder to fsekrit and give permissions to it could be simplest solution for me :)

f0dder

  • Moderator
  • Joined in 2005
  • *****
  • Posts: 9,153
  • [Well, THAT escalated quickly!]
    • View Profile
    • f0dder's place
    • Read more about this member.
    • Donate to Member
Is it only %TEMP% that's protected in this way by AppLocker? In that case, perhaps it's possible for you to run fSekrit in portable mode (see 1.40 release notes) as a workaround.

Because of the way fSekrit works, it has to make this temporary copy of itself - using a constant name would work, but would prevent multiple open notes. There's some possible workarounds for that, but it wouldn't be super pretty :)

If it's of any help, I could add a registry setting to override %TEMP% in the next version, so you don't have to use portable mode.
- carpe noctem

jakaneko

  • Participant
  • Joined in 2010
  • *
  • default avatar
  • Posts: 3
    • View Profile
    • Donate to Member
Thank you! I can find my way with fSekrit.portable :)