Changing permissions on user files for automating Apache VirtualHost creation
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I currently have a small Ubuntu Server 12.04 machine (test environment) with about 3 non-root users created. Each user has their own public_html
directory under their home
...thereby allowing them to deploy multiple apps as named virtual hosts. Each user belongs to the Apache www-data
group, set up as follows:
sudo usermod -a -G www-data [username]
sudo chown -R [username]:www-data /home/[username]/public_html
sudo chmod 2750 /home/[username]/public_html
Now as the root user, I am in the process of creating a bash script that will automate the creation of the folders for the VirtualHost under a prompted user's public_html
as well as creating an associated entry in /etc/apache2/sites-available/
. The script (run with sudo
) will prompt for the user ($uzer
) and the desired virtual host name ($vhost
). So far after running a few checks I eventually get to the following...
mkdir -vp /home/$uzer/public_html/$vhost
mkdir -vp /home/$uzer/public_html/$vhost/www
mkdir -vp /home/$uzer/public_html/$vhost/logs
mkdir -vp /home/$uzer/public_html/$vhost/backups
I need to change the ownership of these newly created folders, so I'm unsure whether I should be doing the following:
chown -vR $uzer:www-data /home/$uzer/public_html/$vhost
chmod 2750 /home/$uzer/public_html/$vhost
My questions:
- Is my folder structure correct/ideal?
- I know I've used recursive (
-R
) option, but should I be repeating the same for$vhost/www
,$vhost/logs
and$vhost/backups
? - Am I correct in thinking that the chmod above is probably redundant?
- Is there a way I can run the
mkdir
commands as the user$uzer
?
ubuntu permissions apache-httpd
add a comment |
up vote
2
down vote
favorite
I currently have a small Ubuntu Server 12.04 machine (test environment) with about 3 non-root users created. Each user has their own public_html
directory under their home
...thereby allowing them to deploy multiple apps as named virtual hosts. Each user belongs to the Apache www-data
group, set up as follows:
sudo usermod -a -G www-data [username]
sudo chown -R [username]:www-data /home/[username]/public_html
sudo chmod 2750 /home/[username]/public_html
Now as the root user, I am in the process of creating a bash script that will automate the creation of the folders for the VirtualHost under a prompted user's public_html
as well as creating an associated entry in /etc/apache2/sites-available/
. The script (run with sudo
) will prompt for the user ($uzer
) and the desired virtual host name ($vhost
). So far after running a few checks I eventually get to the following...
mkdir -vp /home/$uzer/public_html/$vhost
mkdir -vp /home/$uzer/public_html/$vhost/www
mkdir -vp /home/$uzer/public_html/$vhost/logs
mkdir -vp /home/$uzer/public_html/$vhost/backups
I need to change the ownership of these newly created folders, so I'm unsure whether I should be doing the following:
chown -vR $uzer:www-data /home/$uzer/public_html/$vhost
chmod 2750 /home/$uzer/public_html/$vhost
My questions:
- Is my folder structure correct/ideal?
- I know I've used recursive (
-R
) option, but should I be repeating the same for$vhost/www
,$vhost/logs
and$vhost/backups
? - Am I correct in thinking that the chmod above is probably redundant?
- Is there a way I can run the
mkdir
commands as the user$uzer
?
ubuntu permissions apache-httpd
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I currently have a small Ubuntu Server 12.04 machine (test environment) with about 3 non-root users created. Each user has their own public_html
directory under their home
...thereby allowing them to deploy multiple apps as named virtual hosts. Each user belongs to the Apache www-data
group, set up as follows:
sudo usermod -a -G www-data [username]
sudo chown -R [username]:www-data /home/[username]/public_html
sudo chmod 2750 /home/[username]/public_html
Now as the root user, I am in the process of creating a bash script that will automate the creation of the folders for the VirtualHost under a prompted user's public_html
as well as creating an associated entry in /etc/apache2/sites-available/
. The script (run with sudo
) will prompt for the user ($uzer
) and the desired virtual host name ($vhost
). So far after running a few checks I eventually get to the following...
mkdir -vp /home/$uzer/public_html/$vhost
mkdir -vp /home/$uzer/public_html/$vhost/www
mkdir -vp /home/$uzer/public_html/$vhost/logs
mkdir -vp /home/$uzer/public_html/$vhost/backups
I need to change the ownership of these newly created folders, so I'm unsure whether I should be doing the following:
chown -vR $uzer:www-data /home/$uzer/public_html/$vhost
chmod 2750 /home/$uzer/public_html/$vhost
My questions:
- Is my folder structure correct/ideal?
- I know I've used recursive (
-R
) option, but should I be repeating the same for$vhost/www
,$vhost/logs
and$vhost/backups
? - Am I correct in thinking that the chmod above is probably redundant?
- Is there a way I can run the
mkdir
commands as the user$uzer
?
ubuntu permissions apache-httpd
I currently have a small Ubuntu Server 12.04 machine (test environment) with about 3 non-root users created. Each user has their own public_html
directory under their home
...thereby allowing them to deploy multiple apps as named virtual hosts. Each user belongs to the Apache www-data
group, set up as follows:
sudo usermod -a -G www-data [username]
sudo chown -R [username]:www-data /home/[username]/public_html
sudo chmod 2750 /home/[username]/public_html
Now as the root user, I am in the process of creating a bash script that will automate the creation of the folders for the VirtualHost under a prompted user's public_html
as well as creating an associated entry in /etc/apache2/sites-available/
. The script (run with sudo
) will prompt for the user ($uzer
) and the desired virtual host name ($vhost
). So far after running a few checks I eventually get to the following...
mkdir -vp /home/$uzer/public_html/$vhost
mkdir -vp /home/$uzer/public_html/$vhost/www
mkdir -vp /home/$uzer/public_html/$vhost/logs
mkdir -vp /home/$uzer/public_html/$vhost/backups
I need to change the ownership of these newly created folders, so I'm unsure whether I should be doing the following:
chown -vR $uzer:www-data /home/$uzer/public_html/$vhost
chmod 2750 /home/$uzer/public_html/$vhost
My questions:
- Is my folder structure correct/ideal?
- I know I've used recursive (
-R
) option, but should I be repeating the same for$vhost/www
,$vhost/logs
and$vhost/backups
? - Am I correct in thinking that the chmod above is probably redundant?
- Is there a way I can run the
mkdir
commands as the user$uzer
?
ubuntu permissions apache-httpd
ubuntu permissions apache-httpd
edited Dec 7 at 23:48
Rui F Ribeiro
38.7k1479128
38.7k1479128
asked Apr 26 '13 at 10:43
maGz
5012516
5012516
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
Q: Is my folder structure correct/ideal?
A: Folder structure seems fine.
Q: I know I've used recursive (-R) option, but should I be repeating the same for $vhost/www, $vhost/logs and $vhost/backups?
A: It would be redundant to run it on those directories
Q: Am I correct in thinking that the chmod above is probably redundant?
Yes technically it's redundant because your initial sudo that cretes the directories is setting the 'set group id bit', but setting that bit, (the 2 in 2750), is not a guarantee. I've seen directories with this on where users have either moved files into the directory or accidentally changed the group on files, so I'd leave it.
Is there a way I can run the mkdir commands as the user $uzer?
root$ su -u $user -c "mkdir ..."
Also you could save a step on the chmod of the /www, /log, & /backups by using the mkdir --mode=...
switch.
For example
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/www
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/logs
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/backups
slm, thank you for your response. Please could you elaborate on your last statement by saving a step on chmod. how would I use the--mode
switch?
– maGz
Apr 26 '13 at 13:39
slm, thank you! You've given me solid feedback :)
– maGz
Apr 27 '13 at 16:35
No problem, glad I was able to help, good luck with your project!
– slm♦
Apr 27 '13 at 16:39
add a comment |
up vote
0
down vote
- Actually if doesn't matter what folder structure you are using.
- If you are using
-R
option in chown, it will only effect to the files and directories which are present at the time you are running the command. - No, because always you have to use
chmod
command to change the permission if you are making any changes manually. - You can ask
/etc/sudoers
file to allows $user to create any directory withmkdir
command.
Thanks Nitesh! Let me try this out and I'll post back here
– maGz
Apr 26 '13 at 11:20
Regarding (3), My question of whether thechmod
was redundant or not, is due to the fact that when the user is initially created thesudo chmod 2750 /home/[username]/public_html
command should set the permissions for any new files/folders created under public_html to750
...that's what the extra bit2
is for I think
– maGz
Apr 26 '13 at 11:24
#4 is an extremely large security risk, allowing arbitrary code execution by that user.
– Chris Down
Apr 26 '13 at 12:43
@Chris: yup, you are right, its a large security risk, but google will help you for sure.
– Nitesh B.
Apr 27 '13 at 8:02
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f73746%2fchanging-permissions-on-user-files-for-automating-apache-virtualhost-creation%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Q: Is my folder structure correct/ideal?
A: Folder structure seems fine.
Q: I know I've used recursive (-R) option, but should I be repeating the same for $vhost/www, $vhost/logs and $vhost/backups?
A: It would be redundant to run it on those directories
Q: Am I correct in thinking that the chmod above is probably redundant?
Yes technically it's redundant because your initial sudo that cretes the directories is setting the 'set group id bit', but setting that bit, (the 2 in 2750), is not a guarantee. I've seen directories with this on where users have either moved files into the directory or accidentally changed the group on files, so I'd leave it.
Is there a way I can run the mkdir commands as the user $uzer?
root$ su -u $user -c "mkdir ..."
Also you could save a step on the chmod of the /www, /log, & /backups by using the mkdir --mode=...
switch.
For example
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/www
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/logs
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/backups
slm, thank you for your response. Please could you elaborate on your last statement by saving a step on chmod. how would I use the--mode
switch?
– maGz
Apr 26 '13 at 13:39
slm, thank you! You've given me solid feedback :)
– maGz
Apr 27 '13 at 16:35
No problem, glad I was able to help, good luck with your project!
– slm♦
Apr 27 '13 at 16:39
add a comment |
up vote
3
down vote
accepted
Q: Is my folder structure correct/ideal?
A: Folder structure seems fine.
Q: I know I've used recursive (-R) option, but should I be repeating the same for $vhost/www, $vhost/logs and $vhost/backups?
A: It would be redundant to run it on those directories
Q: Am I correct in thinking that the chmod above is probably redundant?
Yes technically it's redundant because your initial sudo that cretes the directories is setting the 'set group id bit', but setting that bit, (the 2 in 2750), is not a guarantee. I've seen directories with this on where users have either moved files into the directory or accidentally changed the group on files, so I'd leave it.
Is there a way I can run the mkdir commands as the user $uzer?
root$ su -u $user -c "mkdir ..."
Also you could save a step on the chmod of the /www, /log, & /backups by using the mkdir --mode=...
switch.
For example
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/www
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/logs
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/backups
slm, thank you for your response. Please could you elaborate on your last statement by saving a step on chmod. how would I use the--mode
switch?
– maGz
Apr 26 '13 at 13:39
slm, thank you! You've given me solid feedback :)
– maGz
Apr 27 '13 at 16:35
No problem, glad I was able to help, good luck with your project!
– slm♦
Apr 27 '13 at 16:39
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Q: Is my folder structure correct/ideal?
A: Folder structure seems fine.
Q: I know I've used recursive (-R) option, but should I be repeating the same for $vhost/www, $vhost/logs and $vhost/backups?
A: It would be redundant to run it on those directories
Q: Am I correct in thinking that the chmod above is probably redundant?
Yes technically it's redundant because your initial sudo that cretes the directories is setting the 'set group id bit', but setting that bit, (the 2 in 2750), is not a guarantee. I've seen directories with this on where users have either moved files into the directory or accidentally changed the group on files, so I'd leave it.
Is there a way I can run the mkdir commands as the user $uzer?
root$ su -u $user -c "mkdir ..."
Also you could save a step on the chmod of the /www, /log, & /backups by using the mkdir --mode=...
switch.
For example
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/www
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/logs
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/backups
Q: Is my folder structure correct/ideal?
A: Folder structure seems fine.
Q: I know I've used recursive (-R) option, but should I be repeating the same for $vhost/www, $vhost/logs and $vhost/backups?
A: It would be redundant to run it on those directories
Q: Am I correct in thinking that the chmod above is probably redundant?
Yes technically it's redundant because your initial sudo that cretes the directories is setting the 'set group id bit', but setting that bit, (the 2 in 2750), is not a guarantee. I've seen directories with this on where users have either moved files into the directory or accidentally changed the group on files, so I'd leave it.
Is there a way I can run the mkdir commands as the user $uzer?
root$ su -u $user -c "mkdir ..."
Also you could save a step on the chmod of the /www, /log, & /backups by using the mkdir --mode=...
switch.
For example
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/www
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/logs
mkdir -vp --mode=2750 /home/$uzer/public_html/$vhost/backups
edited Apr 26 '13 at 13:44
answered Apr 26 '13 at 11:26
slm♦
246k66507673
246k66507673
slm, thank you for your response. Please could you elaborate on your last statement by saving a step on chmod. how would I use the--mode
switch?
– maGz
Apr 26 '13 at 13:39
slm, thank you! You've given me solid feedback :)
– maGz
Apr 27 '13 at 16:35
No problem, glad I was able to help, good luck with your project!
– slm♦
Apr 27 '13 at 16:39
add a comment |
slm, thank you for your response. Please could you elaborate on your last statement by saving a step on chmod. how would I use the--mode
switch?
– maGz
Apr 26 '13 at 13:39
slm, thank you! You've given me solid feedback :)
– maGz
Apr 27 '13 at 16:35
No problem, glad I was able to help, good luck with your project!
– slm♦
Apr 27 '13 at 16:39
slm, thank you for your response. Please could you elaborate on your last statement by saving a step on chmod. how would I use the
--mode
switch?– maGz
Apr 26 '13 at 13:39
slm, thank you for your response. Please could you elaborate on your last statement by saving a step on chmod. how would I use the
--mode
switch?– maGz
Apr 26 '13 at 13:39
slm, thank you! You've given me solid feedback :)
– maGz
Apr 27 '13 at 16:35
slm, thank you! You've given me solid feedback :)
– maGz
Apr 27 '13 at 16:35
No problem, glad I was able to help, good luck with your project!
– slm♦
Apr 27 '13 at 16:39
No problem, glad I was able to help, good luck with your project!
– slm♦
Apr 27 '13 at 16:39
add a comment |
up vote
0
down vote
- Actually if doesn't matter what folder structure you are using.
- If you are using
-R
option in chown, it will only effect to the files and directories which are present at the time you are running the command. - No, because always you have to use
chmod
command to change the permission if you are making any changes manually. - You can ask
/etc/sudoers
file to allows $user to create any directory withmkdir
command.
Thanks Nitesh! Let me try this out and I'll post back here
– maGz
Apr 26 '13 at 11:20
Regarding (3), My question of whether thechmod
was redundant or not, is due to the fact that when the user is initially created thesudo chmod 2750 /home/[username]/public_html
command should set the permissions for any new files/folders created under public_html to750
...that's what the extra bit2
is for I think
– maGz
Apr 26 '13 at 11:24
#4 is an extremely large security risk, allowing arbitrary code execution by that user.
– Chris Down
Apr 26 '13 at 12:43
@Chris: yup, you are right, its a large security risk, but google will help you for sure.
– Nitesh B.
Apr 27 '13 at 8:02
add a comment |
up vote
0
down vote
- Actually if doesn't matter what folder structure you are using.
- If you are using
-R
option in chown, it will only effect to the files and directories which are present at the time you are running the command. - No, because always you have to use
chmod
command to change the permission if you are making any changes manually. - You can ask
/etc/sudoers
file to allows $user to create any directory withmkdir
command.
Thanks Nitesh! Let me try this out and I'll post back here
– maGz
Apr 26 '13 at 11:20
Regarding (3), My question of whether thechmod
was redundant or not, is due to the fact that when the user is initially created thesudo chmod 2750 /home/[username]/public_html
command should set the permissions for any new files/folders created under public_html to750
...that's what the extra bit2
is for I think
– maGz
Apr 26 '13 at 11:24
#4 is an extremely large security risk, allowing arbitrary code execution by that user.
– Chris Down
Apr 26 '13 at 12:43
@Chris: yup, you are right, its a large security risk, but google will help you for sure.
– Nitesh B.
Apr 27 '13 at 8:02
add a comment |
up vote
0
down vote
up vote
0
down vote
- Actually if doesn't matter what folder structure you are using.
- If you are using
-R
option in chown, it will only effect to the files and directories which are present at the time you are running the command. - No, because always you have to use
chmod
command to change the permission if you are making any changes manually. - You can ask
/etc/sudoers
file to allows $user to create any directory withmkdir
command.
- Actually if doesn't matter what folder structure you are using.
- If you are using
-R
option in chown, it will only effect to the files and directories which are present at the time you are running the command. - No, because always you have to use
chmod
command to change the permission if you are making any changes manually. - You can ask
/etc/sudoers
file to allows $user to create any directory withmkdir
command.
edited Apr 26 '13 at 12:29
Anthon
60.1k17102163
60.1k17102163
answered Apr 26 '13 at 11:18
Nitesh B.
3711518
3711518
Thanks Nitesh! Let me try this out and I'll post back here
– maGz
Apr 26 '13 at 11:20
Regarding (3), My question of whether thechmod
was redundant or not, is due to the fact that when the user is initially created thesudo chmod 2750 /home/[username]/public_html
command should set the permissions for any new files/folders created under public_html to750
...that's what the extra bit2
is for I think
– maGz
Apr 26 '13 at 11:24
#4 is an extremely large security risk, allowing arbitrary code execution by that user.
– Chris Down
Apr 26 '13 at 12:43
@Chris: yup, you are right, its a large security risk, but google will help you for sure.
– Nitesh B.
Apr 27 '13 at 8:02
add a comment |
Thanks Nitesh! Let me try this out and I'll post back here
– maGz
Apr 26 '13 at 11:20
Regarding (3), My question of whether thechmod
was redundant or not, is due to the fact that when the user is initially created thesudo chmod 2750 /home/[username]/public_html
command should set the permissions for any new files/folders created under public_html to750
...that's what the extra bit2
is for I think
– maGz
Apr 26 '13 at 11:24
#4 is an extremely large security risk, allowing arbitrary code execution by that user.
– Chris Down
Apr 26 '13 at 12:43
@Chris: yup, you are right, its a large security risk, but google will help you for sure.
– Nitesh B.
Apr 27 '13 at 8:02
Thanks Nitesh! Let me try this out and I'll post back here
– maGz
Apr 26 '13 at 11:20
Thanks Nitesh! Let me try this out and I'll post back here
– maGz
Apr 26 '13 at 11:20
Regarding (3), My question of whether the
chmod
was redundant or not, is due to the fact that when the user is initially created the sudo chmod 2750 /home/[username]/public_html
command should set the permissions for any new files/folders created under public_html to 750
...that's what the extra bit 2
is for I think– maGz
Apr 26 '13 at 11:24
Regarding (3), My question of whether the
chmod
was redundant or not, is due to the fact that when the user is initially created the sudo chmod 2750 /home/[username]/public_html
command should set the permissions for any new files/folders created under public_html to 750
...that's what the extra bit 2
is for I think– maGz
Apr 26 '13 at 11:24
#4 is an extremely large security risk, allowing arbitrary code execution by that user.
– Chris Down
Apr 26 '13 at 12:43
#4 is an extremely large security risk, allowing arbitrary code execution by that user.
– Chris Down
Apr 26 '13 at 12:43
@Chris: yup, you are right, its a large security risk, but google will help you for sure.
– Nitesh B.
Apr 27 '13 at 8:02
@Chris: yup, you are right, its a large security risk, but google will help you for sure.
– Nitesh B.
Apr 27 '13 at 8:02
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f73746%2fchanging-permissions-on-user-files-for-automating-apache-virtualhost-creation%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown