Re: [sage-support] Re: Server and certificate chain

[kcrisman]

Jori, are you using Jonathan Gutow's branch for proxying?  If so, that 
would be great - I hope to work on sagenb updating later today.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Server and certificate chain

[Jori Mäntysalo]

On Tue, 17 Nov 2015, kcrisman wrote:


Jori, are you using Jonathan Gutow's branch for proxying?


No.

I rearranged things. We have now a) redirection http://sage.our.unit -> 
https://sage.our.unit and b) documentation online at 
http://sage-doc.our.unit.


This seems to now work. Apache is used as a proxy to locally running 
sagenb.


--
Jori Mäntysalo

Re: [sage-support] How to hide output when opening a sagemath worksheet

[Jori Mäntysalo]

On Tue, 17 Nov 2015, Gabriel Cardona wrote:


I evaluate it and hide the output, but when I open the worksheet again the
'2' is not hidden (I want my students to open the worksheet and evaluate the
expression themselves).


Can you just use Action / Delete All Output?

--
Jori Mäntysalo

[sage-support] Re: error in Sage

[Paul Leopardi]

Hi,
I have also just encountered the incorrect sign for BooleanFunction 
walsh_hadamard_transform(). 
In addition, I would like to point out that the documentation at
http://doc.sagemath.org/html/en/reference/cryptography/sage/crypto/boolean_function.html
 
agrees with the usual definition and not with the current implementation, 
and the doctest on that page does not check for correct sign. Finally, the 
sign on the Walsh Hadamard transform affects the definition of the dual, 
self-dual bent functions, etc. In particular, the function $x_1 x_2$ is 
self dual under the usual definition
http://www.inderscienceonline.com/doi/abs/10.1504/IJICoT.2010.032864 but 
not when when the current implementation is used. Clearly the current sign 
is a bug, rather than just a difference in convention.
All the best, Paul

On Tuesday, 30 December 2014 18:18:47 UTC+11, William wrote:
>
> -- Forwarded message -- 
> From: Aneta Buraczyńska  
> Date: Mon, Dec 29, 2014 at 11:03 PM 
> Subject: error in Sage 
> To: William Stein  
>
>
> Dear Mr William Stein, 
>
> I am writing with request for contact to Sage creators or reading my 
> problem. In module sage.crypto.boolean_function there is a function: 
> walsh_hadamard_transform(). I think this function gives wrong results. 
> For instance for function f defined by truth table (1, 0, 0, 0, 0, 1, 
> 1, 1) sage gives vector (0, 0, 0, 0, -4, 4, 4, 4) as a result, but the 
> correct value is (0, 0, 0, 0, 4, -4, -4, -4). All functions that I 
> verified have in sage error result due to incorrect signs. On appendix 
> I send a document with the calculations showing my statement. 
>
> I will be grateful for help in this problem. 
>
> Yours Sincerely, 
>
> Aneta Buraczyńska 
>
>
>
>
> -- 
> William Stein 
> Professor of Mathematics 
> University of Washington 
> http://wstein.org 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] How to hide output when opening a sagemath worksheet

[Gabriel Cardona]

Hi all,

I am preparing a worksheet for my students and have found a problem about 
hiding output. 
To put it simple, assume I have a single line in my worksheet:
1+1
I evaluate it and hide the output, but when I open the worksheet again the 
'2' is not hidden (I want my students to open the worksheet and evaluate 
the expression themselves).

Is there a way to get what I want?

Thanks in advance

  Biel

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Build on OS X 10.10.3 Stops at BRiAl: checking whether python2-2.7.9 version is >= 2.7... no

[Taylor Lee]

Kind of a weird error, the configure script that comes with BRiAl seems to 
think that the built in version of python2-2.7 is too old. Not sure where 
to go from here.





checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin14.3.0 dyld
checking how to hardcode library paths into programs... immediate
checking whether python2-2.7.9 version is >= 2.7... no
configure: error: Python interpreter is too old
Error configuring BRiAl

real 0m6.666s
user 0m3.072s
sys 0m2.721s

Error installing package brial-0.8.4.3

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the relevant part of the log file
  /Users/taylorlee/Sage/sage-6.9/logs/pkgs/brial-0.8.4.3.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/Users/taylorlee/Sage/sage-6.9/local/var/tmp/sage/build/brial-0.8.4.3 and 
type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd 
'/Users/taylorlee/Sage/sage-6.9/local/var/tmp/sage/build/brial-0.8.4.3' && 
'/Users/taylorlee/Sage/sage-6.9/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.

make[2]: *** 
[/Users/taylorlee/Sage/sage-6.9/local/var/lib/sage/installed/brial-0.8.4.3] 
Error 1
make[1]: *** [all] Error 2

