2017年杭州市区义务教育阶段 学校招生工作时间安排

2017年杭州市区义务教育阶段 学校招生工作时间安排

http://www.jlyzx.net/NewsIndex.aspx?page=mhnry&an=systemarticle&aid=26302

 

日  期 内   容
4月初 1.民办中小学启动招生宣传,可通过校园开放日等形式适当宣传学校教育教学改革的成效和学校自主招生工作方案。

2.滨江区流动人口随迁子女入学按《杭州市滨江区居住证持有人积分申请子女入学细则》执行(4月初可登录“新滨江人帮帮网”:http://www.juters.com或“滨江教育信息网”:http://www.bjqjyj.cn查阅《积分入学公告》及相关政策内容)。

4月上旬 1.小学召开毕业生家长会,家长核对确认《2017年杭州市区小学毕业生户籍、学籍情况调查表》。

2.在市区外学校就读的杭州市区户籍小学毕业生报名(欲参加民办初中招生网上报名的,需在4月14日前到户籍所在区教育局(社发局)登记填表)。

4月14日 小学毕业生杭外推荐工作截止。
4月15日 市区民办小学报名。
4月17日—5月19日 滨江区流动人口随迁子女家长向居住地所在街道办事服务中心积分受理窗口提交积分入学申请。
4月21日 1.2017年杭外初中招生电脑派位。

2.小学发放《2017年杭州市区小学毕业生户籍、学籍情况调查回执》。

4月25—26日 民办初中招生网上报名。
4月27日 1.民办初中网上报名结果查询。

2.监护人书面确认民办初中网上报名结果。

5月3日17∶00后 市教育局公布各民办初中报名人数(以网报监护人书面确认为依据)。
5月4日 报名人数超过派位计划的民办初中电脑派位。
5月4日晚—5月7日晚 民办初中派位结果查询。
5月6—7日 民办初中派位学校组织自主招生。
5月13—14日 未招满的民办初中组织续报名招生。

(对象:未被录取的学生)

5月18日 市区民办初中招生结束。
5月10—19日 2017年杭州市区流动人口随迁子女小学一年级入学网上预登记(滨江区流动人口随迁子女积分入学在居住地所在街道办事服务中心受理,不在此预登记范围)。
6月8—15日 流动人口随迁子女小学一年级入学预登记信息相关部门核查结果网上查询。
6月24—25日 市区公办小学招生报名。
6月上旬—7月5日 各区开展公办初中分配工作。

 

 

2016年报名汇总

2016年杭州市钱塘外语学校一年级新生招生简章

招生对象:西湖区(2009年9月1日至2010年8月31日出生)。
招生人数:4班,每班36
招生办法:由家长带孩子自愿报名,学校自主录取。
报名时间:4月16日上午8:30—11:30,下午13:00—15:00
报名地点:杭州市钱塘外语学校小学部校内(文二路281号花园西村内)
注意事项:
出生证、家庭户口簿、房产证、家长身份证、适龄儿童的预防接种证原件
以上材料的复印件一份

学军小学求智校区教育服务区及咨询时间

来源:发布时间:2017-03-20点击数:38
http://www.hzxjxx.com/website/content/detail.action?schoolId=1&columnId=16&contentId=33962

为了更好地做好2017年新生招生工作,方便服务区内家长政策咨询,特向社会公布学军小学求智校区的服务区范围及咨询信息:
一、学军小学求智校区教育服务区
东至马塍路(另含下马塍居民区的马塍路24、26、28、29、30、31、32、33、34、35号),南至文三路,西至保俶北路,北至文二路。
二、新生入学咨询时间
1、3月1日~4月30日,2017年新生入学事宜咨询方式为“电话咨询”
2、电话咨询时间:每周二、四下午13:30~16:30
3、咨询电话:89988369

GCM-AES加密算法

1.GCM

GCM基于并行化设计,因此可以提供高效的吞吐率和低成本、低时延。本质是消息在变形的CTR模式下加密,密文结果与密钥以及消息长度在GF(2^128)域上相乘,计算流程如下所示。其输入输出和CCM基本一致。CCM和GCM的具体计算过程可以参看《密码学与网络安全》第五版,书中有详细的介绍。FRC5288 中介绍了TLS1.2 中的GCM应用。下面贴出openssl中AES-GCM的实例。

 

将明文P按128bit分组,用n和u表示明文总长度为(n-1)x 128 + u,1  u  128。即明文由一系列的n数据组成,最后一组数据长度为u,其他长度均为128位。

记这些明文块为P1,P2,P3…P(n-1),Pn*。同样,密文数据块长度相同,记为C1,C2,C3…C(n-1),Cn*。Pn*,Cn*长度为u。附加鉴别数据块记为A1,A2,…A(m-1),Am*,
Am*长度为v,A总长度为(m-1)x 128 + v,≤ v ≤ 128
加密算法由下面的公式给出:
其中||表示串连接

len表述数据(bit)长度

E(K,Y)表示用密钥K对Y做AES加密
incr()是将数据的最低32位看成一个无符号数,将其加1后取模2^32,即incr(F||I)=F||(I+1)mod2^32
GHASH函数定义如下:

Chrome 58.0 report https Not Secure error (net::ERR_CERT_COMMON_NAME_INVALID)

访问自制的c++ server,用了SSL证书,因为证书的问题,chrome 58报告Not Secure不安全:

There are issues with the site’s certificate chain (net::ERR_CERT_COMMON_NAME_INVALID).

原因是chrome 58开始,去掉了COMMON NAME校验域名,就是说不再用CN去校验了!我的证书刚好是这样颁发的:CN=127.0.0.1
取而代之的是”使用者可选名称”,英文是subjectAltName

于是生成证书的时候就要改改了,修改openssl.cfg

除了127.0.0.1外,顺便增加了localhost。改完后运行openssl命令生成证书,注意红色部分,是新加的:

1)生成服务器证书:
openssl req -new -sha256 -key server_key.pem -out server_req.pem -subj “/C=CN/ST=BC/L=HZ/O=HuQingyu/OU=HuQingyu/CN=127.0.0.1” -config openssl.cfg -extensions v3_req

