fSekrit still in development?

[TT1]

It has such potential...  Any chance of releasing the source for peer review?

[f0dder]

I unfortunately haven't had time to work on fSekrit for (quite) a while - I'm hopefully going to have a bit more spare time in 2011 (knock on wood).

Opensourcing it is planned, check this post. The codebase (still) needs to be cleaned up before I release the source, though - and I have to figure out how to get "grafting" working with git so I can split the project in a public repository and a private repository where I can see all the old source code history from the closed-source subversion days.

And that doesn't seem to be super easy, the best I've been able to find so far is this - but that's not a full solution.

[SKA]

Dear f0dder

Maybe this link may give you some ideas :
http://liquidninja.c.../deploying-with-git/

Rgds/ HNY 2011
SKA

[f0dder]

Maybe this link may give you some ideas :
http://liquidninja.c.../deploying-with-git/

-SKA (December 28, 2010, 11:31 PM)

Thanks, but not of much use to me

I'm fairly comfortable with basic Git usage, my problem lies with the pretty special history grafting stuff.

[webfork]

Definitely in agreement with TT1, ideally with a GPL'd license.

I'm aware I could make my endorsement a bit more effective by actually donating to your project, but I'm not in a good way with money right now, so its just one more forum post on the matter.

If 2011 also ends up too busy to go through a code cleanup, please consider a deadline of some type to post the code as-is.  I've just seen a lot of closed-source projects disappear over the last year and their code gather dust.  Opening code isn't a sure way to avoid that, but it can help.

[f0dder]

Definitely in agreement with TT1, ideally with a GPL'd license.

-webfork (December 30, 2010, 05:55 PM)

Still not sure which license I'm going to stick on it, but there's no way I'll even consider tainting my project with that nasty piece of crap

[rxantos]

How about:
1. Leave the free version close sourced
2. Charge for the code for whoever wants to look at it.

OR:

Open the source, while retaining all rights. Which means that people can look at it, review it, find flaws, submit patches, etc. But cannot just put it, legally, on another application without your consent.

Of course nothing will stop an unscrupulous person to just ignore your license and use the code anyway.

[f0dder]

How about:
1. Leave the free version close sourced
2. Charge for the code for whoever wants to look at it.

-rxantos (January 21, 2011, 02:12 PM)

That would be pointless for fSekrit - the goal of opensourcing it is the "confidence" it instills in users (ie., no hidden backdoors, flaws, etc) as well as ensuring the program lives on and the documents are accessible even if I get hit by a truck.

Open the source, while retaining all rights. Which means that people can look at it, review it, find flaws, submit patches, etc. But cannot just put it, legally, on another application without your consent.

-rxantos (January 21, 2011, 02:12 PM)

I dunno which license I'm going to use (part from not being GPL), but I'm not sure such a restrictive license makes sense - it's not exactly like fSekrit is a big source of income for me, and it doesn't contain any rocket science.

I'd definitely prefer people not forking it, but rather have them submit patches to me, but oh well.

[panzer]

Is it Ok for you if I make an extension for browser so if you select text-right click-on menu click on send to fsekrit, text is coppied into your software automatically (basically, it just opens fsekrit directly from browser and copy text in it) and leave the changelog.txt out of the package (readme.txt and fsekrit.txt will still be there)?

[f0dder]

Is it Ok for you if I make an extension for browser so if you select text-right click-on menu click on send to fsekrit, text is coppied into your software automatically (basically, it just opens fsekrit directly from browser and copy text in it) and leave the changelog.txt out of the package (readme.txt and fsekrit.txt will still be there)?

-panzer (February 03, 2011, 02:41 AM)

I would prefer if you keep the changelog as well, but you're welcome to rename both readme and changelog to have a "fsekrit-*" prefix or similar

How do you plan on making the extension work, btw? Considering that the user has to enter his passphrase before fSekrit will accept pasted text.

[panzer]

Actually, it was made last year and works just fine. I just now realised that changelog was not in there. I will include changelog, I promise.

I just made a version where you can only open the Fsekrit and then click on paste. My friend from forum made autoit script so text is pasted automatically. He is smarter than I am. 

You select text in your browser - right click - on menu you select send to Fsekrit. Fsekrit opens with text in it. You just have to click save as and put a password in. Simple 

[panzer]

Ok. I changed the extension so changelog is now included. Mods on the forum will hopefully remove the old version with my new one on extensions page.

You can sleep calmly now. 

Extension are really small: the version without automatic copy/paste is only 48 kb big, while the other one (with automatic copy/paste) is 270kb big now.

[f0dder]

Ah, so it opens a blank fSekrit document and pastes the stuff - guess that could be useful for some people.

[SKA]

panzer

where could one get these two extensions from ?

SKA

[panzer]

They are made for K-meleon browser only:

http://kmeleon.sourc...um/read.php?9,108471

[panzer]

They do not work in FF, Opera, Chrome, etc.  Sorry ...

[panzer]

Ah, so it opens a blank fSekrit document and pastes the stuff - guess that could be useful for some people.

-f0dder (February 03, 2011, 12:10 PM)

Well, mods finally updated my extension so you can sleep calmly now.

Cheers