real 0m8.739s
user 0m4.139s
sys 0m3.257s
***
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all'):

* package: brial-0.8.4.3
  log file: /Users/taylorlee/Sage/sage-6.9/logs/pkgs/brial-0.8.4.3.log
  build directory: 
/Users/taylorlee/Sage/sage-6.9/local/var/tmp/sage/build/brial-0.8.4.3

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

make: *** [all] Error 1

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Repeat of report of incorrect sign for walsh_hadamard_transform().

[Paul Leopardi]

I am reposting a comment I just added to the topic, "Fwd: error in Sage" in 
the hopes that it will be more likely to be seen this way.

Hi,
I have also just encountered the incorrect sign for BooleanFunction 
walsh_hadamard_transform(). 
In addition, I would like to point out that the documentation at
http://doc.sagemath.org/html/en/reference/cryptography/sage/crypto/boolean_function.html
 
agrees with the usual definition and not with the current implementation, 
and the doctest on that page does not check for correct sign. Finally, the 
sign on the Walsh Hadamard transform affects the definition of the dual, 
self-dual bent functions, etc. In particular, the function $x_1 x_2$ is 
self dual under the usual definition
http://www.inderscienceonline.com/doi/abs/10.1504/IJICoT.2010.032864 but 
not when when the current implementation is used. Clearly the current sign 
is a bug, rather than just a difference in convention.
All the best, Paul

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Using Sage in C++

[Jeroen Demeyer]

On 2015-11-17 06:14, Nils Bruin wrote:

It's very easy to write a sage program that's listening on one
pipe for input (in whatever format you require--you can make it binary
if you want) and write output on another, i.e. just a little server.


You could try to use 0MQ for this. It has bindings for many languages, 
including C++ and Python. Sage already includes it.


But I agree with Nils that you should certainly also consider the 
reverse: using your C++ program within Sage.


--
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Build on OS X 10.10.3 Stops at BRiAl: checking whether python2-2.7.9 version is >= 2.7... no

[Volker Braun]

Which OSX version is that? If you are not on the latest and greatest then 
you do have unfixed serious security issues in your OS. If you are willing 
to take that risk you can just install a sufficiently new Python version.



On Tuesday, November 17, 2015 at 10:03:44 AM UTC-5, Taylor Lee wrote:
>
> Kind of a weird error, the configure script that comes with BRiAl seems to 
> think that the built in version of python2-2.7 is too old. Not sure where 
> to go from here.
>
>
>
>
>
> checking if g++ supports -c -o file.o... yes
> checking if g++ supports -c -o file.o... (cached) yes
> checking whether the g++ linker (ld) supports shared libraries... yes
> checking dynamic linker characteristics... darwin14.3.0 dyld
> checking how to hardcode library paths into programs... immediate
> checking whether python2-2.7.9 version is >= 2.7... no
> configure: error: Python interpreter is too old
> Error configuring BRiAl
>
> real 0m6.666s
> user 0m3.072s
> sys 0m2.721s
> 
> Error installing package brial-0.8.4.3
> 
> Please email sage-devel (http://groups.google.com/group/sage-devel)
> explaining the problem and including the relevant part of the log file
>   /Users/taylorlee/Sage/sage-6.9/logs/pkgs/brial-0.8.4.3.log
> Describe your computer, operating system, etc.
> If you want to try to fix the problem yourself, *don't* just cd to
> /Users/taylorlee/Sage/sage-6.9/local/var/tmp/sage/build/brial-0.8.4.3 and 
> type 'make' or whatever is appropriate.
> Instead, the following commands setup all environment variables
> correctly and load a subshell for you to debug the error:
>   (cd 
> '/Users/taylorlee/Sage/sage-6.9/local/var/tmp/sage/build/brial-0.8.4.3' && 
> '/Users/taylorlee/Sage/sage-6.9/sage' --sh)
> When you are done debugging, you can type "exit" to leave the subshell.
> 
> make[2]: *** 
> [/Users/taylorlee/Sage/sage-6.9/local/var/lib/sage/installed/brial-0.8.4.3] 
> Error 1
> make[1]: *** [all] Error 2
>
> real 0m8.739s
> user 0m4.139s
> sys 0m3.257s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all'):
>
> * package: brial-0.8.4.3
>   log file: /Users/taylorlee/Sage/sage-6.9/logs/pkgs/brial-0.8.4.3.log
>   build directory: 
> /Users/taylorlee/Sage/sage-6.9/local/var/tmp/sage/build/brial-0.8.4.3
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> make: *** [all] Error 1
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.