2)用CA签名
openssl ca -days 18250 -in server_req.pem -out server.pem -config openssl.cfg -extensions v3_req

 

server_key.pem就是private rsa key,自己生成吧,这里省略了。

这样https://127.0.0.1和https://localhost都变绿了,赞~

How to use ECDHE when ssl connection

当我用Chrome访问自己的C++ Server,我收到了一个警告:”Not Secure”:

Obsolete Connection Settings
The connection to this site uses a strong protocol (TLS 1.2), an obsolete key exchange (RSA), and an obsolete cipher (AES_128_CBC with HMAC-SHA1).

这里有2个问题:
1)key exchange用了RSA
2)cipher不够强

key exchange的话,需要使用ECDHE (or alias name EECDH)、GCM
代码参考: https://github.com/petere/postgresql-commitfest/commit/3164721462d547fa2d15e2a2f07eb086a3590fd5

在SSL_CTX_set_cipher_list之前需要初始化ECDH:

使用时

 

其中,ECDHE-RSA-AES128-GCM-SHA256解决了第二个问题。更改后,用Chrome就通过了

The connection to this site is encrypted and authenticated using a strong protocol (TLS 1.2), a strong key exchange (ECDHE_RSA with P-256), and a strong cipher (AES_128_GCM).

 

测试小工具openssl.exe使用:
openssl s_client -host 127.0.0.1 -port 443 -cipher AES128

其中cipher可以换成其他,比如
ECDHE:AES128-GCM-SHA256

乐视1 pro(X800) ROOT

网上找了找,很难找到能简单ROOT的。试过所有的一键ROOT软件,都不行。最后试了找到了这个工具:
https://bbs.le.com/thread-799883-1.html

可以刷入第三方Recovery TWRP,貌似还可以刷回来,不过我不需要了,刷成TWRP蛮好,也没试过能不能刷回来。
这个贴的精华是:
http://pan.baidu.com/s/1o6y1GRS 密码: zdwc

赶快下哦,何时失效我就不知道了

然后到TWRP下刷入UPDATE-SuperSU-v2.79.zip刷机包,就能ROOT了

然后下载百度手机卫士(极客版)–安全防护(高级版本换了个地方,稍微找找也能找到)–超强模式,冻结、卸载不需要的软件

该死的Live、应用商店、百度输入法,都去死吧,哈哈……

参考冻结应用:
https://bbs.le.com/thread-895345-1.html
https://bbs.le.com/thread-871707-1.html?typeid=679

最后,卸载百度安全卫士

把SuperSU的ROOT权限去掉,万事大吉

 

How to Pass Command Line Arguments to MSI Installer Custom Actions

, 14 Dec 2006

https://www.codeproject.com/articles/16767/how-to-pass-command-line-arguments-to-msi-installe

When writing unattended installs, it’s very handy to be able to send command line parameters to your custom actions that run during your application’s setup.

Article Image

Introduction

This article will illustrate how to pass command line parameters to Install Custom Actions so that you can enable silent setups that can take advantage of command line supplied parameters without having to recompile the setups. Some uses of this ability might include:

  • An unattended install that is being deployed into multiple environments that would need to access web services at environment specific URLs.
  • An unattended install that would record a product key into the registry.
  • An install that is called from a batch file or a package that needs to supply data that the user would normally enter.

After spending some time Googling in the internet, I was finally able to guess my way into a method of passing this data that would work in my target setup situations:

  • Running the setup.exe file, and passing command line parameters.
  • Running the MSI file, and passing command line parameters.
  • Running MSIEXEC, and passing command line parameters.

There were several stumpers that I encountered while working on this solution, which instantly got my documentation juices flowing, so now it’s article time!

The Solution

There are loads of articles out on the internet that show you how to create custom actions that your setup package can run to show custom dialogs, and perform other types of actions during an installation. I’m going to lightly cover adding the custom action, but I’m going to focus on passing the command line parameters to the custom action, and managing the data through to the uninstallation of the application.

The trick to the solution is that the command line parameters are added to a special collection inside the guts of the setup framework. This collection also houses the well known parameters such as TARGETDIR, and others. You can get a list of the contents of this collection by running any MSI file, and specifying the /l* <logfile> parameter.

Fig. 1: Some of the properties that you have access to from a custom action.

To generate the data in the above screen, I used this command line:

While I was pretty excited to see that the command line parameters were parsed and stored into this internal collection, I had no idea how to get at the data after that point. The problem was that the Installer Custom Actions didn’t seem to have any visibility to the command line arguments when the installation was run from MSIEXEC. It turns out, that you have to pass the values from the Property internal collection (Fig. 1) through more arguments that you specify in the custom actions screen in the setup project! Some pictures here are worth about a million words. Let’s go ahead and add the primary project output for your application to the Custom Actions, and setup the CustomActionData property to map the command line arguments to your Custom Action’s InstallContext.

Fig. 2: Open the Custom Actions view.

Fig. 3: Add the primary project output to the Install Custom Action.

Fig. 4: Attach the values for each command line argument to new arguments that will be attached to the installer’s InstallContext property when your custom action is run.

OK, I want to spend a little time with Fig. 4, as that’s where a lot of the magic is happening. First, notice the quotes around the values. These are necessary to enable values with spaces to be passed into the Install Context from the command line. Next, notice that the values are surrounded by square brackets, and are upper case. The square brackets indicate that the value is to be filled in from the Properties collection. The value names must be uppercase, or they will not be found in the Properties collection from the installer’s internal property dictionary. If you refer back to the log file captured in Fig. 1, you’ll see that when the command line was parsed, the value names were all converted to uppercase. As you might have guessed, the CustomActionData property is case sensitive when it lines up the value names to the actual value in the installer’s internal property directory.

So far so good, we’ve got the data from the command line to the installer’s InstallContext property. Now, let’s go to some code so that I can show you how to read it from the context into some strong type variables, and then persist it into the state dictionary so that the command line parameters can also be used during an uninstall.

First, let’s take a look at the InstallerCustomActions class. This class is derived from the System.Configuration.Install.Installer class, and is marked with the RunInstaller attribute. When this combination occurs, and the project output is added to the Custom Actions screen (Fig. 4 again), then the various methods in System.Configuration.Install.Installer can be overloaded and will give you the ability to slide in your own code at key locations in the install process.

The goal of this class is to:

  1. Show a dialog window during installation that shows two sample command line parameters (MyCustomParameter and MyOtherCustomParameter).
  2. Persist the values of the sample parameters to the state dictionary.
  3. Show a dialog window during uninstallation, that shows the persisted values of the sample parameters.

Next, let’s take a quick look at the CustomParameters class. This class works as a loader for the custom parameter values from either the installation context or from the installation state. The implementation is pretty straightforward, have a look at the comments for more information.

Conclusion

Well, I hope you find this short article helpful. I found it interesting that it took so many hops to get this data from the command line to some actual code that I could control, but the flexibility was worth the effort. If you intend to install and uninstall the sample application several times, you’ll find the following command lines useful.

Install the application without user intervention and full logging:

Uninstall the application without user intervention:

History

  • 12/14/2006 – Initial release to CodeProject.

 

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here